On Sun, Jul 07, 2019 at 03:13:14AM -0600, brynn wrote:
Hi Friends, I'm having trouble setting up notifications for GitLab properly. I want to be notified whenever a bug I've reported has been changed. And otherwise, whenever someone tags my name with @.
So far, I get notified about Vectors team stuff whenever someone uses @all or @brynn. But I haven't gotten a single notification about a bug report. Not even when I post a new bug report.
When you go to the Project page, there is a dropdown with a Bell on it. This has the notification options I think you're looking for.
I would have thought Global Notification would trump allelse. But there are other options below that (for Groups and Projects). So obviously global doesn't trump everything, but in that case, I don't understand how to decide how to set anything. What exactly does global mean for gitlab?
If you have any other projects at gitlab, then global settings affect all of them the same.
Part of the trouble I'm having is that when I look at the main Inkscape page, it has Subgroups and Projects, and lists 13 different items. But up in the dark blue bar at the top, is has dropdown lists for Projects and Groups. None of these 3 areas seem to be consistent.
The top bar is specific to you. For people that have several pieces of software hosted at gitlab (or that are participating in several open source groups), the contents of the dark blue bar will cover all these activities. Whereas the main Inkscape page pertains only to components specific to Inkscape itself (whether or not you've personally participated in them).
For example, why is the main Inkscape project a Group rather than a Project?
In gitlab jargon, a "Group" is what we think of as an Open Source Project, such as Inkscape or Gimp. It seems to work best to think of a Group as a defined collection of people - what we'd call a "team" like Inkscape Vectors or Inkscape Docs. Permissions and access control is handled at the Group level; someone who has rights in a particular Group can use those rights for everything that Group owns.
Groups can own multiple pieces of software, for example we maintain lib2geom in addition to the inkscape core codebase; Gitlab refers to these specific pieces of software as "Projects".
Projects don't need to just be for software, and can be used whereever you want to group some information into a distinct collection. For instance, we use Projects for collecting documentation files. Inkscape's Inbox is a Project, too.
And if groups are the highest level, why don't they have Groups first in the bar, rather than 2nd?
Got me. It's a good question.
Most people probably are coming to gitlab caring about a specific project.
And if Group is the highest level, why is the Vectors team a Group too?
Vectors is a "Sub-Group" of the main Inkscape group. Subgroups let you create organizational hierarchies. We have Sub-Groups for each of Inkscape's main teams - Docs, Infra, Website, etc.
In fact, if we wanted we could add a third level, sub-sub-groups, if for instance Vectors wanted to split out sub-teams we could. Currently I don't think we have so many people involved in the project that this is needed, but maybe some day.
Keep in mind, the main *practical* reason for defining Sub-Groups is that it allows finer grained permissions / access control for git commits, bug management, and so on.
And then when I look at the Notifications page for settings, it has Groups and Projects separate, but it does not identify all the groups or projects in which I've participated, and there isn't any way to add more on my own.
This part has been confusing to me as well, particularly for moving bugs from project to project
Related - When someone migrates one of my bug reports, it's listed under their name. How can I still get notified about changes to those? Do I have to make a reply or mark something?
If you look down towards the bottom of the right side of the bug report you should see a Notifications switch. Toggle that for the bugs you want to follow. Ideally, whomever migrates the bug would add you for notifications, but few reporters will have gitlab accounts.