Group related gitlab issue labels

With the documentation revamp week approaching, I think now is a good time to have a look at how we organize our gitlab issue labels. I do not propose a full revamp of the labels as this would be very confusing and break issue tracking. Instead, I would propose to group related labels together.

Grouped issues are easier to find, easier to spot, and consistently sorted in the issue overview. They allow us to maintain a more hygenic issue environment. Note that I am not proposing to scope them, I propose to group them by prefixing them. You can only assign a single label from a given scope to an issue, but by prefixing we can still have multiple of these labels attached to the same issue.

It seems that there are two major types of issue labels that we can categorize: components and processes.

Components

I would propose to prefix these with component: (other suggestions are welcome). I believe the following labels would fall under this:

• component: StorageClass
• component: EOS
• component: File Catalogue
• component: Front end (Admin interface)
• component: Front end (EOS interface)
• component: Front end (gRPC)
• component: FST GC
• component: FTS
• component: Media Changer
• component: MGM GC
• component: mhVTL
• component: Object Store
• component: Postgres Scheduler
• component: Scheduler
• component: Scheduler Algorithms
• component: Tape Server

Processes/workflows

I would propose to prefix these with e.g. process or proc. Perhaps this group can be split up further, as I am not fully happy with this grouping. Suggestions are welcome. For some of these workflow: might also be nice, but this then clashes with out existing workflow scope. A solution could be to update the existing workflow scope to e.g. progress. Again, I don't know the best solution here; suggestions welcome.

• proc: Archival
• proc: Repack
• proc: Retrieve
• proc: Labelling

Possibly also the following:

• proc: Reporting
• proc: Monitoring
• proc: RAO