Project

General

Profile

Feature #15080

Integrate the staging website with the interface

Added by u almost 2 years ago. Updated about 1 month ago.

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

100%

Feature Branch:
Type of work:
End-user documentation
Blueprint:
Starter:
Affected tool:
Translation Platform

Subtasks

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


Related issues

Related to Tails - Feature #16872: Make it obvious to translators that they are visiting the staging website Confirmed
Blocked by Tails - Feature #15084: Review & Rubberducking Resolved 12/19/2017
Blocks Tails - Feature #15360: Refresh the Weblate staging website more often In Progress 03/02/2018

History

#2 Updated by u almost 2 years ago

#3 Updated by u over 1 year ago

  • 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 u over 1 year ago

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 #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 over 1 year ago

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

#6 Updated by u about 1 year ago

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

#7 Updated by u 12 months ago

  • Assignee changed from u 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 10 months ago

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

#9 Updated by anonym 9 months ago

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

#10 Updated by u 8 months ago

  • Parent task changed from #15079 to #11763

#11 Updated by intrigeri 7 months ago

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 #11763, no?

#12 Updated by CyrilBrulebois 7 months ago

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

#13 Updated by CyrilBrulebois 5 months ago

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

#14 Updated by hefee 5 months ago

  • Target version deleted (Tails_3.15)

#15 Updated by intrigeri 4 months ago

  • Affected tool set to Translation Platform

#16 Updated by intrigeri 4 months ago

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

#17 Updated by intrigeri 3 months ago

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

#18 Updated by u 3 months ago

  • Parent task changed from #11763 to #15095

#19 Updated by u 3 months ago

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 #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 about 1 month ago

  • Related to Feature #16872: Make it obvious to translators that they are visiting the staging website added

#21 Updated by intrigeri about 1 month ago

  • 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 about 1 month ago

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

#23 Updated by intrigeri about 1 month ago

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

#24 Updated by intrigeri about 1 month ago

  • Parent task deleted (#15095)

Also available in: Atom PDF