Repository navigation
Translate commons principles into contribution and stewardship guidance - #9
Draft
raelovejoy wants to merge 2 commits into
Draft
raelovejoy wants to merge 2 commits into
raelovejoy wants to merge 2 commits into
Conversation
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.
Extends contribution guidance, human stewardship review, the organization front door, and an optional PR-template prompt. Makes authority, privacy/publication, dissent, maintenance burden, and handoff explicit without assigning new offices or configuring automation.
Changed files: CONTRIBUTING.md, PROJECT_STEWARDSHIP.md, PULL_REQUEST_TEMPLATE.md, and README.md. Their blobs remain exactly as prepared in the original commons draft. The separate profile-only invitation has been consolidated into the refreshed profile in #10, where it is explicitly presented as a proposal. This removes the profile conflict without incorporating these substantive guidance changes into the professional refresh.
Validation: the four substantive files were compared byte for byte with original head e95fda3. A local tree-only compatibility check with #10 passes and preserves both README additions. No code/runtime behavior changes. No branch was merged by the check.
Existing registry work #5 remains separate. Shared source proposal: Root-Sequence/root-sequence#43. The canonical main-anchor links in these guidance files still depend on accepting that proposal first; until then inspect the proposed section in #43. This dependency is not publication authorization.
Keep in draft. The guidance remains a review-pending proposal, not evidence of operating governance or authorization to change roles, privacy, release gates, or project holds. No main update, merge, deployment, participant research, or canon adoption. Canonical refresh progress: Root-Sequence/root-sequence#46.