incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Incubator Wiki] Update of "DocumentationPlan" by RobertBurrellDonkin
Date Thu, 03 Aug 2006 22:12:27 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.

The following page has been changed by RobertBurrellDonkin:

The comment on the change is:
Long opinionated bit that will need editing

    * Starting Point Matrix - Open or Close Community; Open, Closed Or Even No Source but
Must Bring An Active Community! Experience of the incubator and requirement are likely to
differ for different people on the matrix. 
     * Community, no code: the process is the longest and the most difficult. These projects
are rare and probably require the active backing of one or more well known figure with proven
ability in community building.
     * Open Source, Open Development in an existing open community: the process should potentially
be quick. the major effort should be in completing the legal side (the provinance of the code
needs to be completely tracked - this may mean that some areas of the code base may need to
be replaced with fresh implementations; learning how to create releases that comply with apache
policy; replacing or modularizing any dependencies that do not comply with apache policy).
it's also useful for both sides to get to know each other better during this period.
+    * Pre-proposal - the proposal is a formal document. In some cases, it can be useful to
discuss whether there is any interest before the proposal stage. for example

+    * Apache is about community. Quite a lot of interest is required to create a viable community
without code. Unless you have a trackrecord in community building then people may well be
sceptical. You may well . Please don't take this as being mean spirited - it's actually good
advice. It's often easier to start a successful new project as a dictatorship. You don't have
to worry about recruiting new committers, about satisfying the Apache criteria for graduation
or about the voting rules. There are a number of places where open source hosting is available
at no cost. Later, you may find as the project matures and you have build your community you
may decide that you want to propose the project for incubation. The Apache community model
makes many things easier for developers of mature projects with large and active communities:
it's legal support and organisational framework. Or you might decide that you want to create
your own foundation similar to Apache probably with li
 ke minded projects. That's cool too. You don't have to be part of Apache to benefit from
the legal documentation and organisational model. In fact, Apache has good relations with
other open source foundations and this networking helps information flow all parties. Some
other projects have benefited from advice from Apache members during the period when they
set up their foundations. So it might be worth dropping back in.
   * [ Guide To Mailing Lists] needs tidying
up. the index page has a missing link to this page. the website content should be replaced
with a link to the website guide. 
    * more content on mailing list best practices would be good but perhaps should be in the
foundation docs

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message