Re: [Tails-dev] Testing the ISO Verification Extension

2015-11-27 Thread sajolida
sajolida:
> Giorgio Maone:
>> On 18/11/2015 19:54, sajolida wrote:

Meta: I created a bunch of tickets on Redmine to track all these pending
issues. Feel free to reassign them to tchou if you think that should be
on our plate, or to me for review (using "QA Check: Ready for QA").

>>> I read this too fast. Actually, we don't want the extension to open the
>>> file browser of the OS right now. After clicking on the "Next" button,
>>> people will go through step-by-step instructions and we'll tell them
>>> when to use the ISO image.
>>
>> So, when you click "Next" the extension should NOT open the file browser
>> NOR reload the page to initial state, correct?
>> What should happen exactly, instead? Should I just leave it up to you
>> (i.e. the web page)?
> 
> Sorry for being unclear here. The cases where the extension should reset
> were not super clear to us either until now. We gave it a second thought
> this morning. We think that the extension should reset (ie. go back to
> the state it is right after installing) in the following cases only:
> 
> 1. The IDF has changed. I'm not sure exactly when the extension
> downloads the IDF again as of now, but whenever the IDF changes (for
> example if we issue an emergency release) and the user goes back to the
> same page the extension should reset. We can probably skip the corner
> cases when the IDF changes *while* the user is downloading.
> 
> 2. The "Download again" button is clicked.
> 
> 3. The "Cancel" button is clicked.
> 
> So yes, after giving it a second though, when the user clicks on the
> "Next" button the extension should not reset. We'll simply use an href
> to redirect to or toggle the rest of the instructions if needed. In some
> cases the instructions might be on the very same page already and we
> might not even have a "Next" button.
> 
> In other words, I think that we'll rescue the logic you had already for
> the "Next" button and make it the "Download again" button.
> 
> Regarding opening the file browser, neither the "Download again" nor the
> "Cancel" button nor the "Next" button should open the file browser.
> But maybe we might want to open the file browser from the same page,
> later on in the rest of the instructions. But this would be outside of
> the big div #download-and-verify. Can you still give us that possibility?

I created #10682 to track the issue of opening the file browser.

>>> Here are the new issues:
>>>
>>> 1. Clicking the "Next" button should also bring back #use-button to
>>>"show" and #use-text to "hide".
>>
>> So, if you click "Next", you get the "Use Firefox extension" button
>> again visible, right?
>> What is exactly supposed to happen when you click it, though?
> 
> Sorry but we're changing a bit our minds here. Forget about the "Next"
> button. As said in the previous point, the "Download again" and "Cancel"
> buttons should reset the full state of the page as when the extension
> was installed. That means with the "Use Firefox extension" (and the
> minor BitTorrent option) visible again.
> 
> We might find a better wording for the "Download again" button but the
> idea is to give the user a way of resetting everything. For example, if
> they come back after delete the ISO or something...
> 
>>> 2. #bittorrent-minor should also be visible when #use-button
>>>and #install-button are visible. See slides 3 and 4.
>>
>> OK, done in latest commit.
> 
> I don't see this. I tested with 0.2.5 and it didn't work. I also don't
> see any change while search on 'bittorrent' in the Git history as of
> 1039f5f. Maybe you forgot to push?

Created #10676 for that. Assigned to tchou for the moment.

>>> 3. Clicking #use-button or #install-button should #i_have_iso (when
>>>the download starts).
>> You mean *hide* #i_have_iso, correct? Tentatively done, then.
> 
> Sorry for the missing word. You understand correctly, I meant "Clicking
> #use-button or #install-button should hide #i_have_iso". Still, I don't
> see this in 0.2.5. See screenshot in attachment.

Created #10677 for that. Assigned to tchou as well.

>>> 4. The page reloads every 10s. Why? It makes it blink pretty badly on
>>>Tor Browser and also sometimes loses state.
>>
>> Weird, can you consistently reproduce, and how?
> 
> Yes, when in Tails, Tor Browser outside of Tails and FF38. See this
> screencast. The first blinking and reset appears at 0:49, then it goes on:
> 
> https://dl.poivron.org/p27bqufzog2ekqmkqttt-cbt2g3hglv62s4jv
> 
> Note that I need to force a reload of the page for this to happen. If I
> don't reload the page it doesn't blink.

