I usually am reluctant in revisiting old decisions, especially ones
that were so discussed, like this one. Some summaries of previous
discussion are at ,  . But Alex makes some good points and after
the migration I think we should consider whether backwards
compatibility of incoming links is worth the limited control we have
over github.com/apache/sling, which many times is an entry point for
The basic proposal as I see it would be to add a new 'sling' top-level
github repo, which means that:
1. we control what goes in there - README.md most importantly
2. old links to sling commits and files will be broken .
TBH, I am not sure #2 is such a bad thing, given that I've seen people
still link to files in the old repo.