Tails

#1 Updated by intrigeri 2017-12-12 08:24:09

• blocks Feature #13244: Core work 2017Q4: Foundations Team added

#2 Updated by intrigeri 2017-12-23 09:29:06

• Description updated
• Status changed from Confirmed to In Progress
• % Done changed from 0 to 10

Added current status + spec.

#3 Updated by intrigeri 2017-12-23 10:15:37

• % Done changed from 10 to 20

The cheapest solution I can think of is maintaining this list on a blueprint on our website. It satisfies all the MUST but for “Display the bug title in that list” we need to maintain a copy of that metadata in the blueprint, which is a bit painful but probably acceptable.

I initially thought we could address most of the other requirements with a little bit of client-side JS but any call to the GitLab Issues API must be authenticated, so I don’t see how we use it on our (static) website. This could be solved this way:

• use the blueprint only as a list of issues
• host a nice web page somewhere on our infra:
  • retrieve the list of issues from the blueprint
  • authenticate to GNOME’s GitLab and retrieve metadata for these issues
  • generate (statically or dynamically) a HTML table with the data (and optionally include JS to filter & sort)

I don’t think we need to go that far initially but it would be much nicer so once I’ve implement the cheap, 100%-blueprint-based approach, I’ll file a “Starter” ticket so any interested contributor can write this piece of code :)

#4 Updated by intrigeri 2017-12-23 10:44:03

• Description updated

#5 Updated by intrigeri 2017-12-23 11:04:46

• Assignee changed from intrigeri to anonym
• % Done changed from 20 to 50
• QA Check set to Ready for QA

Done. What do you think?

Please reassign to me if happy so I can set Redmine up for the next (bonus) steps.

#6 Updated by intrigeri 2018-01-01 16:38:01

• blocked by deleted (Feature #13244: Core work 2017Q4: Foundations Team)

#7 Updated by intrigeri 2018-01-01 16:38:06

• blocks Feature #13245: Core work 2018Q1: Foundations Team added

#8 Updated by anonym 2018-01-23 19:52:53

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

#9 Updated by intrigeri 2018-01-25 11:53:20

• Assignee changed from anonym to intrigeri
• QA Check changed from Ready for QA to Dev Needed
• Blueprint set to https://tails.boum.org/blueprint/GNOME_bugs_that_affect_Tails/

More projects were moved to GitLab so I’ll have to update the blueprint.

#10 Updated by intrigeri 2018-02-16 14:05:49

• Assignee changed from intrigeri to anonym
• QA Check changed from Dev Needed to Ready for QA

intrigeri wrote:
> More projects were moved to GitLab so I’ll have to update the blueprint.

Actually they have moved Git but not bug tracking yet. For example, GNOME Shell developers want to first gain a bit of experience with GitLab before they make a decision. So:

• please take a first look at my proposal
• this ticket will remain open as a continuous task for me (adding links to the blueprint as GNOME projects move their issue tracking to GitLab) until all our “AffectsTails” bugs have been migrated, which can take months

#11 Updated by bertagaz 2018-03-14 11:32:27

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

#13 Updated by intrigeri 2018-04-08 13:56:21

• blocked by deleted (Feature #13245: Core work 2018Q1: Foundations Team)

#14 Updated by intrigeri 2018-04-08 13:56:25

• blocks Feature #15139: Core work 2018Q2: Foundations Team added

#15 Updated by bertagaz 2018-05-10 11:09:31

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

#16 Updated by intrigeri 2018-05-25 10:26:39

• Assignee changed from anonym to segfault
• Estimated time set to 0 h

segfault, can you please quickly review my reasoning and implementation?

#17 Updated by segfault 2018-05-26 20:57:14

• Assignee changed from segfault to intrigeri
• Estimated time deleted (0 h)
• QA Check changed from Ready for QA to Pass

intrigeri wrote:
> segfault, can you please quickly review my reasoning and implementation?

Looks good to me.

#18 Updated by intrigeri 2018-05-27 07:24:54

• Target version changed from Tails_3.8 to Tails_3.9
• % Done changed from 50 to 60
• QA Check deleted (Pass)

Thank you segfault!

Now:

intrigeri wrote:
> * this ticket will remain open as a continuous task for me (adding links to the blueprint as GNOME projects move their issue tracking to GitLab) until all our “AffectsTails” bugs have been migrated, which can take months

GNOME is now in the process of migrating all remaining bugzilla tickets. I’ve subscribed to those we’ve tagged so I’ll know when they’re migrated and will update the blueprint continuously.

#19 Updated by intrigeri 2018-05-27 07:25:15

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

#20 Updated by intrigeri 2018-05-27 07:25:24

• blocked by deleted (Feature #15139: Core work 2018Q2: Foundations Team)

#21 Updated by intrigeri 2018-05-27 07:25:31

• blocks Feature #15506: Core work 2018Q4: Foundations Team added

#22 Updated by intrigeri 2018-10-12 20:34:49

• Status changed from In Progress to Resolved
• Assignee deleted (intrigeri)
• % Done changed from 60 to 100
• QA Check set to Pass

I’ve updated the blueprint with all the tickets that got migrated since last time I work on this. GNOME is now done migrating but some projects decided to stick to Bugzilla for now, so we’ll have to live with two lists for a while.