#702 Requesting Sponsor status in Fedora
Closed: accepted by kevin. Opened by ljavorsk.

I would like to become a Sponsor in Fedora to help new contributors join the project and grow the community.

I have been actively involved in Fedora for almost six years, during which I have gained both packager and proven-packager status.

As a sponsor, I would like to mentor and guide aspiring packagers, helping them navigate the process and contribute effectively.

FAS Account: ljavorsk
Maintained Packages (63): View Packager Dashboard
Other Activities: Fedora Badges

I must admit I didn't have too much time for the formal reviews, but in these two, I was either a reviewer or a mentor to a reviewer (colleague):
fim
minizip-ng

PS: I was more into the Fedora Changes, where I have a record of 8 accepted changes in Fedora so far.


Hi Lukas! It looks like you maintain quite a few packages and probibly know packaging pretty well, but not too many reviews yet.

The sponsor guidelines ( https://docs.fedoraproject.org/en-US/fesco/Packager_sponsor_policy/ ) mentions:

"Have done five high quality, nontrivial package reviews" (which is not a hard requirement, but still very nice to have).

Would you perhaps be able to do some more reviews so sponsors could get a better idea?

I know Lukas in person. He is very communicative, and I believe he can help many newcomers. So, +1 from me. But I acknowledge that the low number of package reviews he can prove could be a problem for others.

I would rather not exempt him from this requirement, we've got a lot of people who don't understand the fundamentals of package reviews and that's literally the job of packager sponsors, so no proof of that understanding makes it hard to justify.

Thank you all for the feedback. I viewed the package reviews as something that doesn't prove the skills of a Fedora packager. Yes, it is crucial to do it once or twice to get a good grasp of the packaging guidelines and the good practices. Still, from my 5+ years of experience, I can tell that the actual packaging and getting to know how all of Fedora's tools and services work is much more valuable.

However, if you feel like this should be something I should improve on, I'll try to work on that. I'm planning to do one review for one of my colleagues, and hopefully, I will find some time to do more, even though since I have quite a lot of other responsibilities, it's harder to find some extra.

I viewed the package reviews as something that doesn't prove the skills of a Fedora packager.

The reviews shows how you communicate with people that are new to packaging and new to Fedora. We saw people in past that communicate... not well. So technical knowledge is only a part of good traits of Sponsor.

Also, package reviews expose the reviewer to different language ecosystems and special corners of the distribution, as well as different ways of thinking about and doing packaging. In my experience, doing reviews regularly is important to keep up with the developments in the other parts of the distro.

Once you are a sponsor, doing package reviews is an important part of that. Please do the handful of reviews recommended by the guidelines.

Hi,

I’ve incorporated your feedback and completed two additional non-trivial package reviews [1][2].

Additionally, I led a sponsoring session for two of our new hires at Red Hat, who successfully became packagers under the supervision of @msuchy. During these sessions, I gained valuable insights from Mirek on the foundational principles of Fedora key knowledge essential for new packagers.

Could you please re-evaluate my request?

[1] MySQL-8.4
[2] credcheck

Gentle ping @ngompa @zbyszek @kevin

Hey @ljavorsk

I'm +1 to this request now, those reviews looked thoughtfull and had a nice amount of explaining things and back and forth.

Other sponsors: votes?

I'm okay with him becoming a sponsor too. +1

+1

Hi guys, I've been on PTO, but this seems to be stuck.

Should I do some additional work to request the sponsor role?

+1 for the sponsor bit too

Sorry about that. I see 4 +1s and 0 -1's so this request is approved.

Use your powers wisely!

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

Metadata