On Friday 12 January 2018 15:34:52 Daniel Klco wrote: > All, Hi Dan,
> Having followed the migration from SVN -> GitHub, I have to admit that I > still find it challenging to navigate the new GitHub structure. > > Based on what I've seen with Sling and other Apache projects, I wonder if > we could do the following to make it easier for new users: > > > - Include link in every README back to the Sling Aggregator project, > instructing users who want to understand the codebase to begin there > - Have the Sling Aggregator write out a list of all of the Sling project > pages > - Add CONTRIBUTING.md and CODE_OF_CONDUCT.md linking back to the pages > on the Sling / Apache sites into every repo > - Hook up tools like Code Climate, Coveralls and TravisCI to run on > commit > - Any other ideas? > > I'd think some of these things we could do pretty simply with a script, and > some we'd probably want to do one at a time as we do new releases. > > Any thoughts, questions or concerns? have a look at SLING-7331 (wip). You will find a script in branch tooling for processing repos and POMs and a new index at https://oliverlietz.github.io/apache-sling-aggregator/. Not sure if we need CONTRIBUTING.md and CODE_OF_CONDUCT.md in every repository if we polish our main site. Regards, O. > Regards, > Dan
