docs: add CONTRIBUTING, GOVERNANCE and OWNERS, plus issue and PR templates - #223
Open
willhama wants to merge 1 commit into
Open
docs: add CONTRIBUTING, GOVERNANCE and OWNERS, plus issue and PR templates#223willhama wants to merge 1 commit into
willhama wants to merge 1 commit into
Conversation
…lates The AAIF Project Lifecycle Policy expects Growth and Impact stage projects to document 'a means by which one may become a core maintainer... preferably laid out in a GOVERNANCE.md file and references a CONTRIBUTING.md and OWNERS.md file'. This repository currently has none of those, nor any issue or pull request templates. CONTRIBUTING.md states what gets merged and how fast, and gives objective, checkable requirements for the most common contribution by far: adding a tool to the compatibility list. The requirement that matters is evidence that the tool reads AGENTS.md in a released version, linked in the PR, so a reviewer can verify an entry without installing anything. It also records that the default answer to format changes is no, and routes them to the Technical Committee. GOVERNANCE.md separates the two things this repository holds, a deliberately stable format and an actively changing website, since conflating them is what stalls proposals. It defines contributor, triager and maintainer, makes triage the easiest role to earn because triage is the bottleneck, and documents inactivity, emeritus and escalation to the TC when no maintainer is reachable. OWNERS.md is drafted from public commit history and is explicitly marked as needing confirmation by the people named in it, since a contributor without write access cannot read the permission list. The templates target the actual queue problem: the PR template makes the compatibility evidence mandatory, and ISSUE_TEMPLATE/config.yml routes format changes to aaif/project-proposals before they become pull requests here. Only markdown and YAML change, so no application code is affected and pnpm lint was not run. Signed-off-by: marcwi <marc@optohive.com>
|
Someone is attempting to deploy a commit to the openai Team on Vercel. A member of the Team first needs to authorize it. |
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
1 participant
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.
No description provided.