Hi Alex, Thanks for taking this discussion to the dev list, there is a real need to improve our landing page.
Please see my individual response below. I'm explaining the process we went through to arrive at this situation, not countering your arguments. In the end I'm happy to work with whatever solution we have an agreement on, including reversing the current approach. On Thu, 2018-01-25 at 23:54 +0000, Alexander Klimetschek wrote: > 1. restore the apache/sling named repo, since that should help with > SEO and "keeping" the existing brand If you go to https://github.com/apache/sling it still works, just that you're redirected to another repo. > > 2. have a readme in there as the github landing page, just like any > github project nowadays, which should include an about project and > most information how to use sling/download it, find source repos and > how to build it. Similar to the project information page [3], but > more easily digestible with less text. Fully agreed, we can easily do this as a one-off change. > > 3. move the aggregator [2] to apache/sling, as that feels like a > natural place (since this all happens on the new "master" branch, > there is no conflict with the old sling code base in there) The constraint that we worked with is that many links would be pointing to https://github.com/apache/sling and these would be broken if we added another 'sling' repository to the mix. So we decided to keep the old 'sling' repository in place, renamed, so links would not break. We also switched the default branch so that people would not start browsing the code since it's now outdated. What is presented on the landing page is actually https://svn.apache.org/repos/asf/sling/branches/archived/ > 4. have a curated list of repos in there (could be a separated > markdown prominently linked from the main readme given its size), > which would provide some categorization and e.g. start with the > important stuff at the top. Guidelines for creating new > repos/changing repos should hint at updating this readme. But even if > it's not 100% up to date all the time, the vast majority of repos > that don't change over time will be explorable. The Sling SVN repository is read-only to make sure we don't accidentally commit changes there. We would need to go through infra for each change so frequent updates Thanks, Robert
