You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whimsical.apache.org by Craig L Russell <cl...@apache.org> on 2015/08/29 18:42:01 UTC

Re: Unable to match expected number of names

> On Aug 29, 2015, at 4:18 AM, Sam Ruby <ru...@intertwingly.net> wrote:
> 
> On Fri, Aug 28, 2015 at 11:47 PM, Craig L Russell
> <cr...@oracle.com> wrote:
>> 
>> If one of the whimsy tools finds no entry in iclas.txt but something in getent or LDAP (two different sources imho), I would recommend highlighting such a name, perhaps with a marker such as ¿Tom Pappas? or somesuch.
> 
> It would be helpful to drop down to code at this point:
> 
> $ ruby -r 'whimsy/asf' -e "puts ASF::Person.new('ea').public_name"
> Melissa Warnkin
> 
> I have a library called 'whimsy/asf'.  It is used by many tools.  It
> provides a class named ASF::Person.  That class has an instance method
> named public_name.
> 
> An example of a tool that makes use of that information:
> 
> https://whimsy.apache.org/roster/committer/?q=melissa

If you’re looking for reliable information, we might consider using iclas.txt which as we both agree is definitive.

I’d have no problem adding the Executive Assistant and the Virtual people to that file, since there is no ambiguity about the information. Each line contains a mapping from apache id (not unique since there are a number of “notinavail” entries), email address (unique, but not reliable since ldap has a forwarding address which is definitive), full name, and public name (which I think we agree can be changed upon request).

So the ea entry probably would look like: 

ea:Melissa Warnkin:Melissa Warnkin:missywarnkin@yahoo.com:Executive Assistant

Similarly, all of the Virtual people would have Virtual as the last entry.

All of this would be noted at the top of the file.

Craig
> 
> We should probably continue this on dev@whimsical.
> 
> - Sam Ruby

Craig L Russell
Secretary, Apache Software Foundation
clr@apache.org http://db.apache.org/jdo




Re: Unable to match expected number of names

Posted by Sam Ruby <ru...@intertwingly.net>.
On Sun, Aug 30, 2015 at 3:36 PM, Sam Ruby <ru...@intertwingly.net> wrote:
> On Sun, Aug 30, 2015 at 3:30 PM, Craig L Russell
> <cr...@oracle.com> wrote:
>> I just now updated iclas.txt to include Melissa Warnkin with the entry:
>>
>> ea:Melissa Warnkin:Melissa Warnkin:missywarnkin@yahoo.com:President;Executive Assistant
>>
>> But the roster https://whimsy.apache.org/roster/committer/ea continued to rely on LDAP for the name.
>
> The cron job that runs svn up runs every 15 minutes.  Log of the last

Correction: every 10 minutes.

- Sam Ruby

