Hi, I usually am reluctant in revisiting old decisions, especially ones that were so discussed, like this one. Some summaries of previous discussion are at [1], [2] . 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 developers.
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. Thoughts? Thanks, Robert [1]: https://lists.apache.org/thread.html/9e1ceee36af811ba3d2a0a2baa249 8077281f0d3c1da29747a833ea3@%3Cdev.sling.apache.org%3E [2]: https://issues.apache.org/jira/browse/SLING-7183
