[Tails-dev] [review'n'merge] March contributors meeting notes

[segfault]

Hi, here are the notes of today's meeting. Please review and merge.
Cheers!
>From 835a9183ed777d727db35afaaa2489a796466a12 Mon Sep 17 00:00:00 2001
From: segfault 
Date: Fri, 3 Mar 2017 22:35:00 +
Subject: [PATCH 1/1] March contributos meeting notes

---
 wiki/src/contribute/meetings/201703.mdwn | 58 
 1 file changed, 58 insertions(+)
 create mode 100644 wiki/src/contribute/meetings/201703.mdwn

diff --git a/wiki/src/contribute/meetings/201703.mdwn b/wiki/src/contribute/meetings/201703.mdwn
new file mode 100644
index 00..c2073af46d
--- /dev/null
+++ b/wiki/src/contribute/meetings/201703.mdwn
@@ -0,0 +1,58 @@
+[[!meta title="March 2017 online meeting"]]
+
+[[!toc levels=1]]
+
+
+# Hole in the roof
+
+intrigeri will work on [[!tails_ticket 8449 desc="Tails Upgrader fails to install some IUKs"]] and the related [[!tails_ticket 11839 desc="After automatic upgrade from Tails 2.5 to 2.6, keyboard and mouse stop working"]].
+emmapeel will see if she can take care of [[!tails_ticket 5597 desc="obfsproxy design documentation"]].
+
+
+# Volunteers to handle important tickets flagged for next release, but without assignee
+
+All the tickets for Tails 2.12 were already assigned!
+
+
+# Availability
+
+* emmapeel will be in Valencia with sajolida... plans to warm up to some funders, localisation lab, guardian project people. also pushing for the spanish translation of course
+* intrigeri: plans: mostly reproducible builds sprint, Stretch sprint, Tor dev meeting. maybe start working on my keynote for cryptorave. and smaller 2.x Foundations Team stuff like tor and Linux upgrades. availability: mostly available for Tails but mostly busy with my commitments.
+* spriver: I'll work on #12260 and #5323. and doc updates for 3.0 during the Stretch sprint. availability: medium for Tails, mostly at weekends
+* segfault: I plan to work on the Tails Server beta release, but I'm very busy with other stuff, so I'm not sure how much I will be able to work on this. Availablility will be low.
+
+
+# Important missing bits in the next monthly report
+
+Report not written yet. Emmapeel will do it or mentor someone new until the 12th.
+
+
+# Discussions
+
+## [[!tails_ticket 6972 desc="Create a \"Sponsors\" page"]]
+
+We agreed on listing sponsors by year, and adding the ones for 2016. We postponed the discussion about 2015 and before, and the "when do we clean the 2016 section" topic too. There were no volunteers for this, thus the assignment falls to the fundraising team.
+
+
+##[[!tails_ticket 12076 desc="Have a sponsor per release"]]
+
+We discussed the concerns about this. Some of us have the feeling this might hurt the public image of the project, making it look cheap or more dependent from sponsors than previously conceived. On the other hand, we acknowledge that the release funding would actually be unrestricted funding, in contrast to other funding which is sometimes only for a specific purpose. It was noted that we need more funding in general and that we would like to have more unrestricted funding. We agreed that we would be ok with this if we make it clear what exactly the sponsor paid for (and what they didn't).
+
+
+## [[!tails_ticket 11882 desc="Consider disabling recent usage and history in privacy settings by default"]]
+
+We agreed that we are not convinced the proposed patch would be a security improvement. Intrigeri will write a comment on the ticket asking for clarification and explaining our thoughts.
+
+
+## [[!tails_ticket 12104 desc="Decide whether we can drop DKMS modules support"]]
+
+We acknowledge that losing clipboard sharing is an important UX hit for VirtualBox user. Whether that's a good enough reason to 1. spend tons of time maintaining the DKMS thing; 2. making grsec much harder to get in Tails; was not something we could make up our mind firmly about. But we were leaning towards 'no' as an answer.
+
+
+## [[!tails_ticket 9003 desc="Cleanup outdated blueprints"]]
+
+We agreed to move the old blueprints to an archive page.
+
+## Other tickets
+We postponed the discussions of [[!tails_ticket 9900 desc="Improve Website search"]] and [[!tails_ticket 12214 desc="Consider documenting a way to manually backup persistent data"]]. cbrownstein noted that they would like to work on [[!tails_ticket 12214 desc="Consider documenting a way to manually backup persistent data"]].
+
-- 
2.11.0

___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] [Tails-testers] Request for JavaFX on Tails 3.0