> run can be found here:
>
> https://whimsy.apache.org/logs/update-svn
>
> Now that it has run, Melissa's name is taken from iclas.txt.
>
>> Why?
>>
>> Craig
>
> - Sam Ruby
>
>>> On Aug 30, 2015, at 9:06 AM, Craig L Russell <cr...@oracle.com> wrote:
>>>
>>>
>>>> On Aug 30, 2015, at 3:10 AM, sebb <se...@gmail.com> wrote:
>>>>
>>>> On 30 August 2015 at 03:17, Sam Ruby <ru...@intertwingly.net> wrote:
>>>>> On Sat, Aug 29, 2015 at 10:11 PM, Craig L Russell
>>>>> <cr...@oracle.com> wrote:
>>>>>> Sweet!
>>>>>>
>>>>>> Now maybe if you have access to getent passwd <id> you could add that to the columns displayed by public_names.
>>>>>
>>>>> Hmm.  I do and don't.
>>>>>
>>>>> [rubys@whimsy-vm:~]$ getent passwd clr
>>>>> clr:*:2018:2018:Craig L Russell:/home/clr:/usr/local/bin/bash
>>>>>
>>>>> [rubys@minotaur:~]$getent passwd clr
>>>>> clr:*:2018:2018:Craig L. Russell:/home/clr:/usr/local/bin/bash
>>>>>
>>>>>> We are almost at the bottom turtle.
>>>>>
>>>>> There seems to be more turtles.
>>>>>
>>>>>> Craig
>>>>>
>>>>> - Sam Ruby
>>>>>
>>>>> P.S.  For those just tuning in, Craig added a '.' after his middle
>>>>> initial on mino.  His change seems to be persistent but not
>>>>> propagated.
>>>>
>>>> Obviously the passwords on mino are taken from LDAP.
>>>> Notice the second getent field which is "*"; that tells the system to
>>>> go elsewhere for authentication.
>>>> Therefore there is no need to export changes from LDAP to the passwd file.
>>>> Or vice-versa.
>>>
>>> From this, I conclude that
>>>
>>> 1. any local changes anyone made using chfn are strictly local and not visible from current whimsy tooling
>>>
>>> 2. LDAP cn is essentially write-once (during object creation) and from then, read-only
>>>
>>> If we amend iclas.txt to include the ea and virtual folks there is no longer a need for whimsy to use LDAP cn.
>>>
>>> We should give folks a way to request that their public name be changed by contacting secretary.
>>>
>>> Craig
>>>> So if such sync is wanted, it would have to be added.
>>>>
>>>> <snip/>
>>>
>>> Craig L Russell
>>> Architect, Oracle
>>> http://db.apache.org/jdo
>>> 408 276-5638 mailto:Craig.Russell@oracle.com
>>> P.S. A good JDO? O, Gasp!
>>>
>>
>> Craig L Russell
>> Architect, Oracle
>> http://db.apache.org/jdo
>> 408 276-5638 mailto:Craig.Russell@oracle.com
>> P.S. A good JDO? O, Gasp!
>>

Re: Unable to match expected number of names

Posted by Sam Ruby <ru...@intertwingly.net>.
On Sun, Aug 30, 2015 at 3:30 PM, Craig L Russell
<cr...@oracle.com> wrote:
> I just now updated iclas.txt to include Melissa Warnkin with the entry:
>
> ea:Melissa Warnkin:Melissa Warnkin:missywarnkin@yahoo.com:President;Executive Assistant
>
> But the roster https://whimsy.apache.org/roster/committer/ea continued to rely on LDAP for the name.

The cron job that runs svn up runs every 15 minutes.  Log of the last
run can be found here:

https://whimsy.apache.org/logs/update-svn

Now that it has run, Melissa's name is taken from iclas.txt.

> Why?
>
> Craig

- Sam Ruby

>> On Aug 30, 2015, at 9:06 AM, Craig L Russell <cr...@oracle.com> wrote:
>>
>>
>>> On Aug 30, 2015, at 3:10 AM, sebb <se...@gmail.com> wrote:
>>>
>>> On 30 August 2015 at 03:17, Sam Ruby <ru...@intertwingly.net> wrote:
>>>> On Sat, Aug 29, 2015 at 10:11 PM, Craig L Russell
>>>> <cr...@oracle.com> wrote:
>>>>> Sweet!
>>>>>
>>>>> Now maybe if you have access to getent passwd <id> you could add that to the columns displayed by public_names.
>>>>
>>>> Hmm.  I do and don't.
>>>>
>>>> [rubys@whimsy-vm:~]$ getent passwd clr
>>>> clr:*:2018:2018:Craig L Russell:/home/clr:/usr/local/bin/bash
>>>>
>>>> [rubys@minotaur:~]$getent passwd clr
>>>> clr:*:2018:2018:Craig L. Russell:/home/clr:/usr/local/bin/bash
>>>>
>>>>> We are almost at the bottom turtle.
>>>>
>>>> There seems to be more turtles.
>>>>
>>>>> Craig
>>>>
>>>> - Sam Ruby
>>>>
>>>> P.S.  For those just tuning in, Craig added a '.' after his middle
>>>> initial on mino.  His change seems to be persistent but not
>>>> propagated.
>>>
>>> Obviously the passwords on mino are taken from LDAP.
>>> Notice the second getent field which is "*"; that tells the system to
>>> go elsewhere for authentication.
>>> Therefore there is no need to export changes from LDAP to the passwd file.
>>> Or vice-versa.
>>
>> From this, I conclude that
>>
>> 1. any local changes anyone made using chfn are strictly local and not visible from current whimsy tooling
>>
>> 2. LDAP cn is essentially write-once (during object creation) and from then, read-only
>>
>> If we amend iclas.txt to include the ea and virtual folks there is no longer a need for whimsy to use LDAP cn.
>>
>> We should give folks a way to request that their public name be changed by contacting secretary.
>>
>> Craig
>>> So if such sync is wanted, it would have to be added.
>>>
>>> <snip/>
>>
>> Craig L Russell
>> Architect, Oracle
>> http://db.apache.org/jdo
>> 408 276-5638 mailto:Craig.Russell@oracle.com
>> P.S. A good JDO? O, Gasp!
>>
>
> Craig L Russell
> Architect, Oracle
> http://db.apache.org/jdo
> 408 276-5638 mailto:Craig.Russell@oracle.com
> P.S. A good JDO? O, Gasp!
>

