incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas Dudziak <tom...@gmail.com>
Subject Re: Is there a "no graduate" option?
Date Thu, 22 Dec 2005 23:18:05 GMT
> > It takes as long as it takes.
> >
> > The only requirement I have is that there is a continued effort towards
> > attracting community.  If a project goes completely dormant (i.e. no
> > traffic whatsoever), then yes it can fail and should be terminated.
> >
> > However, placing arbitrary limits on the Incubation period is the opposite
> > of what we want to achieve.  It would "force" a community to meet
> > artificial deadlines when that may be the worst thing we could do.
>
> +1
>
> but it would be a very good idea to have some sort of process for
> domancy: no development for even a month should ring alarm bells and
> call for either active intervention (if there is still a community) or
> a move to dormacy.

I wonder whether there isn't another problem here: that of the
(missing) oversight of the PMC that originally voted the project into
incubation. For instance, while I'm on the DB PMC and voted e.g. Derby
into incubation (just to pick an example), I did not really follow its
way through incubation for all the usual reasons (too much work, own
projects, bla, bla, bla). And I don't think that is much different for
other PMCs.

Now the problem that I see is that I was not 'forced' to take more
care about the projects that I vote into incubation. Correct me if I'm
wrong on this assumption, but in my naive view the incubator PMC has
the role of ensuring that the project learns/follows the ASF ways,
building a community etc. Whereas the DB PMC in my example would deal
with things regarding the 'content' of the project.

If now for instance, the DB PMC would somehow automatically get the
the incubation mails for the projects that it voted into incubation
and its reports, oversight from this PMC might enhance. After all it
involves more work to actively delete mails than to not get them in
the first place.
And thus potential problems with incubated problems would surface
sooner, and the workload of the Incubator PMC might decrease - one
individual PMC has only a few projects in incubation whereas the
Incubator PMC has to take care of all incubated projects.

Tom

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


Mime
View raw message