Repository navigation
config: publish Magpie's project configuration and AI contribution policy - #1412
Merged
Merged
Conversation
…tion policy Commit the framework checkout's own project configuration under .apache-magpie-overrides/ so every contributor gets working pr-management, release-management, issue, repo-health and contributor-growth skills on clone, without running /magpie-setup config. - project.md: identity, repositories, mailing lists (dev@, users@, commits@, private@magpie.apache.org); security tracker, CNA queue, project board and mail backends marked as not used, since reports follow the ASF default process via security@apache.org. - pmc-roster.md: the 21 PMC members from projects.apache.org. - release-trains.md / release-build.md: main is the only release train; git-archive source zip with sha512, RAT via .rat-excludes. - issue-tracker-config.md / reassess-pool-defaults.md: GitHub Issues on apache/magpie, with the triage, reassess and stale queries. - fix-workflow.md: no backport labels; Generated-by trailer. - reviewer-roster.md: derived from the last six months of history. - Contributor-growth configs: template thresholds, six-month window. Add docs/ai-contribution-policy.md, which restates the ASF Generative Tooling Guidance for this project, and link it from CONTRIBUTING.md. The contributor-growth skills judge AI-assisted contributions against it, and code review links to it. Generated-by: Claude Opus 5
4 tasks done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
.apache-magpie-overrides/, so pr-management, release-management, issue, repo-health and contributor-growth skills work on a fresh clone without each contributor running/magpie-setup config.44 of 54 in-repo skills now have their full
requires_configset; the 10 that do not are security-family skills, which need a private tracker Magpie does not run.docs/ai-contribution-policy.md, restating the ASF Generative Tooling Guidance for this project, and link it fromCONTRIBUTING.md→ Authoring with an agent.contributor-to-committerandcontributor-nominationjudge AI-assisted contributions against it;pr-management-code-reviewlinks to it.What the configuration records:
apache/magpieonmain;dev@,users@,commits@,private@magpie.apache.org.security@apache.org. Those fields say "not used" with that reason rather than carrying placeholders.mainis the only release train (0.1.0, RM @potiuk);git archivesource zip,sha512only, RAT via.rat-excludes; no backport labels.needs triagelabel.Generated-by:, ascommit-attribution.tomlalready sets.Type of change
.claude/skills/<name>/) — eval fixtures updated belowtools/<system>/*.md)tools/*/withpyproject.toml)docs/,README.md,CONTRIBUTING.md)projects/_template/)prek, workflows, validators).apache-magpie-overrides/)Test plan
prek run --all-filespasseslychee --offline --include-fragmentsover.apache-magpie-overrides/*.md, the policy doc andCONTRIBUTING.md: 0 errors.Run explicitly because the lychee hook skips hidden directories, so the override files are otherwise unchecked.
The templates' relative links assumed a deeper directory; they were re-pointed at targets that exist from
.apache-magpie-overrides/.requires_config:resolved against the committed files: 44/54 complete, the 10 remaining all security-family.RFC-AI-0004 compliance
<PROJECT>,<tracker>,<upstream>,<security-list>) used in all skill / tool prose (thecheck-placeholdersprek hook is the mechanical gate)None apply: no skill or tool prose changes. Concrete Magpie values live only in the adopter-config layer, which is where they belong.
Linked issues
None.
Notes for reviewers (optional)
[DISCUSS]on dev@ before merge.TODOstrings in these files are the templates' own instructions ("replace every TODO"), not unfilled values.Generative AI disclosure: this change was authored with Claude Code (Claude Opus 5); every value was reviewed by the author, and the commit carries a
Generated-by:trailer.🤖 Generated with Claude Code