Hi,

2014-06-19 8:14 GMT+02:00 Roman Shaposhnik <r...@apache.org>:

> Hi!
>
> based on a recent thread inspired by observing
> some of the podlings, I'd like to kick start a discussion
> around making an amendment to our Incubator
> policy:
>     http://incubator.apache.org/incubation/Incubation_Policy.html
>
> It feels like we're missing one important part to
> the whole process -- a fair criteria for addressing
> podlings that are unlikely to make it to the TLP.
>

I think it is a good idea to add such criteria.


>
> Ultimately, the incubator is the place where we teach
> the projects to do two things:
>    * effectively manage releases
>    * effectively manage the community
>
> To this end, I'd like to prose a very simplistic criteria
> for a potential retirement from the incubator: unless both
> of of the following applies project get put to a retirement
> IPMC vote:
>    * there has been a release in the past 12 months
>    * there has been a bona-fine change to a community
>       structure in the past 12 months
>
> Do share your thoughts. I intend to put an amendment for
> a vote next week.
>

IMHO the list created by Christian makes more sense. Looking at the podling
I'm coming from (Celix), we didn't make a release in the first year. Most
important reason being that not much source was written when we entered. In
fact, this is something I see coming up often regarding discussions about
graduation and time in the incubator. I somehow have the feeling that most
people expect new podlings to enter the incubator with a (fairly) complete
source code, making it possible to get through the incubator in one year.
And looking at the most podlings, this is probably true, but can't be said
for all.

Don't get me wrong, I understand the incubator isn't that much about source
code and completeness, but to be able to grow a community and attract
users, a working codebase is needed. This is something we struggled with in
the first year. Nonetheless we had discussions on the list, we had commits
and we had talks at conferences. So making a release and a community change
as the retirement criteria would IMO be too harsh for Celix when we started.

In the end I think it al depends on the podling, committers and the
mentors. Some form of measurement and criteria is good to have, but it has
to be broad enough, and leave enough space for a podling to determine their
own fate.



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


-- 
Met vriendelijke groet,

Alexander Broekhuis

Reply via email to