Re: Limited search and find a file after git repo split

2018-07-16 Thread Alexander Klimetschek
Ah, great, that's useful!

Maybe add that link to the sling-old-svn-mirror README [1], 
apache/sling-aggregator [2] and the modules page [3].

Here is one more realistic query for me: search for the SlingMainServlet source 
code:


https://sourcegraph.com/search?q=repo:%5Egithub%5C.com/apache/sling-*++file:SlingMainServlet.java

[1] https://github.com/apache/sling-old-svn-mirror
[2] https://github.com/apache/sling-aggregator
[3] https://github.com/apache/sling-aggregator/blob/master/docs/modules.md

Cheers,
Alex

> On 12.07.2018, at 22:00, Chetan Mehrotra  wrote:
> 
> At times I have used sourcegraph to search across repos like
> https://sourcegraph.com/search?q=repo:%5Egithub%5C.com/apache/sling-*++file:pom.xml.
> It seems to pickup most of the repo matching given pattern
> Chetan Mehrotra
> 
> 
> On Wed, Jul 11, 2018 at 3:10 AM, Alexander Klimetschek
>  wrote:
>> Thanks!
>> 
>>> On 29.06.2018, at 12:50, Daniel Klco  wrote:
>>> 
>>> Okay, I had a minute so I made a quick tweak, adding in a paragraph with a
>>> link to the aggregator and modules list:
>>> 
>>> https://github.com/apache/sling-old-svn-mirror
>>> 
>>> On Fri, Jun 29, 2018 at 3:39 PM Daniel Klco  wrote:
>>> 
 I'm not sure we can do much about the old svn mirror being indexed, but
 adding a link to the Sling Aggregator sure would help.
 
 On Fri, Jun 29, 2018 at 3:30 PM Alexander Klimetschek
  wrote:
 
> It seems nothing has really improved :) I just ended up on
> https://github.com/apache/sling-old-svn-mirror, trying to find sources
> from Sling, but really have no clue where it is, and the links on that
> readme don't help at all.
> 
> Cheers,
> Alex
> 
>> On 02.02.2018, at 19:12, Alexander Klimetschek
>  wrote:
>> 
>> On 30.01.2018, at 23:41, Robert Munteanu  wrote:
>>> After a quick look at the github pages my only suggestion is using the
>>> advanced search page
>>> 
>>> https://github.com/search/advanced
>>> 
>>> and filling in all the sling repos in the repo field. The search would
>>> then be something like this
>>> 
>>> org:apache repo:org-apache-sling-api ResourceResolver
>>> 
>>> Unfortunately it does not seem to work :-( .
>> 
>> Too many repos :)
>> 
>> The root problem I think is that all apache projects are under one
> github organization. A github org is the natural place for 
> multi-repository
> projects, and most features like search work well across all repos in one
> org.
>> 
>> Maybe the ASF can be persuaded to support "apache-"
> organizations, with github somehow locking the "apache-*" namespace.
> Although I doubt this would ever happen.
>> 
>> Cheers,
>> Alex
>> 
> 
> 
>> 



Re: Limited search and find a file after git repo split

2018-07-12 Thread Chetan Mehrotra
At times I have used sourcegraph to search across repos like
https://sourcegraph.com/search?q=repo:%5Egithub%5C.com/apache/sling-*++file:pom.xml.
It seems to pickup most of the repo matching given pattern
Chetan Mehrotra


On Wed, Jul 11, 2018 at 3:10 AM, Alexander Klimetschek
 wrote:
> Thanks!
>
>> On 29.06.2018, at 12:50, Daniel Klco  wrote:
>>
>> Okay, I had a minute so I made a quick tweak, adding in a paragraph with a
>> link to the aggregator and modules list:
>>
>> https://github.com/apache/sling-old-svn-mirror
>>
>> On Fri, Jun 29, 2018 at 3:39 PM Daniel Klco  wrote:
>>
>>> I'm not sure we can do much about the old svn mirror being indexed, but
>>> adding a link to the Sling Aggregator sure would help.
>>>
>>> On Fri, Jun 29, 2018 at 3:30 PM Alexander Klimetschek
>>>  wrote:
>>>
 It seems nothing has really improved :) I just ended up on
 https://github.com/apache/sling-old-svn-mirror, trying to find sources
 from Sling, but really have no clue where it is, and the links on that
 readme don't help at all.

 Cheers,
 Alex

> On 02.02.2018, at 19:12, Alexander Klimetschek
  wrote:
