Commit 4fbd1747 authored by Tails developers's avatar Tails developers

doc: talk-dev → contribute

parent 292629df
......@@ -142,5 +142,5 @@ msgid "Talk with us"
msgstr "Mit uns Reden"
#. type: Content of: <div><div><div>
msgid "[[!inline pages=\"talk-dev\" raw=\"yes\"]]"
msgid "[[!inline pages=\"contribute/talk\" raw=\"yes\"]]"
msgstr ""
......@@ -137,5 +137,5 @@ msgid "Talk with us"
msgstr ""
#. type: Content of: <div><div><div>
msgid "[[!inline pages=\"talk-dev\" raw=\"yes\"]]"
msgid "[[!inline pages=\"contribute/talk\" raw=\"yes\"]]"
msgstr ""
......@@ -137,5 +137,5 @@ msgid "Talk with us"
msgstr ""
#. type: Content of: <div><div><div>
msgid "[[!inline pages=\"talk-dev\" raw=\"yes\"]]"
msgid "[[!inline pages=\"contribute/talk\" raw=\"yes\"]]"
msgstr ""
......@@ -85,7 +85,7 @@ Sorry about that.
<h1>Talk with us</h1>
[[!inline pages="talk-dev" raw="yes"]]
[[!inline pages="contribute/talk" raw="yes"]]
</div> <!-- #talk -->
......
......@@ -108,7 +108,7 @@ unless you are sure it is really easy you should:
[[some|todo/macchanger]] [[tasks|todo/usb_install_and_upgrade]] are
much harder to get right than one could initially expect, and you'd
better see how difficult it is to implement what you want.
2. **[[Tell us|talk-dev]] about your plans.** This helps making sure
2. **[[Tell us|contribute/talk]] about your plans.** This helps making sure
your idea fits nicely into the [[big picture|contribute/design]]
and nobody is currently working on the same task.
......@@ -133,7 +133,7 @@ Before diving into technical details please consider reading our
(quite short) [[contribute/merge policy]].
You can submit small, easy changes as Git patches (prepared with the
`git format-patch` command) over [[email|talk-dev]] or post on the
`git format-patch` command) over [[email|contribute/talk]] or post on the
[[patches page|patch]].
For bigger, harder changes that will might require a few review/fix
......@@ -168,4 +168,4 @@ also needed if you need to [[customize]] Tails.
# Talk to us
[[!inline pages="talk-dev" raw="yes"]]
[[!inline pages="contribute/talk" raw="yes"]]
......@@ -18,14 +18,14 @@ do let us know — ideally, by submitting a patch with your fix.
The easiest documentation tasks may be found by looking at documentation section on the [[/TODO]] list (items tagged `todo/documentation`). Small fixes and
enhancements are greatly welcome, and can be done either directly in
this wiki's web interface, by [[sending us|talk-dev]] Git patches, or
this wiki's web interface, by [[sending us|contribute/talk]] Git patches, or
by publishing a [[Git]] branch.
But there is more: Tails [[end-user documentation|support]] needs lots
of work. A plan was thought through and sent to the [Tails development
mailing-list](https://boum.org/mailman/listinfo/tails-dev/) on Thu, 17
Feb 2011. Documentation writers coordinate themselves using our usual
[[development communication channels|talk-dev]]. On the technical
[[development communication channels|contribute/talk]]. On the technical
side, a dedicated `doc-rework` [[Git]] branch has been setup to host
this work.
......@@ -37,4 +37,4 @@ translators|contribute/how/translate]] for details.
# Talk to us
[[!inline pages="talk-dev" raw="yes"]]
[[!inline pages="contribute/talk" raw="yes"]]
[[!meta title="Help other Tails users"]]
Replying on the [[forum]] or hanging out on [[our IRC channel|talk-dev]] and
Replying on the [[forum]] or hanging out on [[our IRC channel|contribute/talk]] and
providing assistance to new users is incredibly valuable.
......@@ -16,4 +16,4 @@ and we can smoothly learn to work together.
# Talk to us
[[!inline pages="talk-dev" raw="yes"]]
[[!inline pages="contribute/talk" raw="yes"]]
......@@ -97,7 +97,7 @@ while custom Tails programs live in the `devel` branch.
2. Translate whatever you can in your preferred PO file editor.
3. Commit the changes you made to `.po` files.
4. Use the `git format-patch` command to prepare patches.
5. [[Send us|talk-dev]] your patches.
5. [[Send us|contribute/talk]] your patches.
6. Frequently merge changes from our main repository into yours.
#### Ask us to pull from your Git branch
......@@ -108,7 +108,7 @@ while custom Tails programs live in the `devel` branch.
2. Translate whatever you can in your preferred PO file editor.
3. Commit the changes you made to `.po` files.
4. Push your changes to your online Git repository.
5. [[Ask us|talk-dev]] to pull from the branch you worked on.
5. [[Ask us|contribute/talk]] to pull from the branch you worked on.
6. Frequently merge changes from our main repository into yours.
# Supported languages
......@@ -132,4 +132,4 @@ work happier and more sustainable.
# Talk to us
[[!inline pages="talk-dev" raw="yes"]]
[[!inline pages="contribute/talk" raw="yes"]]
......@@ -25,5 +25,5 @@ branch to be reviewed and get more exposure.
If you find the `devel` branch in a non-building state and can
identify the root cause of it to a recent commit, fix it if you wish,
but don't let it disturb you otherwise: just revert the faulty commit
and [[inform the other developers|talk-dev]] so that the author knows
and [[inform the other developers|contribute/talk]] so that the author knows
s/he needs to fix his/her stuff before reapplying it at a later point.
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