From: Michael Stapelberg Date: Fri, 19 Feb 2016 17:41:30 +0000 (+0100) Subject: move CONTRIBUTING.md to .github/ directory X-Git-Tag: 4.12~12 X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=fe5e7b0c81855a18dc3a4556e2964764bb6cbd2b;p=i3%2Fi3 move CONTRIBUTING.md to .github/ directory See https://github.com/blog/2111-issue-and-pull-request-templates --- diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md new file mode 100644 index 00000000..474355ad --- /dev/null +++ b/.github/CONTRIBUTING.md @@ -0,0 +1,32 @@ +# Contributing + +## i3status/i3lock bug reports and feature requests + +Note that bug reports and feature requests for related projects should be filed in the corresponding repositories for [i3status](https://github.com/i3/i3status) and [i3lock](https://github.com/i3/i3lock). + +## i3 bug reports and feature requests + +1. Read the [debugging instructions](http://i3wm.org/docs/debugging.html). +2. Make sure you include a link to your logfile in your report (section 3). +3. Make sure you include the i3 version number in your report (section 1). +4. Please be aware that we cannot support compatibility issues with + closed-source software, as digging into compatibility problems without + having access to the source code is too time-consuming. Additionally, + experience has shown that often, the software in question is responsible for + the issue. Please raise an issue with the software in question, not i3. + +## Pull requests + +* Before sending a pull request for new features, please check with us that the + feature is something we want to see in i3 by opening an issue which has + ”feature request” or ”enhancement” in its title. +* Use the `next` branch for developing and sending your pull request. +* Use `clang-format` to format your code. +* Run the [testsuite](http://i3wm.org/docs/testsuite.html) + +## Finding something to do + +* Find a [reproducible bug](https://github.com/i3/i3/issues?utf8=%E2%9C%93&q=is%3Aopen+label%3Areproducible+label%3Abug+) from the issue tracker. These issues have been reviewed and confirmed by a project contributor. +* Find an [accepted enhancement](https://github.com/i3/i3/issues?utf8=%E2%9C%93&q=is%3Aopen+label%3Aaccepted+label%3Aenhancement) from the issue tracker. These have been approved and are ok to start working on. + +There's a very good [overview of the codebase](http://i3wm.org/docs/hacking-howto.html) available to get you started. diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md deleted file mode 100644 index 474355ad..00000000 --- a/CONTRIBUTING.md +++ /dev/null @@ -1,32 +0,0 @@ -# Contributing - -## i3status/i3lock bug reports and feature requests - -Note that bug reports and feature requests for related projects should be filed in the corresponding repositories for [i3status](https://github.com/i3/i3status) and [i3lock](https://github.com/i3/i3lock). - -## i3 bug reports and feature requests - -1. Read the [debugging instructions](http://i3wm.org/docs/debugging.html). -2. Make sure you include a link to your logfile in your report (section 3). -3. Make sure you include the i3 version number in your report (section 1). -4. Please be aware that we cannot support compatibility issues with - closed-source software, as digging into compatibility problems without - having access to the source code is too time-consuming. Additionally, - experience has shown that often, the software in question is responsible for - the issue. Please raise an issue with the software in question, not i3. - -## Pull requests - -* Before sending a pull request for new features, please check with us that the - feature is something we want to see in i3 by opening an issue which has - ”feature request” or ”enhancement” in its title. -* Use the `next` branch for developing and sending your pull request. -* Use `clang-format` to format your code. -* Run the [testsuite](http://i3wm.org/docs/testsuite.html) - -## Finding something to do - -* Find a [reproducible bug](https://github.com/i3/i3/issues?utf8=%E2%9C%93&q=is%3Aopen+label%3Areproducible+label%3Abug+) from the issue tracker. These issues have been reviewed and confirmed by a project contributor. -* Find an [accepted enhancement](https://github.com/i3/i3/issues?utf8=%E2%9C%93&q=is%3Aopen+label%3Aaccepted+label%3Aenhancement) from the issue tracker. These have been approved and are ok to start working on. - -There's a very good [overview of the codebase](http://i3wm.org/docs/hacking-howto.html) available to get you started.