Ate,
Lastly, documentation is a high concern in my organization, as well as others. Some are scared to use a product that is lightly documented, so adding more/better/accurate docs would be a tremendous benefit for Jetspeed. As the code becomes more stable, I have to agree that this would be a well rewarded effort.
Don't forget most good developers are pathologically bad documenters :)
Also, in my experience, the most useful documentation usually comes from new user/developer experiences discovering the product and describing their experience and pitfalls encountered.
If you really want a top notch documentation, please try and use the
wiki to report on your install/config experiences, issues encountered and things you want to do with J2 but can't find how to do.
This kind of feedback helps us put the emphasis where it's needed, explaining better the difficult points and not losing too much energy on documenting obscure things of limited value or miss some major functional areas.
Basically, every user can help make the documentation as helpful as possible by giving feedback on their experience.
Just create a new page in the Jetspeed2 wiki :
http://wiki.apache.org/portals/Jetspeed2
and let us know about it !
-- Raphaël Luta - [EMAIL PROTECTED] Apache Portals - Enterprise Portal in Java http://portals.apache.org/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
