www-infrastructure-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan D. Cabrera" <l...@toolazydogs.com>
Subject Re: Brooklyn not in http://people.apache.org/committers-by-project.html
Date Tue, 20 Jan 2015 19:22:25 GMT

> On Jan 20, 2015, at 11:19 AM, jan i <jani@apache.org> wrote:
> 
> On 20 January 2015 at 20:12, Alan D. Cabrera <list@toolazydogs.com> wrote:
> 
>> 
>>> On Jan 20, 2015, at 11:08 AM, sebb <sebbaz@gmail.com> wrote:
>>> 
>>> On 20 January 2015 at 18:12, Alan D. Cabrera <adc@toolazydogs.com>
>> wrote:
>>>> 
>>>>> On Jan 20, 2015, at 10:08 AM, David Nalley <david@gnsa.us> wrote:
>>>>> 
>>>>> Is there a reason it needs to be added?
>>>> 
>>>> That seems like an odd question and I would turn it around and ask, is
>> there a reason why it shouldn’t?
>>>> 
>>>>> IIRC that page is derived from the authorization file for SVN -
>>> 
>>> Yes
>>> 
>>>>> Brooklyn doesn't use svn, so no listing.
>>> 
>>> It does not *need* an entry in asf-auth, but one can be provided.
>>> 
>>>> Time to fix the tooling… :)  Where’s the code that generates those
>> pages?
>>> 
>>> The tooling is not broken.
>>> 
>>> There is currently no readily accessible data defining the members of
>>> the Brooklyn podling.
>>> 
>>> Once a podling graduates, it will have an LDAP group.
>> 
>> Then what about all the other podlings that are on this page?
>> 
> 
> Documentation for podlings says you should update that file, so I did it
> for corinthia even though we use git, and it worked nicely.

What file are you speaking of?

> I really do not care whether I have to update the svn authz file or another
> file, and we need to keep the information somewhere.

Neither do I.  Just trying to fix Brooklyn.


Regards,
Alan


Mime
View raw message