summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJesse Weinstein <jesse@wefu.org>2015-10-11 11:34:40 -0700
committerJesse Weinstein <jesse@wefu.org>2015-10-11 11:34:40 -0700
commit51828bcfaba3e146b345ad76f00cfad476cd5028 (patch)
tree18dc88ac8be42290196d1b90761664a199a754b2
parentcbdbc98ad39187b42569cf663f64b60eb05021c1 (diff)
Add mention of forking on GitLab
-rw-r--r--wiki/src/contribute/how/documentation.mdwn9
1 files changed, 5 insertions, 4 deletions
diff --git a/wiki/src/contribute/how/documentation.mdwn b/wiki/src/contribute/how/documentation.mdwn
index db2a55e..1a4466e 100644
--- a/wiki/src/contribute/how/documentation.mdwn
+++ b/wiki/src/contribute/how/documentation.mdwn
@@ -28,10 +28,11 @@ But there are still many ways you can start contributing:
[[ask us for review|contribute/talk]].
- Small fixes and enhancements to the current documentation are
- greatly welcome. This can be done by [[sending us|contribute/talk]]
- Git patches, by publishing a [[Git]] branch, or simply by email on
- the public mailing list. In the general case, this work should be
- based on the `master` branch.
+ greatly welcome. This can be done by sending Git patches to [[the
+ tails-dev mailing list|contribute/talk]], or by publishing a
+ [[Git]] branch (e.g. to a fork on
+ [GitLab](https://gitlab.com/Tails/tails)). In general,
+ documentation changes should be based on the `master` branch.
Documentation writers coordinate themselves using our usual
[[development communication channels|contribute/talk]].