Bug #17050
Translation platform: design & implement long-term maintenance & support plan
0%
Description
Team: hefee, intrigeri, u, drebs
Meeting planned for November 21st 2019 14-17h Berlin/Amsterdam time.
Subtasks
Related issues
|
Related to Tails - |
Resolved | 2020-04-01 | 2020-04-01 |
|
Related to Tails - |
Resolved |
History
#1 Updated by intrigeri 2019-09-13 09:31:33
- related to
Bug #16994: Weblate database switch to PostgreSQL added
#2 Updated by Anonymous 2019-09-13 09:34:56
- related to
Bug #16943: Upgrade to Weblate 3.x added
#3 Updated by intrigeri 2019-09-13 10:22:31
- Target version set to Tails_4.1
#4 Updated by intrigeri 2019-09-13 17:49:04
- Description updated
#5 Updated by Anonymous 2019-09-26 13:20:39
This will happen on November 21st 2019.
#6 Updated by hefee 2019-10-01 23:00:00
- blocks
Bug #17063: Cleanup translate-server.git added
#7 Updated by hefee 2019-10-16 14:55:59
- blocked by deleted (
Bug #17063: Cleanup translate-server.git
#8 Updated by Anonymous 2019-10-21 14:38:45
- Description updated
#9 Updated by sajolida 2019-11-10 16:08:16
Once you’re done here, make sure to update summit.git:Teams.mdwn. Thanks!
#10 Updated by intrigeri 2019-11-21 15:18:14
- Status changed from Confirmed to In Progress
- Target version changed from Tails_4.1 to Tails_4.3
As per today’s meeting (notes sent over email to the 4 people who were part of the thread):
- We’ll define the maintainers’ responsibilities incrementally in the next few months, while doing the work together.
- Around February we’ll start formally handing the job over to the maintainer.
#11 Updated by intrigeri 2019-11-22 07:57:32
- Blueprint set to https://tails.boum.org/blueprint/translation_platform/#maintainers-responsibilities
#12 Updated by intrigeri 2019-12-22 10:03:27
- Assignee set to intrigeri
#13 Updated by intrigeri 2020-01-15 09:25:57
Hi drebs & hefee!
Here’s a gentle reminder that we’re supposed to dump notes into https://tails.boum.org/blueprint/translation_platform/#maintainers-responsibilities along the way, as we do work that we think may qualify as “Maintain the translation platform” core work.
I see this did not happen yet but perhaps this is happening elsewhere (totally fine by me); I want to encourage you to handle this in another way that would work better for you, if you’d like :)
Brainstorm-style idea: while reporting your clocking info for Q4 on this front, maybe you’ll see what you spent time on, and it could be a good time to sum it up somewhere.
Cheers!
#14 Updated by intrigeri 2020-02-07 08:46:50
- Target version changed from Tails_4.3 to Tails_4.4
#15 Updated by intrigeri 2020-02-20 08:57:23
- Assignee changed from intrigeri to drebs
I’ve added all I could think of to the blueprint. How about we do this:
- Until the end of March: you two do the same (suggestion: in my experience, for this sort of things, incrementally works better than after the fact :)
- Early April: we meet to finalize this, in time to provide the info needed by the Tails budget forecasting process (we’ll know how much time we’ve actually spent on this over 4.5 months, we’ll have better visibility on the big things ahead, and depending on what we include in the role description, the budget we request for next year may vary).
I.e. a more relaxed timeline for the handover than what we decided in November, i.e.: “Around February we’ll start formally handing the job over to the maintainer”.
If you folks prefer to stick to the original timeline and finalize this earlier than April, that’s totally fine by me :)
?
#16 Updated by CyrilBrulebois 2020-03-12 09:55:58
- Target version changed from Tails_4.4 to Tails_4.5
#17 Updated by CyrilBrulebois 2020-04-07 17:05:15
- Target version changed from Tails_4.5 to Tails_4.6
#18 Updated by CyrilBrulebois 2020-05-06 04:28:56
- Target version changed from Tails_4.6 to Tails_4.7