One idea is to schedule a review after the project has been in the incubator longer than the median time (say after 2 years). Deep-dive into what is going right and wrong, identify things that can be fixed, and set targets. And schedule another review a year later. Or schedule a vote to retire.
One might even do this review (gasp!) over Zoom, so that people can ask questions and have them answered in real time. It sounds shockingly invasive, considering we at Apache tend to do everything asynchronously. But it's better than the alternative, which is a slow death as mentors and initial committers drift away. Julian On Tue, Oct 18, 2022 at 12:27 PM Justin Mclean <jus...@classsoftware.com> wrote: > > Hi, > > Looking at the longest incubating projects, one has graduated and needs some > cleanup, one had a reboot, one is discussing a reboot, and several have roll > calls in progress or are discussing retirement. However there are two or > three other projects that either should retire or graduate and have been > incubating for far too long. > > But taking a step back what can we do to make projects life though the > incubator shorter? Would having more resources help? (If so what resources?) > What else might we be able to do - offer training for instance? > > Kind Regards, > Justin > > > --------------------------------------------------------------------- > 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
