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.