Re: [Tails-dev] dconf-editor dropped, gedit-plugins, systemd, w32codecs

2016-03-09 Thread maddonkeykong 
 Original Message 
From: Austin English 
Apparently from: tails-dev-boun...@boum.org
To: The Tails public development discussion list 
Subject: Re: [Tails-dev] dconf-editor dropped, gedit-plugins, systemd,w32codecs
Date: Tue, 8 Mar 2016 20:44:40 -0600

> TL;DR: I think we should ship as many codecs as we can, to allow as
> wide of access to media as possible.
> 
> On Mon, Mar 7, 2016 at 4:38 AM, intrigeri  wrote:
> > Austin English wrote (07 Mar 2016 03:05:46 GMT) :
> >> That said, including win32 codecs is probably worthwhile.

RE: win32 codecs - I agree. So let's say we have win32 codecs installed. Can 
Totem handle these codecs, or do we need to install another video player?

Now regardless of video player, there are a few different browser plugins 
available in the repos to directly handle these codecs. The problem is, you 
probably don't want these to load into Tor Browser.

So what could be used instead? The unsafe browser or a separate profile or 
browser with the codecs and plugin capability?
___
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] dconf-editor dropped, gedit-plugins, systemd, w32codecs

2016-03-09 Thread maddonkeykong 
minor correction from the mail I just sent:

the opening line of my research page should read:

dconf-editor mysterious disappearance in 2.0.1 solved! dconf-tools is missing!

and not:

dconf-tools mysterious disappearance in 2.0.1 solved! dconf-tools is missing!
___
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] dconf-editor dropped, gedit-plugins, systemd, w32codecs

2016-03-09 Thread maddonkeykong 
 Original Message 
From: intrigeri 
Apparently from: tails-dev-boun...@boum.org
To: Anonymous 
Cc: tails-dev@boum.org
Subject: Re: [Tails-dev] dconf-editor dropped, gedit-plugins, systemd,w32codecs
Date: Mon, 07 Mar 2016 11:38:27 +0100

> Hi,
> 
> Anonymous wrote (07 Mar 2016 01:17:01 GMT) :
> > 1. Why was dconf-editor dropped from Tails?
> 
> According to our Git history, we've never shipped it in Tails.
[SNIP]

I did some research on this and yes the 'dconf-editor' program was installed, 
but not directly. The package which did install it has been removed in 2.0.1. I 
have not yet tried 2.2 but I assume the situation is the same.

Here's what I found:

###
dconf-tools mysterious disappearance in 2.0.1 solved! dconf-tools is missing!

(A) Let's look in Tails 1.8.1
(B) Let's look in Tails 2.0.1
(C) Let's look at Debian's site
(D) In closing
###

(A) Let's look in Tails 1.8.1:

