None

Source string added

  1. Tails
  2. wiki/src/news/summit_2013.*.po
  3. English
Taking advantage of Redmine, we have started classifying tasks in various useful ways: e.g. **easy tickets** 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. and web development.
2 weeks ago
None

Source string added

  1. Tails
  2. wiki/src/news/summit_2013.*.po
  3. English
The most noticeable technical change that happened during the summit was perhaps our **move to Redmine** for managing our tasks and 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.
2 weeks ago
None

Source string added

  1. Tails
  2. wiki/src/news/summit_2013.*.po
  3. English
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. 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.
2 weeks ago
None

Source string added

  1. Tails
  2. wiki/src/news/summit_2013.*.po
  3. English
Our take on this is first reflected by 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.
8 months ago
None

Source string added

  1. Tails
  2. wiki/src/news/summit_2013.*.po
  3. English
The **Pidgin and OTR documentation** was rewritten to be clearer and more precise, as well as our explanation of the way random nicknames are generated for Pidgin accounts.
2 years ago

Search