Repository navigation
Remove references to unrelated personal projects from OpenDKG policies - #7
Merged
Merged
Conversation
…/membership-agreement.yml
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
Remove references to a personal project outside OpenDKG throughout the organization's current policy files, onboarding documentation, Issue Form, PR template and membership-validation source/tests.
The OpenDKG policy scope remains defined generically: repositories owned by the OpenDKG organization, subject to the repository-specific license and provenance requirements. No personally owned or external project is named in the current policy documents.
Adoption and exact policy version
The newly corrected Contributor Agreement v1.0 and Governance v1.0 are both present in immutable commit:
d56279b4f3c25dd8f9e68699d61be23a0c7a6b07This replaces the previously pinned consent revision. The form, validator and test fixture now use the new revision. Prior personal acceptance to the older agreement is not consent to this new revision. Each of the three original cofounders must personally review and affirmatively accept the updated version.
Cautions