Tails

#1 Updated by sajolida 2017-10-16 14:06:31

• Parent task set to Feature #14474

#2 Updated by sajolida 2017-11-14 13:23:09

• Target version changed from Tails_3.3 to Tails_3.5

#3 Updated by sajolida 2017-12-12 10:44:40

• Parent task deleted (Feature #14474)

Seeing the great results of the survey, this work is definitely something that we’ll reuse in the future for general user experience research. So I’m moving this task out of VeraCrypt into Core UX.

#4 Updated by sajolida 2017-12-12 10:44:53

• blocks Feature #14761: Core work 2017Q4 → 2018Q1: User experience added

#5 Updated by anonym 2018-01-23 19:52:51

• Target version changed from Tails_3.5 to Tails_3.6

#6 Updated by sajolida 2018-03-13 13:07:47

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

#7 Updated by sajolida 2018-03-27 20:24:17

• blocked by deleted (Feature #14761: Core work 2017Q4 → 2018Q1: User experience)

#8 Updated by sajolida 2018-03-27 20:24:23

• blocks Feature #15392: Core work 2018Q2 → 2018Q3: User experience added

#9 Updated by sajolida 2018-04-17 07:51:43

• Assignee changed from sajolida to intrigeri
• QA Check set to Info Needed

As discussed elsewhere, I read again the thread we had on tails-ux@ about the platform and all the subtickets of this task.

https://mailman.boum.org/pipermail/tails-ux/2017-September/003472.html

As reservations or limitations on this first implementation, I only found the fact that the email server might not be ready to send emails to all email servers (Feature #14768#note-6). But I don’t think we will need to use the emailing feature of LimeSurvey in the near future.

So in terms of development and once we’ll solve Feature #15466 for good, I think that the platform will be ready for production.

Now regarding the maintenance:

• I’m happy to apply the updates myself as part of UX. It will be pretty fast once I’ll get more into the habit.
• I’m also happy to help with more important updates that might not be as simple to apply.
• Do you think that the rest of the maintenance can be taken over by sysadmins?

#10 Updated by sajolida 2018-04-17 09:39:11

• blocks Feature #14545: Quantitative survey of our user base added

#11 Updated by intrigeri 2018-04-27 09:35:10

• Assignee changed from intrigeri to sajolida

sajolida wrote:
> * I’m happy to apply the updates myself as part of UX. It will be pretty fast once I’ll get more into the habit.
> * I’m also happy to help with more important updates that might not be as simple to apply.

I’m a bit confused by the second sentence: the setup we’ve put in place gives you the power and responsibility to manage the limesurvey service, which includes keeping it up-to-date. So I don’t understand what you mean with “help with more important updates”. But perhaps that’s related to:

> * Do you think that the rest of the maintenance can be taken over by sysadmins?

I can’t speak for them but personally I’d rather stick to the platform/service split we’ve put in place (sysadmins provide the OS, service administrators manage the service).

#12 Updated by sajolida 2018-05-02 11:45:02

• Assignee changed from sajolida to intrigeri
• Target version deleted (Tails_3.7)

Sorry for the unclear formulations.

By “more important updates” I meant upgrades that I couldn’t do only myself through Git. Let’s say some dependencies change and LimeSurvey need more Debian packages or do stuff on the web server or MySQL that I don’t have the permissions to do. But yeah, it probably what you mean by the “platform/service split we’ve put in place”.

I also wanted to clarify if the general maintenance of this VM can be considered part of the sysadmins work. For example, upgrading the VM to a newer version of Debian.

For the first iteration your part of the “platform/service split” was paid with a dedicated budget. I’m wondering now how your part of the split would be paid if we keep this survey platform in the future. But I’m otherwise happy with how the split is done :)

#13 Updated by intrigeri 2018-05-29 08:02:18

• Assignee changed from intrigeri to sajolida

> Sorry for the unclear formulations.

No problem. I’m glad we’re close to having this in production!

> By “more important updates” I meant upgrades that I couldn’t do only myself through Git. Let’s say some dependencies change and LimeSurvey need more Debian packages or do stuff on the web server or MySQL that I don’t have the permissions to do. But yeah, it probably what you mean by the “platform/service split we’ve put in place”.

OK, got it now! This falls nicely into the “Help service administrators set up their service” line of the sysadmin budget (and that section actually lists switching our survey platform to production as an example of what this budget could be used for). I’m happy to be responsible for this part of the sysadmin work on the survey platform.

I think it’ll be very little work because I’ve set things up in a way that gives you plenty of autonomy in the vast majority of cases, e.g. you own your Apache virtual host and you have all privileges on your MariaDB database :)

> I also wanted to clarify if the general maintenance of this VM can be considered part of the sysadmins work. For example, upgrading the VM to a newer version of Debian.

Yes:

• basic day-to-day maintenance will be added to sysadmin shifts [done by bertagaz + groente]
• more involved maintenance such as upgrading to a new version of Debian need to be taken from other existing budget lines (e.g. we have decided to skip Buster but we still have a few hours to upgrade specific VMs to Buster if really needed) and if there’s no such thing yet we can use our “Needs that may pop up along the way” budget line (that’s allocated based on cost/benefit analysis) [done by whoever on the sysadmin team picks it up]

Anything else?

#14 Updated by sajolida 2018-06-01 18:48:49

• Assignee changed from sajolida to intrigeri
• QA Check deleted (Info Needed)

Nope. So we can declare our survey platform in production as soon as the upgrade notifications are fixed: Feature #15466.

Yeah!

#15 Updated by sajolida 2018-10-29 14:20:43

• blocked by deleted (Feature #15392: Core work 2018Q2 → 2018Q3: User experience)

#16 Updated by sajolida 2018-10-29 14:20:49

• blocks Feature #16080: Core work 2018Q4 → 2019Q2: User experience added

#17 Updated by intrigeri 2019-04-07 09:07:59

• Status changed from Confirmed to In Progress
• Assignee changed from intrigeri to sajolida
• QA Check set to Ready for QA
• Type of work changed from Research to Sysadmin

The last subtask is ready for QA, please close this one if happy there :)

#18 Updated by sajolida 2019-04-17 18:46:19

• Status changed from In Progress to Resolved
• Assignee deleted (sajolida)
• Target version set to Tails_3.14
• QA Check deleted (Ready for QA)

Yeah! \o/

#19 Updated by intrigeri 2019-05-05 08:23:55

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

#20 Updated by anonym 2019-05-06 15:03:13

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

#21 Updated by intrigeri 2019-05-06 18:15:38

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