On Fri, Dec 15, 2017 at 10:56:10AM -0500, Avram Lubkin wrote: > I'm also not sure the best place to point them to. shields.io does let you > set a target for both the left and the right sides, but I just set the > target within readme.rst and pointed both badges to the Bodhi updates page > for the package. > > Anyone have a better way to generate dynamic badges? Should badge > generation be a part of the Fedora infrastructure? I'm for us serving them. Full transparency: shields.io says "no tracking" but that doesn't mean they don't do _counting_. I also have no interest in tracking, but a lot of interest in counting. (How many distinct projects use this? How many people look at them? Super-interesting!) It seems like they don't really need to be dynamic and _could_ just be static content we serve from https://getfedora.org/static/, right? That way, we wouldn't need to stand up a new service or anything ongoing except an update when we put out a new release. That wouldn't allow per-project linking though. If you are doing something dynamic, I'd suggest https://src.fedoraproject.org/ as a target, and then include a README.md with instructions on how to dnf install your package. Anyway: can you file an infrastructure ticket for this? I doubt it will be high priority, but on the other hand, it seems like something an infrastructure apprentice could tackle. -- Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> Fedora Project Leader _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
