Tails

#1 Updated by Anonymous 2017-12-19 16:25:29

• Status changed from Confirmed to Resolved
• % Done changed from 0 to 100

#2 Updated by Anonymous 2017-12-19 16:25:47

• Target version set to Tails_3.5

#3 Updated by emmapeel 2018-01-17 13:02:40

• blocked by Feature #12223: Puppetize machine translation service on translate.lizard added

#4 Updated by Anonymous 2018-03-01 08:51:18

• Status changed from Resolved to In Progress
• Target version changed from Tails_3.5 to Tails_3.7
• % Done changed from 100 to 50

@emmapeel: assuming we’ll have the new weblate version installed, we’ll have to reconfigure some things, so I’m reopening this ticket unless there is another one for this?

#5 Updated by Anonymous 2018-03-13 16:06:39

• related to Bug #15409: Configure addons in Weblate added

#6 Updated by emmapeel 2018-04-03 11:11:16

• related to deleted (Bug #15409: Configure addons in Weblate)

#7 Updated by emmapeel 2018-04-03 11:11:19

• blocks deleted (Feature #12223: Puppetize machine translation service on translate.lizard)

#8 Updated by emmapeel 2018-04-03 11:12:21

• Status changed from In Progress to Duplicate

I dont see the difference between this ticket and Feature #11759.

#9 Updated by emmapeel 2018-04-03 11:12:38

• is duplicate of Feature #11759: Install & configure a fresh weblate on the VM added

#10 Updated by Anonymous 2018-04-03 14:37:59

• Status changed from Duplicate to Confirmed

This ticket is about configuration while 11759 was about the initial installation. So let’s close the other one if we consider it done? I have reopened this ticket because once we upgrade, we’ll likely have more configuration to do.

#12 Updated by emmapeel 2018-04-06 08:23:37

• Assignee deleted (emmapeel)

Please stop creating layers of umbrella tickets because it makes the work harder to organize.

Can you decide on one ticket between this one and 11759, and try to create more atomic tickets intead of this general ones?

We can move the pending tickets to the remaining ticket then.

#13 Updated by Anonymous 2018-04-06 09:01:48

• Assignee set to emmapeel

emmapeel wrote:
> Please stop creating layers of umbrella tickets because it makes the work harder to organize.

For me this organization works well. The main tickets correspond to sponsor deliverables as defined within our fundraising and accounting. This makes it easier for me to track which part of the work has been done and which hasn’t.

If you’d like to tell me exactly how this impacts your work and makes it harder to organize as you say, let’s change the organization. Otherwise I propose to drop this kind of discussion which makes us both lose a lot of time.

> Can you decide on one ticket between this one and 11759, and try to create more atomic tickets intead of this general ones?

You reopened Feature #11759 yourself (see your own comment https://labs.riseup.net/code/issues/11759#note-13).

While Feature #15074 is about setting up Weblate itself via it’s adminstration panel. So I don’t see how anything is duplicate here. Both tickets talk about completely different things. This ticket here is still open because when we upgrade Weblate to the latest version, you’ll likely have some work to do here again, at least verify that all is correct. If you prefer, let’s rename this ticket to “Verify Weblate setup after upgrade”.

> We can move the pending tickets to the remaining ticket then.

If you want to move the subtasks from Feature #11759 somewhere else, go ahead.

#14 Updated by bertagaz 2018-05-10 11:09:05

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

#15 Updated by intrigeri 2018-06-26 16:27:41

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

#16 Updated by Anonymous 2018-08-17 15:18:07

• Status changed from Confirmed to Resolved

#17 Updated by intrigeri 2019-06-27 17:16:41

• Assignee deleted (emmapeel)