Feature #9183

Have a test website on staging.tails.boum.org

Added by sajolida 2015-04-07 17:48:18 . Updated 2019-07-24 15:42:25 .

Status:
Duplicate
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
Start date:
2015-04-07
Due date:
% Done:

100%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

This will allow us to:

  • Develop web prototypes without polluting our main repo.
  • Have web prototypes available for review or testing online.
  • Allow more people to push changes through Git.

Subtasks

Feature #9184: Create a master repo for staging.tails.boum.org Rejected bertagaz

0
Feature #9185: Propose an ikiwiki configuration for staging.tails.boum.org Rejected

0
Feature #9186: Have boum.org deploy staging.tails.boum.org Rejected

0
Feature #9187: Document staging.tails.boum.org Rejected

0

History

#1 Updated by sajolida 2015-04-07 17:48:38

  • Subject changed from Have test website on staging.tails.boum.org to Have a test website on staging.tails.boum.org

#2 Updated by intrigeri 2015-04-20 07:23:34

  • Assignee set to sajolida

(My understanding is that sajolida will coordinate this project and ensure it’s lead to completion.)

#3 Updated by sajolida 2015-09-21 03:14:09

  • Assignee deleted (sajolida)

Same as Feature #9174#note-3.

#4 Updated by sajolida 2015-11-10 01:49:52

Another use of this staging website could be for translators to review translated strings in their context. For example, we could have staging.tails.boum.org download non-review strings from weblate on a regular basis and build them for review.

#5 Updated by intrigeri 2015-12-15 12:43:08

Taking a step back a few months later: it’s super great that we work with boum.org when we have strong reasons to use their services (e.g. trust, logging policy, etc.), but in this case it seems to me that doing it on b.o might take a while => I suggest that anyone who wants to cary this idea to completion thinks about the hosting requirements, and looks into other ikiwiki hosting services, such as https://www.branchable.com/.

#6 Updated by sajolida 2015-12-16 04:49:29

  • Assignee set to sajolida

That’s a cool idea. I’ll have a look!

#7 Updated by sajolida 2016-03-16 16:02:07

#8 Updated by sajolida 2016-03-19 20:44:28

#9 Updated by Anonymous 2018-01-19 15:15:17

  • QA Check set to Info Needed

We do want this as part of our work on Lush / translation platform. Does this work? Can we use the proposed URL? Was there any work done on this that I might not be aware of already? Please reassign to me afterwards.

#10 Updated by intrigeri 2018-01-19 16:28:20

> We do want this as part of our work on Lush / translation platform.

I don’t think so: I think we want a staging website for weblate translations but I don’t think it should be the same as this one.

> Can we use the proposed URL?

I suggest you instead use staging.translate.tails.b.o or similar to avoid competing in the main namespace :)

#11 Updated by sajolida 2018-01-21 12:53:59

  • Assignee deleted (sajolida)

As intrigeri said, the initial goals for both staging are different. The goals for this ticket are in the description of the ticket. The idea would be to have on staging.tails.boum.org different content than on tails.boum.org; content that’s still under development.

while the goals for staging.translate.tails.b.o would be to allow translators to see their work in context; as a start, to work on the content of our master branch.

Still, it might be useful for translators to be able to work on upcoming content. For example, when developping a new page or writing documentation for a new version of Tails, it would be good for translators to also be able to see these content on their staging website.

I think the next step is for you, u, to think a bit more about that and the objectives and restrictions of the staging website for translators:

  • Is it going to build master? Should or could it build something else? Maybe a single ‘staging’ branch into which we could merge content that is not published yet but is ready for translation. Maybe only add more complexity in the future, etc.

Maybe we’ll find out that it is possible to combined the goals for both staging websites somehow. But that’s not an easy question to answer right now I think.

#12 Updated by Anonymous 2018-01-23 10:48:18

  • Assignee set to sajolida

sajolida wrote:
> As intrigeri said, the initial goals for both staging are different. The goals for this ticket are in the description of the ticket. The idea would be to have on staging.tails.boum.org different content than on tails.boum.org; content that’s still under development.

Ack.

> while the goals for staging.translate.tails.b.o would be to allow translators to see their work in context; as a start, to work on the content of our master branch.
>
> Still, it might be useful for translators to be able to work on upcoming content. For example, when developping a new page or writing documentation for a new version of Tails, it would be good for translators to also be able to see these content on their staging website.

Ack.

> * Is it going to build master? Should or could it build something else? Maybe a single ‘staging’ branch into which we could merge content that is not published yet but is ready for translation. Maybe only add more complexity in the future, etc.

As far as I know, currently upcoming translations happen in devel, don’t they?
But I could also imagine to have a ‘staging’ branch. Your call.

#13 Updated by sajolida 2018-01-23 15:52:04

> As far as I know, currently upcoming translations happen in devel, don’t they?

It depends :)

When documenting features for upcoming versions, we merged stuff that’s
ready to be translated into devel, yes.

When working on documentation that is not bound to a particular Tails
version, we usually work in our own branches. For example, when working
on the new download page, we worked on a dedicated branch but not devel.
Same for the first implementation of the Installation Assistant.

> But I could also imagine to have a ‘staging’ branch. Your call.

It could work to have a ‘staging’ branch where we would merge
documentation work that’s ready for publication but not merged yet.

I need to give it more thoughts though. So I suggest you use ‘master’
for the time being and we should be able to switching to another branch
in the future without too much hassle, no?

Maybe keep in mind that we might base the translation platform on
something else than master at some point and:

  • Make this configurable somehow.
  • Tell us if you envision problems with that while developing the platform.

And we can see once we have a first version of the platform.

#14 Updated by sajolida 2018-05-04 15:17:28

  • Assignee deleted (sajolida)
  • QA Check deleted (Info Needed)

I don’t want to have this on my plate anymore.
!!

#15 Updated by sajolida 2019-07-24 15:42:25

  • Status changed from Confirmed to Duplicate

I haven’t felt the need for this in years. Let’s reopen it if the need arises again.