#12739 Fix group 'db-sig'
Closed: Fixed with Explanation by kevin. Opened by mschorm.

The main goal is to revive this historical group.

The group currently consists of Red Hat employees from the Red Hat Databases team, who maintain these components both in Fedora and RHEL.

The employees come and go, or transition, so number of the users are not supposed to be there anymore, and new are missing.
Honza Horak and Pavel Raiskup (the only group sponsors) both transitioned from our team, so the plan is for them to remove themselves, once I'm made the new group sponsor.

I'm looking for a better and more flexible way to maintain access for this group of Red Hat employees to the components they maintain, than setting the user list on every such component.
That's why I want to promote this group to a packaging group.

--

2 issues here:

1)
please add 'mschorm' as a sponsor of the group

2)
Fix the group so it can be added as a maintainer of a package (help me make it a proper packaging group)


2)
fix the group so it can be added as a maintainer of a package

It looks like the group db-sig isn’t known to Pagure yet:

pagure=> select * from pagure_group where group_name='infra-sig';
 id | group_name | display_name |   description   | group_type | user_id |          created           
----+------------+--------------+-----------------+------------+---------+----------------------------
  5 | infra-sig  | infra-sig    | Group infra-sig | user       |     791 | 2017-08-04 16:39:59.657293
(1 row)
pagure=> select * from pagure_group where group_name='db-sig';
 id | group_name | display_name | description | group_type | user_id | created 
----+------------+--------------+-------------+------------+---------+---------
(0 rows)
pagure=>

I’m not sure if this is supposed to be added manually to the database, or if groups are synchronized via a cron job or similar – couldn’t find anything pertinent in the SOPs.

As a current sponsor of the db-sig, let me provide my +1 for @mschorm becoming a sponsor.

A packaging group has a number of requirements over just a tracking group.

https://docs.fedoraproject.org/en-US/infra/howtos/groups_in_fedora/#_pkgdb_groups

In particular, we need to make a private mailing list, set some properties on the group, add it to src.fp.o and then you will need to create a bugzilla user for it.

I added the whole story to the ticket description.

Yes Kevin, that's what I'm aiming for.
I can provide the necessary info when I'm made the group sponsor.

+1, please make @mschorm a sponsor.

Metadata Update from @phsmoura:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: low-gain, low-trouble, ops

Metadata Update from @kevin:
- Issue assigned to kevin

ok. I think I have setup everything except the bugzilla account. I will leave that to you. ( db-sig@lists.fedoraproject.org )

Please let me know if you see anything amiss!

Sorry for the delay here.

Metadata Update from @kevin:
- Issue close_status updated to: Fixed with Explanation
- Issue status updated to: Closed (was: Open)

Thanks @kevin
I created and configured the BZ account.

All I need now is clarification to some aspects I'm not familiar with:

1) What happens when a user that is not a packager is part of the group, and that group is added as a commiter to a package?
Will the user outside of package group be restricted from pushing commits? (that's what I would expect)

2) Do groups receive any kind of Fedora notifications, as set in
https://notifications.fedoraproject.org/ ? (I configured the ones in BZ)

I'd like to avoid duplicate notifications from packages for people who are part of the group and get the notifications from a given package for their own accounts already.

1) I think your expectation is correct. I think when we moved to ipa we tried to setup things so there would be requirements on some groups, but there was not any way to refect that.
But without 'packager' group someone in a pkgdb group still wouldn't be able to push any changes.

2) Sadly no, the notifications are per user only (as far as I know). You (as a user) could add a notification about a group, but you can't enable notifications for the entire group.
( @abompard right? )

Metadata