summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChandan Singh <chandan@chandansingh.net>2020-04-21 20:37:00 +0000
committerbst-marge-bot <marge-bot@buildstream.build>2020-05-01 19:28:22 +0000
commite3c2792dbdd5f7dfa4851e35ff802fe6a90a3bf9 (patch)
tree6e6ef918130ae1d8f213fb9991df69060efa7cf0
parent9796d1da5266183574da3e968d5b892624aa3033 (diff)
downloadbuildstream-e3c2792dbdd5f7dfa4851e35ff802fe6a90a3bf9.tar.gz
CONTRIBUTING: Remove link for obsolete issue policieschandan/no-nosoftware
As discussed in https://mail.gnome.org/archives/buildstream-list/2020-April/msg00009.html, we want to get rid of the nosoftware subgroup. These issue policies are the only remaining link from here to the nosoftware subgroup. I propose to remove this link because the linked are obsolete and overly process-oriented. Our current practices don't reflect those policies either. For example, I don't think any of us are religiously using labels like backlog/todo/doing etc. In my opinion, the description at https://gitlab.com/BuildStream/buildstream/-/labels is sufficient for documenting what labels mean, and we don't need to force everything to have one label of each category. We can obviously improve the label descriptions if they are lacking.
-rw-r--r--CONTRIBUTING.rst4
1 files changed, 0 insertions, 4 deletions
diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst
index 70741bcc5..cbf99367f 100644
--- a/CONTRIBUTING.rst
+++ b/CONTRIBUTING.rst
@@ -12,10 +12,6 @@ to fix an issue, then you should first search the list of `open issues <https://
to see if the issue is already filed, and `open an issue <https://gitlab.com/BuildStream/buildstream/issues/new>`_
if no issue already exists.
-For policies on how to submit an issue and how to use our project labels,
-we recommend that you read the `policies guide
-<https://gitlab.com/BuildStream/nosoftware/alignment/blob/master/BuildStream_policies.md>`_.
-
.. _contributing_fixing_bugs: