On Mon, 3 Feb 2025 at 14:01, Xuanwo <xua...@apache.org> wrote: > > > I think there is probably a requirement to store the reports in ASF svn > > This makes sense to me as well. I believe we can store the generated reports > in SVN.
I doubt that SVN is specifically required. I wonder if they even need to be under version control, given that the reports form part of the board minutes (which are kept in SVN). But if they are required to be kept under a VCS, then that would presumably need to be hosted on ASF hardware. > One question that comes to mind is: where are our old reports? There seems to > be a big gap between 2022 and 2025. > > On Mon, Feb 3, 2025, at 21:29, PJ Fanning wrote: > > I think there is probably a requirement to store the reports in ASF > > svn but the idea of automating some of the generation tasks is > > probably a good item to discuss. > > > > On Mon, 3 Feb 2025 at 14:16, Xuanwo <xua...@apache.org> wrote: > >> > >> Hey, everyone > >> > >> I'm starting this thread to discuss whether it is a good idea to migrate > >> the incubator report workflow to a GitHub-based system. Our current > >> workflow is Confluence-based and involves many manual tasks. I also find > >> Confluence difficult to use, and several other IPMC members seem to share > >> the same feeling. > >> > >> PJ works hard to bring our incubator reports back to life, and I want to > >> offer support in other ways: creating an automated GitHub-based workflow > >> for collecting and formatting reports. > >> > >> My proposed workflow: > >> > >> - Keep genrated reports at > >> https://svn.apache.org/repos/asf/incubator/public/trunk/reports/ > >> > >> (I’m not sure why so many reports are missing; we only have a handful of > >> entries here.) > >> > >> - Establish a repo with layout in this way: > >> > >> reports/{year}/{month}/{project}.md > >> > >> Take today and fury as an example: > >> > >> reports/2025/02/fury.md > >> > >> - Our GitHub Action scripts will automatically generate all templates for > >> projects that require monthly reporting. > >> - All requirements like "Please note that some lines have two spaces at > >> the end. Do not remove these spaces." will be relaxed. Our GitHub Action > >> scripts will collect, format, verify and wanring for projects that not > >> reported. > >> - Our Github Action will generate the finally report by combine those > >> reports together. > >> > >> > >> To submit a report, the project's PPMC members simply need to create a PR > >> at the designated location. > >> To review a report, the project's mentors only need to provide their > >> feedback by adding inline comments to the PR. > >> > >> > >> What do you think? The detailed workflow can be discussed later once this > >> repository has been set up. My main proposal is to move away from > >> confluence and rely on GitHub Actions to reduce the workload we need to > >> manage, make the process easier for all of project ppmc members, mentors > >> and also the IPMC chair. > >> > >> Xuanwo > >> > >> https://xuanwo.io/ > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > >> For additional commands, e-mail: general-h...@incubator.apache.org > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > -- > Xuanwo > > https://xuanwo.io/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
