On Thu, Oct 20, 2022 at 9:17 PM Justin Mclean wrote:
>
> Hi,
>
> > For those programs that have been incubating for more than two years,
> > would it be better for the mentor to sign off with how close the
> > current state of the community is to graduation? The status quo is
> > that we rarely
Hi,
> For those programs that have been incubating for more than two years,
> would it be better for the mentor to sign off with how close the
> current state of the community is to graduation? The status quo is
> that we rarely see in the reports what the specific challenges are for
> podlings
Sent from my iPhone
> On Oct 19, 2022, at 5:38 PM, Justin Mclean wrote:
>
> Hi,
>
>> Is there a maximum time for incubation? Target? I have not read incubator
>> docs closely.
>
> Not really but we expect a projects to exit in 1-3 years, and at 4-5 years we
> tend to ask them to retire,
On Wed, Oct 19, 2022 at 7:37 PM Justin Mclean wrote:
>
> Hi,
>
> > Is there a maximum time for incubation? Target? I have not read incubator
> > docs closely.
>
> Not really but we expect a projects to exit in 1-3 years, and at 4-5 years we
> tend to ask them to retire, but it does vary.
>
> >
Hi,
> Is there a maximum time for incubation? Target? I have not read incubator
> docs closely.
Not really but we expect a projects to exit in 1-3 years, and at 4-5 years we
tend to ask them to retire, but it does vary.
> I could also see a dashboard with milestones [ various requirements
Is there a maximum time for incubation? Target? I have not read incubator
docs closely.
I could also see a dashboard with milestones [ various requirements for
graduation ] at various timelines, and whether projects are ahead/behind
'schedule'.
On Wed, Oct 19, 2022 at 2:34 PM Justin
Hi,
> * Graduation Status
This is included in the current report.
> * Community issues for both users and maintainers
> - what are the barriers of entry for each - complexity in maintenance,
> language use, continued relevance, etc
This should also be in the reports but is perhaps not always
I've been wondering about this as well.
It seems that we can have a rather mature project still incubating after a
number of years.
We can have active consumers relying on it but the momentum of the original
project and maintainers waned.
Multiple external forks have been made with the inability
> One might even do this review (gasp!) over Zoom, so that people can
ask questions and have them answered in real time
+ 1 Julian. I appreciate this.
I'm on one of these projects (Heron) that has been in the incubator for far
too long. I think where Heron fell short in its journey was the
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
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.
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
12 matches
Mail list logo
