on 2/20/02 10:03 AM, "Fernandez Martinez, Alejandro"
<[EMAIL PROTECTED]> wrote:

> Why not start it yourself and anyone can suggest changes.

I love it when people 'get it'. :-)

> On the other hand, why not start it myself. Something like this:

You kick ass. Note that the majority of your bullet points are already in
some form of documentation on the website that no one bothers to read.

> 1.- Introduction
> Who we are, why are we doing this.

http://jakarta.apache.org/site/whoweare.html

> 2.- Project proposal
> Proposal stage, committers needed, community.

http://jakarta.apache.org/site/getinvolved.html
http://jakarta.apache.org/site/newproject.html

> 3.- Code organization and repositories
> Naming of packages, repositories, what to find in them.
> Who touches what.

http://jakarta.apache.org/site/guidelines.html

> 4.- Code quality
> Add copyright notice, add authors.
> Format your code but not others'.

http://jakarta.apache.org/site/dirlayout.html
http://jakarta.apache.org/site/agreement.html

> 4.- Build system
> Use Ant, use Ant, use Ant.
> Use Gump.
> Use Scarab.

Not done yet.

> 5.- Dependencies
> What jar's to use and what to avoid.

http://jakarta.apache.org/site/jars.html

> 6.- Documentation
> Where to look for it.
> What to expect, what not to expect.

Not done yet.

> 7.- Support
> Whom you should ask, what you should figure out yourself.

http://jakarta.apache.org/site/mail.html

> 8.- Licensing and guarantee
> Why you should use Apache license, and what's wrong with other licenses.
> What you can do with Apache products. Giving credit.
> All that implied warranty things.

http://www.apache.org/foundation/licence-FAQ.html

-jon


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to