Re: Unable to match expected number of names

Posted by Craig L Russell <cr...@oracle.com>.
Oops, I put it i the wrong alphabetical location. Seems to work now.

Craig

> On Aug 30, 2015, at 12:30 PM, Craig L Russell <cr...@oracle.com> wrote:
> 
> I just now updated iclas.txt to include Melissa Warnkin with the entry:
> 
> ea:Melissa Warnkin:Melissa Warnkin:missywarnkin@yahoo.com:President;Executive Assistant
> 
> But the roster https://whimsy.apache.org/roster/committer/ea continued to rely on LDAP for the name.
> 
> Why?
> 
> Craig
> 
>> On Aug 30, 2015, at 9:06 AM, Craig L Russell <cr...@oracle.com> wrote:
>> 
>> 
>>> On Aug 30, 2015, at 3:10 AM, sebb <se...@gmail.com> wrote:
>>> 
>>> On 30 August 2015 at 03:17, Sam Ruby <ru...@intertwingly.net> wrote:
>>>> On Sat, Aug 29, 2015 at 10:11 PM, Craig L Russell
>>>> <cr...@oracle.com> wrote:
>>>>> Sweet!
>>>>> 
>>>>> Now maybe if you have access to getent passwd <id> you could add that to the columns displayed by public_names.
>>>> 
>>>> Hmm.  I do and don't.
>>>> 
>>>> [rubys@whimsy-vm:~]$ getent passwd clr
>>>> clr:*:2018:2018:Craig L Russell:/home/clr:/usr/local/bin/bash
>>>> 
>>>> [rubys@minotaur:~]$getent passwd clr
>>>> clr:*:2018:2018:Craig L. Russell:/home/clr:/usr/local/bin/bash
>>>> 
>>>>> We are almost at the bottom turtle.
>>>> 
>>>> There seems to be more turtles.
>>>> 
>>>>> Craig
>>>> 
>>>> - Sam Ruby
>>>> 
>>>> P.S.  For those just tuning in, Craig added a '.' after his middle
>>>> initial on mino.  His change seems to be persistent but not
>>>> propagated.
>>> 
>>> Obviously the passwords on mino are taken from LDAP.
>>> Notice the second getent field which is "*"; that tells the system to
>>> go elsewhere for authentication.
>>> Therefore there is no need to export changes from LDAP to the passwd file.
>>> Or vice-versa.
>> 
>> From this, I conclude that 
>> 
>> 1. any local changes anyone made using chfn are strictly local and not visible from current whimsy tooling
>> 
>> 2. LDAP cn is essentially write-once (during object creation) and from then, read-only
>> 
>> If we amend iclas.txt to include the ea and virtual folks there is no longer a need for whimsy to use LDAP cn.
>> 
>> We should give folks a way to request that their public name be changed by contacting secretary.
>> 
>> Craig
>>> So if such sync is wanted, it would have to be added.
>>> 
>>> <snip/>
>> 
>> Craig L Russell
>> Architect, Oracle
>> http://db.apache.org/jdo
>> 408 276-5638 mailto:Craig.Russell@oracle.com
>> P.S. A good JDO? O, Gasp!
>> 
> 
> Craig L Russell
> Architect, Oracle
> http://db.apache.org/jdo
> 408 276-5638 mailto:Craig.Russell@oracle.com
> P.S. A good JDO? O, Gasp!
> 

Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!


