On Tue, 2002-03-05 at 18:38, Ted Husted wrote: > acoliver wrote: > > I consider the statement "you just need to know where to look for" to be a > > symptom of improper information organization. Such things should be *easy* > > to find. Initiation into our community(ies?) has a higher barrier than I > > prefer, you can never have too much or too well organized documentation. > > (this is not to say that those who don't even read the web page before > > emailling committers "gee is POI written in Java" won't still be > > challenged...and thats a good thing, but that those who are just simple > > minded programmers like me looking for a place to code or who want to know > > "do I have to donate my hello-world app based on" to look. > > Any comments on this? > > http://jakarta.apache.org/site/methodology.html >
I like it... . now that it compiles ;-) Think it should be Apache Jakarta/XML Manual not Apache Manual unless you get the httpd people involved and move it up a site... Add: 1. How to create a patch with -u format 2. How to apply a patch (symmetry) Moderators Guide: where was this last night! whoo! (its not there yet but whoo!) Licensing Add about mixing and matching GPL etc.. I know I know but its a old question. Documentation: Prefer a more documentation activist stance then what these bullets lead me to believe you intend to put... We really should work to improve documentation all around (yes, I'm doing my part) -- Furthermore, documentation should be seen on equal status as code.. As evidence it is not (in many places) see this page: http://jakarta.apache.org/avalon/authors/index.html -- not that the manual should be the springboard for this idea... but it shouldn't reflect the I like having both versions but lean toward the second because the headings make it easier not to be overwhelmed. And thanks for linking to that License FAQ page!!!! Thats exactly what I thought was needed. I think one thing I'd like to see more prominently is something that says "no, you really truly can just do a cvs co, change things, patch them and send those to the list...really truly thats all you have to do! No really!" or something to that effect.. Its a hard concept to grasp (was for me, is for others) at first... I'd be good to have a standard TOC for each project of basic info. It would kinda encourage those projects to fill in any blanks. Those are my initial thoughts -- GREAT WORK.. I'll fill in pieces eventually ... I'm swamped at the moment.... (not that anyone isn't but I'm a little more then usual at the moment..) -Andy > > Note that there are two proposed outlines on the page. > > + Following the Jakarta Way > > and > > + The Volunteer Guides > > In the latter, I'm trying to organize the material around the various > roles people play around here, from a user to a committer to a sys > admin, and have them build on each other. > > -- Ted Husted, Husted dot Com, Fairport NY US > -- Developing Java Web Applications with Struts > -- Tel: +1 585 737-3463 > -- Web: http://husted.com/struts > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- http://www.superlinksoftware.com http://jakarta.apache.org - port of Excel/Word/OLE 2 Compound Document format to java http://developer.java.sun.com/developer/bugParade/bugs/4487555.html - fix java generics! The avalanche has already started. It is too late for the pebbles to vote. -Ambassador Kosh -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
