Thanks!
> On 29.06.2018, at 12:50, Daniel Klco <daniel.k...@gmail.com> 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 <daniel.k...@gmail.com> 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
>> <aklim...@adobe.com.invalid> 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
>>> <aklim...@adobe.com.INVALID> wrote:
>>>>
>>>> On 30.01.2018, at 23:41, Robert Munteanu <romb...@apache.org> 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-<project>"
>>> organizations, with github somehow locking the "apache-*" namespace.
>>> Although I doubt this would ever happen.
>>>>
>>>> Cheers,
>>>> Alex
>>>>
>>>
>>>
