#3200 provenpackager nomination for fche
Closed: Insufficient data by zbyszek. Opened by fche.

I'd like to become a provenpackager. I've packaged or helped package several lowish level RPMs for tens of years, plus investigated packaging nits in many different packages over time. I have been working with fedora infrastructure here and there for 5+. With the security SIG reforming, I may need to be able to make small emergency fixes to packages outside my normal set.

I've read the Provenpackager policy and I will abide it.


I sent the mail to packager-sponsors@fedoraproject.org. I hope I did that correctly.

+0

Please take the following as a mechanical evaluation that doesn't reflect on you as a person. For people with whom we don't work very closely, we sometimes need to look at recorded activity as a crutch. It's always a poor and partial view.

I'm seeing 6 successful koji builds in 2023, just a handful in 2024 and 2022… Not many pull requests or fedora-devel posts. Even if all that is high quality, it doesn't seem enough to warrant jumping to pp access to all packages. I think an intermediate step of more public activity via pull requests and issues must happen first.

+0

I agree with @zbyszek, but I'm going to take it a step further and explicitly vote -1 for now. Frank, you've done good work in the past, but without recent data and a clear view of what changes you need to make, I don't think it's the right time for this promotion.

On the other hand, if you need a provenpackager to help with specific tasks, I'll volunteer to assist.

Hi Frank, you are a legend. Thanx a lot for all your work on Fedora

+1

by me.

https://docs.fedoraproject.org/en-US/fesco/Provenpackager_policy/#_becoming_provenpackager

You must get at least 3 positive votes from sponsors with no negative votes, over a one week review period, to be approved.
If you haven’t been approved after one week, FESCo will vote (normal FESCo voting machanism applies).

As a side not, I noticed a typo in "mechanism", fix in https://pagure.io/fesco/fesco-docs/pull-request/87

This will be discussed during the FESCo meeting today.

Metadata Update from @zbyszek:
- Issue tagged with: meeting

After discussion in the FESCo meeting today, we agreed that the request is withdrawn. (And may be resubmitted later on.)

Metadata Update from @zbyszek:
- Issue untagged with: meeting
- Issue close_status updated to: Insufficient data
- Issue status updated to: Closed (was: Open)

Metadata