Project

General

Profile

Bug #15042

Migrate away from our GNOME "AffectsTails" keyword

Added by intrigeri 8 months ago. Updated 3 months ago.

Status:
In Progress
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
Start date:
12/12/2017
Due date:
% Done:

60%

QA Check:
Feature Branch:
Type of work:
Contributors documentation

Description

GNOME is moving from Bugzilla to their own GitLab instance and we won't get an AffectTails label there, so we need to devise & implement something to replace the "AffectsTails" keyword we've been using on their Bugzilla.

This is currently about 19 open bugs on Bugzilla plus one that's been migrated to GitLab already. I think this number will keep growing: we apply this keyword to bugs faster than they get fixed.

MUST:

  • Publish a usable list of GNOME bugs that affect Tails on a stable URL.
  • Display the bug title in that list.
  • Anyone can easily add a bug to the list (having to create an account somewhere is OK, needing special privileges is not).

SHOULD:

  • Make it clear which bugs were resolved upstream (e.g. allow listing only open ones or automatically strikethrough those that were resolved).

MAY:

  • Display bugs metadata e.g. affected product, bug title, last update time.
  • Allow filtering & sorting based on metadata.

Related issues

Blocks Tails - Feature #15506: Core work 2018Q4: Foundations Team Confirmed 04/08/2018

Associated revisions

Revision 87baa1b6 (diff)
Added by intrigeri 8 months ago

Get ready for GNOME moving to GitLab (refs: #15042)

History

#1 Updated by intrigeri 8 months ago

#2 Updated by intrigeri 8 months ago

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

Added current status + spec.

#3 Updated by intrigeri 8 months ago

  • % 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 8 months ago

  • Description updated (diff)

#5 Updated by intrigeri 8 months ago

  • 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 8 months ago

#7 Updated by intrigeri 8 months ago

#8 Updated by anonym 7 months ago

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

#9 Updated by intrigeri 7 months ago

  • 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 6 months ago

  • 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 5 months ago

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

#12 Updated by intrigeri 5 months ago

I'm tracking the next steps and will create tickets on our side once there's something else for us to do.

#13 Updated by intrigeri 4 months ago

#14 Updated by intrigeri 4 months ago

#15 Updated by bertagaz 3 months ago

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

#16 Updated by intrigeri 3 months ago

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

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

#17 Updated by segfault 3 months ago

  • Assignee changed from segfault to intrigeri
  • Estimated time deleted (0.25 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 3 months ago

  • 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 3 months ago

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

#20 Updated by intrigeri 3 months ago

#21 Updated by intrigeri 3 months ago

Also available in: Atom PDF