Re: Unable to match expected number of names

Posted by Craig L Russell <cr...@oracle.com>.
I just now updated iclas.txt to include Melissa Warnkin with the entry:

ea:Melissa Warnkin:Melissa Warnkin:missywarnkin@yahoo.com:President;Executive Assistant

But the roster https://whimsy.apache.org/roster/committer/ea continued to rely on LDAP for the name.

Why?

Craig

> On Aug 30, 2015, at 9:06 AM, Craig L Russell <cr...@oracle.com> wrote:
> 
> 
>> On Aug 30, 2015, at 3:10 AM, sebb <se...@gmail.com> wrote:
>> 
>> On 30 August 2015 at 03:17, Sam Ruby <ru...@intertwingly.net> wrote:
>>> On Sat, Aug 29, 2015 at 10:11 PM, Craig L Russell
>>> <cr...@oracle.com> wrote:
>>>> Sweet!
>>>> 
>>>> Now maybe if you have access to getent passwd <id> you could add that to the columns displayed by public_names.
>>> 
>>> Hmm.  I do and don't.
>>> 
>>> [rubys@whimsy-vm:~]$ getent passwd clr
>>> clr:*:2018:2018:Craig L Russell:/home/clr:/usr/local/bin/bash
>>> 
>>> [rubys@minotaur:~]$getent passwd clr
>>> clr:*:2018:2018:Craig L. Russell:/home/clr:/usr/local/bin/bash
>>> 
>>>> We are almost at the bottom turtle.
>>> 
>>> There seems to be more turtles.
>>> 
>>>> Craig
>>> 
>>> - Sam Ruby
>>> 
>>> P.S.  For those just tuning in, Craig added a '.' after his middle
>>> initial on mino.  His change seems to be persistent but not
>>> propagated.
>> 
>> Obviously the passwords on mino are taken from LDAP.
>> Notice the second getent field which is "*"; that tells the system to
>> go elsewhere for authentication.
>> Therefore there is no need to export changes from LDAP to the passwd file.
>> Or vice-versa.
> 
> From this, I conclude that 
> 
> 1. any local changes anyone made using chfn are strictly local and not visible from current whimsy tooling
> 
> 2. LDAP cn is essentially write-once (during object creation) and from then, read-only
> 
> If we amend iclas.txt to include the ea and virtual folks there is no longer a need for whimsy to use LDAP cn.
> 
> We should give folks a way to request that their public name be changed by contacting secretary.
> 
> Craig
>> So if such sync is wanted, it would have to be added.
>> 
>> <snip/>
> 
> Craig L Russell
> Architect, Oracle
> http://db.apache.org/jdo
> 408 276-5638 mailto:Craig.Russell@oracle.com
> P.S. A good JDO? O, Gasp!
> 

Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!


Re: Unable to match expected number of names

