Commit 015a2e53 authored by intrigeri's avatar intrigeri
Browse files

Fold "document progress" doc into the GitLab one

parent 409a430a
......@@ -229,9 +229,39 @@ If your team regularly manipulates confidential data, then its issues live under
a dedicated GitLab project, with a different set of members, and possibly
configured so that new issues are confidential by default.
<a id="document-progress"></a>
# How to document progress
See [[contribute/working_together/document_progress]].
## Create and update issues
When you start working on a task, update the corresponding GitLab issue, after
creating one if needed: replace any status label with the *Doing* label.
For details about labels, see [[metadata|GitLab#metadata]].
All the knowledge useful to the others should be kept on that issue,
or at least linked from there.
Please keep the issues you are working on updated, so that they reflect the
actual status of the task, and especially the next thing to do for it to
be completed.
When committing changes that will resolve an issue once merged, please
include `#NNNN` in the commit message, _NNNN_
being the issue number. Then, GitLab will automatically reference this
commit on the corresponding issue, once the branch is pushed to our
[[Git repository|contribute/Git]]. For example:
Remove tails@boum.org duty from frontdesk (#8420)
## Report progress or failure
It is important for the team to know whether somebody is feeling responsible to
make a task happen, or that it's a wishlist/patches-welcome/don't-care-that-much
(would be great, but *We* don't feel committed to make it happen any time soon).
Thus, it is great to state if you'd like to do it, but also to state if you
won't do it anymore. Don't feel guilty: it's better if we all know it won't happen
soon rather than you feel pressured while having other priorities!
# How to request and provide input
......
[[!meta title="Document progress"]]
# Create and update issues
When a developer works on a task, she should create/update a GitLab issue related to
the task. All the knowledge useful to the others should be kept there (or at
least linked from there). She should take care of updating this issue's
[[metadata|/contribute/working_together/GitLab#metadata]] so that they reflect
the actual status of the task, and especially the next thing to do for it to be
solved.
The issues are stored in [[!tails_gitlab "" desc="GitLab"]].
When committing changes that will resolve an issue once merged, please
include `#NNNN` in the commit message, _NNNN_
being the issue number. Then, GitLab will automatically reference this
commit on the corresponding issue, once the branch is pushed to our
main [[Git repository|contribute/Git]]. For example:
Remove tails@boum.org duty from frontdesk (#8420)
# Report progress or failure
It is important for the team to know whether somebody is feeling responsible to
make a task happen, or that it's a wishlist/patches-welcome/don't-care-that-much
(would be great, but *We* don't feel committed to make it happen any time soon).
Thus, it is great to state if you'd like to do it, but also to state if you
won't do it anymore. Don't feel guilty: it's better if we all know it won't happen
soon rather than you feel pressured while having other priorities!
See [[contribute/working_together/GitLab#document-progress]].
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment