www-infrastructure-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alan Cabrera <...@toolazydogs.com>
Subject Re: Canonical sources for information
Date Tue, 28 May 2013 20:50:10 GMT

On May 28, 2013, at 12:10 PM, sebb <sebbaz@gmail.com> wrote:

> On 28 May 2013 18:44, Sam Ruby <rubys@intertwingly.net> wrote:
>> On Tue, May 28, 2013 at 1:31 PM, Alan Cabrera <adc@toolazydogs.com> wrote:
>>> 
>>> On May 28, 2013, at 10:24 AM, sebb <sebbaz@gmail.com> wrote:
>>> 
>>>> On 27 May 2013 22:18, Alan Cabrera <adc@toolazydogs.com> wrote:
>>>>> 
>>>>> On May 27, 2013, at 1:11 PM, Tony Stevenson <pctony@apache.org>
wrote:
>>>>> 
>>>>>> 
>>>>>> On 27 May 2013, at 18:15, Alan Cabrera <adc@toolazydogs.com>
wrote:
>>>>>> 
>>>>>>> I need to know what are the official sources for the following:
>>>>>>> 
>>>>>>> full name from username
>>>>>> 
>>>>>> ldap
>>>>>> 
>>>>>>> whether a person is a corporate member from username
>>>>>> 
>>>>>>> What PMC/PPMCs the person belongs to from username
>>>>>> 
>>>>>> ldap, well this will show group membership.
>>>>>> 
>>>>>>> I need to get access to this data from the Python utilities that
I am writing.
>>>>>> 
>>>>>> ldap is only available from within the ASF network, so you would
have to run this from there.
>>>>> 
>>>>> Inconvenient but not a "deal breaker"
>>>> 
>>>> There is already a cron job that extracts a fair amount of information
>>>> from LDAP (and elsewhere) to produce the people.a.o pages.
>>>> This information is currently published as HTML, for example:
>>>> 
>>>> http://people.apache.org/committer-index.html
>>>> which contains the following information:
>>>> SVN id        Name    SVN Projects
>>>> Member (bold)
>>>> URL (link)
>>>> 
>>>> Maybe it would make more sense to modify that to additionally generate
>>>> the output in CSV/JSON so it can be used by anyone?
>>>> 
>>>> Scripts would then just need HTTP access to get the data, and they
>>>> would only have access to the data that had been cleared for
>>>> publication.
>>> 
>>> That's one way to implement it.  I'm glad we agree that providing HTTP access
to vetted data has value.
>> 
>> Try the following (passing in --user adc:password):
>> 
>> curl -H "Accept:application/json" https://whimsy.apache.org/roster/committer/adc
>> 
>> Let me know if there are ways that I can make this more convenient.
> 
> This requires an LDAP login, which means the code probably cannot be
> safely automated to run on a shared host, as the password would need
> to be stored somewhere.
> 
> Would it be possible to provide access to the public information
> without requiring a login?

How about returning just public information when credentials are not supplied and returning
full information if credentials are supplied?


Regards,
Alan



Mime
View raw message