Commit 89559d88 authored by Tails developers's avatar Tails developers
Browse files

Merge branch 'master' of ssh://webmasters.boum.org/~/wiki

parents 84ba4636 7eb4b0a9
......@@ -17,7 +17,7 @@ on Redmine.
# Other ideas
Nevertheless, if you are a web and/or graphics person, you can surely
Nevertheless, if you are a web or graphics person, you can surely
find other ideas to improve the Tails website! Even if you don't plan
to implement every suggested enhancement yourself, it may be worth
[creating
......
# SOME DESCRIPTIVE TITLE
# Copyright (C) YEAR Free Software Foundation, Inc.
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2013-08-09 08:37+0300\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. type: Plain text
#, no-wrap
msgid "[[!meta title=\"Tails 2013 summit report\"]]\n"
msgstr ""
#. type: Plain text
msgid ""
"A bunch of people spend a dozen days together in July at the third Tails "
"developers yearly summit. This was a great opportunity to have crazy hacking "
"sessions in person, as well as to discuss where we are heading to and how."
msgstr ""
#. type: Title #
#, no-wrap
msgid "Discussions"
msgstr ""
#. type: Plain text
msgid ""
"We mainly discussed the **growth of the project**: given the growing number "
"of users and our super-short release cycle, it is a challenge to keep the "
"project sustainable and maintainable in the mid/long term."
msgstr ""
#. type: Plain text
#, no-wrap
msgid ""
"Our take on this is first reflected by [[!tails_roadmap desc=\"our\n"
"**updated roadmap**\"]]: we now have a better vision of what we want to\n"
"focus on for the next major releases of Tails: the 1.0, 1.1 and 2.0\n"
"milestones are now pretty well defined, and we even were bold enough\n"
"to draft goals for 3.0.\n"
msgstr ""
#. type: Plain text
msgid ""
"Another key aspect on this topic was that we need to **make it easier to "
"contribute** to Tails. We have listed many enhancements that could be made "
"in this direction, especially [on the "
"website](https://labs.riseup.net/code/projects/tails/issues?query_id=115). "
"We also have identified areas that could benefit most from a few new "
"dedicated contributors. We will publish targeted calls for help in the next "
"few months."
msgstr ""
#. type: Plain text
msgid ""
"We also **redesigned our communication channels** to ease involvement of new "
"contributors, to make more workload sharing possible, and to be able to "
"provide better user support. In short:"
msgstr ""
#. type: Bullet: ' * '
msgid ""
"Our mailing-lists see quite a lot of traffic these days. This might deter "
"people from reading it. So, we will create two specialized mailing-lists: a "
"private, encrypted one will receive bug reports, while a public one will be "
"dedicated to user support."
msgstr ""
#. type: Bullet: ' * '
msgid ""
"A growing FAQ will be assembled: it will be a tool for self-service help, "
"and should make support work less repetitive."
msgstr ""
#. type: Bullet: ' * '
msgid ""
"In a few months, we will evaluate how all this fares and we will reconsider "
"web support, which is postponed for the moment."
msgstr ""
#. type: Plain text
msgid ""
"Still, the tails-dev mailing-list remains the main communication channel for "
"development and project-wide discussions."
msgstr ""
#. type: Plain text
msgid ""
"This summit gave us the chance to **evaluate and refine processes** that we "
"have set up a year ago, such as our time-based release schedule and a formal "
"merge policy."
msgstr ""
#. type: Plain text
msgid ""
"To end with, the **public development meetings** experiment will be "
"extended, and we will go on having monthly **Low Hanging Fruits "
"sessions**. Not only these sessions are very useful to make Tails better, "
"but we were happy to see new people join these parties recently. We hope to "
"see even more of that in the future: these sessions are great times to "
"**start contributing** to Tails!"
msgstr ""
#. type: Title #
#, no-wrap
msgid "Hack"
msgstr ""
#. type: Plain text
msgid ""
"Hours of meetings were certainly a necessary part of the summit, but we also "
"dedicated a fair share of our time to hands-on activities. Fortunately "
"there is quite a lot of room for improvements in Tails, so we were never "
"left unoccupied."
msgstr ""
#. type: Plain text
msgid ""
"The most noticeable technical change that happened during the summit was "
"perhaps [our **move to "
"Redmine**](https://labs.riseup.net/code/projects/tails) for managing our "
"[tasks](https://labs.riseup.net/code/projects/tails/issues?query_id=108) "
"and [[!tails_roadmap desc=\"plans\"]]. We are not exploiting the full "
"potential of Redmine yet, but it already feels far less messy than how we "
"did previously. Hopefully this will help others get involved! Many thanks go "
"to Riseup for hosting the Redmine instance we use. Note that we will keep "
"using ikiwiki for [[blueprints|blueprint]]."
msgstr ""
#. type: Plain text
msgid ""
"Taking advantage of Redmine, we have started classifying tasks in various "
"useful ways: e.g. [**easy "
"tickets**](https://labs.riseup.net/code/projects/tails/issues?query_id=112) "
"do not require much knowledge of the Tails internals to be solved, and are "
"ideal places to get involved. In passing, other nice custom queries provide "
"lists of tasks involving "
"[sysadmin](https://labs.riseup.net/code/projects/tails/issues?query_id=113) "
"and [web "
"development](https://labs.riseup.net/code/projects/tails/issues?query_id=115)."
msgstr ""
#. type: Plain text
msgid ""
"We spent some time listing problems with early builds of **Tails based on "
"Debian Wheezy**. It is now clearer to us what remains to do: [a few dozens "
"tickets](https://labs.riseup.net/code/issues/6015) were created. Did we "
"mention that any kind of help is warmly welcome? :)"
msgstr ""
#. type: Plain text
msgid ""
"Our **Jenkins instance** also had been taken care of: it is getting closer "
"to something we can use and rely upon as part of our daily workflow."
msgstr ""
#. type: Plain text
msgid ""
"A lot of branches were **merged for the upcoming 0.20 release**, including "
"the installation of Dasher and a first step towards the replacement of "
"TrueCrypt."
msgstr ""
#. type: Plain text
#, no-wrap
msgid ""
"The **Pidgin and OTR documentation** was [[!tails_devel_gitweb\n"
"wiki/src/doc/anonymous_internet/pidgin.mdwn desc=\"rewritten\"]] to be\n"
"clearer and more precise, as well as our explanation of the way random\n"
"nicknames are generated for Pidgin accounts.\n"
msgstr ""
#. type: Plain text
msgid ""
"More steps have also been done towards **not starting Iceweasel** on "
"startup."
msgstr ""
#. type: Title #
#, no-wrap
msgid "At the end is the beginning"
msgstr ""
#. type: Plain text
msgid ""
"As you can guess, this summit was as intense as the previous ones. Tails is "
"living decisive times, so we expect the next year to be pretty "
"interesting. *You* can perhaps make the difference, so do not hesitate "
"[[joining the dance|contribute]]!"
msgstr ""
# SOME DESCRIPTIVE TITLE
# Copyright (C) YEAR Free Software Foundation, Inc.
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2013-08-09 08:37+0300\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. type: Plain text
#, no-wrap
msgid "[[!meta title=\"Tails 2013 summit report\"]]\n"
msgstr ""
#. type: Plain text
msgid ""
"A bunch of people spend a dozen days together in July at the third Tails "
"developers yearly summit. This was a great opportunity to have crazy hacking "
"sessions in person, as well as to discuss where we are heading to and how."
msgstr ""
#. type: Title #
#, no-wrap
msgid "Discussions"
msgstr ""
#. type: Plain text
msgid ""
"We mainly discussed the **growth of the project**: given the growing number "
"of users and our super-short release cycle, it is a challenge to keep the "
"project sustainable and maintainable in the mid/long term."
msgstr ""
#. type: Plain text
#, no-wrap
msgid ""
"Our take on this is first reflected by [[!tails_roadmap desc=\"our\n"
"**updated roadmap**\"]]: we now have a better vision of what we want to\n"
"focus on for the next major releases of Tails: the 1.0, 1.1 and 2.0\n"
"milestones are now pretty well defined, and we even were bold enough\n"
"to draft goals for 3.0.\n"
msgstr ""
#. type: Plain text
msgid ""
"Another key aspect on this topic was that we need to **make it easier to "
"contribute** to Tails. We have listed many enhancements that could be made "
"in this direction, especially [on the "
"website](https://labs.riseup.net/code/projects/tails/issues?query_id=115). "
"We also have identified areas that could benefit most from a few new "
"dedicated contributors. We will publish targeted calls for help in the next "
"few months."
msgstr ""
#. type: Plain text
msgid ""
"We also **redesigned our communication channels** to ease involvement of new "
"contributors, to make more workload sharing possible, and to be able to "
"provide better user support. In short:"
msgstr ""
#. type: Bullet: ' * '
msgid ""
"Our mailing-lists see quite a lot of traffic these days. This might deter "
"people from reading it. So, we will create two specialized mailing-lists: a "
"private, encrypted one will receive bug reports, while a public one will be "
"dedicated to user support."
msgstr ""
#. type: Bullet: ' * '
msgid ""
"A growing FAQ will be assembled: it will be a tool for self-service help, "
"and should make support work less repetitive."
msgstr ""
#. type: Bullet: ' * '
msgid ""
"In a few months, we will evaluate how all this fares and we will reconsider "
"web support, which is postponed for the moment."
msgstr ""
#. type: Plain text
msgid ""
"Still, the tails-dev mailing-list remains the main communication channel for "
"development and project-wide discussions."
msgstr ""
#. type: Plain text
msgid ""
"This summit gave us the chance to **evaluate and refine processes** that we "
"have set up a year ago, such as our time-based release schedule and a formal "
"merge policy."
msgstr ""
#. type: Plain text
msgid ""
"To end with, the **public development meetings** experiment will be "
"extended, and we will go on having monthly **Low Hanging Fruits "
"sessions**. Not only these sessions are very useful to make Tails better, "
"but we were happy to see new people join these parties recently. We hope to "
"see even more of that in the future: these sessions are great times to "
"**start contributing** to Tails!"
msgstr ""
#. type: Title #
#, no-wrap
msgid "Hack"
msgstr ""
#. type: Plain text
msgid ""
"Hours of meetings were certainly a necessary part of the summit, but we also "
"dedicated a fair share of our time to hands-on activities. Fortunately "
"there is quite a lot of room for improvements in Tails, so we were never "
"left unoccupied."
msgstr ""
#. type: Plain text
msgid ""
"The most noticeable technical change that happened during the summit was "
"perhaps [our **move to "
"Redmine**](https://labs.riseup.net/code/projects/tails) for managing our "
"[tasks](https://labs.riseup.net/code/projects/tails/issues?query_id=108) "
"and [[!tails_roadmap desc=\"plans\"]]. We are not exploiting the full "
"potential of Redmine yet, but it already feels far less messy than how we "
"did previously. Hopefully this will help others get involved! Many thanks go "
"to Riseup for hosting the Redmine instance we use. Note that we will keep "
"using ikiwiki for [[blueprints|blueprint]]."
msgstr ""
#. type: Plain text
msgid ""
"Taking advantage of Redmine, we have started classifying tasks in various "
"useful ways: e.g. [**easy "
"tickets**](https://labs.riseup.net/code/projects/tails/issues?query_id=112) "
"do not require much knowledge of the Tails internals to be solved, and are "
"ideal places to get involved. In passing, other nice custom queries provide "
"lists of tasks involving "
"[sysadmin](https://labs.riseup.net/code/projects/tails/issues?query_id=113) "
"and [web "
"development](https://labs.riseup.net/code/projects/tails/issues?query_id=115)."
msgstr ""
#. type: Plain text
msgid ""
"We spent some time listing problems with early builds of **Tails based on "
"Debian Wheezy**. It is now clearer to us what remains to do: [a few dozens "
"tickets](https://labs.riseup.net/code/issues/6015) were created. Did we "
"mention that any kind of help is warmly welcome? :)"
msgstr ""
#. type: Plain text
msgid ""
"Our **Jenkins instance** also had been taken care of: it is getting closer "
"to something we can use and rely upon as part of our daily workflow."
msgstr ""
#. type: Plain text
msgid ""
"A lot of branches were **merged for the upcoming 0.20 release**, including "
"the installation of Dasher and a first step towards the replacement of "
"TrueCrypt."
msgstr ""
#. type: Plain text
#, no-wrap
msgid ""
"The **Pidgin and OTR documentation** was [[!tails_devel_gitweb\n"
"wiki/src/doc/anonymous_internet/pidgin.mdwn desc=\"rewritten\"]] to be\n"
"clearer and more precise, as well as our explanation of the way random\n"
"nicknames are generated for Pidgin accounts.\n"
msgstr ""
#. type: Plain text
msgid ""
"More steps have also been done towards **not starting Iceweasel** on "
"startup."
msgstr ""
#. type: Title #
#, no-wrap
msgid "At the end is the beginning"
msgstr ""
#. type: Plain text
msgid ""
"As you can guess, this summit was as intense as the previous ones. Tails is "
"living decisive times, so we expect the next year to be pretty "
"interesting. *You* can perhaps make the difference, so do not hesitate "
"[[joining the dance|contribute]]!"
msgstr ""
# SOME DESCRIPTIVE TITLE
# Copyright (C) YEAR Free Software Foundation, Inc.
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2013-08-09 08:37+0300\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. type: Plain text
#, no-wrap
msgid "[[!meta title=\"Tails 2013 summit report\"]]\n"
msgstr ""
#. type: Plain text
msgid ""
"A bunch of people spend a dozen days together in July at the third Tails "
"developers yearly summit. This was a great opportunity to have crazy hacking "
"sessions in person, as well as to discuss where we are heading to and how."
msgstr ""
#. type: Title #
#, no-wrap
msgid "Discussions"
msgstr ""
#. type: Plain text
msgid ""
"We mainly discussed the **growth of the project**: given the growing number "
"of users and our super-short release cycle, it is a challenge to keep the "
"project sustainable and maintainable in the mid/long term."
msgstr ""
#. type: Plain text
#, no-wrap
msgid ""
"Our take on this is first reflected by [[!tails_roadmap desc=\"our\n"
"**updated roadmap**\"]]: we now have a better vision of what we want to\n"
"focus on for the next major releases of Tails: the 1.0, 1.1 and 2.0\n"
"milestones are now pretty well defined, and we even were bold enough\n"
"to draft goals for 3.0.\n"
msgstr ""
#. type: Plain text
msgid ""
"Another key aspect on this topic was that we need to **make it easier to "
"contribute** to Tails. We have listed many enhancements that could be made "
"in this direction, especially [on the "
"website](https://labs.riseup.net/code/projects/tails/issues?query_id=115). "
"We also have identified areas that could benefit most from a few new "
"dedicated contributors. We will publish targeted calls for help in the next "
"few months."
msgstr ""
#. type: Plain text
msgid ""
"We also **redesigned our communication channels** to ease involvement of new "
"contributors, to make more workload sharing possible, and to be able to "
"provide better user support. In short:"
msgstr ""
#. type: Bullet: ' * '
msgid ""
"Our mailing-lists see quite a lot of traffic these days. This might deter "
"people from reading it. So, we will create two specialized mailing-lists: a "
"private, encrypted one will receive bug reports, while a public one will be "
"dedicated to user support."
msgstr ""
#. type: Bullet: ' * '
msgid ""
"A growing FAQ will be assembled: it will be a tool for self-service help, "
"and should make support work less repetitive."
msgstr ""
#. type: Bullet: ' * '
msgid ""
"In a few months, we will evaluate how all this fares and we will reconsider "
"web support, which is postponed for the moment."
msgstr ""
#. type: Plain text
msgid ""
"Still, the tails-dev mailing-list remains the main communication channel for "
"development and project-wide discussions."
msgstr ""
#. type: Plain text
msgid ""
"This summit gave us the chance to **evaluate and refine processes** that we "
"have set up a year ago, such as our time-based release schedule and a formal "
"merge policy."
msgstr ""
#. type: Plain text
msgid ""
"To end with, the **public development meetings** experiment will be "
"extended, and we will go on having monthly **Low Hanging Fruits "
"sessions**. Not only these sessions are very useful to make Tails better, "
"but we were happy to see new people join these parties recently. We hope to "
"see even more of that in the future: these sessions are great times to "
"**start contributing** to Tails!"
msgstr ""
#. type: Title #
#, no-wrap
msgid "Hack"
msgstr ""
#. type: Plain text
msgid ""
"Hours of meetings were certainly a necessary part of the summit, but we also "
"dedicated a fair share of our time to hands-on activities. Fortunately "
"there is quite a lot of room for improvements in Tails, so we were never "
"left unoccupied."
msgstr ""
#. type: Plain text
msgid ""
"The most noticeable technical change that happened during the summit was "
"perhaps [our **move to "
"Redmine**](https://labs.riseup.net/code/projects/tails) for managing our "
"[tasks](https://labs.riseup.net/code/projects/tails/issues?query_id=108) "
"and [[!tails_roadmap desc=\"plans\"]]. We are not exploiting the full "
"potential of Redmine yet, but it already feels far less messy than how we "
"did previously. Hopefully this will help others get involved! Many thanks go "
"to Riseup for hosting the Redmine instance we use. Note that we will keep "
"using ikiwiki for [[blueprints|blueprint]]."
msgstr ""
#. type: Plain text
msgid ""
"Taking advantage of Redmine, we have started classifying tasks in various "
"useful ways: e.g. [**easy "
"tickets**](https://labs.riseup.net/code/projects/tails/issues?query_id=112) "
"do not require much knowledge of the Tails internals to be solved, and are "
"ideal places to get involved. In passing, other nice custom queries provide "
"lists of tasks involving "
"[sysadmin](https://labs.riseup.net/code/projects/tails/issues?query_id=113) "
"and [web "
"development](https://labs.riseup.net/code/projects/tails/issues?query_id=115)."
msgstr ""
#. type: Plain text
msgid ""
"We spent some time listing problems with early builds of **Tails based on "
"Debian Wheezy**. It is now clearer to us what remains to do: [a few dozens "
"tickets](https://labs.riseup.net/code/issues/6015) were created. Did we "
"mention that any kind of help is warmly welcome? :)"
msgstr ""
#. type: Plain text
msgid ""
"Our **Jenkins instance** also had been taken care of: it is getting closer "
"to something we can use and rely upon as part of our daily workflow."
msgstr ""
#. type: Plain text
msgid ""
"A lot of branches were **merged for the upcoming 0.20 release**, including "
"the installation of Dasher and a first step towards the replacement of "
"TrueCrypt."
msgstr ""
#. type: Plain text
#, no-wrap
msgid ""
"The **Pidgin and OTR documentation** was [[!tails_devel_gitweb\n"
"wiki/src/doc/anonymous_internet/pidgin.mdwn desc=\"rewritten\"]] to be\n"
"clearer and more precise, as well as our explanation of the way random\n"
"nicknames are generated for Pidgin accounts.\n"
msgstr ""
#. type: Plain text
msgid ""
"More steps have also been done towards **not starting Iceweasel** on "
"startup."
msgstr ""
#. type: Title #
#, no-wrap
msgid "At the end is the beginning"
msgstr ""
#. type: Plain text
msgid ""
"As you can guess, this summit was as intense as the previous ones. Tails is "
"living decisive times, so we expect the next year to be pretty "
"interesting. *You* can perhaps make the difference, so do not hesitate "
"[[joining the dance|contribute]]!"
msgstr ""
[[!meta title="Tails 2013 summit report"]]
A bunch of people spend a dozen days together in July at the third
Tails developers yearly summit. This was a great opportunity to have
crazy hacking sessions in person, as well as to discuss where we are
heading to and how.
# Discussions
We mainly discussed the **growth of the project**: given the growing
number of users and our super-short release cycle, it is a challenge
to keep the project sustainable and maintainable in the mid/long term.
Our take on this is first reflected by [[!tails_roadmap desc="our
**updated roadmap**"]]: we now have a better vision of what we want to
focus on for the next major releases of Tails: the 1.0, 1.1 and 2.0
milestones are now pretty well defined, and we even were bold enough
to draft goals for 3.0.
Another key aspect on this topic was that we need to **make it easier
to contribute** to Tails. We have listed many enhancements that could
be made in this direction, especially [on the
website](https://labs.riseup.net/code/projects/tails/issues?query_id=115).
We also have identified areas that could benefit most from a few new
dedicated contributors. We will publish targeted calls for help in the
next few months.
We also **redesigned our communication channels** to ease involvement
of new contributors, to make more workload sharing possible, and to be
able to provide better user support. In short:
* Our mailing-lists see quite a lot of traffic these days.
This might deter people from reading it. So, we will create two
specialized mailing-lists: a private, encrypted one will receive
bug reports, while a public one will be dedicated to user support.