On 06.02.2008, at 22:15, Roland Weber wrote:
Hi Erik,
charter == mission statement
bylaws == project guidelines
Both can be pretty simple and don't need to be ultra-extensive, just
spelling out the basics (in case of the bylaws: pmc membership,
voting
guidelines, commit and release guidelines, ...).
Oleg wanted to write a document on our development process,
and I had also considered to write something about RTC/CTR
into the bylaws. So you think we should put that there?
Yes, we can certainly put that into the bylaws though an additional
doc outlining various other details of the dev process also can't
hurt (e.g. covering patch format, style guide, ...) :)
As said, adapting the Jakarta Guidelines seems like the most sensible
and easiest to do - it's all in there already (AFAIK they are based
on the ones from HTTP, just a tad bit more elaborate).
Here's another simple but good example:
http://httpd.apache.org/dev/guidelines.html
Thanks. I had a brief look earlier, will give it some
more attention later this week. Time sure flies :-(
Just an example of a very simple set of guidelines - they are
sufficient but we can certainly improve them (like Jakarta and others
did).
Cheers,
Erik
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
