We don’t need LLM skills. The Incubator has forgotten the tools it already has. Does anyone look directly at the objective guidelines from the early Incubator that are the main measure provided in the daily clutch analysis available at https://incubator.apache.org/clutch/? A quick review of this table should give a list of those podlings that are objectively close to graduation. You can go into the detail and see that all releases and repositories for each podling. For example, if you look at https://incubator.apache.org/clutch/seata.html you have to ask where is Seata’s graduation resolution? To me it looks like it’s at least one year delayed.
This clutch effort was originally created in 2009 and refreshed in 2017. The process could add an occasional email around email reminders monthly on how to use this page for an assessment. Best, Dave > On Nov 8, 2026, at 12:32 AM, Paul King via general > <[email protected]> wrote: > > I'd be keen to see what results Justin's latest Maturity and Graduation > self-assessment AI skills reveal. We possibly need to polish them a little > more but then it would be interesting to see whether we could email some kind > of summary to podlings each month. > > Cheers, Paul. > > On 2026-11-05 19:50 UTC Rich Bowen wrote: >> Hi, friends, >> >> I’m reluctant to speak up, because I know that these kinds of comments have >> been received very adversarially in the past, but in light of the threads on >> members@, I wonder if there’s an appetite to hear comments, and maybe make >> some adjustments as a result. >> >> Over the past 2 weeks, as a result of the threads on member@, I have been >> having informal conversations with people in incubating projects - both >> project members and mentors - about projects that appear to me, a complete >> outsider, ready to graduate, trying to understand why they are not, and what >> can be done to help them get there. I wanted to share some insights. I hope >> they are not unwelcome, or taken as criticism, but, rather, as an attempt to >> suggest an area where a small improvement or nudge might have some >> beneficial results. >> >> In the conversations with project members, when I’ve asked what it would >> take to get you from where you are to graduation, the overwhelming response >> was “We’re not sure”, with a side of “we’re waiting for the mentors to tell >> us what’s next.” >> >> In conversations with mentors, I get the opposite answer - we’re not sure >> why the project isn’t asking to graduate, we’re waiting for them to take >> that step. There have also been a number of answers that don’t seem to line >> up with actual Incubator graduation requirements, as I understand from my >> rather extensive and exhausting reading over the past 2 weeks. Things about >> code quality, number of companies which are part of the PMC, and volume of >> commit activity were answers that were common. >> >> This disconnect is troubling, and I wonder if there’s a way to cross that >> gap. >> >> I know we have a *TON* of data around incubating projects. I know that we, >> collectively, have a lot of opinions about what each project needs to do in >> order to graduate. I’m at a bit of a loss to understand how that isn’t >> communicated to those projects. I see a bunch of dashboards and score cards, >> like, for example https://incubator.apache.org/clutch/index.html (although I >> was told by a few people that “we don’t use that any more”, which was >> confusing, since it says it was updated this morning). I wonder if we >> can/should be more proactive in trumpeting to these projects what they >> should be doing to get over the finish line. >> >> Please forgive me if this is already being done (indeed, I think it is!) but >> these conversations lead me to believe that it’s not being heard. I’m >> looking for ways that we can do proactive, specific, targeted outreach to >> projects to help them know exactly what their path to graduation is, in >> clear ways that are actionable. I’m certainly happy to do (some of) this >> work. I am not currently an Incubator PMC member, but I’m not just trying to >> say “you’re doing it wrong” from the sidelines. Rather, I want to know if >> and how I can help. >> >> —Rich >> --------------------------------------------------------------------- >> 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
