Feature #15080

Integrate the staging website with the interface

Added by Anonymous 2017-12-19 16:38:48 . Updated 2020-04-23 12:25:11 .

Status:
Confirmed
Priority:
Normal
Assignee:
Category:
Target version:
Start date:
2018-06-11
Due date:
% Done:

100%

Feature Branch:
Type of work:
End-user documentation
Blueprint:

Starter:
Affected tool:
Translation Platform
Deliverable for:

Description

Subtasks

Bug #15649: Make sure users / translators know that they are visiting the staging wiki when they do Rejected

0

Related issues

Related to Tails - Feature #16872: Make it obvious to visitors of the staging website that it is not trustworthy Confirmed
Related to Tails - Feature #16872: Make it obvious to visitors of the staging website that it is not trustworthy Confirmed
Blocked by Tails - Feature #15084: Review & Rubberducking Resolved 2017-12-19
Blocks Tails - Feature #15360: Refresh the Weblate staging website more often In Progress 2018-03-02

History

#2 Updated by Anonymous 2017-12-19 17:43:04

#3 Updated by Anonymous 2018-03-02 15:37:40

  • Target version changed from Tails_3.7 to Tails_3.8

Current status: staging website should use it’s own git repository which should contain all translations, also unreviewed ones. However, we have not yet defined how we will create this repository.

#4 Updated by Anonymous 2018-06-19 09:45:51

We have a script that takes care of this now, see https://labs.riseup.net/code/issues/15077#note-15 I propose we follow up on Feature #15077 for technical issues and we can recycle this ticket here to think about how to make staging easily known to translators.

#5 Updated by intrigeri 2018-06-26 16:27:44

  • Target version changed from Tails_3.8 to Tails_3.9

#6 Updated by Anonymous 2018-09-03 17:42:08

  • Target version changed from Tails_3.9 to Tails_3.11

#7 Updated by Anonymous 2018-11-02 17:53:24

  • Assignee set to drebs
  • Type of work changed from Code to End-user documentation

Hi drebs,

we need to document the existence and functioning (it is updated once a day automatically) staging.translate.tails.boum.org on the translator’s pages in wiki/src/contribute/how/translate.

#8 Updated by CyrilBrulebois 2018-12-16 14:07:46

  • Target version changed from Tails_3.11 to Tails_3.12

#9 Updated by anonym 2019-01-30 11:59:12

  • Target version changed from Tails_3.12 to Tails_3.13

#10 Updated by Anonymous 2019-02-07 15:20:25

#11 Updated by intrigeri 2019-03-12 17:21:34

u wrote:
> we need to document the existence and functioning (it is updated once a day automatically) staging.translate.tails.boum.org on the translator’s pages in wiki/src/contribute/how/translate.

I’m a bit confused: I thought this ticket was about linking to the staging website from the Weblate interface, so that translators know where they can see how their work would look like on a live website.

What you’ve described here seems to belong more to Feature #11763, no?

#12 Updated by CyrilBrulebois 2019-03-20 14:34:05

  • Target version changed from Tails_3.13 to Tails_3.14

#13 Updated by CyrilBrulebois 2019-05-23 21:23:20

  • Target version changed from Tails_3.14 to Tails_3.15

#14 Updated by hefee 2019-05-24 18:50:10

  • Target version deleted (Tails_3.15)

#15 Updated by intrigeri 2019-06-27 17:48:45

  • Affected tool set to Translation Platform

#16 Updated by intrigeri 2019-06-27 17:49:51

  • related to Feature #15360: Refresh the Weblate staging website more often added

#17 Updated by intrigeri 2019-07-02 08:58:46

Feature #15360#note-11 is relevant wrt. prioritizing this task (or not :)

#18 Updated by Anonymous 2019-07-19 16:45:24

#19 Updated by Anonymous 2019-07-19 17:05:35

intrigeri wrote:
> u wrote:
> > we need to document the existence and functioning (it is updated once a day automatically) staging.translate.tails.boum.org on the translator’s pages in wiki/src/contribute/how/translate.
>
> I’m a bit confused: I thought this ticket was about linking to the staging website from the Weblate interface, so that translators know where they can see how their work would look like on a live website.
>
> What you’ve described here seems to belong more to Feature #11763, no?

Correct, yes. The current status of this ticket is:

We might - optionally - want to make translators aware of the existence of the staging website. It’ll be in the documentation, and additionally I would propose that we just add a sentence to the login screen of Weblate with a link.

I would not aim at doing more at this point, like adding a link for each component.

#20 Updated by intrigeri 2019-09-13 09:46:14

  • related to Feature #16872: Make it obvious to visitors of the staging website that it is not trustworthy added

#21 Updated by intrigeri 2019-09-13 09:53:15

  • Assignee deleted (drebs)

u and I agreed that it’s sufficient to do:

  1. Add a link to the staging website on the Weblate homepage + an explanatory sentence.
  2. Report a feature request to Weblate upstream about adding links from each component’s page.

Let’s first do the other SponsorL things and then see if there’s budget left.

#22 Updated by intrigeri 2019-09-13 09:54:32

  • related to deleted (Feature #15360: Refresh the Weblate staging website more often)

#23 Updated by intrigeri 2019-09-13 09:54:40

  • blocks Feature #15360: Refresh the Weblate staging website more often added

#24 Updated by intrigeri 2019-09-13 09:55:26

#25 Updated by intrigeri 2020-01-06 12:52:58

  • Deliverable for deleted (Sponsor_L)

#27 Updated by emmapeel 2020-04-23 12:25:11

I have added a project message that says: ’To review the results of your translations go to https://staging.tails.boum.org/' but maybe is a bit annoying in all component pages.

I closed it for my account and it went away.

Let me know what you think about it, and if it is a nice way of providing the staging address.

#28 Updated by zen 2020-04-24 13:39:04

  • related to Feature #16872: Make it obvious to visitors of the staging website that it is not trustworthy added