On 30/07/13 14:14, intrigeri wrote:
> the next Tails developers meeting will take place on Thursday, August
> 8, on #tails-dev (OFTC) at 8pm UTC (10pm CEST). Every Tails
> contributor is welcome to attend.
Here is the report of what we did tonight.
Next low-hanging fruits session
===============================
Introduction
------------
Low-hanging fruits meeting: spend a while together on many small tasks
that take less than 2 hours each, and are waiting in our TODO list for
too long.
During these meetings, we exceptionally allow ourselves to do the
review & merge process on IRC instead of the usual email-based
workflow, so this should all go pretty smoothly. Then, we report back
on tails-dev.
We also use these meetings to review stuff that's waiting in
the queue.
Decisions
---------
The August low-hanging fruits session will take place on Thursday 15th
August 14:00 CEST. intrigeri will announce it.
Next shifts: WAN and RM
=======================
Introduction
------------
These are roles we take shifts for, and help us organize ourselves:
-
https://tails.boum.org/contribute/working_together/roles/release_manager/
-
https://tails.boum.org/contribute/working_together/roles/welcome_and_annoying_nitpicker/
Current situation:
- anonym is the RM for 0.20
- sajolida is acting as the WAN until August 28.
Decisions
---------
sajolida will ask bertagaz & alan if they want to be WAN after
August 28. Else, either he'll do it, or intrigeri will, or we'll do
without a WAN.
intrigeri will act as a RM for 0.20.1 scheduled on September 9th, and
0.21 2013-10-29, and 0.21.1 2013-12-11. He'll try to find people to
help me and share the work.
Have a consistent path to persistence root?
===========================================
https://labs.riseup.net/code/issues/5854
This looks like a one-line change inside tails-greeter, to name the
opened volume consistently. anonym will tackle it during the August
low-hanging fruits session, and if it's more complicated we'll
reconsider it.
Test suite: fs shares vs snapshots
==================================
https://labs.riseup.net/code/issues/5571
This is no practical issue right now, since we only use FS shares for
things that don't care about these bugs:
* MAT: should be moved to a dedicated feature anyway
* `usb_install`: doesn't use background snapshots
... but a limitation in what we can do in the future, when we want to
have libvirt fs shares work even when scenarios are using
a background snapshot.
1. reproduce the kernel bug with a recent kernel
2. report that kernel bug, because we are committing to behave this
way with our upstreams
3. ask on libvir-list or libvirt-users
4. close that ticket.
