[Pkg-owncloud-commits] [owncloud-doc] 28/33: Can't tag/close unless you're added to the repo

[David Prévot]

This is an automated email from the git hooks/post-receive script.

taffit pushed a commit to branch master
in repository owncloud-doc.

commit 9d6a991492e528b775125dc911e284b2407a97c3
Author: Jos Poortvliet <jospoortvliet at gmail.com>
Date:   Thu Dec 4 15:41:51 2014 +0100

    Can't tag/close unless you're added to the repo
---
 developer_manual/bugtracker/triaging.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/developer_manual/bugtracker/triaging.rst b/developer_manual/bugtracker/triaging.rst
index 6cf98ba..a6e073c 100644
--- a/developer_manual/bugtracker/triaging.rst
+++ b/developer_manual/bugtracker/triaging.rst
@@ -41,7 +41,7 @@ General considerations
 * It might even be fixed, sometimes! It can also be fruitful to contact the `developers on irc <irc://freenode/#owncloud-dev>`_. Tell them you're triaging bugs and share what problem you bumped into. Or just ask on the test-pilots mailing list.
 * To ensure no two people are working on the same issue, we ask you to simply add a comment like "I am triaging this" in the issue you want to work on, and when done, before or after executing the triaging actions, note similarly that you're done.
 
-    Open question: do you need to sign the contributor agreement for this? Shouldn't be the case...
+    To be able to tag and close issues, you need to have access to the repository. For the core and sync app repositories this also means having signed the contributor agreement. However, this isn't really needed for triaging as you can comment after you're done triaging and somebody else can execute those actions.
 
 Finding bugs to triage
 ======================

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-owncloud/owncloud-doc.git