Posted by Craig L Russell <cr...@oracle.com>.
> On Aug 30, 2015, at 3:10 AM, sebb <se...@gmail.com> wrote:
> 
> On 30 August 2015 at 03:17, Sam Ruby <ru...@intertwingly.net> wrote:
>> On Sat, Aug 29, 2015 at 10:11 PM, Craig L Russell
>> <cr...@oracle.com> wrote:
>>> Sweet!
>>> 
>>> Now maybe if you have access to getent passwd <id> you could add that to the columns displayed by public_names.
>> 
>> Hmm.  I do and don't.
>> 
>> [rubys@whimsy-vm:~]$ getent passwd clr
>> clr:*:2018:2018:Craig L Russell:/home/clr:/usr/local/bin/bash
>> 
>> [rubys@minotaur:~]$getent passwd clr
>> clr:*:2018:2018:Craig L. Russell:/home/clr:/usr/local/bin/bash
>> 
>>> We are almost at the bottom turtle.
>> 
>> There seems to be more turtles.
>> 
>>> Craig
>> 
>> - Sam Ruby
>> 
>> P.S.  For those just tuning in, Craig added a '.' after his middle
>> initial on mino.  His change seems to be persistent but not
>> propagated.
> 
> Obviously the passwords on mino are taken from LDAP.
> Notice the second getent field which is "*"; that tells the system to
> go elsewhere for authentication.
> Therefore there is no need to export changes from LDAP to the passwd file.
> Or vice-versa.

From this, I conclude that 

1. any local changes anyone made using chfn are strictly local and not visible from current whimsy tooling

2. LDAP cn is essentially write-once (during object creation) and from then, read-only

If we amend iclas.txt to include the ea and virtual folks there is no longer a need for whimsy to use LDAP cn.

We should give folks a way to request that their public name be changed by contacting secretary.

Craig
> So if such sync is wanted, it would have to be added.
> 
> <snip/>

Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!


Re: Unable to match expected number of names

Posted by sebb <se...@gmail.com>.
On 30 August 2015 at 03:17, Sam Ruby <ru...@intertwingly.net> wrote:
> On Sat, Aug 29, 2015 at 10:11 PM, Craig L Russell
> <cr...@oracle.com> wrote:
>> Sweet!
>>
>> Now maybe if you have access to getent passwd <id> you could add that to the columns displayed by public_names.
>
> Hmm.  I do and don't.
>
> [rubys@whimsy-vm:~]$ getent passwd clr
> clr:*:2018:2018:Craig L Russell:/home/clr:/usr/local/bin/bash
>
> [rubys@minotaur:~]$getent passwd clr
> clr:*:2018:2018:Craig L. Russell:/home/clr:/usr/local/bin/bash
>
>> We are almost at the bottom turtle.
>
> There seems to be more turtles.
>
>> Craig
>
> - Sam Ruby
>
> P.S.  For those just tuning in, Craig added a '.' after his middle
> initial on mino.  His change seems to be persistent but not
> propagated.

Obviously the passwords on mino are taken from LDAP.
Notice the second getent field which is "*"; that tells the system to
go elsewhere for authentication.
Therefore there is no need to export changes from LDAP to the passwd file.
Or vice-versa.
So if such sync is wanted, it would have to be added.

<snip/>

Re: Unable to match expected number of names

Posted by Sam Ruby <ru...@intertwingly.net>.
On Sat, Aug 29, 2015 at 10:11 PM, Craig L Russell
<cr...@oracle.com> wrote:
> Sweet!
>
> Now maybe if you have access to getent passwd <id> you could add that to the columns displayed by public_names.

Hmm.  I do and don't.

[rubys@whimsy-vm:~]$ getent passwd clr
clr:*:2018:2018:Craig L Russell:/home/clr:/usr/local/bin/bash

[rubys@minotaur:~]$getent passwd clr
clr:*:2018:2018:Craig L. Russell:/home/clr:/usr/local/bin/bash

> We are almost at the bottom turtle.

There seems to be more turtles.

> Craig

- Sam Ruby

P.S.  For those just tuning in, Craig added a '.' after his middle
initial on mino.  His change seems to be persistent but not
propagated.

