From fdc7d547d5f0306aed6b0527e8c2843353e1b464 Mon Sep 17 00:00:00 2001 From: Mitchell Cuevas <6131188+cuevasm@users.noreply.github.com> Date: Wed, 3 Sep 2025 14:28:49 -0700 Subject: [PATCH] Removing unrelated guidelines, instructions are in readme Removed the entire contributing guidelines section from the document. --- CONTRIBUTING.md | 28 ---------------------------- 1 file changed, 28 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 2e0093a..8b13789 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,29 +1 @@ -# Contributing -Stacks governance is a community-run initiative! As such, it cannot work without your help, and without the input of as many community members as possible. You do not need anyone’s permission to get involved and contribute to the initiative. The #governance working group channel on [Blockstack Discord](https://discordapp.com/invite/ny6wGkx) is a great place to begin getting involved, as many community members regularly share ideas, updates, and resources there. You can also find a number of topics under the [governance category](https://forum.blockstack.org/c/governance) on the Blockstack Community Forum which need your input. - -## Submitting an Issue - -Issues are generally related to an action, and are encouraged as a starting point to do things such as: - -- discuss a topic -- add an agenda item -- propose a change -- provide information -- track a project task - -## Submitting a Pull Request - -Pull requests are welcomed and encouraged! Please follow this general procedure: - -1. Fork/clone the repository -1. Create a new branch related to the PR: `git checkout -b my-branch-name` -1. Make changes and push to your fork -1. Submit a pull request for review - -## Resources - -- [How to Contribute to Open Source](https://opensource.guide/how-to-contribute/) -- [About Issues](https://help.github.com/en/github/managing-your-work-on-github/about-issues) -- [Using Pull Requests](https://help.github.com/articles/about-pull-requests/) -- [Write a good commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)