Project

General

Profile

Feature #14540

Survey platform

Added by sajolida 10 months ago. Updated 22 days ago.

Status:
Confirmed
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
-
Start date:
10/03/2017
Due date:
% Done:

89%

QA Check:
Feature Branch:
Type of work:
Research
Blueprint:
Starter:
Affected tool:

Subtasks

Feature #14768: Estimate cost of sysadmin work for a 1-time use survey platformResolved

Bug #14769: Fix handling of the nginx access.log on www.lizardResolved

Feature #14795: Requirements for LimeSurveyResolvedintrigeri

Feature #14827: Set up VM for LimeSurveyResolved

Feature #14828: Notify LimeSurvey admins when a security update is availableResolved

Feature #14859: Set up basic monitoring of LimeSurveyResolvedintrigeri

Feature #14881: Document the survey platform in /contributeResolved

Feature #15466: No notifications from LimeSurvey since LimeSurvey 2.72.2 (November 10)Confirmedintrigeri

Feature #15467: Cannot update backups of LimeSurveyResolved


Related issues

Blocks Tails - Feature #15392: Core work 2018Q2 → 2018Q3: User experience Confirmed 03/09/2018
Blocks Tails - Feature #14545: Quantitative survey of our user base Confirmed 08/30/2017

History

#1 Updated by sajolida 8 months ago

  • Parent task set to #14474

#2 Updated by sajolida 7 months ago

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

#3 Updated by sajolida 6 months ago

  • Parent task deleted (#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 6 months ago

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

#5 Updated by anonym 5 months ago

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

#6 Updated by sajolida 3 months ago

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

#7 Updated by sajolida 3 months ago

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

#8 Updated by sajolida 3 months ago

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

#9 Updated by sajolida 2 months ago

  • 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 (#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 #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 2 months ago

#11 Updated by intrigeri about 2 months ago

  • 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 about 2 months ago

  • 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 26 days ago

  • 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 22 days ago

  • 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: #15466.

Yeah!

Also available in: Atom PDF