Hi Dave,

Thanks for the feedback and clarification, and thanks to Jarek for summarising 
the intent well.

To answer your direct question: the draft is posted to the incubator general 
list as a starting point for PPMC discussion, not placed directly into CWiki. 
The [PODLING TO COMPLETE] sections are intentional; the draft is structurally 
incomplete by design so the PPMC has to engage actively rather than just filing 
it as-is.

It's worth emphasising that this is still an experiment. A good way to test it 
in practice would be for a few podlings to opt in and try it out, so we can see 
how it works in practice before drawing wider conclusions.

On your specific suggestions:

(1) Mentor sign-off position: the traditional position has been at the bottom 
of the report, and I'd prefer to keep that convention for now to avoid 
confusion with existing tooling and expectations.

(2) PPMC member sign-off section: I think this is a reasonable addition and 
worth including. It makes explicit who in the PPMC has reviewed the report, 
which is useful.

(3) Community written summary: I agree this is the most important suggestion, 
and I'd like to include it. A free-form human-written section at the top is 
exactly the kind of thing that breaks the mechanical nature of the report and 
demonstrates genuine reflection. I'll add this.

(4) Excluding unsigned reports: I'd expect we continue with current practice 
here.

On the exit strategy section for podlings over 18 months: I understand the 
intent, but I don't think a blanket time-based trigger is the right approach. 
The Incubator already has three well-documented transition paths: graduation, 
withdrawal, and retirement, each appropriate for different situations. Some 
podlings have complex licensing issues, some have larger lessons to work 
through, and some (as your Pony Mail example illustrates well) are genuinely 
unique cases that don't fit a standard timeline at all.

The CWiki Lifecycle and Transition  [1] and the Incubator Case Studies [2] both 
document this. The Incubator is not a one-size-fits-all process, and I think 
the report should reflect that nuance rather than impose a time-based trigger.

Kind Regards,
Justin

1. 
https://cwiki.apache.org/confluence/display/INCUBATOR/Lifecycle+and+Transition
2. https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Case+Studies
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to