>
> On 30.01.2018, at 23:41, Robert Munteanu  wrote:
>> After a quick look at the github pages my only suggestion is using the
>> advanced search page
>>
>> https://github.com/search/advanced
>>
>> and filling in all the sling repos in the repo field. The search would
>> then be something like this
>>
>> org:apache repo:org-apache-sling-api ResourceResolver
>>
>> Unfortunately it does not seem to work :-( .
>
> Too many repos :)
>
> The root problem I think is that all apache projects are under one
 github organization. A github org is the natural place for multi-repository
 projects, and most features like search work well across all repos in one
 org.
>
> Maybe the ASF can be persuaded to support "apache-"
 organizations, with github somehow locking the "apache-*" namespace.
 Although I doubt this would ever happen.
>
> Cheers,
> Alex
>


>


Re: Limited search and find a file after git repo split

2018-07-10 Thread Alexander Klimetschek
Thanks!

> On 29.06.2018, at 12:50, Daniel Klco  wrote:
> 
> Okay, I had a minute so I made a quick tweak, adding in a paragraph with a
> link to the aggregator and modules list:
> 
> https://github.com/apache/sling-old-svn-mirror
> 
> On Fri, Jun 29, 2018 at 3:39 PM Daniel Klco  wrote:
> 
>> I'm not sure we can do much about the old svn mirror being indexed, but
>> adding a link to the Sling Aggregator sure would help.
>> 
>> On Fri, Jun 29, 2018 at 3:30 PM Alexander Klimetschek
>>  wrote:
>> 
>>> It seems nothing has really improved :) I just ended up on
>>> https://github.com/apache/sling-old-svn-mirror, trying to find sources
>>> from Sling, but really have no clue where it is, and the links on that
>>> readme don't help at all.
>>> 
>>> Cheers,
>>> Alex
>>> 
 On 02.02.2018, at 19:12, Alexander Klimetschek
>>>  wrote:
 
 On 30.01.2018, at 23:41, Robert Munteanu  wrote:
> After a quick look at the github pages my only suggestion is using the
> advanced search page
> 
> https://github.com/search/advanced
> 
> and filling in all the sling repos in the repo field. The search would
> then be something like this
> 
> org:apache repo:org-apache-sling-api ResourceResolver
> 
> Unfortunately it does not seem to work :-( .
 
 Too many repos :)
 
 The root problem I think is that all apache projects are under one
>>> github organization. A github org is the natural place for multi-repository
>>> projects, and most features like search work well across all repos in one
>>> org.
 
 Maybe the ASF can be persuaded to support "apache-"
>>> organizations, with github somehow locking the "apache-*" namespace.
>>> Although I doubt this would ever happen.
 
 Cheers,
 Alex
 
>>> 
>>> 



Re: Limited search and find a file after git repo split

2018-06-29 Thread Daniel Klco
Okay, I had a minute so I made a quick tweak, adding in a paragraph with a
link to the aggregator and modules list:

https://github.com/apache/sling-old-svn-mirror

On Fri, Jun 29, 2018 at 3:39 PM Daniel Klco  wrote:

> I'm not sure we can do much about the old svn mirror being indexed, but
> adding a link to the Sling Aggregator sure would help.
>
> On Fri, Jun 29, 2018 at 3:30 PM Alexander Klimetschek
>  wrote:
>
>> It seems nothing has really improved :) I just ended up on
>> https://github.com/apache/sling-old-svn-mirror, trying to find sources
>> from Sling, but really have no clue where it is, and the links on that
>> readme don't help at all.
>>
>> Cheers,
>> Alex
>>
>> > On 02.02.2018, at 19:12, Alexander Klimetschek
>>  wrote:
>> >
>> > On 30.01.2018, at 23:41, Robert Munteanu  wrote:
>> >> After a quick look at the github pages my only suggestion is using the
>> >> advanced search page
>> >>
>> >> https://github.com/search/advanced
>> >>
>> >> and filling in all the sling repos in the repo field. The search would
>> >> then be something like this
>> >>
>> >> org:apache repo:org-apache-sling-api ResourceResolver
>> >>
>> >> Unfortunately it does not seem to work :-( .
>> >
>> > Too many repos :)
>> >
>> > The root problem I think is that all apache projects are under one
>> github organization. A github org is the natural place for multi-repository
>> projects, and most features like search work well across all repos in one
>> org.
>> >
>> > Maybe the ASF can be persuaded to support "apache-"
>> organizations, with github somehow locking the "apache-*" namespace.
>> Although I doubt this would ever happen.
>> >
>> > Cheers,
>> > Alex
>> >
>>
>>


Re: Limited search and find a file after git repo split

2018-06-29 Thread Daniel Klco
I'm not sure we can do much about the old svn mirror being indexed, but
adding a link to the Sling Aggregator sure would help.

