On Fri, 23 Jan 2026 at 23:59, sebb <[email protected]> wrote: > > On Fri, 23 Jan 2026 at 22:59, Dave Fisher <[email protected]> wrote: > > > > > > > > > On Jan 23, 2026, at 2:02 PM, Dave Fisher <[email protected]> wrote: > > > > > > Hi Hervé, > > > > > >> On Jan 18, 2026, at 6:39 PM, Hervé Boutemy <[email protected]> wrote: > > >> > > >> I'm willing to continue maintenance on projects.a.o and help its > > >> evolution to adapt to ATR-way for PMCs to manage their projects data. > > >> (I have no knowledge on reporter.a.o, cannot help) > > > > > > Thank you! > > > > > >> Once ATR will provide project and releases info, no reason we should not > > >> be able to easily adapt to the new, better, data source. > > >> On "Possibly upgrade projects.apache.org into a simple public asfquart > > >> site", you'll have to explain what a "simple public asfquart site" is: > > >> current website is a simple static website. > > >> > > >> We'll have to define how to work together: > > >> - issue tracker: existing Jira? somewhere else like GitHub Issues? > > > > > > - Currently I have GH issues attached to the ATR repository via a Project > > > VM tracking issue: > > > https://github.com/apache/tooling-trusted-releases/issues/495 > > > - Sebb is working a new test server which will be like the existing > > > server. It will checkout branches from the existing svn repositories. > > > > Sebb decided he doesn’t need this for himself. I’ll work on it next week > > myself. > > There is already a Docker setup that can be used to test, and an SVN > branch: tooling project. > It's a lot easier to test changes locally, and the website is not > public, so errors in authentication are unlikely to leak data. > > My plan is to test Reporter using parallel ATR and Whimsy requests > (comparing the two).
ATR should read BAT; Reporter does not use ATR. > Once the ATR API is working and integrated into Reporter, the whimsy > code can be dropped, and the code merged back into the live instance. ATR should read BAT; Reporter does not use ATR. > I don't see a need for a test instance, especially since the changes > are limited to a single fairly simple module. > > However, I did create a node definition in Puppet: > https://github.com/apache/infrastructure-p6/tree/env-tooling-project-vm > This can be adjusted for use once the VM has been created > > > > - Once that is in place you should be able to ssh onto the machine and > > > make changes as the tooling team is ready. > > > - ATR Project track is here: > > > https://github.com/apache/tooling-trusted-releases/issues/469 - it will > > > be a week or two before we start work on those issues. > > > - BAT Reporter integration issues can be found in the private > > > apache/tooling-agenda repository. > > > > > > It is an open question if we migrate the reporter and project code to GH. > > > We can make that decision as we go along. > > > > > >> - mailing list: here dev@community or somewhere else? > > > > > > [email protected] or the #apache-trusted-release slack channel. If > > > you would prefer a separate slack channel I can set it up. > > > > > > Best, > > > Dave > > > > > >> > > >> Best Regards, > > >> > > >> Hervé > > >> > > >> On 2026/01/09 20:14:32 Dave Fisher wrote: > > >>> Comdev maintains a projects vm that hosts two websites that share > > >>> backend data models. > > >>> These two websites need to be updated due to their interactions with > > >>> two of the Tooling > > >>> Initiative's projects: the Board Agenda Tool (BAT) which has replaced > > >>> the Whimsy Agenda Tool, > > >>> and the Apache Trusted Releases platform (ATR) which will track > > >>> releases and require PMCs > > >>> to define all of their projects. > > >>> > > >>> The following changes are planned to be implemented by the Tooling Team > > >>> with the support > > >>> of volunteers. > > >>> > > >>> 1. The Reporter https://reporter.apache.org needs the following work. > > >>> - Submit pmc reports to the BAT instead of Whimsy > > >>> - The board wants to link from the BAT to the "CHI" for a project > > >>> - The board may want to change the report wizard > > >>> - The committer / PMC start date mapping needs to be moved somewhere > > >>> else > > >>> - Voluntary release additions are replaced with data from ATR > > >>> - Updates to the "CHI" may be required by the board > > >>> > > >>> 2. The Projects site https://project.apache.org needs the following > > >>> work. > > >>> - Committer timelines should only use the timelines2 version which > > >>> meets our recent > > >>> 10,000th committer announcement > > >>> - Releases tab is inaccurate and depends on intrepretation, the data > > >>> must come from ATR > > >>> - ATR requires PMC projects to be declared, PMCs voluntarily and > > >>> manually editing DOAP > > >>> needs to stop > > >>> > > >>> Here is the plan: > > >>> > > >>> A. Build a test Projects VM and enable the tooling team and other > > >>> volunteers to make, > > >>> test, and deploy changes to the current legacy vm and websites. The > > >>> Tooling team > > >>> appreciates help from any ASF Member or Comdev PMC Member. If you wish > > >>> to volunteer > > >>> let us know. We plan to start on this step next week. > > >>> > > >>> B. Modify the reporter to work with the BAT. Make other changes as the > > >>> board requires. > > >>> > > >>> C. Modify the projects vm to work with the ATR. > > >>> - Extract project info from existing DOAP. > > >>> - ATR projects track issue - > > >>> https://github.com/apache/tooling-trusted-releases/issues/469 > > >>> - Gather project and release information from ATR. > > >>> > > >>> D. Upgrade gunicorn service based reporter to a new git based asfquart > > >>> site. This update > > >>> will enable MFA along with eventual support from Infra. > > >>> > > >>> E. Possibly upgrade projects.apache.org into a simple public asfquart > > >>> site. It's less clear > > >>> if this is needed. > > >>> > > >>> The Tooling team would appreciate help from any ASF Member or Comdev > > >>> PMC Member who wishes > > >>> to volunteer. Let us know and we will provide access to the test vm. > > >>> > > >>> Best, > > >>> Dave > > >>> > > >>> > > >>> --------------------------------------------------------------------- > > >>> 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] > > > > > > > > > --------------------------------------------------------------------- > > 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]
