1 # SOME DESCRIPTIVE TITLE
2 # Copyright (C) YEAR Free Software Foundation, Inc.
3 # This file is distributed under the same license as the PACKAGE package.
4 # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
9 "Project-Id-Version: PACKAGE VERSION\n"
10 "POT-Creation-Date: 2013-08-10 21:09+0300\n"
11 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
12 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
13 "Language-Team: LANGUAGE <LL@li.org>\n"
16 "Content-Type: text/plain; charset=UTF-8\n"
17 "Content-Transfer-Encoding: 8bit\n"
21 msgid "[[!meta title=\"Tails 2013 summit report\"]]\n"
26 "A bunch of people spend a dozen days together in July at the third Tails "
27 "developers yearly summit. This was a great opportunity to have crazy hacking "
28 "sessions in person, as well as to discuss where we are heading to and how."
38 "We mainly discussed the **growth of the project**: given the growing number "
39 "of users and our super-short release cycle, it is a challenge to keep the "
40 "project sustainable and maintainable in the mid/long term."
46 "Our take on this is first reflected by [[!tails_roadmap desc=\"our\n"
47 "**updated roadmap**\"]]: we now have a better vision of what we want to\n"
48 "focus on for the next major releases of Tails: the 1.0, 1.1 and 2.0\n"
49 "milestones are now pretty well defined, and we even were bold enough\n"
50 "to draft goals for 3.0.\n"
55 "Another key aspect on this topic was that we need to **make it easier to "
56 "contribute** to Tails. We have listed many enhancements that could be made "
57 "in this direction, especially [on the website](https://labs.riseup.net/code/"
58 "projects/tails/issues?query_id=115). We also have identified areas that "
59 "could benefit most from a few new dedicated contributors. We will publish "
60 "targeted calls for help in the next few months."
65 "We also **redesigned our communication channels** to ease involvement of new "
66 "contributors, to make more workload sharing possible, and to be able to "
67 "provide better user support. In short:"
70 #. type: Bullet: ' * '
72 "Our mailing-lists see quite a lot of traffic these days. This might deter "
73 "people from reading it. So, we will create two specialized mailing-lists: a "
74 "private, encrypted one will receive bug reports, while a public one will be "
75 "dedicated to user support."
78 #. type: Bullet: ' * '
80 "A growing FAQ will be assembled: it will be a tool for self-service help, "
81 "and should make support work less repetitive."
84 #. type: Bullet: ' * '
86 "In a few months, we will evaluate how all this fares and we will reconsider "
87 "web support, which is postponed for the moment."
92 "Still, the tails-dev mailing-list remains the main communication channel for "
93 "development and project-wide discussions."
98 "This summit gave us the chance to **evaluate and refine processes** that we "
99 "have set up a year ago, such as our time-based release schedule and a formal "
105 "To end with, the **public development meetings** experiment will be "
106 "extended, and we will go on having monthly **Low Hanging Fruits sessions**. "
107 "Not only these sessions are very useful to make Tails better, but we were "
108 "happy to see new people join these parties recently. We hope to see even "
109 "more of that in the future: these sessions are great times to **start "
110 "contributing** to Tails!"
120 "Hours of meetings were certainly a necessary part of the summit, but we also "
121 "dedicated a fair share of our time to hands-on activities. Fortunately "
122 "there is quite a lot of room for improvements in Tails, so we were never "
128 "The most noticeable technical change that happened during the summit was "
129 "perhaps [our **move to Redmine**](https://labs.riseup.net/code/projects/"
130 "tails) for managing our [tasks](https://labs.riseup.net/code/projects/tails/"
131 "issues?query_id=108) and [[!tails_roadmap desc=\"plans\"]]. We are not "
132 "exploiting the full potential of Redmine yet, but it already feels far less "
133 "messy than how we did previously. Hopefully this will help others get "
134 "involved! Many thanks go to Riseup for hosting the Redmine instance we use. "
135 "Note that we will keep using ikiwiki for [[blueprints|blueprint]]."
140 "Taking advantage of Redmine, we have started classifying tasks in various "
141 "useful ways: e.g. [**easy tickets**](https://labs.riseup.net/code/projects/"
142 "tails/issues?query_id=112) do not require much knowledge of the Tails "
143 "internals to be solved, and are ideal places to get involved. In passing, "
144 "other nice custom queries provide lists of tasks involving [sysadmin]"
145 "(https://labs.riseup.net/code/projects/tails/issues?query_id=113) and [web "
146 "development](https://labs.riseup.net/code/projects/tails/issues?"
152 "We spent some time listing problems with early builds of **Tails based on "
153 "Debian Wheezy**. It is now clearer to us what remains to do: [a few dozens "
154 "tickets](https://labs.riseup.net/code/issues/6015) were created. Did we "
155 "mention that any kind of help is warmly welcome? :)"
160 "Our **Jenkins instance** also had been taken care of: it is getting closer "
161 "to something we can use and rely upon as part of our daily workflow."
166 "A lot of branches were **merged for the upcoming 0.20 release**, including "
167 "the installation of Dasher and a first step towards the replacement of "
173 "The **Pidgin and OTR documentation** was [rewritten](http://git.tails.boum."
174 "org/tails/tree/wiki/src/doc/anonymous_internet/pidgin.mdwn?h=doc/better-"
175 "pidgin-and-otr-documentation) to be clearer and more precise, as well as our "
176 "explanation of the way random nicknames are generated for Pidgin accounts."
181 "More steps have also been done towards **not starting Iceweasel** on startup."
186 msgid "At the end is the beginning"
191 "As you can guess, this summit was as intense as the previous ones. Tails is "
192 "living decisive times, so we expect the next year to be pretty interesting. "
193 "*You* can perhaps make the difference, so do not hesitate [[joining the "
194 "dance|contribute]]!"