I've recently noticed that there is a Fedora badge that can be used in GitHub readme files to show what version of a software is available in the Fedora repositories:
https://github.com/nest/nest-simulator/blob/master/README.md
The markdown code is:
[](https://src.fedoraproject.org/rpms/nest)
One can go to shields.io to generate these for any package in markdown or rst (or other formats).
So, when we package something from GitHub, it'll be good to open pull requests to show that it is now available in Fedora. That'll increase visibility.
I've also just e-mailed the -devel list about this: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/EKUF7REIIG6TOBNOTFOQLRFDRS6FUZMK/
What do people think of this?
(If it's a good idea, we can think about adding this to @vanessa_kris 's outreachy task list. it's a simple enough task, and good git practice too)
Thanks @ankursinha! It is good to know Fedora badges.
I will generate badges for some of packages I maintain.
Just a note. For Python packages, use the name of the rpm, not the source rpm. So python3-xx instead of python-xx.
python3-xx
python-xx
For consistency, let us:
So it'll come out something like this:
If you've seen the discussion on the -devel list, you'll see that we can also use repology packages but I have a couple of minor concerns with them that I've also noted in the thread. So for a start, I think we can stick to shields.io badges and upstream can modify them to use repology if they wish.
Log in to comment on this ticket.