Re: Making github.com/apache/sling a git repo, moving away old svn mirror (Re: apache/sling as github landing repository)

On 27.02.2018, at 22:07, Robert Munteanu wrote: > IIUC the proposal was to import the old svn mirror as a git repo, and > Betrand argued this would be a really large repo, and that's an > impediment for something which would be heavily cloned. You are right. It could be two

Re: Making github.com/apache/sling a git repo, moving away old svn mirror (Re: apache/sling as github landing repository)

On Thu, 2018-02-15 at 20:57 +, Alexander Klimetschek wrote: > On 12.02.2018, at 01:23, Robert Munteanu wrote: > > 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 -

Re: Making github.com/apache/sling a git repo, moving away old svn mirror (Re: apache/sling as github landing repository)

On 12.02.2018, at 01:23, Robert Munteanu wrote: > 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

Re: Making github.com/apache/sling a git repo, moving away old svn mirror (Re: apache/sling as github landing repository)

On Mon, Feb 12, 2018 at 10:23 AM, Robert Munteanu wrote: > ...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

Making github.com/apache/sling a git repo, moving away old svn mirror (Re: apache/sling as github landing repository)

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

Re: apache/sling as github landing repository

Hi Jason, On Sat, 2018-02-10 at 09:24 -0500, Jason E Bailey wrote: > And this would be one of those occasions where I thought I knew what > I was talking about and I was wrong. What I was referencing was > something I was led to believe was submodules but is so convoluted > that I don't want to

Re: apache/sling as github landing repository

And this would be one of those occasions where I thought I knew what I was talking about and I was wrong. What I was referencing was something I was led to believe was submodules but is so convoluted that I don't want to go there. I can see where submodules would be really useful in some

Re: apache/sling as github landing repository

On Thu, Feb 8, 2018 at 4:27 PM, Jason E Bailey wrote: > I'll work on standing something up as a POC so that there is something > tangible... Great, thanks! -Bertrand

Re: apache/sling as github landing repository

I'll work on standing something up as a POC so that there is something tangible. - Jason On Thu, Feb 8, 2018, at 9:29 AM, Bertrand Delacretaz wrote: > On Thu, Feb 8, 2018 at 2:25 PM, Jason E Bailey wrote: > > ...an aggregated view that just reflects the status of

Re: apache/sling as github landing repository

On Thu, Feb 8, 2018 at 2:25 PM, Jason E Bailey wrote: > ...an aggregated view that just reflects the status of submodules... I'm +1 on at least experimenting with that if you can do it without too much effort. -Bertrand

Re: apache/sling as github landing repository

Correct. That's exactly what I was trying to articulate, an aggregated view that just reflects the status of submodules. - Jason On Thu, Feb 8, 2018, at 4:15 AM, Bertrand Delacretaz wrote: > Hi, > > On Thu, Feb 8, 2018 at 1:37 AM, Jason E Bailey wrote: > > ...In either case,

Re: apache/sling as github landing repository

Hi, On Thu, Feb 8, 2018 at 1:37 AM, Jason E Bailey wrote: > ...In either case, you'd end up with a central location with a snapshot of > the latest code that is individually managed in it's own repo IIUC this has no impact on the existing repositories, it's just an

Re: apache/sling as github landing repository

What we have is a jenkinsFile so that, as part of the commit , it triggers the repository that's acting as the uber repository to update it's submodules. This could even be modified slightly so that a given submodule is only updated on it's release rather then every update. In either case,

Re: apache/sling as github landing repository

Git submodules don't work well in this situation, as the will point to a particular revision of the submodule. You'd have to constantly change the super repository whenever there was a commit in a submodule. Sling uses Android's repo for this purpose. The super repo is called sling-aggregator

Re: apache/sling as github landing repository

Has there been any consideration of using git submodules to have a single git repository that reflects all the other repositories? It would allow for a central view, facilitate search, and still maintain a separation of the individual projects. - Jason On Fri, Feb 2, 2018, at 10:16 PM,

Re: apache/sling as github landing repository

On 31.01.2018, at 00:23, Robert Munteanu wrote: > Links to commits and files from the old sling repo. For example > > * https://github.com/apache/sling/commit/368f5f9c9f6d4c0e2602065687d95e > b173f94b85 > * https://github.com/apache/sling/blob/trunk/bundles/extensions/bundler

Re: apache/sling as github landing repository

On Wed, Jan 31, 2018 at 4:05 PM, Robert Munteanu wrote: > ...perhaps we should consider making the aggregator the 'sling' > repository, explaining where the old links went in a README, and > keeping 'sling-old-svn-mirror' without a redirect... That would work for me. As long