[Collin Sullivan]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello hello,

>>> I'll assume that the package Martus needs is either 
>>> libopenjfx-java or libopenjfx-jni.

When I tested this, it appeared that both were required for openjfx to
run. Marking either for removal also marked openjfx for removal.


> OK, please let us know once you have the exact list of dependencies
> missing in Tails.

I've managed to get Martus up and running after installing via Synaptic:

+ openjfx
+ libopenjfx-java
+ libopenjfx-jni

And nothing else.


> I suggest you look into this using a Tails experimental ISO based 
> on Debian Stretch:
> 
> https://nightly.tails.boum.org/build_Tails_ISO_feature-stretch/lastSuc
cessful/archive/build-artifacts/

Ah,
>
> 
thanks. I missed this and was testing with the vanilla Tails 3.0
beta 1, and was able to get Martus to run and do all of the important
things (create records, connect and backup to the server, perform
searches, etc.). Let me know if you think it worth testing with
nightly, too.


>> 2) I could look again, but the libraries we need (I think) were 
>> not available in the Tails default repositories, so we needed to 
>> add new ones. That's another step for the user.
> 
> I expect this might have been fixed with Tails 2.x, or will be in 
> 3.x. But you may want to double-check :)

I did have to add the stretch tester repository to Synaptic, as I did
not find any of those libraries in the included/default repos.


>> 3) The less our partners/users need to use root / su / sudo, the
>>  better. Both for security and ease of use.
> 
> Absolutely, especially if command line is involved. This drawback 
> will be alleviated once there's a GUI to configure additional 
> software (I'm pretty sure it'll still require an administration 
> password for the initial setup, but at least there will be fewer 
> steps that require command line usage, and they will be required
> by your custom stuff rather than by Tails limitations).

Cool. I'm also imagining that, if Tails were to ship with Martus,
Martus might be included as part of the Persistence setup itself -- at
the step where the user chooses which applications to configure to
save to persistence (keyrings, Pidgin contacts, printers, etc etc
etc), they could also select Martus.

One intangible of having Martus ship with Tails is that it sort of
gets the Tails Seal of Approval. Tails is known to take its security
and privacy seriously, and I've observed people making the assumption
that, if something is included in Tails, it's as if the devs are
recommending it, so they trust it a bit more. Coaching users on how to
add non-Tails software to Tails is a bit risky (lest they add other,
non-recommended applications), and removes a bit of that sheen, as it
were.

Anyway, a bit of positive movement on the testing side, and it sounds
like some of the Tails team will be at IFF next week. Happy to talk
more about this stuff there!

Cheers,
Collin



- -- 
Collin Sullivan
Human Rights Outreach Associate
Benetech Human Rights Program

Email: colli...@benetech.org
GPG: 0x35F83A6678657D4D
XMPP: collin.sulli...@riseup.net
OTR: A0946621 68E641FA 4DFBF9F0 10B20AA9 88601348
11C7957D 5A99DAF7 1D0DD4BC EE243287 943AD67A

Twitter: @MartusProject

https://www.benetech.org - Technology Serving Humanity
https://www.martus.org - Martus Human Rights Bulletin System
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0

iQIcBAEBCAAGBQJYub8pAAoJEN3b1xdSAv8hwZ0P/Rlbp+W/z09FFIU2PPyHVWU6
f1+u4Kg0x/M1YQQPM5hFrhKCQjC9zBzZpnngdba7x+x+EHXElPl6uEq4Epm8Ltu2
5EKytDy6J4MV4AuJcKnCx4Pfu/7jIKrrmO6N/bL+lJNA3Jl/eHGc6BI5cimAIMIl
iLx3jvaP78CbKr7fN+vWfI6jeVpwxcv+NYvp+rJjv5sBk8OoufoMaZ9DM/7cvOCJ
diWGoHISXNtoG9GWGzxVPG1/HTS0xI5K0Pjhsbxl7k2+y1d3YXXJ9LwWUFCcHrNb
wndzmZycgbYiHNABaXvHJ+hoCEAkwqA4Y87ntcSxcUvMw14425Q9YX0VYucgGVY4
etPaSNs8qk/ZYbjNYPHbrlaw5jRUvbJ/Dxy7UbqjZJmmJHHwdJWKzPkuyjnfUDhh
UxuiSjqbNQPAsqKfKXgWSe856fl8J3N6TywwqJAjmNdPXHtdbslWc/9msvi+sBer
3hD7eqee2jM1M9i8oAuWe4bDPWRy9YUddufiMYAu4oQYQXQsLESd9b4hJCMzwc1V
wMxR/thTtkFmIqvyOM2oY5Sq+ge9M4k+rLyNJKaphvqc/5Mcx4NW0UP62TRS3u4/
48yJr294Rdn4Ss8/zqqJbUzkSlELFla7h8tU7Cm/p9uy6wuwEVQPj62mszhMEdL1
lZir1k2WbY5DxIZagzEp
=e8Pi
-END PGP SIGNATURE-
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

