@Bertrand, Personally, I had a lot of trouble figuring out where to go to find / how to efficiently check out the code for Sling after the move to GitHub. I'd suspect that a majority of potential contributors would be coming through GitHub, so I'd highly suggest we put some effort in to make it easier to understand how the individual modules contribute to the overall Sling application.
I do not think it would take a significant effort to do as @Alex proposes and make the sling/sling repository as the starting point with the aggregator, update the submodule readme files to have a getting started shell and point users back to to the sling/sling repository to get started. As for having a list on the site, it's always nice to have multiple repetitions as long as we keep them in sync automatically. On Mon, Jan 29, 2018 at 4:44 AM, Bertrand Delacretaz <bdelacre...@apache.org > wrote: > On Mon, Jan 29, 2018 at 10:30 AM, Nicolas Peltier > <npelt...@adobe.com.invalid> wrote: > > ...I agree having one list might be better, but wouldn’t it make sense > to have the list in GitHub, to avoid ping-pong > > if you come from GitHub browsing ?... > > I don't think it makes much of a difference as long as things are > properly linked. It's not like we have millions of users hitting those > URLs ;-) > > What's important for me is to have an autogenerated list so it doesn't > become stale, if needed adding tags or badges to the repositories to > get a better classification (see other thread about that from 2 > minutes ago). > > And whoever does the work decides ;-) ...so far I did that for > http://sling.apache.org/repolist.html but I'm open to improvements of > course, including moving if there's consensus on that > > -Bertrand >