>> On Aug 29, 2015, at 6:24 PM, Sam Ruby <ru...@intertwingly.net> wrote:
>>
>> On Sat, Aug 29, 2015 at 8:39 PM, Craig L Russell
>> <cr...@oracle.com> wrote:
>>>
>>>>
>>>> Based on your description, I don't think I need to update anything in
>>>> order to support this.  Names present in icla.txt will take precedence
>>>> over LDAP in the current code.
>>>
>>> Nope, at least not in https://whimsy.apache.org/roster/committer/hyan which prefers An Hong Yun over Hongyun An.
>>
>> Fixed.  Thanks!
>>
>> Note: I'm only displaying LDAP and legal names when they differ.  Compare:
>>
>> https://whimsy.apache.org/roster/committer/ea
>> https://whimsy.apache.org/roster/committer/clr
>> https://whimsy.apache.org/roster/committer/brianb
>>
>> - Sam Ruby
>
> Craig L Russell
> Architect, Oracle
> http://db.apache.org/jdo
> 408 276-5638 mailto:Craig.Russell@oracle.com
> P.S. A good JDO? O, Gasp!
>

Re: Unable to match expected number of names

Posted by Craig L Russell <cr...@oracle.com>.
Sweet!

Now maybe if you have access to getent passwd <id> you could add that to the columns displayed by public_names.

We are almost at the bottom turtle.

Craig

> On Aug 29, 2015, at 6:24 PM, Sam Ruby <ru...@intertwingly.net> wrote:
> 
> On Sat, Aug 29, 2015 at 8:39 PM, Craig L Russell
> <cr...@oracle.com> wrote:
>> 
>>> 
>>> Based on your description, I don't think I need to update anything in
>>> order to support this.  Names present in icla.txt will take precedence
>>> over LDAP in the current code.
>> 
>> Nope, at least not in https://whimsy.apache.org/roster/committer/hyan which prefers An Hong Yun over Hongyun An.
> 
> Fixed.  Thanks!
> 
> Note: I'm only displaying LDAP and legal names when they differ.  Compare:
> 
> https://whimsy.apache.org/roster/committer/ea
> https://whimsy.apache.org/roster/committer/clr
> https://whimsy.apache.org/roster/committer/brianb
> 
> - Sam Ruby

Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!


Re: Unable to match expected number of names

Posted by Sam Ruby <ru...@intertwingly.net>.
On Sat, Aug 29, 2015 at 8:39 PM, Craig L Russell
<cr...@oracle.com> wrote:
>
>>
>> Based on your description, I don't think I need to update anything in
>> order to support this.  Names present in icla.txt will take precedence
>> over LDAP in the current code.
>
> Nope, at least not in https://whimsy.apache.org/roster/committer/hyan which prefers An Hong Yun over Hongyun An.

Fixed.  Thanks!

Note: I'm only displaying LDAP and legal names when they differ.  Compare:

https://whimsy.apache.org/roster/committer/ea
https://whimsy.apache.org/roster/committer/clr
https://whimsy.apache.org/roster/committer/brianb

- Sam Ruby

Re: Unable to match expected number of names

Posted by Craig L Russell <cr...@oracle.com>.
> On Aug 29, 2015, at 4:16 PM, Sam Ruby <ru...@intertwingly.net> wrote:
> 
> On Sat, Aug 29, 2015 at 6:11 PM, Craig L Russell
> <cr...@oracle.com> wrote:
>> Hi Sebb,
>> 
>>> On Aug 29, 2015, at 9:55 AM, sebb <se...@gmail.com> wrote:
>>> 
>>>> If you’re looking for reliable information, we might consider using iclas.txt which as we both agree is definitive.
>>>> 
>>>> I’d have no problem adding the Executive Assistant and the Virtual people to that file, since there is no ambiguity about the information. Each line contains a mapping from apache id (not unique since there are a number of “notinavail” entries), email address (unique, but not reliable since ldap has a forwarding address which is definitive), full name, and public name (which I think we agree can be changed upon request).
>>> 
>>> I assume the full name can also be changed on request?
>>> 
>>>> So the ea entry probably would look like:
>>>> 
>>>> ea:Melissa Warnkin:Melissa Warnkin:missywarnkin@yahoo.com:Executive Assistant
>>>> 
>>>> Similarly, all of the Virtual people would have Virtual as the last entry.
>>>> 
>>>> All of this would be noted at the top of the file.
>>> 
>>> However the file would no longer serve as the definitive list of
>>> people who have provided ICLAs
>>> Which is surely just as important?
>> 
>> The file is set up to allow non-ICLA signers to be represented. If an ICLA is filed, the 5th field is “Signed CLA;path-to-file-in-documents-iclas”.
>> 
>> So if the 5th field is not “Signed CLA” we then have a non-CLA entry. I don’t have a problem with that as long as:
>> 
>> 1. It’s rare.
>> 2. It’s documented.
>> 3. It’s useful.
> 
> WFM.  Your call.
> 
> Based on your description, I don't think I need to update anything in
> order to support this.  Names present in icla.txt will take precedence
> over LDAP in the current code.

