potiuk opened a new pull request, #55: URL: https://github.com/apache/airflow-steward/pull/55
## Summary Group 1 of the Airflow-isms audit. Pure prose, low risk. All affected sections already pointed at `<project-config>/<file>` for the actual project-specific values; the parenthetical `(for Airflow, ...)` was adding noise without value, and at the framework level the singular project name shouldn't appear as a privileged example. **Files touched** (~10): - `AGENTS.md` — naming-conventions reference, CVE allocation form note - `docs/security/process.md` — CVE allocation skill description; "provider-wave" cadence wording → generic - `docs/security/how-to-fix-a-security-issue.md` — three pointers - `docs/prerequisites.md` — CVE-tool note + dev-toolchain reference - `docs/pr-management/README.md` — provenance paragraph reworded; **also** removed a stale "follow-up PR will extract Airflow defaults" claim that was outdated since #52 landed that extraction - `tools/vulnogram/allocation.md` — three qualifiers; the `apache-airflow-providers-smtp` wrong-product example reworded as a generic multi-package family example - `tools/vulnogram/tool.md` — `For Airflow (cve_tool: vulnogram)` → `For adopters declaring cve_tool: vulnogram` - `tools/ponymail/operations.md` — "provider-wave cut date" → "project's release-cadence cut date" ## What's NOT in this PR (follow-ups) - **Group 2** — skill business logic still embeds Airflow-specifics: `security-issue-fix` clone-path probing (`~/code/airflow`, etc.), `security-cve-allocate` title-normalization regex with `Apache Airflow` literals, `security-issue-import-from-pr` path-to-scope mapping (`providers/<name>/`, `airflow-core/`, `task-sdk/`), `pr-management-code-review` provider-tree section. Those need new `<project-config>/project.md` knobs (`upstream_name`, `upstream_clone_path_candidates`, `upstream_package_path_regex`, `version_pattern`, `cve_tool_subject_pattern`) and code changes in the skills. Substantive — lands in a separate PR. - **Group 3** — vulnogram tool docstring/help-text examples (`apache-airflow`, `apache-airflow-project-foo`). Cosmetic; the underlying code is already config-driven. Lands in a third PR. ## Test plan - [x] `prek run --all-files` clean - [x] `grep -nE "for Airflow|For Airflow,|airflow,? see"` across `AGENTS.md docs/ tools/` returns zero hits - [ ] Visual review of each diff hunk to confirm the `<project-config>/` pointer is preserved everywhere -- 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]
