Directions
Hi All,
Someone asked me the other day what the ApacheWay was and so I pointed them to a long list of documents and saw panic. So I explained it to them. Furthermore I tried to give them a physical layout and explain how various things fit in, we discovered some questions I couldn't answer (so I figured I'd go to the source).....
I thought it would be chill if we could start documenting the ApacheWay or at least the parts we agree on. I suggest as a convention the agreeable things go on the first page and anything that someone completely disagrees with should go on a page linked from the first.
Questions and topics for discussion should go on the bottom of the page.....
The ApacheWay is.....
2. CommunityBasedDecisionMaking
4. Openness
In many OpenSource communities the CodeIsKing. In the ApacheWay the community is the most important thing. Of course it's only important if code is produced, but the fact is that most Apache projects could be reproduced in a reasonable number of months by a dedicated full time team. The community giving continued development, evolution, invention is what makes us strong; not just the code we already have.
Questions:
While writing the above, two thoughts came to mind. I'm hoping if they can be cleared up that I can add additional values to the above based on what I learn from whomever answers them. Thanks for your help.
HowDoesIncubatorFitIn - How does the new IncubatorProject which serves as a "gatekeeper" where a predetermined set of individuals make the decisions determine what projects add to Apache's greatness fit into the above values? (in progress)
HowDoesCommonsFitIn - How does the new CommonsProject which was created before any actual code or community was formed to go into it fit in with these values and the rest of the Community at large?
WhatDoesTheBoardDecide - What decisions are best left the the board?
WhatDoTheMembersDo - What purpose do the members not on the board really serve?