Repository navigation
Translate commons principles into contribution and stewardship guidance - #9
Draft
raelovejoy wants to merge 3 commits into
Draft
raelovejoy wants to merge 3 commits into
raelovejoy wants to merge 3 commits into
Conversation
2 of 4 tasks
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.
Proposes a repository-work application of the published commons collaboration principles. The contribution section keeps disagreement and privacy visible; stewardship prompts ask about real powers, maintenance burden, handoff, and stopping. The PR template adds an optional prompt rather than a required new process.
Refreshed against current main
2ac252195775efcef42506027e033c5e84e99fab, preserving the published profile, registry seed, and completed publication-status corrections. The new contribution section explicitly remains proposed until project-local adoption; the README pointer is shorter and distinguishes the published source from proposed local practice. Four documentation files differ from main.Validation: complete changed passages and surrounding contribution/stewardship/template context reviewed; scoped whitespace and added relative links/fragments pass; the source anchor is verified in published root main. Profile, registry, and context blobs match main exactly. No code or workflow changes.
Shared source #43 is now published as
95f6b73af47a4eb3e75ba3f0829e692af526bb11; the canonical main anchor exists. This AI-assisted refresh leaves the local application proposed and awaiting review. Publication of the source does not adopt these practices in this project, grant access or roles, release project holds, or authorize participant research. No merge or deployment was performed by the agent.