Commit e7678995 authored by intrigeri's avatar intrigeri
Browse files

Merge branch 'master' of webmasters.boum.org:wiki

parents 18f7820b d1da3ca1
......@@ -10,7 +10,7 @@ Releases
* [[Tails 1.2.3 was released on January 15, 2015.|news/version_1.2.3]] (minor release)
* [[Tails 1.3 was released on February 24, 2015.|news/version_1.3]] (major release)
* The next release (1.3.1) is [[planned for the 7th of April|contribute/calendar]].
* The next release (1.3.1) is [[planned for April 7|contribute/calendar]].
Code
====
......@@ -21,8 +21,6 @@ The complete list of improvements is in the release announcements. Some major po
* Tails now ships the <span class="application">Electrum</span> Bitcoin client.
* Support obfs4 Tor bridges.
You can also contribute, see our call for help: [[Help have a Windows camouflage in Tails Jessie!|news/windows_camouflage_jessie]]
Documentation and website
=========================
......@@ -31,8 +29,6 @@ Documentation and website
- We explained the risks of [[accessing internal
hard disks|doc/encryption_and_privacy/your_data_wont_be_saved_unless_explicitly_asked#access_hdd]] from Tails.
- We documented how to [[empty the trash of the persistent volume|doc/encryption_and_privacy/secure_deletion#index4h1]].
- ... and plenty of small improvements everywhere :)
User experience
......@@ -56,14 +52,14 @@ User experience
Infrastructure
==============
* Our test suite covers 172 scenarios, 85 (!) more than in July 2014. That's a huge improvement because each release can be automatically tested to avoid regressions instead of having to manually perform the same tests each time. There is still some way to go, but someday releasing will be fast, safe and easy :)
* Our test suite covers 172 scenarios, 85 (!) more than in July 2014. That's a huge improvement because each release can be automatically tested to avoid regressions instead of having to manually perform the same tests each time. There is still some way to go, but someday releasing will be fast, safe, and easy :)
* Tails ships a new certificate in 1.2.3, and a new signing key in 1.3.
* We rewrote the history of our main Git repository to make it four times smaller.
This should make the new contributors' experience much nicer.
* We upgraded the hardware of our main server so that it can handle the short and mid-term plans we have for it: [[!tails_ticket 6196 desc="automatically building ISO images from all active branches"]]), and then [[!tails_ticket 5288 desc="running our automated test suite on these ISO images"]].
* We upgraded the hardware of our main server so that it can handle the short and mid-term plans we have for it: [[!tails_ticket 6196 desc="automatically building ISO images from all active branches"]], and then [[!tails_ticket 5288 desc="running our automated test suite on these ISO images"]].
Funding
=======
......@@ -75,18 +71,22 @@ Funding
Outreach
========
* We passed a call for [[help to have a Windows camouflage in Tails Jessie|news/windows_camouflage_jessie]]!
* Tails now has a [[code of conduct|contribute/working_together/code_of_conduct]]!
* Some Tails developers attended [FOSDEM](https://fosdem.org/2015/) in Brussels, saw some interesting talks and I hear the Belgian beer was good.
* Two of us attended [FOSDEM](https://fosdem.org/2015/) in Brussels, saw some interesting talks and I hear the Belgian beer was good.
* A Tails developer gave a talk at the Sapienza University of Rome, Italy ([slides](https://tails.boum.org/contribute/how/promote/material/slides/Roma-Uni_Sapienza-20150127/Tails.shtml)). Thanks a lot to the local organizers!
* One of us gave a talk at the Sapienza University of Rome, Italy ([slides](https://tails.boum.org/contribute/how/promote/material/slides/Roma-Uni_Sapienza-20150127/Tails.shtml)). Thanks a lot to the local organizers!
On-going discussions
====================
* [[We did not reach an agreement yet|https://mailman.boum.org/pipermail/tails-dev/2015-January/007821.html]] about [[!tails_ticket 8665 desc="removing Adblock Plus"]] (to have a fingerprint closer to the Tor Browser Bundle's one) or keeping it (because it's more comfortable for users).
* People try to come up with the best ideas for [[Tor Monitor|http://git.tails.boum.org/alan/tor-monitor]], a [[!tails_ticket 6841 desc="replacement for Vidalia"]] in Tails/Jessie. This is [[discussed on tails-dev|https://mailman.boum.org/pipermail/tails-dev/2015-February/thread.html#8038]].
* People try to come up with the best ideas for [[Tor Monitor|http://git.tails.boum.org/alan/tor-monitor]], a [[!tails_ticket 6841 desc="replacement for Vidalia"]] in Tails Jessie. This is [[discussed on tails-dev|https://mailman.boum.org/pipermail/tails-dev/2015-February/thread.html#8038]].
* What kind of [verification mechanism](https://mailman.boum.org/pipermail/tails-dev/2015-February/008059.html) shall we do in the future [[ISO verification extension|blueprint/bootstrapping/extension]].
Press & Testimonials
====================
......@@ -106,7 +106,7 @@ Translation and internationalization
* The Spanish and Italian translation teams are still at the organizing stages so their translations have not started yet.
* For all those languages (and other ones!), [[new translators are really welcome!|contribute/how/translate/]]
* For all those languages (and other ones!), [[new translators are really welcome|contribute/how/translate/]]!
All website PO files
--------------------
......
......@@ -18,3 +18,5 @@ The goals are to:
* Enjoy doing non-urgent things and have some fun together.
* Get a lot of small improvements into the next Tails release.
* Cleanup our todo list a bit.
* Try to handle bug fixes for the next release that are not assigned to
anybody.
[[!meta title="March 2015 online meeting"]]
[[!toc levels=1]]
# Volunteers to handle "[Hole in the roof](https://labs.riseup.net/code/versions/198)" tickets this month
intrigeri started with [[!tails_ticket 6840]].
anonym will also look into it also into [[!tails_ticket 7546]].
We agreed to drop [[!tails_ticket 5985]] from the "holes in the roof" list and noted,
that [[!tails_ticket 5318]] should be taken care of when the Greeter is rewritten ([[!tails_ticket 8230]]).
# Availability and plans for monthly low-hanging fruits meeting
At least 5 people would like to attend.
# [[!tails_ticket 8586 desc="Create a directory of organizations doing Tails training"]]
We agreed that the Tails homepage should contain such a list,
under the following conditions:
* We note that the list is not exhaustive.
* We keep in touch with the organizations listed and for each organization
we need someone committed to update the page.
* We make the target audience clear and get the agreement of the org before adding them.
This is important to make sure, that organizations aren't overrun by interested parties.
* We try not to duplicate work of other organizations.
intrigeri can create such a page one of these month. BitingBird might also be interested.
# [[!tails_ticket 7400 desc="Don't start Vidalia in Windows 8 camouflage?"]]
We agreed to make this a low priority wishlist ticket.
The ticket is also related to [[!tails_ticket 9002]] about a green onion feature
in post-Vidalia Tails.
# [[!tails_ticket 8873 desc="Decide which kind of verification would the ISO verification extension do"]]
We decided that the problem space of this ticket is not appropriate for a monthly meeting.
Instead please read the [blueprint](https://tails.boum.org/blueprint/bootstrapping/extension/#verification)
and comment on the [mailing list thread](https://mailman.boum.org/pipermail/tails-dev/2015-March/008333.html).
# Important tickets with milestone, but without assignee, see the [mailing-list](https://mailman.boum.org/pipermail/tails-dev/2015-February/008239.html)
The questions is: How do we handle unexpected and high-priority tasks, when all the people who usually do this are already overwhelmed?
We decide to discuss these tasks in the monthly meetings similar to the way
holes-in-the-roof are already handled. These tickets can also be prioritized at
low-hanging fruits meetings.
sajolida will take care of updating the meetings template,
To be better prepared for such emergency events we should, in the future,
also budget time for bug fixing when fundraising.
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