#2404 Request to be a provenpackager sponsor/administrator
Closed: Accepted by cverna. Opened by churchyard.

I like to have a right to add new provenpackagers, so I can handle tickets like https://pagure.io/fesco/issue/2398 to cover for @kevin when he's swamped with other tasks (such as he is now with the DC move).

The current list of people with the right is:

https://admin.fedoraproject.org/accounts/group/members/provenpackager/*/administrator

From that, only @kevin is on FESCo.

I am happy if somebody else on FESCo has this right, it doesn't have to be me, but I am volunteering to do it.


I think everybody on FESCo should have these rights. We have policies written around that so it should not be a big deal.

I think everybody on FESCo should have these rights.

I can fully support this idea.

+1 for giving the privilege to Miro

-1 for giving the privilege to everyone on FESCo: I think it's prudent to keep this significant privilege limited. For example, I don't expect I'd ever make use of this. OTOH, for people who ask for it because they actually want to get involved in this and make use of it, I'd always vote +1.

I think it makes sense to have members of FESCo who are provenpackagers to get the admin (or at least sponsor) role automatically. This helps to ensure there's a broader group of people who can handle these requests. Looking at the current list, there are a lot of names that I don't see around much these days.

I'd even be okay with FESCo members who aren't provenpackagers to get the sponsor bit while they're on FESCo. The way I see it, FESCo members are elected by the community because they're trusted to make technical decisions for Fedora. Being able to perform a bureaucratic operation related to packaging seems well within the scope of that mandate.

Another alternative would be to grant sponsor/admin status to FPC members instead. In either case, the point is to ensure there are people available who can push the appropriate button.

Another alternative would be to grant sponsor/admin status to FPC members instead.

Since the procedure of becoming a provenpackager happens in the fesco tracker, I'd rather not mix FPC into the process (because at the end, only members of both groups will be able to take the appropriate action).

I'm fine giving more folks that ability (less work for me is always great :)

Granting this for everyone in fesco and then removing it when they left would be more work, IMHO, and you do have the case of fesco members that are not provenpackagers at all.

How about instead we provide a path for this like being added to provenpackager? ie, @churchyard could simply open a "I'd like to be a provenpackager sponsor" and collect votes for a week, etc?

In any case, I think it would be good to have a few more active people to handle these requests... however we choose them.

I don't think sponsors need to vote about this. Neither I think a framework for this is necessary. I'm not asking to be able to give out provenpackager rights as I see fit, I only ask for the tool to be able to handle the tickets.

What shall we do with this? I'd like to keep the request simple: "Add @churchyard as administrator of provenpackager group."

If anybody thinks we need a better long term solution, we can discuss this afterwards.

My vote stands, i.e. still +1.

+1 for adding Miro

+1 for adding Miro too.

+1 for adding Miro.

+1 for adding Miro

APPROVED (+6, 0, -0)

@kevin, could you please add me?

Metadata Update from @churchyard:
- Issue assigned to kevin
- Issue tagged with: pending announcement

I've upgraded your provenpackager membership. :) Enjoy!

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

Thank you! Keeping open for announcement.

BTW Whoever wants to propose a more sophisticated approach, feel free to do so.

Metadata Update from @churchyard:
- Assignee reset
- Issue status updated to: Open (was: Closed)

Announced in https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/EFW5QEMGQBTPTQWGC5775QVZHMKTMW4T/

Metadata Update from @cverna:
- Issue close_status updated to: Accepted
- Issue status updated to: Closed (was: Open)

Metadata