Created #10678 for this one.

>>> 8. When doing "Resume", the progress bar goes to 100%, displays ???,
>>>and then go back to where it was once the download really started
>>>again. The progress bar should instead freeze where it is until the
>>>download starts again for real.
>>
>> Tentatively fixed in 0.2.5
> 
> Ack for the progress bar. Now, there's still a minor glitch as the
> displayed 

Re: [Tails-dev] Release versioning

2015-11-27 Thread sajolida
intrigeri:
> sajolida wrote (26 Nov 2015 13:36:52 GMT) :
 B. Switch to "even for major releases / odd for minor ones", call the
first Tails/Jessie release 2.0, and then
> [...]
>> I agree with anonym. I don't mind doing the work needed for B.
> 
> Yay, we've got a decision then!
> 
>> And I'm fine with having 2.0 on January 26 and 2.2 on March 8.
> 
> Cool.

Please review 095e86b and 145da9a.

I also moved all tickets from 1.9 to 2.0 and sent a email about that to
everybody.

I renamed in Redmine "1.10" into "2.2", "1.11" into "2.3", "1.12" into
"2.4", "1.13" into "2.5" and "1.14" into "2.6" in the calendar and in
Redmine?

Anything else?
___
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] Heads up: Tails 1.9 is now Tails 2.0, check your tickets

2015-11-27 Thread sajolida
Hi,

As we know finished deciding the release schedule for Tails Jessie, we
know that Tails 1.9 will indeed by Tails 2.0 (aka Tails Jessie).

So I moved all tickets marked for 1.9 to 2.0. But the freeze for 2.0 is
exceptionally very soon, on December 11 (even before Tails 1.8). So
please check the tickets assigned to you and make sure that whatever
needs to get in the ISO will be realistically done in time for December 11.
___
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] Does LHF still make sense?

2015-11-27 Thread sajolida
Muri Nicanor:
> in the monthly meeting yesterday we talked about the LHF sessions [0].
> i was at two or three of these in the last four or five month and there
> was noone there (although i must say, i didn't speak up, i just wanted
> to know what was happening there and jump in if it was interesting).
> other attandents of the monthly meeting also reported that noone showed
> up to the LHF sessions (but some used the time for working on tickets).
> 
> i always saw the LHF meeting as a place for new people to start working
> on tails, but if no new people show up, maybe there are other ways to
> reach out to new contributers?
> 
> did anyone have other LHF experiences in the last few month? is maybe
> the time or the date the problem why nobody shows up? is the LHF still
> worth the organizing?
> 
> we decided to stop announcing the LHF sessions, until there's a better plan.

Nobody answered this thread in three weeks, so I disabled the automatic
announcement.

___
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] Installation Assistant (+ ISO Verification Extension + Tails Install in Debian): release schedule

2015-11-27 Thread sajolida
Hi,

I'm putting tails-ux in copy but the implications of these mostly affect
development work so please answer on tails-dev.

Last week-end we did intensive testing of the current prototype for the
Installation Assistant. We spent 18 hours testing the whole process with
16 people and many findings came out of it.

You can check the rainbow table [1] if you want to see our findings.
Today I'll also write a more specific email about the work left to be
done on the extension.

[1]:
https://labs.riseup.net/code/attachments/download/1070/ux-testing-20151120.ods

Then we decided on the release schedule for the whole thing. And I want
to check with Girgio and u whether that's fine with them. We thought
about doing:

- A beta release in time for 1.8 (December 15). The assistant would be
advertised in the release notes, maybe tweet about it and send a mail to
tails-testers. That's tracked by #8590 and subtasks.

- A final release in time for or before (January 26). The assistant
would then replace the current installation instructions and be linked
from the current "Download" button on the website (renamed "Install").
That's tracked by #8592 and subtasks.

So by December 15 we would need to have:

- The Debian and Ubuntu packages ready in backports and PPA. So we can
do the beta with the final instructions for them.
- A version of the extension uploaded to addons.mozilla.org so we can
point to it instead of maone.net.

Does that seems feasible to you?
___
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] stats on upgrade time

2015-11-27 Thread Spencer

Hi,



Adam Burns:
Uniquely identify each Tails image to assess and profile their usage
frequencies as per above?



I think that is called spying :)

Wordlife,
Spencer



___
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.