asf-tooling commented on issue #444:
URL:
https://github.com/apache/tooling-trusted-releases/issues/444#issuecomment-4410303475
<!-- gofannon-issue-triage-bot v2 -->
**Automated triage** — analyzed at `main@2da7807a`
**Type:** `discussion` • **Classification:** `no_action` •
**Confidence:** `medium` • ⚠️ **Possibly stale**
**Application domain(s):** `project_committee_management`,
`shared_infrastructure`
### Summary
This is a large tracking/planning issue for migrating features from
projects.apache.org (comdev website) into this repository. It lists numerous
public pages, JSON data files, cronjobs, and charts that currently live on
projects.apache.org. The prior discussion reveals unresolved architectural
questions: @dave2wave noted that 'Several parts of projects.apache.org belong
on Infra's planned catalog server' and suggested discussing with @Humbedooh.
@sebbASF clarified that PAO fetches JSON from Whimsy rather than parsing
committees-info.txt directly, and both agreed timelines2.html should replace
timelines.html. No implementation work has begun in this repository for these
features.
### Where new code would go
- `atr/get/projects.py` — new file
If project listing pages were implemented, they would likely follow the
pattern of existing GET route modules in atr/get/
- `atr/tasks/` — new file
Cronjobs for parsing releases, generating repos data, and podling data
would likely be implemented as background tasks following the existing task
pattern
### Proposed approach
This issue is an open-ended RFC/epic with no consensus on scope or
destination. The prior discussion reveals that (1) the architectural home for
these features is undecided — some may belong in a separate 'PMC catalog
server' per @dave2wave, (2) data sources and accuracy questions remain
(timelines accuracy, LDAP date corrections from Whimsy), and (3) dependencies
on other systems (Whimsy JSON, SVN dist, reporter.apache.org) need to be
mapped. No patch is appropriate until the architectural discussion between
@dave2wave and @Humbedooh resolves where these features should live.
### Open questions
- Has the discussion between @dave2wave and @Humbedooh about the PMC catalog
server happened, and what was decided about feature placement?
- Which specific features from projects.apache.org are in-scope for this
repository vs. a separate catalog server?
- What is the status of the planned PMC catalog server mentioned by
@dave2wave?
- Are there any other repositories where this migration work has begun?
### Staleness assessment
_opened 133 days ago; last human comment 128 days ago._
Last human activity was 128 days ago (2025-12-31), exceeding the 90-day
threshold. The issue is a planning/tracking epic with no implementation started
in this repository. However, the features described haven't been implemented
elsewhere either, and the architectural discussion about where they belong
(here vs. a separate catalog server) was never resolved.
_The agent reviewed this issue and is not proposing patches in this run.
Review the existing-code citations and open questions above before deciding
next steps._
### Files examined
- `.asf.yaml`
- `.github/PULL_REQUEST_TEMPLATE.md`
- `.github/dependabot.yml`
- `.github/labeler.yml`
- `.github/linters/.markdown-lint.yml`
- `.github/workflows/allowlistchecker.yml`
- `.github/workflows/analyze.yml`
- `.github/workflows/build.yml`
---
*Draft from a triage agent. A human reviewer should validate before merging
any change. The agent did not run tests or verify diffs apply.*
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