Nope, at least not in https://whimsy.apache.org/roster/committer/hyan which prefers An Hong Yun over Hongyun An.
> 
> Over time, it may be desirable to present the value of this field in
> the roster tool.  Perhaps along with a hypertext link to the ICLA
> itself -- this link would only be shown to if the visitor to the site
> is an ASF member.

I think there’s not much left to do now, since the only exceptions to “found in iclas.txt” are the known ea and virtual folks.

So what is left now is:

1. to prefer iclas.txt to ldap in all of the whimsy tooling; 
2. to allow secretary role to change ldap entries
3. resolve how users can edit their full name/public name/ldap cn/getent passwd entry

Craig
> 
> - Sam Ruby
> 
> P.S.  I've updated public_names to add a table of ids that are LDAP only:
> 
> https://whimsy.apache.org/officers/public_names#missing
> 
>> Craig
>>> 
>>> Can't you just use the info from LDAP in those cases where there is no ICLA?
>>> 
>>> 
>> 
>> Craig L Russell
>> Architect, Oracle
>> http://db.apache.org/jdo
>> 408 276-5638 mailto:Craig.Russell@oracle.com
>> P.S. A good JDO? O, Gasp!
>> 

Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!


Re: Unable to match expected number of names

Posted by Sam Ruby <ru...@intertwingly.net>.
On Sat, Aug 29, 2015 at 6:11 PM, Craig L Russell
<cr...@oracle.com> wrote:
> Hi Sebb,
>
>> On Aug 29, 2015, at 9:55 AM, sebb <se...@gmail.com> wrote:
>>
>>> If you’re looking for reliable information, we might consider using iclas.txt which as we both agree is definitive.
>>>
>>> I’d have no problem adding the Executive Assistant and the Virtual people to that file, since there is no ambiguity about the information. Each line contains a mapping from apache id (not unique since there are a number of “notinavail” entries), email address (unique, but not reliable since ldap has a forwarding address which is definitive), full name, and public name (which I think we agree can be changed upon request).
>>
>> I assume the full name can also be changed on request?
>>
>>> So the ea entry probably would look like:
>>>
>>> ea:Melissa Warnkin:Melissa Warnkin:missywarnkin@yahoo.com:Executive Assistant
>>>
>>> Similarly, all of the Virtual people would have Virtual as the last entry.
>>>
>>> All of this would be noted at the top of the file.
>>
>> However the file would no longer serve as the definitive list of
>> people who have provided ICLAs
>> Which is surely just as important?
>
> The file is set up to allow non-ICLA signers to be represented. If an ICLA is filed, the 5th field is “Signed CLA;path-to-file-in-documents-iclas”.
>
> So if the 5th field is not “Signed CLA” we then have a non-CLA entry. I don’t have a problem with that as long as:
>
> 1. It’s rare.
> 2. It’s documented.
> 3. It’s useful.

WFM.  Your call.

Based on your description, I don't think I need to update anything in
order to support this.  Names present in icla.txt will take precedence
over LDAP in the current code.

Over time, it may be desirable to present the value of this field in
the roster tool.  Perhaps along with a hypertext link to the ICLA
itself -- this link would only be shown to if the visitor to the site
is an ASF member.

- Sam Ruby

P.S.  I've updated public_names to add a table of ids that are LDAP only:

https://whimsy.apache.org/officers/public_names#missing