$ cat /etc/*release
TAILS_PRODUCT_NAME="Tails"
TAILS_VERSION_ID="1.8.1"

##

$ dpkg -l | grep dconf-tools
ii  dconf-tools 0.12.1-3 i386 simple configuration storage system - utilities

##

Synaptic -> Settings -> Preferences -> Appearance -> Show package properties in 
the main window

##

selected package: dconf-tools
clicked on the Installed Files tab
one of the binaries is called, "dconf-editor"

##

dconf-editor is listed in Applications->System Tools as "dconf Editor"

##

$ whereis dconf-editor
dconf-editor: /usr/bin/dconf-editor /usr/bin/X11/dconf-editor 
/usr/share/dconf-editor

###

(B) Let's look in Tails 2.0.1:

$ cat /etc/*release
TAILS_PRODUCT_NAME="Tails"
TAILS_VERSION_ID="2.0.1"

##

$ dpkg -l | grep dconf
ii  dconf-cli0.22.0-1   
  i386 simple configuration storage system - utilities
ii  dconf-gsettings-backend:i386 0.22.0-1   
  i386 simple configuration storage system - GSettings back-end
ii  dconf-service0.22.0-1   
  i386 simple configuration storage system - D-Bus service
ii  libdconf1:i386

- None of the above packages contain the dconf-editor program.
- The package 'dconf-tools' is missing in Tails 2.0.1 but available in 1.8.1

###

(C) Let's look at Debian's site:

https://packages.debian.org/jessie/dconf-tools

Package: dconf-tools (0.22.0-1) 
transitional dummy package
DConf is a low-level key/value database designed for storing desktop 
environment settings. 
This package is a transitional package installing dconf-cli and dconf-editor, 
it can safely be removed

Other Packages Related to dconf-tools
dep: dconf-cli 
dep: dconf-editor 

###

(D) In closing, a few of the most recent but older versions had 'dconf-tools' 
installed,
which supplied the dconf-editor program.

I'd like to request 'dconf-tools' to return again, so we can use 'dconf-editor'.

Thank you for your support.
___
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] [review'n'merge] meeting notes

2016-03-09 Thread segfault 
Hey,

I corrected the part about the pinentry decision.

cheers


emmapeel:
> 
> 
> emmapeel:
>> here you go!
>>
>> please add things you find missing...
>>
>>
> maybe i was not clear enough on the subject... please review the
> attachment and merge or correct...
> 
> 
> 
> 
> ___
> 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.
> 
>From 42b117c8d6dc31c2ac9f84bc61e1987f6fe0907b Mon Sep 17 00:00:00 2001
From: emma peel 
Date: Fri, 4 Mar 2016 12:09:48 +
Subject: [PATCH] 2016 March meeting notes

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

diff --git a/wiki/src/contribute/meetings/201603.mdwn b/wiki/src/contribute/meetings/201603.mdwn
new file mode 100644
index 000..beaa8c8
--- /dev/null
+++ b/wiki/src/contribute/meetings/201603.mdwn
@@ -0,0 +1,56 @@
+1. Volunteers to handle "Hole in the roof" tickets this month
+-
+
+- anonym might already have dealt with [[!tails_ticket 7182]]: Identical branch HEADs can result in Vagrant building from the wrong branch
+- intrigeri is working on [[!tails_ticket 5650]] (rngd)
+- bertagaz is also working in background on [[!tails_ticket 7675]] 
+- [[!tails_ticket 6311]] is better done after [[!tails_ticket 6310]]
+
+2. Volunteers to handle important tickets flagged for next release, but without assignee
+
+
+- [[!tails_ticket 11075]]: Remove "Power Off" and "Reboot" from Applications → System Tools: we finally didn't had time to deal with this.
+- [[!tails_ticket 11175]]:  Decrease I/O load created by isotesters on lizard - this one was meant for bertagaz.
+
+3. Availability and plans until the next meeting
+
+
+- intrigeri: in March I should be mostly available for Tails. focus on SponsorS deliverables (mainly: freezable APT repo). except I'll have 1 week "off" (with lots time with new/wannabe contributors)
+- emmapeel is frontdesk,Valencia, translators, doc tickets, translation worflow
+- sajolida
+0. Refine the ideal workflow and review early mockups on [[network connection|https://tails.boum.org/blueprint/network_connection/]] (on Sunday).
+1. Make plans on what to do now and what to postpone regarding IA+DAVE.
+2. Invoice the two latest funders milestone.
+3. Start working on the redesign of the download page.
+- muri: iff, beach, cij; then clearing translation backlog; doing some other tickets i've on my watchlist; also thinking about writing a small python keysingning ui
+- anonym: I expect to be available all non-weekends all of March. I'll re-focus again on test suite robustness work, particularly on [[!tails_ticket 9521]] and trying out dogtail a bit more ([[!tails_ticket 7729]], [[!tails_ticket 10721]]). it also looks like I'll work on Icedove integration, unexpectedly. And look at Tails verifier.
+- ticketbot: Tails ☺ Feature #9521: Use the chutney Tor network simulator in our test suite https://labs.riseup.net/code/issues/9521
+- ticketbot: Tails ☺ Feature #7729: Evaluate using LDTP and/or dogtail to improve our automated test suite https://labs.riseup.net/code/issues/7729
+- ticketbot: Tails ☺ Feature #10721: Improve automated GUI testing robustness using "GUI aware" technologies https://labs.riseup.net/code/issues/10721
+- segfault: I will have more time in the next month than in february. I still want to work on the boot and upgrade process and on Tails server [[!tails_ticket 5688]]). And I'm looking forward to the review of the Tails verifier :)
+- bertagaz: March, mostly available hopefully, but focused on the monitoring deployment
+
+Discuss
+---
+
+[[!tails_ticket 11047]]: Decide if we want to have monthly reports and who should edit them 
+---
+
+- Everybody likes reports, but nobody gives input for them. Maybe a report that is incomplete is ok.
+- sajolida feels is a lot of effort to go through the logs or ask people for input.
+- Many of the 5 people that committed to make reports is not on this meeting so we skip the decision...
+- sajolida: is happy to manage the April report (or March) even, but somebody has to handle the weight of the Feb report
+
+[[!tails_ticket 11099]] Decide which pinentry we want to ship
+-
+
+- This and other related pinentry tickets will be taken by segfault. We decided to use pinentry-gtk2 with the --no-global-grab option, which fixes #11038. We preferred this over pinentry-gnome3, because pinentry-gnome3 grabs the mouse, which would be

Re: [Tails-dev] Porting Tails to Debian Stretch

2016-03-09 Thread intrigeri 
hey,

sajolida wrote (09 Mar 2016 12:19:48 GMT) :
>> We are in particular looking for one person to be
>> responsible for the documentation-side of things, since we feel
>> keeping it sort-of up-to-date will help us identify regressions
>> early.

> I can be this person.

Excellent! I've updated the blueprint accordingly.

>> Regarding timelines, the freeze for Debian Stretch will be in
>> early December, so the work has to start early enough so issues
>> can be identified and fixed before that (post-freeze fixes are
>> generally much harder). Due to other committments me and
>> intrigeri will not be able to start this until some time early
>> August, which will give us almost four months for this work
>> before the Stretch freeze. We intend to kickstart this effort
>> with a sprint where we meet face to face, and other participants
>> will of course be welcome.

> Now the Stretch freeze has been postponed to 2017-02-05.

> I don't know what my calendar for the summer and fall will be but I
> can't guarantee right now that I can also jump from "intrigeri will not
> be able to start this until some time early August" to "kickstart this
> effort with a sprint [in August]" (implicit in your email).

Please let us know when you know more when you can start, then :)

Note that the very first sprint (that we would like to have in August
2016) might not be very exciting to doc people, given what we expect
to be the goals there. Quoting the blueprint:

* August 2016 — start working on Tails 3.0 (1 week sprint with
  all involved people) :intrigeri:anonym:kytv:
  - get feature/stretch to build and boot
  - update the automated test suite to test Tails/Stretch ISO images

… so it's no big deal if you join us for the 2nd sprint only.

Cheers,
-- 
intrigeri
___
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] Porting Tails to Debian Stretch

2016-03-09 Thread sajolida 
anonym:
> Me and intrigeri have deviced a plan for how we will deal with
> the migration to Debian Stretch, with the details being available
> in this blueprint:
> 
> https://tails.boum.org/blueprint/Debian_Stretch/
> 
> In short, we do not want to repeat the way we did Jessie
> migration -- we think we can do better! The idea is to leverage
> our up-coming freezable APT repo [0] to take snapshots of Debian
> Testing (= Stretch) and have sprints to put Tails into shape
> around these snapshots regularly, without the delta growing too
> big neither against Debian Stretch or Tails/Jessie. We will also
> use this experiment as a benchmark for the idea to make Tails
> into a semi-rolling release based on Debian Testing, which is
> pretty exciting!

All of this sounds good.

> This is an early notice for this plan draft. Our hopes is that
> more people will get involved this time, for a more collective
> effort. We are in particular looking for one person to be
> responsible for the documentation-side of things, since we feel
> keeping it sort-of up-to-date will help us identify regressions
> early.

I can be this person.

> Regarding timelines, the freeze for Debian Stretch will be in
> early December, so the work has to start early enough so issues
> can be identified and fixed before that (post-freeze fixes are
> generally much harder). Due to other committments me and
> intrigeri will not be able to start this until some time early
> August, which will give us almost four months for this work
> before the Stretch freeze. We intend to kickstart this effort
> with a sprint where we meet face to face, and other participants
> will of course be welcome.

Now the Stretch freeze has been postponed to 2017-02-05.

I don't know what my calendar for the summer and fall will be but I
can't guarantee right now that I can also jump from "intrigeri will not
be able to start this until some time early August" to "kickstart this
effort with a sprint [in August]" (implicit in your email).
___
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] [help needed] explaining the way we use Redmine fields

2016-03-09 Thread emmapeel 
Hello:

Muri and I are working on the documentation for our Redmine bug
tracker[1], and would benefit for some more insight on

- Categories
- Type of work
- Affected tool

specially, and also a review of the descriptions we are giving to the
rest of the fields of course. I think we have gathered, and maybe
duplicated a bit, the information that is already on the Release process
documentation, but maybe we are missing some undocumented details.

You can test the branch doc/10719-redmine_fields at
https://git-tails.immerda.ch/emmapeel/tails/ or see the proposed changes
here:

https://git-tails.immerda.ch/emmapeel/tails/tree/wiki/src/contribute/working_together/Redmine.mdwn?h=doc/10719-redmine_fields#n81


Thanks in advance!



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] [review'n'merge] meeting notes

2016-03-09 Thread emmapeel 


emmapeel:
> here you go!
> 
> please add things you find missing...
> 
> 
maybe i was not clear enough on the subject... please review the
attachment and merge or correct...


From 42b117c8d6dc31c2ac9f84bc61e1987f6fe0907b Mon Sep 17 00:00:00 2001
From: emma peel 
Date: Fri, 4 Mar 2016 12:09:48 +
Subject: [PATCH] 2016 March meeting notes

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

diff --git a/wiki/src/contribute/meetings/201603.mdwn b/wiki/src/contribute/meetings/201603.mdwn
new file mode 100644
index 000..beaa8c8
--- /dev/null
+++ b/wiki/src/contribute/meetings/201603.mdwn
@@ -0,0 +1,56 @@
+1. Volunteers to handle "Hole in the roof" tickets this month
+-
+
+- anonym might already have dealt with [[!tails_ticket 7182]]: Identical branch HEADs can result in Vagrant building from the wrong branch
+- intrigeri is working on [[!tails_ticket 5650]] (rngd)
+- bertagaz is also working in background on [[!tails_ticket 7675]] 
+- [[!tails_ticket 6311]] is better done after [[!tails_ticket 6310]]
+
+2. Volunteers to handle important tickets flagged for next release, but without assignee
+
+
+- [[!tails_ticket 11075]]: Remove "Power Off" and "Reboot" from Applications → System Tools: we finally didn't had time to deal with this.
+- [[!tails_ticket 11175]]:  Decrease I/O load created by isotesters on lizard - this one was meant for bertagaz.
+
+3. Availability and plans until the next meeting
+
+
+- intrigeri: in March I should be mostly available for Tails. focus on SponsorS deliverables (mainly: freezable APT repo). except I'll have 1 week "off" (with lots time with new/wannabe contributors)
+- emmapeel is frontdesk,Valencia, translators, doc tickets, translation worflow
+- sajolida
+0. Refine the ideal workflow and review early mockups on [[network connection|https://tails.boum.org/blueprint/network_connection/]] (on Sunday).
+1. Make plans on what to do now and what to postpone regarding IA+DAVE.
+2. Invoice the two latest funders milestone.
+3. Start working on the redesign of the download page.
+- muri: iff, beach, cij; then clearing translation backlog; doing some other tickets i've on my watchlist; also thinking about writing a small python keysingning ui
+- anonym: I expect to be available all non-weekends all of March. I'll re-focus again on test suite robustness work, particularly on [[!tails_ticket 9521]] and trying out dogtail a bit more ([[!tails_ticket 7729]], [[!tails_ticket 10721]]). it also looks like I'll work on Icedove integration, unexpectedly. And look at Tails verifier.
+- ticketbot: Tails ☺ Feature #9521: Use the chutney Tor network simulator in our test suite https://labs.riseup.net/code/issues/9521
+- ticketbot: Tails ☺ Feature #7729: Evaluate using LDTP and/or dogtail to improve our automated test suite https://labs.riseup.net/code/issues/7729
+- ticketbot: Tails ☺ Feature #10721: Improve automated GUI testing robustness using "GUI aware" technologies https://labs.riseup.net/code/issues/10721
+- segfault: I will have more time in the next month than in february. I still want to work on the boot and upgrade process and on Tails server [[!tails_ticket 5688]]). And I'm looking forward to the review of the Tails verifier :)
+- bertagaz: March, mostly available hopefully, but focused on the monitoring deployment
+
+Discuss
+---
+
+[[!tails_ticket 11047]]: Decide if we want to have monthly reports and who should edit them 
+---
+
+- Everybody likes reports, but nobody gives input for them. Maybe a report that is incomplete is ok.
+- sajolida feels is a lot of effort to go through the logs or ask people for input.
+- Many of the 5 people that committed to make reports is not on this meeting so we skip the decision...
+- sajolida: is happy to manage the April report (or March) even, but somebody has to handle the weight of the Feb report
+
+[[!tails_ticket 11099]] Decide which pinentry we want to ship
+-
+
+- This and other related pinentry tickets will be taken by segfault. We will drop the custom code! yay!
+- pinentry-gtk2 + no-grab is acceptable, given the UX regression seems to affect very, very few users (but the UX improvement would affect many users)
+- [[!tails_ticket 11038]] pinentry and gnome shell's top bar cause freeze
+- 
+
+[[!tails_ticket 11042]] alt + shift switch the keyboard layout without indicating it in the keyboard layout menu
+
+- intrigeri takes it

Re: [Tails-dev] Onion Circuits upstream maintenance

2016-03-09 Thread Sascha Steinbiss 

Hi all,


do you already have a plan wrt. how Onion Circuits shall be maintained
upstream, e.g. who is handling proposed contributions?

[...]

I'm asking because I noticed that Sascha (who did most of the
packaging work for Debian so far) has marked a patch he authored as
"Forwarded: via email" (in passing, Sascha: it seems useful to replace
"via email" with the actual email address you forwarded to),
presumably forwarded to you privately.


Just for the record, I have improved that patch before sending any email 
after an additional suggestion from pabs. I also opened a new ticket in 
the Tails Redmine (#11203) regarding that issue (also updating 
Forwarded: tag in the Debian package to the corresponding Redmine URL 
[1]) and attached the patch there. All changes to the Debian package are 
now in the pkg-privacy team's git as well.


I noticed other tickets regarding Onion Circuits in the Redmine recently 
(#11192, #11195, #11173, ...) so to me this looked like the 'canonical' 
way of contributing to Onion Circuits development. So if this approach 
is OK with you then I will be happy to continue doing so in the future 
to keep my upstream contributions open and visible.


Cheers
Sascha

[1] https://labs.riseup.net/code/issues/11203

___
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] Onion Circuits upstream maintenance

2016-03-09 Thread intrigeri 
Hi Alan,

do you already have a plan wrt. how Onion Circuits shall be maintained
upstream, e.g. who is handling proposed contributions?

I'm asking because I noticed that Sascha (who did most of the
packaging work for Debian so far) has marked a patch he authored as
"Forwarded: via email" (in passing, Sascha: it seems useful to replace
"via email" with the actual email address you forwarded to),
presumably forwarded to you privately.

In other words: do you want to handle this personally, via private
communication with you? If yes, what kind of latency do you expect to
have for looking at submitted patches?

Thanks for writing Onion Circuits in the first place!

Cheers,
-- 
intrigeri
___
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] New mirror from France

2016-03-09 Thread intrigeri 
Hi Mathias,

Mathias wrote (08 Mar 2016 22:03:19 GMT) :
> The groupuscule unixcorn.org is pleased to announce the availability of a new 
> mirror,
> accessible from http and https (not forced) : http://tails.unixcorn.org
>  & https://tails.unixcorn.org
> 
> Hope that will be useful.

Thanks for your proposal! We'll need to go through some more steps
before we can use this new mirror:

  https://tails.boum.org/contribute/how/mirror/#http

I'm setting Reply-To so that we follow up on this discussion where
such matters are usually discussed :)

Cheers,
-- 
intrigeri
___
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.