Hi,

You are not wrong. I have seen the same split. I would not close it by
pushing a project out early.

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.

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.

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.

-=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

Reply via email to