> Craig
>>
>> Can't you just use the info from LDAP in those cases where there is no ICLA?
>>
>>
>
> Craig L Russell
> Architect, Oracle
> http://db.apache.org/jdo
> 408 276-5638 mailto:Craig.Russell@oracle.com
> P.S. A good JDO? O, Gasp!
>

Re: Unable to match expected number of names

Posted by Craig L Russell <cr...@oracle.com>.
Hi Sebb,

> On Aug 29, 2015, at 9:55 AM, sebb <se...@gmail.com> wrote:
> 
>> If you’re looking for reliable information, we might consider using iclas.txt which as we both agree is definitive.
>> 
>> I’d have no problem adding the Executive Assistant and the Virtual people to that file, since there is no ambiguity about the information. Each line contains a mapping from apache id (not unique since there are a number of “notinavail” entries), email address (unique, but not reliable since ldap has a forwarding address which is definitive), full name, and public name (which I think we agree can be changed upon request).
> 
> I assume the full name can also be changed on request?
> 
>> So the ea entry probably would look like:
>> 
>> ea:Melissa Warnkin:Melissa Warnkin:missywarnkin@yahoo.com:Executive Assistant
>> 
>> Similarly, all of the Virtual people would have Virtual as the last entry.
>> 
>> All of this would be noted at the top of the file.
> 
> However the file would no longer serve as the definitive list of
> people who have provided ICLAs
> Which is surely just as important?

The file is set up to allow non-ICLA signers to be represented. If an ICLA is filed, the 5th field is “Signed CLA;path-to-file-in-documents-iclas”.

So if the 5th field is not “Signed CLA” we then have a non-CLA entry. I don’t have a problem with that as long as:

1. It’s rare.
2. It’s documented.
3. It’s useful.

Craig
> 
> Can't you just use the info from LDAP in those cases where there is no ICLA?
> 
> 

Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!


Re: Unable to match expected number of names

Posted by sebb <se...@gmail.com>.
On 29 August 2015 at 17:42, Craig L Russell <cl...@apache.org> wrote:
>
>> On Aug 29, 2015, at 4:18 AM, Sam Ruby <ru...@intertwingly.net> wrote:
>>
>> On Fri, Aug 28, 2015 at 11:47 PM, Craig L Russell
>> <cr...@oracle.com> wrote:
>>>
>>> If one of the whimsy tools finds no entry in iclas.txt but something in getent or LDAP (two different sources imho), I would recommend highlighting such a name, perhaps with a marker such as ¿Tom Pappas? or somesuch.
>>
>> It would be helpful to drop down to code at this point:
>>
>> $ ruby -r 'whimsy/asf' -e "puts ASF::Person.new('ea').public_name"
>> Melissa Warnkin
>>
>> I have a library called 'whimsy/asf'.  It is used by many tools.  It
>> provides a class named ASF::Person.  That class has an instance method
>> named public_name.
>>
>> An example of a tool that makes use of that information:
>>
>> https://whimsy.apache.org/roster/committer/?q=melissa
>
> If you’re looking for reliable information, we might consider using iclas.txt which as we both agree is definitive.
>
> I’d have no problem adding the Executive Assistant and the Virtual people to that file, since there is no ambiguity about the information. Each line contains a mapping from apache id (not unique since there are a number of “notinavail” entries), email address (unique, but not reliable since ldap has a forwarding address which is definitive), full name, and public name (which I think we agree can be changed upon request).

I assume the full name can also be changed on request?

> So the ea entry probably would look like:
>
> ea:Melissa Warnkin:Melissa Warnkin:missywarnkin@yahoo.com:Executive Assistant
>
> Similarly, all of the Virtual people would have Virtual as the last entry.
>
> All of this would be noted at the top of the file.

However the file would no longer serve as the definitive list of
people who have provided ICLAs
Which is surely just as important?

Can't you just use the info from LDAP in those cases where there is no ICLA?

> Craig
>>
>> We should probably continue this on dev@whimsical.
>>
>> - Sam Ruby
>
> Craig L Russell
> Secretary, Apache Software Foundation
> clr@apache.org http://db.apache.org/jdo
>
>
>