Thanks all. Created [1] for the ASF Infra team. [1]: https://issues.apache.org/jira/browse/INFRA-26366
On Wed, 2024-12-11 at 08:48 +0100, Julian Sedding wrote: > +1 > > Julian > > On Tue, 10 Dec 2024 at 22:48, Jörg Hoh > <[email protected]> wrote: > > > > makes totally sense, +1 > > > > Am Di., 10. Dez. 2024 um 15:18 Uhr schrieb Robert Munteanu < > > [email protected]>: > > > > > Hi, > > > > > > https://github.com/apache/sling has redirected to > > > https://github.com/apache/sling-old-svn-mirror for at least 6 > > > year now. > > > The reasoning back then was to make sure that whatever links were > > > floating around to the git-SVN mirror were not broken. > > > > > > I think that concern no longer applies and right now it's more > > > important to have a friendlier top-level > > > https://github.com/apache/sling repository. > > > > > > I therefore propose the following: > > > > > > 1. Ask INFRA to redirect to > > > https://github.com/apache/sling-aggregator/ > > > instead. This is a repository we control and as close as it gets > > > to > > > 'front door to Sling on GitHub'. > > > > > > 2. Update the aggregator README to be geared more towards Sling > > > users, > > > e.g. briefly explain what Sling is and provide some top-level > > > links. > > > Right now the aggregator README assumes they what a full Sling > > > checkout > > > . > > > > > > 3. Once everything is ready, ask INFRA to rename sling-aggregator > > > to > > > sling and we now have a nice, short, repository name on GitHub. > > > > > > Thoughts? > > > > > > Thanks, > > > Robert > > > > > > Disclaimer: no new Git repositories will be created as part of > > > the > > > implementation. > > > > > > > > > -- > > https://cqdump.joerghoh.de
