Just an "outsider" Measures is for me tick boxes, do this, then do that, then this and there you go. it's a conveyer belt, it's a Project manager taking you through a gant chart and being surprised when you get to the end and it does not work.
A Mentors project for me is hold the hand of the new project, guide them, some grow at one rate, others at another, part of this is naturally, whats being done atm, whats needed, how do we get from A to B. if these are on a "page" thats there to help the Podling and the menter, for sure, but don't add tools, i.e. LLM's and then say well we've added this, this should fix it. G On Mon, Nov 9, 2026 at 3:49 AM Dave Fisher via general < [email protected]> wrote: > Hi - > > > On Nov 5, 2026, at 2:44 PM, Ed Espino via general < > [email protected]> wrote: > > > > Hi, > > > > You are not wrong. I have seen the same split. I would not close it by > > pushing a project out early. > > What’s early? There’s a VOTE to retire a project because it was not pushed > out at all. > > > > > A few things only get learned if the project has to do them while it is > > still here. Security is one. It may not come up at all. If it does, > someone > > has to answer the reporter and figure out what the report actually is. > That > > mail belongs on the private list. A page that points people at > > [email protected] is not enough. > > Having dealt with a security issue is not a graduation requirement. The > ASF Security team helps both podlings and PMCs handle security reports. > Podlings just need to know that it is their duty just like trademarks. > Having dealt with a trademark issue should not be a graduation requirement. > > > > I would leave the issues out of the podling report. The counts are the > > useful part: how many are open, how long until someone answered, how long > > until one was fixed. The project can see that without the bugs being > > described in a board report. > > > > The same report can carry the other easy things. Blank rows on the status > > page. How long since the last release. New committers, new PPMC members, > > and who from the original PPMC is still around. None of that graduates a > > project. It just makes what is left visible. > > The podling report is about progress in the incubator and should not be > practice towards a board report that may not need to be as you describe in > the last two paragraphs. > > > > > One more thing. The person who writes the report should change from one > > report to the next, the same way the release manager should change. You > > have to look at the whole story to write it. That is how more people find > > out what is left. A tool we run over here does not do that for them. > > A better practice is to review the answers on the dev mailing list. The > report is meant to be the codling’s view. I think doing that and always > thinking about graduation will be the best way to make graduation happen! > > It could be a good discussion to review what the requirements actually are > as a simple list. > > (1) IP transfer as needed. This is really the first thing and should not > wait for the first release attempt. > (2) Establish development at the ASF. > (3) Make at lease one valid ASF Release. > (4) Grow the community. In my experience even a singular new PPMC member > is enough. > > Is there really anything more? Yes, the Maturity Model has more, but big > picture those are the (4). > > The IP Transfer plan(1) should be practically complete by the time the > Champion asks the Incubator to accept the podling. If IP transfer is a > complex event then that can prevent the podling from ever graduating. > > Best, > Dave > > > > > -=e > > -- > > Ed Espino > > > > On Thu, 5 Nov 2026 at 16:38 -0500, Rich Bowen <[email protected]> > wrote: > > > >> 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] > > -- You have the obligation to inform one honestly of the risk, and as a person you are committed to educate yourself to the total risk in any activity! Once informed & totally aware of the risk, every fool has the right to kill or injure themselves as they see fit!
