I like the idea of a checkpoint, and six months seems the right time frame.
How about making the checkpoint a Zoom call, rather than a form? It’s a better use of people’s time — less preparation time, more chance of having a productive and constructive questions and answers in both directions. (I’m expecting this idea to get pushback, because the ASF traditionally does everything asynchronously. But I think we take it too far. There are several things are better done synchronously and face-to-face over video, and this is one of them.) Julian > On Sep 19, 2025, at 3:59 PM, Justin Mclean <[email protected]> wrote: > > Hi, > > I’d like to propose an optional 6-month checkpoint review for podlings, timed > after they have submitted their first four board reports (three monthly and > one quarterly). > A pre-filled template would be generated with key metrics (GitHub > contributors/issues/PRs, mailing list activity, Whimsy data on start date and > committers/PPMC). Mentors would then review the suggested 0–2 scores, adjust > as needed, and add brief commentary. > > By this stage, a healthy podling should generally have added its first new > committer and be working on, or have already made, its first release. The > checkpoint would help identify community health, mentor engagement, and early > warning signs that may impact graduation readiness. > > What do others think about this? > > I've put together a proof of concept, which you can view here. [1] Most of > the AI-generated code can be found here [2]. An example of a generated review > is provided here [3]. > > Thanks, > Justin > > 1. https://cwiki.apache.org/confluence/x/qQsGFw > 2. https://github.com/apache/incubator/tree/master/tools/6MonthReview > 3. https://cwiki.apache.org/confluence/x/rQsGFw > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
