>-----Original Message-----
>From: Marvin Humphrey [mailto:mar...@rectangular.com]
>Sent: Monday, August 06, 2012 12:25 PM
>To: general@incubator.apache.org
>Cc: Grant Ingersoll; Isabel Drost
>Subject: Re: [PROPOSAL] Drill for the Apache Incubator
>
>On Thu, Aug 2, 2012 at 3:12 PM, Ted Dunning <ted.dunn...@gmail.com>
>wrote:
>
>> Initial Source
>> ==============
>> There is no initial source code. All source code will be developed within
>> the Apache Incubator.
>
>Coming in without any source code is going to pose a challenge to this
>podling.
>
>    http://www.apache.org/foundation/how-it-works.html#incubator
>
>    The incubator filters projects on the basis of the likeliness of
>them becoming
>    successful meritocratic communities. The basic requirements for incubation
>    are:
>
>        * a working codebase -- over the years and after several failures, the
>          foundation came to understand that without an initial working
>          codebase, it is generally hard to bootstrap a community. This is
>          because merit is not well recognized by developers without a working
>          codebase. Also, the friction that is developed during the initial
>          design stage is likely to fragment the community.

It seems like there could be flexibility in this requirement, based on a few 
factors.  In this case, a design discussion has been ongoing; but I would also 
think that any community coming in with enough people who know the Apache way 
may also not need as much of a solid starting point code wise.

>
>That last line in particular seems like something to watch out for.
>
>Marvin Humphrey
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>For additional commands, e-mail: general-h...@incubator.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Reply via email to