It's great to see some new ideas to make reporting simpler for podlings!
Xuanwo wrote on 2/3/25 8:14 AM:
...snip...
My proposed workflow:
- Keep genrated reports at
https://svn.apache.org/repos/asf/incubator/public/trunk/reports/
To provide perspective on a few of the questions and replies:
- The process that the Incubator - or it's podlings - uses to create and
edit reports is up to the Incubator. Other than being something that
each PPMC as a whole can review for their podling (including mentors),
there really aren't many other requirements.
In particular, the *process* for creating reports could be on github if
that's what your users want and you can make it work. As long as it's
somewhere under github.com/apache/*, it's fine; we mirror that.
- Whatever process you do design should clearly separate each podling's
PPMC when they write/edit the report, from when someone consolidates
them all into the Incubator report. It would be nice if PPMCs who like
this github workflow could simply keep doing most of it when they
graduate later on.
- The final Incubator must be *submitted* to the board agenda, and there
are a few specific minor formatting requirements there (because the
board agenda has LOTS of reports), but that should be easy to test.
So focus on getting PPMC reports done, and then consolidated into one
specific place for the whole Incubator report. The last step of
actually submitting to the board will likely be elsewhere (either
manually putting into SVN or reporter tooling).
I'd also suggest (but I'm not active here, so!) putting this into a new
repository for reports, so you don't have to worry about settings and
can easily configure notifications separately.
--
- Shane
Member
The Apache Software Foundation
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
