On 2022-10-18 14:34, Julian Hyde wrote:
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.
Brainstorming etc in a synchronous way is totally fine, as long as it is
open and scheduled in an inclusive manner with an exhaustive summary to
the mailing list afterwards. The primary rule about asynchronicity
concerns decisions and the data that flow to and from those decisions.
The rule "if it didn't happen on the mailing list..." is essentially two
parts:
1. Everyone must be allowed to participate in shaping the project
2. All decisions and the inputs that shaped that MUST be archived on the
mailing list for provenance/governance to work as intended.
I am satisfied that having a zoom meeting or whatever (slack huddle??)
would be just fine here. Our board of directors also conduct their
meetings via video :)
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
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
