Skip to content

WIP: Added and partially corrected/modified material from the 'Commun…#5

Draft
cfkaran2 wants to merge 1 commit into
git-bug:trunkfrom
cfkaran2:community_specification
Draft

WIP: Added and partially corrected/modified material from the 'Commun…#5
cfkaran2 wants to merge 1 commit into
git-bug:trunkfrom
cfkaran2:community_specification

Conversation

@cfkaran2

Copy link
Copy Markdown
Contributor

…ity Specification' project.

The Community Specification provides a process and set of legal documents that help projects that are developing specifications do so in a manner that protects all contributors and implementors of the given specification. This commit copied over relevant files, redirected links, corrected typos, and in general made it useful for the 'git-bug-spec' project. I've marked this as a WIP because there are several documents that still need to be filled in, and for which I don't have the correct information. To whit:

  • The 'Contributor Covenant Code of Conduct.md' requires a method of notifying the maintainers of violations. This requires input from @MichaelMure.
  • The 'Notices.md' file requires the same information as above, but suggests adding more than one person as a point of contact, just in case the issue is with one of the points of contact listed.
  • The 'Scope.md' needs to be written out. I haven't had time to do so, but I wanted to include the file with this commit to ensure that it's taken care of before the fork is merged back to the original project.

…ity Specification' project.

The [Community Specification](https://github.com/CommunitySpecification/Community_Specification) provides a process and set of legal documents that help projects that are developing specifications do so in a manner that protects all contributors and implementors of the given specification.  This commit copied over relevant files, redirected links, corrected typos, and in general made it useful for the 'git-bug-spec' project.  I've marked this as a WIP because there are several documents that still need to be filled in, and for which I don't have the correct information.  To whit:

- The 'Contributor Covenant Code of Conduct.md' requires a method of notifying the maintainers of violations.  This requires input from @MichaelMure.
- The 'Notices.md' file requires the same information as above, but suggests adding more than one person as a point of contact, just in case the issue is with one of the points of contact listed.
- The 'Scope.md'  needs to be written out.  I haven't had time to do so, but I wanted to include the file with this commit to ensure that it's taken care of before the fork is merged back to the original project.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant