> On Nov 5, 2026, at 3:54 PM, Christofer Dutz via general
> <[email protected]> wrote:
>
> Hi all,
>
> well my gut-feeling hints at that projects that have matured outside of the
> ASF and were perhaps in a maintenance mode, might be less eager to work on
> procedural things as young and energetic projects.
And, indeed, if they’re already mature, maybe those procedural things are
things that we could automate, or be more helpful about getting them through,
so that they don’t lose momentum?
>
> Possibly providing something like "homework" (milestones) for the projects
> could speed things up or show where there is no willingness to do so. At
> least it would make things we expect a bit more prominent than an ambiguous:
> We expect them to learn all the stuff ... without sensibly segmenting that
> (or even without documenting everything in one spot)
This is exactly what I’m asking. And I *thought* this was the mentors’ job - to
give them those milestones. But many mentors I spoke with seem to believe that
they are just there as a resource, to respond when asked, and not to
proactively prod the podling to action.
Is there a middle ground where the Incubator has mechanisms (scripts, AI
agents, GitHub actions, interns, who cares the actual mechanism) that send out
those prods?
—Rich
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]