nicolaken 2003/10/23 02:58:15
Modified: site site.xml
Added: site howwework.cwiki
Log:
Added a page about how we make decisions.
Revision Changes Path
1.10 +3 -2 incubator/site/site.xml
Index: site.xml
===================================================================
RCS file: /home/cvs/incubator/site/site.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- site.xml 23 Oct 2003 09:09:26 -0000 1.9
+++ site.xml 23 Oct 2003 09:58:15 -0000 1.10
@@ -3,9 +3,10 @@
<about label="About">
<index label="Index" href="index.html"/>
- <whatwedo label="Creation" href="resolution.html"/>
+ <whatwedo label="What we do" href="resolution.html"/>
+ <howwework label="How we work" href="howwework.html"/>
<whoweare label="Who we are" href="whoweare.html"/>
- <howtoparticipate label="How to participate"
href="howtoparticipate.html"/>
+ <howtoparticipate label="How to help" href="howtoparticipate.html"/>
<faq label="FAQ" href="faq.html"/>
</about>
1.1 incubator/site/howwework.cwiki
Index: howwework.cwiki
===================================================================
!!!How we work
Here are some notes about how we have decided to make decisions and
changes to the way we work.
!!How we make decision on our incubation policies
Apache projects usually make releases, and have deliverables. The code
they put in is managed through lazy consensus and voting only when it's
deemed to be required or requested.
Incubator releases are basically Incubated Projects' release to the
Sponsor PMC. So how incubation is done is our "code".
Hence there is no need to "ratify" such rules if there seems to be
consensus, as it's much easier to manage.
Because of this, we do not have the "draft" status on our policy docs
and simply use them as our guide, that will change in need without
having to go through tedious votes when there is good consensus.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
