Feature #15084

Review & Rubberducking

Added by Anonymous about 7 years ago. Updated about 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Tails_3.12
Start date:
2017-12-19
Due date:
% Done:

0%

Feature Branch:
Type of work:
Test
Blueprint:

Starter:
Affected tool:
Deliverable for:
309

Description

Your work will be to review everything I prepared for tickets with parent ticket Feature #15079.

Subtasks

Related issues

Blocked by Tails - Feature #15077: Have a staging website to build planned languages, with a resilient build Resolved 2017-03-14
Blocks Tails - Feature #15078: Review staging website and resilient build Resolved 2018-06-11
Blocks Tails - Feature #15079: Integrate the platform with our Git and ikiwiki infrastructure Resolved 2017-03-14
Blocks Tails - Feature #15080: Integrate the staging website with the interface Confirmed 2018-06-11
Blocks Tails - Feature #15081: Adjust our production website Rejected 2017-12-19
Blocks Tails - Feature #15083: Test the setup extensively and deal with unexpected problems Rejected 2017-12-19

History

#2 Updated by Anonymous about 7 years ago

#3 Updated by Anonymous about 7 years ago

  • blocked by Feature #15077: Have a staging website to build planned languages, with a resilient build added

#4 Updated by Anonymous about 7 years ago

  • blocks Feature #15078: Review staging website and resilient build added

#5 Updated by Anonymous about 7 years ago

  • blocks deleted (Feature #15077: Have a staging website to build planned languages, with a resilient build)

#6 Updated by Anonymous about 7 years ago

  • blocked by deleted (Feature #15078: Review staging website and resilient build)

#7 Updated by Anonymous about 7 years ago

  • blocked by Feature #15077: Have a staging website to build planned languages, with a resilient build added

#8 Updated by Anonymous about 7 years ago

  • blocks Feature #15078: Review staging website and resilient build added

#9 Updated by Anonymous about 7 years ago

  • blocks Feature #15079: Integrate the platform with our Git and ikiwiki infrastructure added

#10 Updated by Anonymous about 7 years ago

  • blocks Feature #15080: Integrate the staging website with the interface added

#11 Updated by Anonymous about 7 years ago

#12 Updated by Anonymous about 7 years ago

  • blocks Feature #15082: Have the Weblate Git communicate with our main Git repository added

#13 Updated by Anonymous about 7 years ago

  • blocks Feature #15083: Test the setup extensively and deal with unexpected problems added

#14 Updated by emmapeel about 7 years ago

  • Status changed from New to Confirmed

#15 Updated by Anonymous about 7 years ago

  • QA Check set to Info Needed

Hey groente, when you have some time, could you have a look at https://labs.riseup.net/code/issues/10034#note-19 and corresponding SVG and tell us if you think we missed something or if something is not understandable?

#16 Updated by groente about 7 years ago

  • Assignee deleted (groente)

hey, sorry for the late reply. the overview in weblate_hooks.svg looks good, great to have some overview there. the only thing that is unclear to me is the difference between (Weblate Git) and (Weblate Git non & reviewed strings), are these separate repo’s or just branches of the same repo? and where will they reside?

#17 Updated by Anonymous about 7 years ago

groente wrote:
> hey, sorry for the late reply. the overview in weblate_hooks.svg looks good, great to have some overview there. the only thing that is unclear to me is the difference between (Weblate Git) and (Weblate Git non & reviewed strings), are these separate repo’s or just branches of the same repo? and where will they reside?

We don’t know yet but I think they will be separate repositories. Weblate Git contains only strings that have been reviewed by several translators. We use this Git repository to push to tails.git -> so it should only contain validated strings.

The other one (Weblate Git non & reviewed strings) will be used to generate the staging website and may also contain unreviewed, but translated strings.

#18 Updated by Anonymous about 7 years ago

  • QA Check deleted (Info Needed)

Reassigning back to groente once we have more things to review.

#19 Updated by bertagaz about 7 years ago

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

#20 Updated by Anonymous about 7 years ago

  • Assignee set to groente

Reassigning this back to groente as this is “your” parent task for things to review. :)

#21 Updated by intrigeri about 7 years ago

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

#22 Updated by intrigeri about 7 years ago

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

#23 Updated by intrigeri about 6 years ago

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

#24 Updated by CyrilBrulebois about 6 years ago

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

#25 Updated by intrigeri about 6 years ago

  • Status changed from Confirmed to Resolved
  • Assignee deleted (groente)

Let’s call this done: this was specifically about the original plan for SponsorL, which is over now. We’ll track the next steps and the reviews elsewhere; in particular, Feature #16326.

#26 Updated by intrigeri about 6 years ago

  • blocked by deleted (Feature #15082: Have the Weblate Git communicate with our main Git repository)