On Wed, 2017-10-04 at 10:01 +0200, Konrad Windszus wrote: > > On 4. Oct 2017, at 09:57, Robert Munteanu <[email protected]> > > wrote: > > > > On Tue, 2017-10-03 at 17:03 +0200, Konrad Windszus wrote: > > > > On 3. Oct 2017, at 16:35, Bertrand Delacretaz <bdelacretaz@apac > > > > he.o > > > > rg> wrote: > > > > > > > > Hi, > > > > > > > > On Tue, Oct 3, 2017 at 3:50 PM, Konrad Windszus <[email protected] > > > > e> > > > > wrote: > > > > > ...I think we also once discussed on the mailing list where > > > > > to > > > > > put bundle documentation: either in the readme or in the site > > > > > itself... > > > > > > > > Now that we have complete control over the website we might > > > > generate > > > > http://sling.apache.org/documentation/bundles.html (or part of > > > > it) > > > > using the GitHub API, or the module list that we use for > > > > Jenkins, > > > > and > > > > mostly use the module's README.md from now on. > > > > > > That sounds really good. > > > @Robert: Would it be possible to maintain the module list as > > > separate > > > JSON file (currently contained in > > > https://svn.apache.org/repos/asf/sling/trunk/tooling/jenkins/crea > > > te_j > > > obs.groovy). > > > > My plan is to access the repositories using the Sling API rather > > than > > define a big list which can get out of date. > > I guess you mean GitHub API, right :-)?
Right :-)
