You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by Robert Munteanu <ro...@apache.org> on 2024/12/10 14:18:17 UTC
Updating github.com/apache/sling redirect
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.
Re: Updating github.com/apache/sling redirect
Posted by Robert Munteanu <ro...@apache.org>.
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
> <jh...@googlemail.com.invalid> wrote:
> >
> > makes totally sense, +1
> >
> > Am Di., 10. Dez. 2024 um 15:18 Uhr schrieb Robert Munteanu <
> > rombert@apache.org>:
> >
> > > 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
Re: Updating github.com/apache/sling redirect
Posted by Julian Sedding <js...@gmail.com>.
+1
Julian
On Tue, 10 Dec 2024 at 22:48, Jörg Hoh <jh...@googlemail.com.invalid> wrote:
>
> makes totally sense, +1
>
> Am Di., 10. Dez. 2024 um 15:18 Uhr schrieb Robert Munteanu <
> rombert@apache.org>:
>
> > 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
Re: Updating github.com/apache/sling redirect
Posted by Jörg Hoh <jh...@googlemail.com.INVALID>.
makes totally sense, +1
Am Di., 10. Dez. 2024 um 15:18 Uhr schrieb Robert Munteanu <
rombert@apache.org>:
> 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
RE: Updating github.com/apache/sling redirect
Posted by Stefan Seifert <st...@diva-e.com.INVALID>.
+1
stefan
Re: Updating github.com/apache/sling redirect
Posted by Konrad Windszus <ko...@windszus.net>.
Sounds good to me.
Konrad
> On 10. Dec 2024, at 15:18, Robert Munteanu <ro...@apache.org> wrote:
>
> 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.
Re: Updating github.com/apache/sling redirect
Posted by Konrad Windszus <kw...@apache.org>.
+1
Konrad
> On 10. Dec 2024, at 15:18, Robert Munteanu <ro...@apache.org> wrote:
>
> 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.