On Fri, Jun 29, 2018 at 3:30 PM Alexander Klimetschek
 wrote:

> It seems nothing has really improved :) I just ended up on
> https://github.com/apache/sling-old-svn-mirror, trying to find sources
> from Sling, but really have no clue where it is, and the links on that
> readme don't help at all.
>
> Cheers,
> Alex
>
> > On 02.02.2018, at 19:12, Alexander Klimetschek
>  wrote:
> >
> > On 30.01.2018, at 23:41, Robert Munteanu  wrote:
> >> After a quick look at the github pages my only suggestion is using the
> >> advanced search page
> >>
> >> https://github.com/search/advanced
> >>
> >> and filling in all the sling repos in the repo field. The search would
> >> then be something like this
> >>
> >> org:apache repo:org-apache-sling-api ResourceResolver
> >>
> >> Unfortunately it does not seem to work :-( .
> >
> > Too many repos :)
> >
> > The root problem I think is that all apache projects are under one
> github organization. A github org is the natural place for multi-repository
> projects, and most features like search work well across all repos in one
> org.
> >
> > Maybe the ASF can be persuaded to support "apache-"
> organizations, with github somehow locking the "apache-*" namespace.
> Although I doubt this would ever happen.
> >
> > Cheers,
> > Alex
> >
>
>


Re: Limited search and find a file after git repo split

2018-06-29 Thread Alexander Klimetschek
It seems nothing has really improved :) I just ended up on 
https://github.com/apache/sling-old-svn-mirror, trying to find sources from 
Sling, but really have no clue where it is, and the links on that readme don't 
help at all.

Cheers,
Alex

> On 02.02.2018, at 19:12, Alexander Klimetschek  
> wrote:
> 
> On 30.01.2018, at 23:41, Robert Munteanu  wrote:
>> After a quick look at the github pages my only suggestion is using the
>> advanced search page
>> 
>> https://github.com/search/advanced
>> 
>> and filling in all the sling repos in the repo field. The search would
>> then be something like this
>> 
>> org:apache repo:org-apache-sling-api ResourceResolver
>> 
>> Unfortunately it does not seem to work :-( .
> 
> Too many repos :)
> 
> The root problem I think is that all apache projects are under one github 
> organization. A github org is the natural place for multi-repository 
> projects, and most features like search work well across all repos in one org.
> 
> Maybe the ASF can be persuaded to support "apache-" organizations, 
> with github somehow locking the "apache-*" namespace. Although I doubt this 
> would ever happen.
> 
> Cheers,
> Alex
> 



Re: Limited search and find a file after git repo split

2018-02-02 Thread Alexander Klimetschek
On 30.01.2018, at 23:41, Robert Munteanu  wrote:
> After a quick look at the github pages my only suggestion is using the
> advanced search page
> 
>  https://github.com/search/advanced
> 
> and filling in all the sling repos in the repo field. The search would
> then be something like this
> 
>  org:apache repo:org-apache-sling-api ResourceResolver
> 
> Unfortunately it does not seem to work :-( .

Too many repos :)

The root problem I think is that all apache projects are under one github 
organization. A github org is the natural place for multi-repository projects, 
and most features like search work well across all repos in one org.

Maybe the ASF can be persuaded to support "apache-" organizations, 
with github somehow locking the "apache-*" namespace. Although I doubt this 
would ever happen.

Cheers,
Alex



Re: Limited search and find a file after git repo split

2018-01-30 Thread Robert Munteanu
Hi Alex,

On Wed, 2018-01-31 at 01:30 +, Alexander Klimetschek wrote:
> One thing that doesn't work well anymore after the repo split is
> 
> a) quickly navigate to a file (hit key "T" in github) across all
> Sling code (e.g. if you know the api or have a stacktrace, but no
> idea what repo that is)
> b) search
> 
> Unfortunately, github only indexes the main branch for b), so you
> can't search the "old" code base in [1] anymore. Granted, that would
> soon only only for historical purposes.
> 
> For the current code, you can approach b) by searching in the entire
> "apache" organization, but then you might also find a lot of noise
> from other projects.
> 
> I can't tell you how often I have been using a) or b) to navigate and
> read Sling code, it's a key tool for me.
> 
> Any ideas?

After a quick look at the github pages my only suggestion is using the
advanced search page

  https://github.com/search/advanced

and filling in all the sling repos in the repo field. The search would
then be something like this

  org:apache repo:org-apache-sling-api ResourceResolver

Unfortunately it does not seem to work :-( . If we find something that
works this way we can create a custom search link on sling.apache.org
and allow searching from there.

Thanks,

Robert