Re: apache/sling as github landing repository

On Wed, 2018-01-31 at 10:00 +0100, Bertrand Delacretaz wrote: > Hi, > > On Wed, Jan 31, 2018 at 9:23 AM, Robert Munteanu > wrote: > > On Wed, 2018-01-31 at 00:13 +, Alexander Klimetschek wrote: > > > ... 4. add the aggregator and new landing page readme on the > > >

Re: apache/sling as github landing repository

Hi, On Wed, Jan 31, 2018 at 9:23 AM, Robert Munteanu wrote: > On Wed, 2018-01-31 at 00:13 +, Alexander Klimetschek wrote: >>... 4. add the aggregator and new landing page readme on the master >> branch, which will be push-able for committers... >> > ...The only downside

Re: apache/sling as github landing repository

On Wed, 2018-01-31 at 00:13 +, Alexander Klimetschek wrote: > On 30.01.2018, at 01:38, Robert Munteanu wrote: > > 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

Re: apache/sling as github landing repository

On 30.01.2018, at 01:38, Robert Munteanu wrote: > 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

Re: apache/sling as github landing repository

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

Re: apache/sling as github landing repository

On Mon, Jan 29, 2018 at 7:00 PM, Alexander Klimetschek wrote: > Just to clarify: you guys actually meant "apache/sling", right? Yes, https://github.com/apache/sling should be the "natural" entry point. -Bertrand

Re: apache/sling as github landing repository

On 29.01.2018, at 07:53, Bertrand Delacretaz wrote: > On Mon, Jan 29, 2018 at 4:08 PM, Daniel Klco wrote: >> ...I'd >> suspect that a majority of potential contributors would be coming through >> GitHub... > > Sure, and I agree to make sling/sling

Re: apache/sling as github landing repository

Hi Dan, On Mon, Jan 29, 2018 at 4:08 PM, Daniel Klco wrote: > ...I'd > suspect that a majority of potential contributors would be coming through > GitHub... Sure, and I agree to make sling/sling the default entry point - but it doesn't matter much whether that has the

Re: apache/sling as github landing repository

@Bertrand, Personally, I had a lot of trouble figuring out where to go to find / how to efficiently check out the code for Sling after the move to GitHub. I'd suspect that a majority of potential contributors would be coming through GitHub, so I'd highly suggest we put some effort in to make it

Re: apache/sling as github landing repository

On Mon, Jan 29, 2018 at 10:30 AM, Nicolas Peltier wrote: > ...I agree having one list might be better, but wouldn’t it make sense to > have the list in GitHub, to avoid ping-pong > if you come from GitHub browsing ?... I don't think it makes much of a difference as

Re: apache/sling as github landing repository

I agree having one list might be better, but wouldn’t it make sense to have the list in GitHub, to avoid ping-pong if you come from GitHub browsing ? (Thinking about Alex’s description of the experience of someone arriving on apache/sling GitHub project) > On 29 Jan 2018, at 10:27, Bertrand

Re: apache/sling as github landing repository

On Fri, Jan 26, 2018 at 6:05 PM, Bertrand Delacretaz wrote: > ...I have created a list of all our repositories at > http://sling.apache.org/repolist.html based on the XML list of > projects generated at https://github.com/apache/sling-aggregator And I realize we've

Re: apache/sling as github landing repository

Thanks, maybe we can use the branch from https://github.com/apache/sling-site/tree/scm-project-url-list (mentioned in https://issues.apache.org/jira/browse/SLING-7161 ) as a basis

Re: apache/sling as github landing repository

Hi, On Fri, Jan 26, 2018 at 12:54 AM, Alexander Klimetschek wrote: >... > 1. restore the apache/sling named 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

RE: apache/sling as github landing repository

+1 stefan >-Original Message- >From: Alexander Klimetschek [mailto:aklim...@adobe.com.INVALID] >Sent: Friday, January 26, 2018 12:54 AM >To: dev@sling.apache.org >Subject: apache/sling as github landing repository > >Hi everyone, > >after the move to github and

Re: apache/sling as github landing repository

+1 this absolutely is there right approach for users On Jan 25, 2018 3:54 PM, "Alexander Klimetschek" wrote: Hi everyone, after the move to github and source code modularization (cool), the previous sling repository apache/sling [0] is now empty. Except for a readme

apache/sling as github landing repository

Hi everyone, after the move to github and source code modularization (cool), the previous sling repository apache/sling [0] is now empty. Except for a readme that currently mostly addresses active committers (few, experts that know the context) rather than users of sling (many, newbies that