potiuk opened a new issue, #461:
URL: https://github.com/apache/airflow-steward/issues/461
The vendor-neutral `projects/_template/` scaffold (meant to be copied and
customised by any adopter) still carries Apache Airflow's concrete identity
in
a few places, rather than placeholders or clearly-marked examples. Surfaced
by
the Step 6d genericity audit during a downstream adopter's `/magpie-setup
upgrade` (snapshot `3de27eb`).
### `projects/_template/project.md`
- `bare_name_handles` (~L809-814) seeds Airflow's real roster:
`Jarek: "@potiuk"`, `Ash: "@ashb"`, `Kaxil: "@kaxil"`, `Ephraim:
"@ephraimbuddy"`,
`Jed: "@jedcunningham"`.
- `release_managers` (~L823-827) lists the same real handles
(`@ephraimbuddy`, `@jedcunningham`, `@potiuk`, `@kaxil`).
The surrounding comments do say *"ASF/Airflow default ... Override when:
adapt to
the adopter's roster"*, so this is acknowledged — but a vendor-neutral
template
should ship placeholder handles (e.g. `<contributor>: "@<handle>"`) or a
clearly
fenced *Example* block, not a specific project's live roster.
### `projects/_template/release-management-config.md`
Airflow-specific values presented as the table "Value" column (not
placeholders):
- `vote_dev_list` -> `[email protected]` (~L123)
- `mail_archive_url_template` ->
`https://lists.apache.org/[email protected]` (~L125)
- `announce_cc_lists` -> `[email protected], [email protected]`
(~L158)
- `site_repo` -> `apache/airflow-site` (~L160)
- vote/result/announce subject templates -> `Apache Airflow <version>`
(~L128-129, L159)
(`[email protected]` at ~L157 is the shared ASF list and is correctly
generic.)
### Suggested fix
Replace the concrete values with `<placeholder>` tokens or annotate them as
`Example:` so an arbitrary adopter doesn't inherit Airflow's
roster/lists/site
as defaults. Heuristic audit — please sanity-check for any I missed.
--
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]
