Commit 862f5b35 authored by Tails developers's avatar Tails developers

Wiki/contribute: many small changes after proof-reading with a native speaker.

More to come soon.
parent a4cc8a58
......@@ -9,31 +9,32 @@ Welcome aboard! Please read-on.</p>
</div>
# Forewords
# Foreword
## Why should I read this page?
Every Free Software project's development process is a bit different
from the others. If you don't understand its development process, it
is generally pretty hard for you to contribute in a way that is both
efficient and joyful for you... and for its current core development
team. This document is meant to help *you* understand what you need so
that you can more efficiently and joyfully contribute to Tails.
Every Free Software project is a bit different from the others. If you
don't understand its development process, it is generally pretty hard
for you to contribute in a way that is both efficient and joyful for
you... and for its current core development team. This document is
meant to help *you* understand what you need so that you can more
efficiently and joyfully contribute to Tails.
## Focus on low-effort maintainability
Many, many Live CD projects — including a few privacy-targeted ones —
have lived fast and died young. We explain this on the one hand by
their being one wo/man efforts, on the other hand by design decisions
that made their maintenance too much costly timewise and energywise.
Many, many Live CD projects — including a few ones that aimed at
enhancing their users' privacy — have lived fast and died young. We
explain this by their being one wo/man efforts, as well as design
decisions that made their maintenance much too costly timewise and
energywise.
We want Tails to live as long as it is needed: Tails is not meant to
solely be a pet project.
be solely a pet project.
Since the early days of this project (i.e. early 2009), ease of
maintenance on the long run has been a major factor in any decision we
have made. Nowadays Tails is more alive and kicking than it has ever
been, and we feel this would have been impossible without
maintenance in the long run has been a major factor in every decision
we have made. Nowadays Tails is more alive and kicking than it has
ever been, and we feel this would have been impossible without
this kind of mindset.
Our focus on low-effort maintainability has practical consequences.
......@@ -44,15 +45,15 @@ the Debian Live build tools). Pretty important details about this can
be found in our [[contribute/relationship_with_upstream]] statement
rather than repeated here.
Second, we try **not to reinvent the wheel** too often, and flea the
*Not Invented Here* syndrome like the pest. This implies very few code
is actually written specifically for Tails: most of what we call
"code" work on Tails is more similar to system administration than it
Second, we try **not to reinvent the wheel** too often, and flee the
*Not-Invented-Here* syndrome like the plague. This implies very little
code is actually written specifically for Tails: most of what we call
*code work* on Tails is more similar to system administration than it
is to programming: we mainly glue existing pieces together; when we
happen to need a feature that no software provides yet, we tend to
choose the best among existing tools and do whatever is needed to get
the needed feature upstream... which may, or may not, be writing a
patch ourselves.
pick the best existing tool and do whatever is needed to get the
needed feature upstream... which may, or may not, be writing a patch
ourselves.
# How to get started
......@@ -61,11 +62,11 @@ patch ourselves.
This wiki is used as a basic bug tracking system: we use it to manage
our [[todo]] and [[bugs]] lists as well as our [[contribute/roadmap]].
If you already know which one of the listed tasks you want to fulfill
*and it is only tagged `todo/code`*, you can probably safely skip to
and it *only* has the `todo/code` tag, you can probably safely skip to
the next section.
So you want to contribute code to Tails but do not know where to start
with. Our TODO list is huge and frightening, but...
So you want to contribute code to Tails but do not know where to
start? Our TODO list is huge and frightening, but...
*Do not panic!*
......@@ -73,7 +74,7 @@ Let's see how we can help you picking up a task. A few tips:
* Choose something that matters for you, such as fixing that bug that
annoys you so much or implementing this feature you are missing so
hard.
much.
* Choose something where your singular skills and knowledge are put to
work.
* Have a look to the [[easy tasks|todo/easy]] list: there is
......@@ -81,15 +82,16 @@ Let's see how we can help you picking up a task. A few tips:
it does not require deep knowledge of the Tails internals.
On the one hand, you may want to **start doing practical stuff
immediately**. In this case, see the tasks tagged `todo/code` on the
[[/TODO]] list. You probably want to start looking at the few ones
that are also in the [[easy tasks|todo/easy]] list first so that you
can gain confidence and we can smoothly learn to work together.
immediately**. In this case, see the tasks that are *only* tagged
`todo/code` on the [[/TODO]] list. You probably want to start looking
at the few ones that are also in the [[easy tasks|todo/easy]] list
first so that you can gain confidence and we can smoothly learn to
work together.
On the other hand, you may prefer **picking up a task that requires
some initial thought and discussion** before rushing to your
`$EDITOR`. In this case, you probably want to look at the [[providing
needed input|contribute/how/input]] guidelines.
needed input guidelines|contribute/how/input]].
## Get in touch with our past, present and future
......@@ -97,7 +99,7 @@ So you know what bug you want to fix, what feature you want to
implement.
Duplicated, unfinished or otherwise unusable work makes us sad, so
unless you are sure it is really trivial you should:
unless you are sure it is really easy you should:
1. **Gather results of previous research and discussions.** Search
this wiki and the [developers mailing-list
......@@ -105,10 +107,9 @@ unless you are sure it is really trivial you should:
discussions on the topic you are interested in;
[[some|todo/macchanger]] [[tasks|todo/usb_install_and_upgrade]] are
much harder to get right than one could initially expect, and you'd
better get you a taste of how hard what you want to implement
really is.
better see how difficult it is to implement what you want.
2. **[[Tell us|talk-dev]] about your plans.** This helps making sure
your idea fits nicely into the [[big picture|contribute/design]])
your idea fits nicely into the [[big picture|contribute/design]]
and nobody is currently working on the same task.
# Hack
......@@ -121,8 +122,8 @@ Please think of how you will actually submit your work to us
**before** you have changed 20 files for 10 different reasons ;) In
other words, every commit shall implement one change and be labelled
with a commit message that clearly expresses the rationale of your
changes. This is needed so that we are able to review your work
without too much pain: just explain every proposed change to us
changes. This is needed so that we can review your work
without too much difficulty: just explain every proposed change to us
(almost) the same way as if you would explain it to anyone who lacks
the background.
......@@ -139,7 +140,7 @@ For bigger, harder changes that will might require a few review/fix
cycles before being merged in, it's better if you ask us to review and
pull your work from a dedicated Git topic branch. If you already know
where to host your personal repository in a public online place, this
is great; else you may want to [fork us on
is great; or else you may want to [fork us on
repo.or.cz](http://repo.or.cz/w/tails.git).
FIXME: mob branch on repo.or.cz? mob repository where anyone can
......@@ -149,11 +150,11 @@ create and push `feature/*` and `bugfix/*` branches?
## Follow Tails development
Still here? Well, it seems you're not of the patch-in-a-hurry'n'forget
kind.
Still here? Well, it seems you're not the
*patch-in-a-hurry-and-then-forget* type.
You probably want to subscribe to the [tails-dev mailing
list](https://boum.org/mailman/listinfo/tails-dev/) then. Maybe even
Then you probably want to subscribe to the [tails-dev mailing
list](https://boum.org/mailman/listinfo/tails-dev/). Maybe even
subscribe to this website's RSS feed (see the [[recentchanges]] page)
and/or track the Git commits (using [[our Gitweb|git]]'s RSS
features). And probably read Tails [[specification and security design
......
......@@ -18,13 +18,12 @@ do let us know — ideally, by submitting a patch with your fix.
The easiest documentation tasks may be found by looking at the items
tagged `todo/documentation` on the [[/TODO]] list. Small fixes and
enhancements are greatly welcome, and can be done directly in this
wiki's web interface, by [[sending us|talk-dev]] Git patches, or by
publishing a [[Git]] branch.
enhancements are greatly welcome, and can be done either directly in
this wiki's web interface, by [[sending us|talk-dev]] Git patches, or
by publishing a [[Git]] branch.
But there is more: Tails [[end-user documentation|support]] needs lots
of work. A plan for end-user documentation reorganization was thought
through and sent to the [Tails development
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
......
[[!meta title="Help other Tails users"]]
Hanging our on [[our IRC channel|talk-dev]] and providing assistance
Hanging out on [[our IRC channel|talk-dev]] and providing assistance
to new users is incredibly valuable.
......@@ -8,7 +8,7 @@ to contribute to this effort.
who lack the technical skills needed to actually implement the desired
feature.
Tasks that are currently blocked by the need for input are listed in
Tasks that are currently stalled by the need for input are listed in
the *Research*, *Discuss* and *Test* sections of the [[/TODO]] list.
You probably want to start looking at the ones that are also in the
[[easy tasks list|todo/easy]] first so that you can gain confidence...
......
......@@ -46,8 +46,8 @@ HTTP
To efficiently help Tails users downloading it over HTTP, one needs to
have sufficiently privileged access to a web server with decent
bandwidth: a domestic DSL connection won't help, as won't a shared web
hosting setup that provides FTP access only.
bandwidth: a domestic DSL connection won't help; neither will a shared
web hosting setup that provides FTP access only.
This being said, if you satisfy these practical requirements, please
read on, you are most welcome aboard!
......
[[!meta title="Improve Tails for your language speakers"]]
[[!meta title="Improve Tails in your own language"]]
<div id="intro">
<p>So you want to make it easier to use Tails for your language
speakers. Welcome aboard! Please read-on.</p>
<p>So you want to make it easier to use Tails in your own language.
Welcome aboard! Please read-on.</p>
[[!toc levels=3]]
......@@ -24,7 +24,7 @@ The [[end-user documentation|support]] is being reorganized, please
coordinate with documentation writers before translating content that
may, or may not, evolve quickly: see [[contribute/how/documentation]].
## Other strings
## Other text to be translated
See the *Translate* section of the [[/TODO]] list.
......@@ -40,7 +40,7 @@ error-prone for more serious translation work.
Moreover, parts of Tails (most notably our custom programs) cannot be
translated using the web interface. We therefore recommend anyone
willing to seriously get involved into Tails translation work to use
more appropriate tools, such as a real PO file editor; see bellow for
more appropriate tools, such as a real PO file editor; see below for
details.
## PO editor
......@@ -87,19 +87,19 @@ while custom Tails programs live in the `devel` branch.
#### Ask us to pull from your Git branch
1. Setup [[Git repository|git]]: if you already know where to host
your personal Git repository in a public place, this is great; else
[fork us on repo.or.cz](http://repo.or.cz/w/tails.git).
your personal Git repository in a public place, this is great; or
else [fork us on repo.or.cz](http://repo.or.cz/w/tails.git).
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(es) you worked on.
5. [[Ask us|talk-dev]] to pull from the branch you worked on.
6. Frequently merge changes from our main repository into yours.
# Supported languages
Only a few languages are currently somehow supported in Tails, namely:
Arabic, Chinese, English, French, Italian, German, Portuguese, Russian
and Spanish (Castellano).
Currently, only a few languages are somewhat supported in Tails,
namely: Arabic, Chinese, English, French, Italian, German,
Portuguese and Spanish (Castellano).
Support for only a subset of these languages is enabled on this
website.
......@@ -110,7 +110,7 @@ Adding support for your preferred language is possible, but beware:
* useful translations are no one-shot job and need to be maintained on
the long run, which may take roughly two hours a month.
As a conclusion, forming a translators team dedicated to your
As a conclusion, forming a team of translators dedicated to your
language's support in Tails might be useful to make the maintenance
work happier and more sustainable.
......
......@@ -6,9 +6,10 @@
The Debian Derivatives Guidelines ([[!debwiki
Derivatives/Guidelines]]) encourages "derivative distributions to
mention and define their relationship with Debian". This seems like a
great idea to us, hence this document that generalizes it to Tails
relationship with its upstream projects.
mention and define their relationship with Debian". Because this seems
like a great idea to us, we wrote this statement that not only covers
Tails' relationship with Debian, but also Tails' relationship with any
one of its upstream projects.
# Summary
......
......@@ -6,21 +6,27 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2011-03-19 10:50-0600\n"
"PO-Revision-Date: 2010-11-02 21:14+0100\n"
"POT-Creation-Date: 2011-03-27 13:08+0300\n"
"PO-Revision-Date: 2011-03-27 13:09+0200\n"
"Last-Translator: FULL NAME <[email protected]>\n"
"Language-Team: LANGUAGE <[email protected]>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: ENCODING\n"
"Language: \n"
#. type: Content of: outside any tag (error?)
msgid ""
"[[!meta title=\"Talking in public with other Tails developers and users\"]] "
"If you want to talk <strong>in public</strong> with other Tails developpers "
"[[!meta title=\"Talking in public with other Tails developers and users\"]]"
msgstr ""
#. type: Content of: <p>
msgid ""
"If you want to talk <strong>in public</strong> with other Tails developers "
"and users:"
msgstr ""
"Si vous désirez parler <strong>publiquement</strong> avec d'autres\n"
"développeurs/euses ou utilisateurices de Tails :"
#. type: Content of: <ul><li>
msgid ""
......@@ -71,11 +77,5 @@ msgstr ""
"notre [[clé GnuPG|GnuPG key]] est le seul moyen que la communication soit\n"
"chiffrée du début à la fin."
#~ msgid "If you want to talk publicly to Tails developpers or users:"
#~ msgstr ""
#~ "Si vous désirez parler publiquement aux développeurs/euses ou "
#~ "utilisateurices\n"
#~ "Tails :"
#~ msgid "you may want to join our [[chatroom|chat]];"
#~ msgstr "vous pouvez rejoindre notre [[salon de discussion|chat]] ;"
[[!meta title="Talking in public with other Tails developers and users"]]
If you want to talk <strong>in public</strong> with other Tails developpers and users:
<p>If you want to talk <strong>in public</strong> with other Tails developers and users:</p>
<ul>
<li>
......
......@@ -6,17 +6,17 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2011-01-07 10:08-0800\n"
"PO-Revision-Date: 2010-11-01 20:10+0100\n"
"POT-Creation-Date: 2011-03-27 13:06+0300\n"
"PO-Revision-Date: 2011-03-27 13:07+0200\n"
"Last-Translator: FULL NAME <[email protected]>\n"
"Language-Team: LANGUAGE <[email protected]>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: ENCODING\n"
"Language: \n"
#. type: Content of: outside any tag (error?)
msgid "If you want to talk to Tails developpers or users:"
msgid "If you want to talk to Tails developers or users:"
msgstr ""
"Si vous désirez communiquer avec les développeurs/euses ou les\n"
"utilisateurices Tails :"
......
If you want to talk to Tails developpers or users:
If you want to talk to Tails developers or users:
<ul>
<li>
......
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