[
https://issues.apache.org/jira/browse/SLING-7684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16509654#comment-16509654
]
Dan Klco commented on SLING-7684:
---------------------------------
[~jsedding] Thanks! I was able to run the script against all of the repos and
get the results committed. I'm going to make a few minor tweaks to the script
and then check it into the sling-aggregator project so that we can make it part
of the process.
Every Sling repo *should* now have at least one badge and the logo, as well as
additional badges as relevant, the sling-aggregator also contains all of the
Maven based repos:
[https://github.com/apache/sling-aggregator/blob/master/docs/modules.md]
As well as specific pages for the groups as defined in the default.xml file:
[https://github.com/apache/sling-aggregator/blob/master/docs/groups/auth.md]
And status as defined in the CSV file:
[https://github.com/apache/sling-aggregator/blob/master/docs/status/contrib.md]
I admit I am not in love with the concept of using a CSV or other data file to
track status, but I'm not sure I can think of a better format.
> Add Badges to GitHub Repo Readmes
> ---------------------------------
>
> Key: SLING-7684
> URL: https://issues.apache.org/jira/browse/SLING-7684
> Project: Sling
> Issue Type: Task
> Reporter: Dan Klco
> Assignee: Dan Klco
> Priority: Minor
> Attachments: Sling-Repos.csv, features-page.png, modules-page.png,
> project-readme.png, readrepo.sh
>
>
> Add badges to the README.md files in all of the GitHub repositories
> indicating important status items, links to other resources and other good
> information. Currently looking into:
> *Static Badges*
> * Contrib
> * Deprecated
> * Testing(?)
> * Tooling(?)
> * License
> *Dynamic Badges*
> * Build Status
> * Tests
> * Maven Central
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
