uhm, a shameless pitch for wikis.sun.com (I'm the eng lead there):
wikis.sun.com is a pretty good choice for the grizzly wiki and in fact
the glassfish folks are currently in process of moving part or all of
their docs to us. And the list of other projects that use our wiki is
quite long.
One feature that I really like about our wiki is the ability to draw
diagrams and embed them into wiki pages. In fact all the diagrams[1]
[2] I created for grizzly-sendfile where created with the tools
wikis.sun.com provides and I exported the images so that I could
publish them on kenai.com (with grizzly-sendfile I'm testing kenai's
wiki).
Our wiki is a customized Confluence[3] site which receives a lot of
care and is being upgraded to newer versions with new features and bug
fixes quite often. And despite some occasional outages (due to an
enormous growth of the site), we have a very good uptime.
If you have any questions about the site, just let us know.
cheers,
Igor
[1]
http://kenai.com/projects/grizzly-sendfile/pages/Home#How_does_grizzly-sendfile_work
?
[2]
http://kenai.com/projects/grizzly-sendfile/pages/Algorithms#Blocking_vs_NonBlocking
[3]
http://www.atlassian.com/software/confluence/
On May 6, 2009, at 2:56 AM, Oleksiy Stashok wrote:
> I agree, the idea with wiki was also proposed by Hubert last week.
> I think we need to create it.
>
> we may choose.
> http://wikis.sun.com/dashboard.action
> http://wiki.glassfish.java.net
>
> I would prefer wiki.glassfish, but not aware if there are any
> restrictions... Jeanfracois, do you know any?
>
> Thanks.
>
> WBR,
> Alexey.
>
>
> On May 6, 2009, at 4:25 , testn wrote:
>
>>
>> Thanks! Why don't you first create a wiki so that people can start
>> contributing. Maybe first outline what need to be documented and
>> have people
>> contributing in each area.
>>
>>
>>
>> Jeanfrancois Arcand-2 wrote:
>>>
>>> Salut,
>>>
>>> testn wrote:
>>>> I think what Grizzly really lacks is the documentation.
>>>> Jeanfrancois and
>>>> Alex
>>>> did blog many posts about it. But I think the official
>>>> documentation with
>>>> each release would suit more. Plus it will provide better
>>>> structure for
>>>> newly adopters to jumpstart themselves with Grizzly. Is there
>>>> such a plan
>>>> in
>>>> progress? Last I heard about it was during 1.7 release but I
>>>> didn't see
>>>> much
>>>> changes. I don't want to create a flame but MINA has much better
>>>> documentation and it makes me feel like a better choice.
>>>
>>> Agree 100%, but so far we are just rushing every day to
>>>
>>> (1) Help peoples on this mailing list as fast as we can.
>>> (2) Help new contributors to get up to speed
>>> (3) Design/Integrate Grizzly in products like Sailfin, Glassfish,
>>> where
>>> they play a *major* role. We unfortunately not assigned to only
>>> works on
>>> Grizzly (hopefully our new boss will allow us ;-))
>>>
>>> Again, I agree and we constantly try to improve what we have.
>>> Contributions always welcome!
>>>
>>>
>>> A+
>>>
>>> --Jeanfrancosi
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
>>> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>>>
>>>
>>>
>>
>> --
>> View this message in context: http://www.nabble.com/Grizzly-Documentation-tp23398788p23398992.html
>> Sent from the Grizzly - Users mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
>> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>