On Wed, May 23, 2018 at 5:56 PM, Daniel Klco <[email protected]> wrote: > ...Shields.io seems to be a pretty common standard for GitHub projects so what > if we just use these rather than self-hosting?...
Thinking about it, I suggest using both self-hosted and dynamic badges, for different purposes: a) Self-hosted SVG badges under http://sling.apache.org/res/badges for static repository attributes like deprecated, contrib etc. AFAIK we can copy badges generated at http://shields.io/ there, that website doesn't seem to have any usage restrictions. Having well-known URLs that we control for those makes sure they are consistent and allows us to detect them in scripts. The http://sling.apache.org/repolist.html page for example can be improved to include the badges by parsing the modules README files for badges based on those well-known URLs. And the downloads page could also use that maybe instead of duplicating information by splitting modules in lists. b) Dynamic badges for build results etc., things that are not static attributes of the code repositories WDYT?
