1 [[!meta title="October 2013 online meeting"]]
6 1. Decide if we care about the Pidgin CTCP replies
7 https://labs.riseup.net/code/issues/6283
8 2. Decide on throw keyids
9 https://labs.riseup.net/code/issues/6152
10 3. Test suite: retry when tor fails
11 https://labs.riseup.net/code/issues/5770
13 5. Monthly low-hanging fruits meeting?
15 Decide if we care about the Pidgin CTCP replies
16 -----------------------------------------------
20 * https://labs.riseup.net/code/issues/6283
21 * Parent ticket https://labs.riseup.net/code/issues/5823
23 Pidgin responds to PING returning a time duration and VERSION returning
28 We decided none of those answers to CTCP commands are disclosing much
29 and thus are no big deal for the moment. Tickets are now closed.
32 Decide on throw keyids
33 ----------------------
37 * https://labs.riseup.net/code/issues/6152
38 * Parent ticket https://labs.riseup.net/code/issues/6153
40 --throw-keyids is a GnuPG option that hides the receiver of the encrypted
41 data as a countermeasure against traffic analysis.
42 While working on getting Icedove back to Tails, enabling that
43 option by default, or not, is to discuss.
47 At the monthly meeting, there was a consensus that while --throw-keyids
48 may be useful sometimes, enabling it by default makes OpenPGP even more
49 a usability mess than it already is. Even its most verbose proponents
50 (Torbirdy) stopped enabling it by default recently. So, we won't use this
51 option in Tails. Closing tickets.
54 Test suite: retry when tor fails
55 --------------------------------
59 https://labs.riseup.net/code/issues/5770
61 Some scenarios uses the live Tor network, which is not entirely reliable,
62 so we may get failing scenarios when in fact we just happened to pick a
63 Tor circuit that's too slow, or even one that's broken but Tor fails to
68 Our plate is full enough, let's not try to fix problems we have never
69 seen in the wild. If the need arises in the wild, we'll reopen.
70 In the meantime, let's focus on problems we can experience more widely.
79 Our "broken windows" (https://tails.boum.org/contribute/roadmap/,
80 sorry for the crappy reference) are tasks or issues that, ideally,
81 should have been resolved a while ago, and seeing them still causing
82 problems is demotivating.
84 We try to spend a week focusing on broken windows each month.
85 Recently, most core contributors have been focusing on broken windows
86 all the time, so we skipped them in practice.
88 However, if new contributors want to play with us, it may make sense
89 to revive these specific times.
93 Our schedule are full enough, we're already focusing on high-priority stuff,
94 so we won't be focusing on BW.
96 Monthly low-hanging fruits meeting?
97 -----------------------------------
101 Low-hanging fruits meeting: spend a while together on many small tasks
102 that take less than 2 hours each, and are waiting in our TODO list for
105 During these meetings, we exceptionally allow ourselves to do the
106 review & merge process on IRC instead of the usual email -based
107 workflow, so this should all go pretty smoothly. Then, we report back
110 We also use these meetings to review stuff that's waiting in
115 We'll have two low-hanging fruits meetings in October:
117 - Saturday 12 at 6pm CEST
118 - Tuesday 15 at 6pm CEST