[Tails-dev] Tor Browser 6.5.1 is ready for testing

[Georg Koppen]

Hi!

We are happy to accounce that Tor Browser 6.5.1 is ready for testing.
Bundles can be found on:

https://people.torproject.org/~gk/builds/6.5.1-build2/

This is the first minor release in the 6.5 series and it mainly contains
updates to several of our Tor Browser components: Firefox got updated to
45.8.0esr, Tor to 0.2.9.10, OpenSSL to 1.0.1k, and HTTPS-Everywhere to
5.2.11.

The update to 45.8.0esr made it necessary to rewrite the backported
Mozilla patch that hardened the JavaScript JIT by enforcing W^X on all
pages. Please test the release candidate with that in mind and report
back in case crashes or other issues with that patch in particular show up.

Additionally, we updated the bridges we ship with Tor Browser and fixed
some regressions that came with our last release.

The full changelog since Tor Browser 6.5 is:

Tor Browser 6.5.1 -- March 6 2017
 * All Platforms
   * Update Firefox to 45.8.0esr
   * Tor to 0.2.9.10
   * OpenSSL to 1.0.2k
   * Update Torbutton to 1.9.6.14
 * Bug 21396: Allow leaking of resource/chrome URIs (off by default)
 * Bug 21574: Add link for zh manual and create manual links dynamically
 * Bug 21330: Non-usable scrollbar appears in tor browser security
settings
 * Translation updates
   * Update HTTPS-Everywhere to 5.2.11
   * Bug 21514: Restore W^X JIT implementation removed from ESR45
   * Bug 21536: Remove scramblesuit bridge
   * Bug 21342: Move meek-azure to the meek.azureedge.net backend and
cymrubridge02 bridge
 * Linux
   * Bug 21326: Update the "Using a system-installed Tor" section in
start script

Georg



signature.asc
Description: OpenPGP digital signature
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

[Tails-dev] New time for Tails contributors meetings? [Was: Tails contributors meeting: Friday March 03]

[anonym]

[I'm cross-posting to all these lists since that's where the meeting reminders 
go, but whoever responds to this can perhaps drop all but tails-project@ so we 
focus the discussion on one list.]

sajolida:
> The next Tails contributors meeting is scheduled for:
> 
>   Friday 03 March

At least for me, Fri-Sun are essentially out of the question (in an attempt to 
create some work-life balance, but also due to frequently planning AFK 
activities at those times since that's what works with for people I spend time 
with at those times). Hence, this reason alone means I won't attend 3/7 or 
these meetings. I suspect some others of us are in a similar situation.

I'd like us to pick a time for the meeting that is strictly off weekends. Of 
course, if weekends are *better* for most contributors that frequent our 
meetings, then we perhaps shouldn't.

In the CI team we just decided to have our monthly meetings every first 
Thursday every month; this guarantees that it will be off-weekend, and won't 
interfere with planned releases (Sun-Tue). Would something like that work for 
the contributors meeting? We could perhaps consider:

* every first Wednesday
* every second Thursday
* every first Thursday (and we move our CI team meeting to the second Thursday)

I am not sure how important it is to have in the beginning of the month (e.g. 
vs reports) so I'd like your input on this.

(For the CI team meeting we also decided to have the meeting earlier, 16:00 
CE(S)T, which I'd also like, but I fully understand that this doesn't work for 
most people, so I won't even raise it as a suggestion here. Unless I'm way off 
and most of us actually would prefer this (?).)

Thoughts and feelings?

Cheers!

___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] Tails contributors meeting: Friday March 03

[anonym]

sajolida:
> The next Tails contributors meeting is scheduled for:
> 
>   Friday 03 March

As usual for Fri-Sun, don't count on me.

Cheers!

___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.