Feature #11725

Have a dedicated page for the homepage of Tor Browser in Tails

Added by sajolida 2016-08-25 11:31:16 . Updated 2016-09-20 16:47:48 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Fundraising
Target version:
Tails_2.6
Start date:
2016-08-25
Due date:
% Done:

100%

Feature Branch:
feature/11725-dedicated-homepage
Type of work:
Website
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

This way we could make it more relevant for people inside Tails, from the top of my head:

  • Move “Tor check” from /news to this page.
  • Provide some kind of panel which could be more relevant than /news, for example including pointer to documentation for newcomers.
  • Push and customize donation campaign; I admit that’s this objective :)

Subtasks

History

#1 Updated by sajolida 2016-08-30 07:39:32

  • Assignee changed from sajolida to anonym
  • QA Check set to Ready for QA
  • Feature Branch set to feature/11725-dedicated-homepage

That’s ready. I built an ISO on nightly and tested it (in English and French). Note that the HTML page itself is added by the branch as well so currently it gets a 404 but that’s expected.

Assigning to anonym who original wrote the code I’m modifying here.

We need this change in place for the donation campaign (after 2.6).

#2 Updated by anonym 2016-09-02 05:26:48

  • Status changed from Confirmed to Fix committed
  • Assignee deleted (anonym)
  • % Done changed from 0 to 100
  • QA Check changed from Ready for QA to Pass

Since I need to merge this into master for it to make sense, I’ve had to rebase the branch on master (it was based on devel) and force pushed it. After merging it into master I’ve partially reverted the first commit (“Use a dedicated page as homepage of Tor Browser in Tails (Feature #11725)”) since it does changes inside Tails, and I’ve then reverted that partial revert (!!) in devel. Our Git workflow is fun! :)

#3 Updated by anonym 2016-09-02 06:40:53

  • Assignee set to sajolida
  • QA Check changed from Pass to Info Needed

The new page is not localized, see commt:a311a3e37b0094d173bcac67654c39c415b61703. Does this make sense? If so, please unassign yourself and return the QA Check to Pass.

#4 Updated by sajolida 2016-09-03 11:58:24

> The new page is not localized, see commt:a311a3e37b0094d173bcac67654c39c415b61703.

Shit! I want it translatable.

I wrote a branch based on master to do this. I hope that’s a reasonable
workflow this time :)

It’s web/11725-make-home-translatable.

Can you have a look and merge it if it’s fine. Then we should notify
root@boum.org about the change.

#5 Updated by sajolida 2016-09-03 11:59:41

  • Assignee changed from sajolida to anonym
  • QA Check changed from Info Needed to Ready for QA

Once we’re done with making /home translatable, we should revert a311a3e.

#6 Updated by intrigeri 2016-09-09 14:55:48

  • Status changed from Fix committed to In Progress
  • Assignee changed from anonym to sajolida
  • % Done changed from 100 to 80
  • QA Check changed from Ready for QA to Info Needed

(I’m supposed to be the backup RM for 2 more days. I’m sorry this was not announced anywhere, so this ticket did not land onto my plate.)

> Once we’re done with making /home translatable, we should revert commit:a311a3e.

I have a hard time following this whole thing with reverts of reverts and all, so I have to ask: is it done somewhere yet? If not, should it be tracked by this very ticket, or by another one?

> It’s web/11725-make-home-translatable.

Should I merge this into master?

#7 Updated by sajolida 2016-09-10 10:13:00

  • Assignee changed from sajolida to intrigeri

Currently /home is the homepage in 2.6~rc1 but it’s not translatable.

The remaining steps, I think are:

  1. You review web/11725-make-home-translatable and merge it into master.
  2. We notify root@boum.org of this. You could do it when merging or I could do it right after.
  3. We revert a311a3e in testing. I could do it and ask for review or you could do it directly.

#8 Updated by intrigeri 2016-09-11 14:28:29

  • QA Check changed from Info Needed to Ready for QA

#9 Updated by intrigeri 2016-09-12 02:30:48

I’m on it. I’ve added /home to the core pages, while I’m at it (commit:e8f143b); shout if that’s a mistake. Nitpicking: I’d rather keep some kind of lexical sorting in the po_translatable_pages, but well, not worth doing & testing the change right now.

#10 Updated by intrigeri 2016-09-12 02:39:50

  • Assignee changed from intrigeri to sajolida

sajolida wrote:
> The remaining steps, I think are:

Thanks for the summary! All done.

It would be nice to check if the resulting ISO (built from testing) has the correct homepage when logged in with English locales, a language that has a translation (e.g. French), and a language that has no translation (e.g. Spanish). Can you please do this?

#11 Updated by intrigeri 2016-09-12 02:40:06

  • % Done changed from 80 to 90

#12 Updated by sajolida 2016-09-12 11:09:00

I’ll try but my Internet is pretty flaky at the moment…

#13 Updated by anonym 2016-09-14 15:29:19

  • Status changed from In Progress to Fix committed
  • Assignee deleted (sajolida)
  • % Done changed from 90 to 100
  • QA Check changed from Ready for QA to Pass

I have verified that the new home page is localized properly for tails-documentation in a recent testing build.

#14 Updated by anonym 2016-09-20 16:47:49

  • Status changed from Fix committed to Resolved