Add info about labels

developer_manual/general/codingguidelines.rst

@@ -11,10 +11,48 @@ General
 * Fixes go directly to master, nevertheless they need to be tested thoroughly
 * New features are always developed in a branch and only merged to master once they are fully done
 * Software should work. Only put features into master when they are complete. It's better to not have a feature instead of having one that works poorly.
-* When you are finished, use the merge request function on Github. The other developers will look at it and give you feedback. You can also post your merge request to the mailing list to let people know. See `the code review page for more information <../bugtracker/codereviews.html>`_
+* When you are finished, use the merge request function on Github to create a pull request. The other developers will look at it and give you feedback. You can signify that your PR is ready for review by adding the label "5 - ready for review" to it. You can also post your merge request to the mailing list to let people know. See `the code review page for more information <../bugtracker/codereviews.html>`_
 * Decisions are made by consensus. We strive for making the best technical decisions and as nobody can know everything, we collaborate. That means a first negative comment might not be the final word, neither is positive feedback an immediate GO. ownCloud is built out of modular pieces (apps) and maintainers have a strong influence. In case of disagreement we consult other seasoned contributors.
 * We need a signed contributor agreement from you to commit into the core repository (apps don't need that). All the information is in our `Contributor agreement FAQ <http://owncloud.org/contribute/agreement/>`_.
 
+Labels
+------
+We assign labels to issues and pull requests to make it easy to find them and to signal what needs to be done. Some of these are assigned by the developers, others by QA, bug triagers, project lead or maintainers and so on. It is not desired that users/reporters of bugs assign labels themselves, unless they are developers/contributors to ownCloud.
+
+The most important labels and their meaning:
+
+* #bug - this issue is a bug
+* #enhancement - this issue is a feature request/idea for improvement of ownCloud
+* #design - this needs help from the design team or is a design-related issue/pull request
+* #sharing - this issue or PR is related to sharing
+* #technical debt - this issue or PR is about `technical debt <http://en.wikipedia.org/wiki/Technical_debt>`_
+* #sev1-critical #sev2-high #sev3-medium #sev4-low signify how important the bug is.
+* #Junior Job - these are issues which are relatively easy to solve and ideal for people who want to learn how to code in ownCloud
+* Tags showing the state of the issue or PR, numbered 1-6:
+ * #1 - Backlog - this issue has to be tackled but isn't planned in yet (please don't use, we prefer using a backlog milestone)
+ * #2 - Triaging - this issue has to be `triaged <../bugtracker/triaging.html>`_
+ * #3 - To develop - ready to start development on this
+ * #4 - Developing - development in progress
+ * #5 - To Review - ready for review
+ * #6 - Reviewing - review in progress
+* App tags: #app:files #app:user_ldap #app:files_encryption and so on. These tags indicate the app that is impacted by the issue or which the PR is related to
+* settings tags: #settings:personal #settings:apps #settings:admin and so on. These tags indicate the settings area that is impacted by the issue or which the PR is related to
+* db tags: #db:mysql #db:sqlite #db:PostGreSQL and so on. These tags indicate the database that is impacted by the issue or which the PR is related to
+* browser tags: #browser:ie #browser:safari ands o on. These tags indicate the browser that is impacted by the issue or which the PR is related to
+* #triage - this issue *has to be* `triaged <../bugtracker/triaging.html>`_
+* #needsinfo - this issue needs further information from the reporter, see `triaging <../bugtracker/triaging.html>`_ old tag is #clarification request, please don't use that one anymore.
+* #discussion - this issue needs to be discussed
+* #Security - this is a security related issue
+* #Windows server - this is related to windows server
+* #research - this item requires some research before it can continue
+* #packaging - this is related to packaging
+* #theming - refers to theming issues or improvements
+* #L10n - refers to translation issues or improvements
+* #release note - relevant for the release notes
+* #privacy - refers to issues that might lead to privacy concerns
+* #won't fix - This problem won't be fixed (can be for a wide variety of reasons...)
+
+If you want a label not in the list above, please first discuss on the mailing list.
 
 Coding
 ------