I really like the Per-Release Contribution Badge, but I'd prefer it be per major release, while this makes it sound like you want it per minor release. Per minor release sounds like alot of recurring work that someone needs to do.
I also like the Package Promoted from EPEL to RHEL. Having numbers attached to that, seems very ambitious and like it's something people have any influence over.

Given how well our last badge request went (it's still just sitting there), how about we just go for 1 badge first. Of all the badges I think we need, I think it's the EPEL to RHEL badge.

I agree about per-release being per major release, and I think that may have been what @neil meant. We should make sure we're clear on that in the badge wording when we get to that point.

I agree about the promoted badge being the most important, as that would be a nice achievement for contributors to feel good about, and be achievable for a large number of contributors. The steering committee one would be nice to finish up, could be manually awarded to a small number of people, but would have a lower impact by nature.

I think early badge and the promoted badge would make the most sense as manually awarded badges, but in theory it should be possible to automate the per-release badge (pending what that looks like after badges gets overhauled).

Yes, I've updated the post to be more clear that there are two different proposals for per-release. The first being "per major release" and the latter being per minor:

We also propose the idea of creating recurring badges for each EPEL release starting from EPEL 10 onward. While this would increase the effort required to generate these badges every six months, re-using similar artwork could simplify the process.

I don't have a strong opinion on the per-minor bit--seems like a lot of extra work right now.

Also agreed on the leveling for the EPEL->RHEL badge; I threw that in last minute to add variety :P

It's also worth mentioning that we have a handful of existing badges for EPEL activity.

• Corporate Drone (one EPEL update)
• Corporate Shill (50 EPEL updates)
• Corporate Overlord (200 EPEL updates)

At one point these were working automatically, but I think that has been broken for some time and they've been getting manually awarded. We should get that working too.

It's also been suggested before that we should do badges for EPEL builds and not just updates.

At one point these were working automatically, but I think that has been broken for some time and they've been getting manually awarded. We should get that working too.

My suspicion was incorrect, I confirmed the Corporate badges are still being awarded automatically.

I've filed a badge request for Corporate Promotion for the event of getting a package retired from EPEL due to it being added to RHEL.

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/epel/steering/issues/289

Please continue any further discussion there.