Thanks, maybe we can use the branch from https://github.com/apache/sling-site/tree/scm-project-url-list <https://github.com/apache/sling-site/tree/scm-project-url-list> (mentioned in https://issues.apache.org/jira/browse/SLING-7161 <https://issues.apache.org/jira/browse/SLING-7161>) as a basis instead. That provides already much more information and leveraging the already existing xml file from sling-aggregator is a good idea as long as https://issues.apache.org/jira/browse/SLING-7262 <https://issues.apache.org/jira/browse/SLING-7262> is not resolved. Konrad
> On 26. Jan 2018, at 18:05, Bertrand Delacretaz <bdelacre...@apache.org> wrote: > > Hi, > > On Fri, Jan 26, 2018 at 12:54 AM, Alexander Klimetschek > <aklim...@adobe.com.invalid> wrote: >> ... >> 1. restore the apache/sling named repo... >> 2. have a readme in there as the github landing page, just like any github >> project nowadays, >> which should include an about project and most information how to use >> sling/download it... > > I like the idea in general, thanks! > > We already have download/build information on our website, I think we > shouldn't duplicate - so either remove the webiste info or point to it > from that README, but create something consistent and that does not > easily get stale. > > For now, I have created a list of all our repositories at > http://sling.apache.org/repolist.html based on the XML list of > projects generated at https://github.com/apache/sling-aggregator. It > would be nice to expand it with a few words about each repository but > I haven't checked how to generate that so far - and whether that would > interfere with the repo tool. > > -Bertrand
