Re: Tooling for: Your Apache ICLA has gone missing

[Sam Ruby]

On Tue, Apr 18, 2017 at 7:52 PM, Craig Russell  wrote:
> Of course, Java would throw a NullPointerException but Ruby/Javascript don't 
> care.

Chuckle.  This isn't so much a language feature as a bad design
decision that happened to work out this time.

LDAP is a query mechanism.  ASF::Person.find creates an object that
issues queries.  In other words, ASF::Person.find doesn't itself do a
query and never returns nil.  This can be a PITA if you really want to
know if the user exists.

I now have an alternative that does return nil if the id doesn't exist
in LDAP: ASF::Person['badactor'].

> Thanks!!!
>
> Craig

- Sam Ruby

>> On Apr 18, 2017, at 4:10 PM, Sam Ruby  wrote:
>>
>> On Tue, Apr 18, 2017 at 3:34 PM, Craig Russell  
>> wrote:
>>>
>>> So my proposal for changing the current behavior:
>>>
>>> If field 5 is disabled for any reason, verify that ldap is either missing 
>>> or banned. I don't see the need to distinguish these two cases.
>>
>> Looks like the code already works that way:
>>
>> ASF::Person.find('badactor').banned?
>> => true
>>
>> So the following code should do what you are asking:
>>
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_whimsy_commit_0be74d0f094ba735d11b8609ec64aafb20010ddd&d=DwIBaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=DKWhdZdh69Kb6XA85A6vmYASgWIRD5RAywexyAJQArI&m=rhybZ1RAXU9MA8l6i3zRRJBO_5MUMQFU4-uC8_xh_bw&s=BeAWRc4JU5lApbe5XvZ73m1_bz5uchuMBM6XPMPSvNc&e=
>>
>> - Sam Ruby
>
> Craig L Russell
> Secretary, Apache Software Foundation
> c...@apache.org http://db.apache.org/jdo
>

Re: Tooling for: Your Apache ICLA has gone missing

[Craig Russell]

Of course, Java would throw a NullPointerException but Ruby/Javascript don't 
care.

Thanks!!!

Craig

> On Apr 18, 2017, at 4:10 PM, Sam Ruby  wrote:
> 
> On Tue, Apr 18, 2017 at 3:34 PM, Craig Russell  
> wrote:
>> 
>> So my proposal for changing the current behavior:
>> 
>> If field 5 is disabled for any reason, verify that ldap is either missing or 
>> banned. I don't see the need to distinguish these two cases.
> 
> Looks like the code already works that way:
> 
> ASF::Person.find('badactor').banned?
> => true
> 
> So the following code should do what you are asking:
> 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_whimsy_commit_0be74d0f094ba735d11b8609ec64aafb20010ddd&d=DwIBaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=DKWhdZdh69Kb6XA85A6vmYASgWIRD5RAywexyAJQArI&m=rhybZ1RAXU9MA8l6i3zRRJBO_5MUMQFU4-uC8_xh_bw&s=BeAWRc4JU5lApbe5XvZ73m1_bz5uchuMBM6XPMPSvNc&e=
>  
> 
> - Sam Ruby

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

Re: Tooling for: Your Apache ICLA has gone missing

[Sam Ruby]

On Tue, Apr 18, 2017 at 3:34 PM, Craig Russell  wrote:
>
> So my proposal for changing the current behavior:
>
> If field 5 is disabled for any reason, verify that ldap is either missing or 
> banned. I don't see the need to distinguish these two cases.

Looks like the code already works that way:

ASF::Person.find('badactor').banned?
=> true

So the following code should do what you are asking:

https://github.com/apache/whimsy/commit/0be74d0f094ba735d11b8609ec64aafb20010ddd

- Sam Ruby

Re: Tooling for: Your Apache ICLA has gone missing

[Craig Russell]

> On Apr 18, 2017, at 2:03 AM, sebb  wrote:
> 
> On 18 April 2017 at 00:20, Craig Russell  wrote:
>> Let's see if this approach makes sense.
>> 
>> If the field 5 data is disabled;  then one of the following must 
>> be true:
>> 
>> ASF::Person.find('notsetup') is null or
>> ASF::Person.find('badactor').banned? is true
>> 
>> If not, then signal an error 'disabled but account is active'
> 
> I think the conditions need different errors.

Why?

> A missing LDAP entry needs separate investigation.

There are currently 16 icla-lint entries where there is an icla and no ldap. I 
am not proposing to change this behavior. But if we decide that there is an 
icla.txt that should not have an ldap entry it makes sense to me to annotate 
the icla.txt with disabled; mumble so we don't need to have it flagged each 
time we run icla-lint.
> 
>> I can go back into BadActor later and add disabled; mumble
>> 
>> I can also annotate BannedMember's entry with disabled; mumble
> 
> Should probably also check that LDAP agrees with iclas.txt, e.g. if
> ASF::Person.find('badactor').banned? is true then iclas.txt should be
> flagged disabled and vice versa.

This tool scans iclas.txt and verifies with ldap. I don't think there is 
anything that scans ldap and verifies with iclas.txt.

So my proposal for changing the current behavior:

If field 5 is disabled for any reason, verify that ldap is either missing or 
banned. I don't see the need to distinguish these two cases.
> 
> But in the longer term, why are we maintaining two parallel sets of data?
> Once there is proper logging of LDAP changes, do we still need iclas.txt?
> It has some unique data, but that could presumably be added to LDAP if 
> required.

I have no issues if we want to go down that path. I'm just not volunteering to 
drive it. ;-)

Craig
> 
>> Craig
>> 
>>> On Apr 17, 2017, at 10:29 AM, Craig Russell  
>>> wrote:
>>> 
>>> Workflow:
>>> 
>>> Secretary determines that a replacement icla is not coming.
>>> 
>>> Secretary requests infra to disable the account.
>>> 
>>> Infra disables the account. How does whimsy know that the account is 
>>> disabled?
>>> 
>>> Secretary updates iclas.txt with "disabled; no icla on file"
>>> 
>>> The icla-lint should be able to reconcile disabled account in LDAP with 
>>> disabled account in iclas.txt.
>>> 
>>> How should whimsy committer display disabled accounts? Should there be a 
>>> date stamp when the account was disabled?
>>> 
>>> Craig
>>> 
 On Apr 16, 2017, at 5:08 PM, Craig Russell  
 wrote:
 
 Looks like there is agreement with infra that accounts that were created 
 and now there is no icla on file should be disabled.
 
 I've asked infra to disable a number of these accounts and I've updated 
 iclas.txt to indicate that they are disabled.
 
 If/when the committers show up, it's easy enough to file their iclas and 
 get them back to commit status.
 
 Craig
 
> On Apr 16, 2017, at 11:46 AM, sebb  wrote:
> 
> On 15 April 2017 at 16:30, Sam Ruby  wrote:
>> On Sat, Apr 15, 2017 at 11:21 AM, Craig Russell  
>> wrote:
>>> So how do we handle this?
>>> 
>>> We need to remove the iclas.txt entry for edalquist, which I can do 
>>> manually. We also need to remove the LDAP entry, which I do not even 
>>> know how to do.
>> 
>> Sebb would argue that the ID should be disabled, not removed.
> 
> Yes, because otherwise the id might be reallocated to someone else.
> Also we might lose details of code commits.
> 
>> Whether
>> it is disabling or removing, currently this authority is reserved by
>> the infrastructure team to themselves.  What could be done is a delete
>> account request, much like we currently have a create account request.
> 
> I think deletion is too strong unless it can be shown that the id has
> never been used for a CVS/SVN/Git commit.
> 
>> Should the ID be removed, it would also need to be removed from each
>> group that this individual is a member of:
>> 
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__whimsy.apache.org_roster_committer_edalquist&d=DwIFaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=DKWhdZdh69Kb6XA85A6vmYASgWIRD5RAywexyAJQArI&m=u29WDved3LSsHM8E1RYtvELY463RxF5Lehe_Xi8C1zc&s=P21mBvHTRxHD8i--NFC7vNrm4TvhTc6Gf81QpxiiINM&e=
> 
> +1
> 
>>> Is there a chance we can add a button to the icla-lint whimsy page to 
>>> do both of these?
>> 
>> I generally shy away from writing code that I don't have the karma to 
>> test.  :-)
>> 
>>> Craig
>> 
>> - Sam Ruby
>> 
 Begin forwarded message:
 
 From: Eric Dalquist 
 Subject: Re: Your Apache ICLA has gone missing
 Date: April 15, 2017 at 8:15:30 AM PDT
 To: Craig Russell , edalqu...@apache.org
 Cc: Secretary 
 
 Thanks for letting me know. Unfortunately my current 

Re: Tooling for: Your Apache ICLA has gone missing

[sebb]

On 18 April 2017 at 00:20, Craig Russell  wrote:
> Let's see if this approach makes sense.
>
> If the field 5 data is disabled;  then one of the following must 
> be true:
>
> ASF::Person.find('lrosen') is null or
> ASF::Person.find('lrosen').banned? is true
>
> If not, then signal an error 'disabled but account is active'

I think the conditions need different errors.
A missing LDAP entry needs separate investigation.

> I can go back into lrosen later and add disabled; mumble
>
> I can also annotate Tetsuya's entry with disabled; mumble

Should probably also check that LDAP agrees with iclas.txt, e.g. if
ASF::Person.find('lrosen').banned? is true then iclas.txt should be
flagged disabled and vice versa.

But in the longer term, why are we maintaining two parallel sets of data?
Once there is proper logging of LDAP changes, do we still need iclas.txt?
It has some unique data, but that could presumably be added to LDAP if required.

> Craig
>
>> On Apr 17, 2017, at 10:29 AM, Craig Russell  wrote:
>>
>> Workflow:
>>
>> Secretary determines that a replacement icla is not coming.
>>
>> Secretary requests infra to disable the account.
>>
>> Infra disables the account. How does whimsy know that the account is 
>> disabled?
>>
>> Secretary updates iclas.txt with "disabled; no icla on file"
>>
>> The icla-lint should be able to reconcile disabled account in LDAP with 
>> disabled account in iclas.txt.
>>
>> How should whimsy committer display disabled accounts? Should there be a 
>> date stamp when the account was disabled?
>>
>> Craig
>>
>>> On Apr 16, 2017, at 5:08 PM, Craig Russell  wrote:
>>>
>>> Looks like there is agreement with infra that accounts that were created 
>>> and now there is no icla on file should be disabled.
>>>
>>> I've asked infra to disable a number of these accounts and I've updated 
>>> iclas.txt to indicate that they are disabled.
>>>
>>> If/when the committers show up, it's easy enough to file their iclas and 
>>> get them back to commit status.
>>>
>>> Craig
>>>
 On Apr 16, 2017, at 11:46 AM, sebb  wrote:

 On 15 April 2017 at 16:30, Sam Ruby  wrote:
> On Sat, Apr 15, 2017 at 11:21 AM, Craig Russell  wrote:
>> So how do we handle this?
>>
>> We need to remove the iclas.txt entry for edalquist, which I can do 
>> manually. We also need to remove the LDAP entry, which I do not even 
>> know how to do.
>
> Sebb would argue that the ID should be disabled, not removed.

 Yes, because otherwise the id might be reallocated to someone else.
 Also we might lose details of code commits.

> Whether
> it is disabling or removing, currently this authority is reserved by
> the infrastructure team to themselves.  What could be done is a delete
> account request, much like we currently have a create account request.

 I think deletion is too strong unless it can be shown that the id has
 never been used for a CVS/SVN/Git commit.

> Should the ID be removed, it would also need to be removed from each
> group that this individual is a member of:
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__whimsy.apache.org_roster_committer_edalquist&d=DwIFaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=DKWhdZdh69Kb6XA85A6vmYASgWIRD5RAywexyAJQArI&m=u29WDved3LSsHM8E1RYtvELY463RxF5Lehe_Xi8C1zc&s=P21mBvHTRxHD8i--NFC7vNrm4TvhTc6Gf81QpxiiINM&e=

 +1

>> Is there a chance we can add a button to the icla-lint whimsy page to do 
>> both of these?
>
> I generally shy away from writing code that I don't have the karma to 
> test.  :-)
>
>> Craig
>
> - Sam Ruby
>
>>> Begin forwarded message:
>>>
>>> From: Eric Dalquist 
>>> Subject: Re: Your Apache ICLA has gone missing
>>> Date: April 15, 2017 at 8:15:30 AM PDT
>>> To: Craig Russell , edalqu...@apache.org
>>> Cc: Secretary 
>>>
>>> Thanks for letting me know. Unfortunately my current situation prevents 
>>> me from submitting an ICLA so I should likely be removed as an eligible 
>>> Apache committer for now.
>>>
>>> Thanks,
>>> -Eric Dalquist
>>>
>>> On Sat, Apr 15, 2017 at 8:09 AM Craig Russell >> > wrote:
>>> Dear Eric Dalquist,
>>>
>>> We are reviewing our records to be sure that all submitted ICLAs are on 
>>> file.
>>> Unfortunately, we are unable to locate the ICLA that you submitted 
>>> earlier.
>>>
>>> Can you please resubmit to secret...@apache.org 
>>> ? 
>>> https://urldefense.proofpoint.com/v2/url?u=http-3A__apache.org_licenses_-23submitting&d=DwIFaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=DKWhdZdh69Kb6XA85A6vmYASgWIRD5RAywexyAJQArI&m=u29WDved3LSsHM8E1RYtvELY463RxF5Lehe_Xi8C1zc&s=0x9hY6QUQlsexxFxnFpmkY0MM1ALXTbH1HTk94PXuFY&e=
>>>   
>>> 

Re: Tooling for: Your Apache ICLA has gone missing

[sebb]

On 17 April 2017 at 18:29, Craig Russell  wrote:
> Workflow:
>
> Secretary determines that a replacement icla is not coming.
>
> Secretary requests infra to disable the account.
>
> Infra disables the account. How does whimsy know that the account is disabled?

Generally the shell is set to an invalid exe, or .../false.
See the 'banned?' function:

https://github.com/apache/whimsy/blob/master/lib/whimsy/asf/ldap.rb#L525

Perhaps we should rename the function/give it a better alias?

> Secretary updates iclas.txt with "disabled; no icla on file"
>
> The icla-lint should be able to reconcile disabled account in LDAP with 
> disabled account in iclas.txt.
>
> How should whimsy committer display disabled accounts?

Whimsy does not currently display the disabled flag.

However it is added to
https://whimsy.apache.org/public/public_ldap_people.json
as the boolean attribute 'noLogin', and phoneBook uses that.

Probably Whimsy should use it too.

> Should there be a date stamp when the account was disabled?

That might be tricky to implement.

Re: Tooling for: Your Apache ICLA has gone missing

[Craig Russell]

Let's see if this approach makes sense.

If the field 5 data is disabled;  then one of the following must be 
true:

ASF::Person.find('lrosen') is null or 
ASF::Person.find('lrosen').banned? is true

If not, then signal an error 'disabled but account is active'

I can go back into lrosen later and add disabled; mumble

I can also annotate Tetsuya's entry with disabled; mumble

Craig

> On Apr 17, 2017, at 10:29 AM, Craig Russell  wrote:
> 
> Workflow:
> 
> Secretary determines that a replacement icla is not coming.
> 
> Secretary requests infra to disable the account.
> 
> Infra disables the account. How does whimsy know that the account is 
> disabled? 
> 
> Secretary updates iclas.txt with "disabled; no icla on file"
> 
> The icla-lint should be able to reconcile disabled account in LDAP with 
> disabled account in iclas.txt.
> 
> How should whimsy committer display disabled accounts? Should there be a date 
> stamp when the account was disabled?
> 
> Craig
> 
>> On Apr 16, 2017, at 5:08 PM, Craig Russell  wrote:
>> 
>> Looks like there is agreement with infra that accounts that were created and 
>> now there is no icla on file should be disabled. 
>> 
>> I've asked infra to disable a number of these accounts and I've updated 
>> iclas.txt to indicate that they are disabled.
>> 
>> If/when the committers show up, it's easy enough to file their iclas and get 
>> them back to commit status.
>> 
>> Craig
>> 
>>> On Apr 16, 2017, at 11:46 AM, sebb  wrote:
>>> 
>>> On 15 April 2017 at 16:30, Sam Ruby  wrote:
 On Sat, Apr 15, 2017 at 11:21 AM, Craig Russell  wrote:
> So how do we handle this?
> 
> We need to remove the iclas.txt entry for edalquist, which I can do 
> manually. We also need to remove the LDAP entry, which I do not even know 
> how to do.
 
 Sebb would argue that the ID should be disabled, not removed.
>>> 
>>> Yes, because otherwise the id might be reallocated to someone else.
>>> Also we might lose details of code commits.
>>> 
 Whether
 it is disabling or removing, currently this authority is reserved by
 the infrastructure team to themselves.  What could be done is a delete
 account request, much like we currently have a create account request.
>>> 
>>> I think deletion is too strong unless it can be shown that the id has
>>> never been used for a CVS/SVN/Git commit.
>>> 
 Should the ID be removed, it would also need to be removed from each
 group that this individual is a member of:
 
 https://urldefense.proofpoint.com/v2/url?u=https-3A__whimsy.apache.org_roster_committer_edalquist&d=DwIFaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=DKWhdZdh69Kb6XA85A6vmYASgWIRD5RAywexyAJQArI&m=u29WDved3LSsHM8E1RYtvELY463RxF5Lehe_Xi8C1zc&s=P21mBvHTRxHD8i--NFC7vNrm4TvhTc6Gf81QpxiiINM&e=
  
>>> 
>>> +1
>>> 
> Is there a chance we can add a button to the icla-lint whimsy page to do 
> both of these?
 
 I generally shy away from writing code that I don't have the karma to 
 test.  :-)
 
> Craig
 
 - Sam Ruby
 
>> Begin forwarded message:
>> 
>> From: Eric Dalquist 
>> Subject: Re: Your Apache ICLA has gone missing
>> Date: April 15, 2017 at 8:15:30 AM PDT
>> To: Craig Russell , edalqu...@apache.org
>> Cc: Secretary 
>> 
>> Thanks for letting me know. Unfortunately my current situation prevents 
>> me from submitting an ICLA so I should likely be removed as an eligible 
>> Apache committer for now.
>> 
>> Thanks,
>> -Eric Dalquist
>> 
>> On Sat, Apr 15, 2017 at 8:09 AM Craig Russell > > wrote:
>> Dear Eric Dalquist,
>> 
>> We are reviewing our records to be sure that all submitted ICLAs are on 
>> file.
>> Unfortunately, we are unable to locate the ICLA that you submitted 
>> earlier.
>> 
>> Can you please resubmit to secret...@apache.org 
>> ? 
>> https://urldefense.proofpoint.com/v2/url?u=http-3A__apache.org_licenses_-23submitting&d=DwIFaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=DKWhdZdh69Kb6XA85A6vmYASgWIRD5RAywexyAJQArI&m=u29WDved3LSsHM8E1RYtvELY463RxF5Lehe_Xi8C1zc&s=0x9hY6QUQlsexxFxnFpmkY0MM1ALXTbH1HTk94PXuFY&e=
>>   
>> 
>> Please do *not* use an apache email as your E-Mail address.
>> You can send the original ICLA (if the email address is still valid) or 
>> a new one.
>> 
>> Best regards,
>> 
>> 
>> 
> 
> 

Craig L Russell
c...@apache.org

Re: Tooling for: Your Apache ICLA has gone missing

[Craig Russell]

Workflow:

Secretary determines that a replacement icla is not coming.

Secretary requests infra to disable the account.

Infra disables the account. How does whimsy know that the account is disabled? 

Secretary updates iclas.txt with "disabled; no icla on file"

The icla-lint should be able to reconcile disabled account in LDAP with 
disabled account in iclas.txt.

How should whimsy committer display disabled accounts? Should there be a date 
stamp when the account was disabled?

Craig

> On Apr 16, 2017, at 5:08 PM, Craig Russell  wrote:
> 
> Looks like there is agreement with infra that accounts that were created and 
> now there is no icla on file should be disabled. 
> 
> I've asked infra to disable a number of these accounts and I've updated 
> iclas.txt to indicate that they are disabled.
> 
> If/when the committers show up, it's easy enough to file their iclas and get 
> them back to commit status.
> 
> Craig
> 
>> On Apr 16, 2017, at 11:46 AM, sebb  wrote:
>> 
>> On 15 April 2017 at 16:30, Sam Ruby  wrote:
>>> On Sat, Apr 15, 2017 at 11:21 AM, Craig Russell  wrote:
 So how do we handle this?
 
 We need to remove the iclas.txt entry for edalquist, which I can do 
 manually. We also need to remove the LDAP entry, which I do not even know 
 how to do.
>>> 
>>> Sebb would argue that the ID should be disabled, not removed.
>> 
>> Yes, because otherwise the id might be reallocated to someone else.
>> Also we might lose details of code commits.
>> 
>>> Whether
>>> it is disabling or removing, currently this authority is reserved by
>>> the infrastructure team to themselves.  What could be done is a delete
>>> account request, much like we currently have a create account request.
>> 
>> I think deletion is too strong unless it can be shown that the id has
>> never been used for a CVS/SVN/Git commit.
>> 
>>> Should the ID be removed, it would also need to be removed from each
>>> group that this individual is a member of:
>>> 
>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__whimsy.apache.org_roster_committer_edalquist&d=DwIFaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=DKWhdZdh69Kb6XA85A6vmYASgWIRD5RAywexyAJQArI&m=u29WDved3LSsHM8E1RYtvELY463RxF5Lehe_Xi8C1zc&s=P21mBvHTRxHD8i--NFC7vNrm4TvhTc6Gf81QpxiiINM&e=
>>>  
>> 
>> +1
>> 
 Is there a chance we can add a button to the icla-lint whimsy page to do 
 both of these?
>>> 
>>> I generally shy away from writing code that I don't have the karma to test. 
>>>  :-)
>>> 
 Craig
>>> 
>>> - Sam Ruby
>>> 
> Begin forwarded message:
> 
> From: Eric Dalquist 
> Subject: Re: Your Apache ICLA has gone missing
> Date: April 15, 2017 at 8:15:30 AM PDT
> To: Craig Russell , edalqu...@apache.org
> Cc: Secretary 
> 
> Thanks for letting me know. Unfortunately my current situation prevents 
> me from submitting an ICLA so I should likely be removed as an eligible 
> Apache committer for now.
> 
> Thanks,
> -Eric Dalquist
> 
> On Sat, Apr 15, 2017 at 8:09 AM Craig Russell  > wrote:
> Dear Eric Dalquist,
> 
> We are reviewing our records to be sure that all submitted ICLAs are on 
> file.
> Unfortunately, we are unable to locate the ICLA that you submitted 
> earlier.
> 
> Can you please resubmit to secret...@apache.org 
> ? 
> https://urldefense.proofpoint.com/v2/url?u=http-3A__apache.org_licenses_-23submitting&d=DwIFaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=DKWhdZdh69Kb6XA85A6vmYASgWIRD5RAywexyAJQArI&m=u29WDved3LSsHM8E1RYtvELY463RxF5Lehe_Xi8C1zc&s=0x9hY6QUQlsexxFxnFpmkY0MM1ALXTbH1HTk94PXuFY&e=
>   
> 
> Please do *not* use an apache email as your E-Mail address.
> You can send the original ICLA (if the email address is still valid) or a 
> new one.
> 
> Best regards,
> 
> 
> Craig L Russell
> Secretary, Apache Software Foundation
> c...@apache.org  
> https://urldefense.proofpoint.com/v2/url?u=http-3A__db.apache.org_jdo&d=DwIFaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=DKWhdZdh69Kb6XA85A6vmYASgWIRD5RAywexyAJQArI&m=u29WDved3LSsHM8E1RYtvELY463RxF5Lehe_Xi8C1zc&s=hyS7i2_csMmPtIcRUOZ0bB56UYCJyFzSeY5mhiI-JkY&e=
>   
> 
> 
 
 Craig L Russell
 Secretary, Apache Software Foundation
 c...@apache.org  

Re: Tooling for: Your Apache ICLA has gone missing

[Sam Ruby]

On Sun, Apr 16, 2017 at 8:08 PM, Craig Russell  wrote:
> Looks like there is agreement with infra that accounts that were created and 
> now there is no icla on file should be disabled.
>
> I've asked infra to disable a number of these accounts and I've updated 
> iclas.txt to indicate that they are disabled.
>
> If/when the committers show up, it's easy enough to file their iclas and get 
> them back to commit status.

I suggest adding some form of the above to your board report.

- Sam Ruby

Re: Tooling for: Your Apache ICLA has gone missing

[Craig Russell]

Looks like there is agreement with infra that accounts that were created and 
now there is no icla on file should be disabled. 

I've asked infra to disable a number of these accounts and I've updated 
iclas.txt to indicate that they are disabled.

If/when the committers show up, it's easy enough to file their iclas and get 
them back to commit status.

Craig

> On Apr 16, 2017, at 11:46 AM, sebb  wrote:
> 
> On 15 April 2017 at 16:30, Sam Ruby  wrote:
>> On Sat, Apr 15, 2017 at 11:21 AM, Craig Russell  wrote:
>>> So how do we handle this?
>>> 
>>> We need to remove the iclas.txt entry for edalquist, which I can do 
>>> manually. We also need to remove the LDAP entry, which I do not even know 
>>> how to do.
>> 
>> Sebb would argue that the ID should be disabled, not removed.
> 
> Yes, because otherwise the id might be reallocated to someone else.
> Also we might lose details of code commits.
> 
>> Whether
>> it is disabling or removing, currently this authority is reserved by
>> the infrastructure team to themselves.  What could be done is a delete
>> account request, much like we currently have a create account request.
> 
> I think deletion is too strong unless it can be shown that the id has
> never been used for a CVS/SVN/Git commit.
> 
>> Should the ID be removed, it would also need to be removed from each
>> group that this individual is a member of:
>> 
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__whimsy.apache.org_roster_committer_edalquist&d=DwIFaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=DKWhdZdh69Kb6XA85A6vmYASgWIRD5RAywexyAJQArI&m=u29WDved3LSsHM8E1RYtvELY463RxF5Lehe_Xi8C1zc&s=P21mBvHTRxHD8i--NFC7vNrm4TvhTc6Gf81QpxiiINM&e=
>>  
> 
> +1
> 
>>> Is there a chance we can add a button to the icla-lint whimsy page to do 
>>> both of these?
>> 
>> I generally shy away from writing code that I don't have the karma to test.  
>> :-)
>> 
>>> Craig
>> 
>> - Sam Ruby
>> 
 Begin forwarded message:
 
 From: Eric Dalquist 
 Subject: Re: Your Apache ICLA has gone missing
 Date: April 15, 2017 at 8:15:30 AM PDT
 To: Craig Russell , edalqu...@apache.org
 Cc: Secretary 
 
 Thanks for letting me know. Unfortunately my current situation prevents me 
 from submitting an ICLA so I should likely be removed as an eligible 
 Apache committer for now.
 
 Thanks,
 -Eric Dalquist
 
 On Sat, Apr 15, 2017 at 8:09 AM Craig Russell >>> > wrote:
 Dear Eric Dalquist,
 
 We are reviewing our records to be sure that all submitted ICLAs are on 
 file.
 Unfortunately, we are unable to locate the ICLA that you submitted earlier.
 
 Can you please resubmit to secret...@apache.org 
 ? 
 https://urldefense.proofpoint.com/v2/url?u=http-3A__apache.org_licenses_-23submitting&d=DwIFaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=DKWhdZdh69Kb6XA85A6vmYASgWIRD5RAywexyAJQArI&m=u29WDved3LSsHM8E1RYtvELY463RxF5Lehe_Xi8C1zc&s=0x9hY6QUQlsexxFxnFpmkY0MM1ALXTbH1HTk94PXuFY&e=
   
 
 Please do *not* use an apache email as your E-Mail address.
 You can send the original ICLA (if the email address is still valid) or a 
 new one.
 
 Best regards,
 
 
 Craig L Russell
 Secretary, Apache Software Foundation
 c...@apache.org  
 https://urldefense.proofpoint.com/v2/url?u=http-3A__db.apache.org_jdo&d=DwIFaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=DKWhdZdh69Kb6XA85A6vmYASgWIRD5RAywexyAJQArI&m=u29WDved3LSsHM8E1RYtvELY463RxF5Lehe_Xi8C1zc&s=hyS7i2_csMmPtIcRUOZ0bB56UYCJyFzSeY5mhiI-JkY&e=
   
 
 
>>> 
>>> Craig L Russell
>>> Secretary, Apache Software Foundation
>>> c...@apache.org  
>>> https://urldefense.proofpoint.com/v2/url?u=http-3A__db.apache.org_jdo&d=DwIFaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=DKWhdZdh69Kb6XA85A6vmYASgWIRD5RAywexyAJQArI&m=u29WDved3LSsHM8E1RYtvELY463RxF5Lehe_Xi8C1zc&s=hyS7i2_csMmPtIcRUOZ0bB56UYCJyFzSeY5mhiI-JkY&e=
>>>   
>>> >>  >

Craig L Russell
Architect
craig.russ...@oracle.com
P.S. A good JDO? O, Gasp!

Re: Tooling for: Your Apache ICLA has gone missing

[sebb]

On 15 April 2017 at 16:30, Sam Ruby  wrote:
> On Sat, Apr 15, 2017 at 11:21 AM, Craig Russell  wrote:
>> So how do we handle this?
>>
>> We need to remove the iclas.txt entry for edalquist, which I can do 
>> manually. We also need to remove the LDAP entry, which I do not even know 
>> how to do.
>
> Sebb would argue that the ID should be disabled, not removed.

Yes, because otherwise the id might be reallocated to someone else.
Also we might lose details of code commits.

> Whether
> it is disabling or removing, currently this authority is reserved by
> the infrastructure team to themselves.  What could be done is a delete
> account request, much like we currently have a create account request.

I think deletion is too strong unless it can be shown that the id has
never been used for a CVS/SVN/Git commit.

> Should the ID be removed, it would also need to be removed from each
> group that this individual is a member of:
>
> https://whimsy.apache.org/roster/committer/edalquist

+1

>> Is there a chance we can add a button to the icla-lint whimsy page to do 
>> both of these?
>
> I generally shy away from writing code that I don't have the karma to test.  
> :-)
>
>> Craig
>
> - Sam Ruby
>
>>> Begin forwarded message:
>>>
>>> From: Eric Dalquist 
>>> Subject: Re: Your Apache ICLA has gone missing
>>> Date: April 15, 2017 at 8:15:30 AM PDT
>>> To: Craig Russell , edalqu...@apache.org
>>> Cc: Secretary 
>>>
>>> Thanks for letting me know. Unfortunately my current situation prevents me 
>>> from submitting an ICLA so I should likely be removed as an eligible Apache 
>>> committer for now.
>>>
>>> Thanks,
>>> -Eric Dalquist
>>>
>>> On Sat, Apr 15, 2017 at 8:09 AM Craig Russell >> > wrote:
>>> Dear Eric Dalquist,
>>>
>>> We are reviewing our records to be sure that all submitted ICLAs are on 
>>> file.
>>> Unfortunately, we are unable to locate the ICLA that you submitted earlier.
>>>
>>> Can you please resubmit to secret...@apache.org 
>>> ? http://apache.org/licenses/#submitting 
>>> 
>>> Please do *not* use an apache email as your E-Mail address.
>>> You can send the original ICLA (if the email address is still valid) or a 
>>> new one.
>>>
>>> Best regards,
>>>
>>>
>>> Craig L Russell
>>> Secretary, Apache Software Foundation
>>> c...@apache.org  http://db.apache.org/jdo 
>>> 
>>>
>>
>> Craig L Russell
>> Secretary, Apache Software Foundation
>> c...@apache.org  http://db.apache.org/jdo 
>> 

Re: Tooling for: Your Apache ICLA has gone missing

[Sam Ruby]

On Sat, Apr 15, 2017 at 11:21 AM, Craig Russell  wrote:
> So how do we handle this?
>
> We need to remove the iclas.txt entry for edalquist, which I can do manually. 
> We also need to remove the LDAP entry, which I do not even know how to do.

Sebb would argue that the ID should be disabled, not removed.  Whether
it is disabling or removing, currently this authority is reserved by
the infrastructure team to themselves.  What could be done is a delete
account request, much like we currently have a create account request.

Should the ID be removed, it would also need to be removed from each
group that this individual is a member of:

https://whimsy.apache.org/roster/committer/edalquist

> Is there a chance we can add a button to the icla-lint whimsy page to do both 
> of these?

I generally shy away from writing code that I don't have the karma to test.  :-)

> Craig

- Sam Ruby

>> Begin forwarded message:
>>
>> From: Eric Dalquist 
>> Subject: Re: Your Apache ICLA has gone missing
>> Date: April 15, 2017 at 8:15:30 AM PDT
>> To: Craig Russell , edalqu...@apache.org
>> Cc: Secretary 
>>
>> Thanks for letting me know. Unfortunately my current situation prevents me 
>> from submitting an ICLA so I should likely be removed as an eligible Apache 
>> committer for now.
>>
>> Thanks,
>> -Eric Dalquist
>>
>> On Sat, Apr 15, 2017 at 8:09 AM Craig Russell > > wrote:
>> Dear Eric Dalquist,
>>
>> We are reviewing our records to be sure that all submitted ICLAs are on file.
>> Unfortunately, we are unable to locate the ICLA that you submitted earlier.
>>
>> Can you please resubmit to secret...@apache.org 
>> ? http://apache.org/licenses/#submitting 
>> 
>> Please do *not* use an apache email as your E-Mail address.
>> You can send the original ICLA (if the email address is still valid) or a 
>> new one.
>>
>> Best regards,
>>
>>
>> Craig L Russell
>> Secretary, Apache Software Foundation
>> c...@apache.org  http://db.apache.org/jdo 
>> 
>>
>
> Craig L Russell
> Secretary, Apache Software Foundation
> c...@apache.org  http://db.apache.org/jdo 
> 

Tooling for: Your Apache ICLA has gone missing

[Craig Russell]

So how do we handle this?

We need to remove the iclas.txt entry for edalquist, which I can do manually. 
We also need to remove the LDAP entry, which I do not even know how to do.

Is there a chance we can add a button to the icla-lint whimsy page to do both 
of these?

Craig

> Begin forwarded message:
> 
> From: Eric Dalquist 
> Subject: Re: Your Apache ICLA has gone missing
> Date: April 15, 2017 at 8:15:30 AM PDT
> To: Craig Russell , edalqu...@apache.org
> Cc: Secretary 
> 
> Thanks for letting me know. Unfortunately my current situation prevents me 
> from submitting an ICLA so I should likely be removed as an eligible Apache 
> committer for now.
> 
> Thanks,
> -Eric Dalquist
> 
> On Sat, Apr 15, 2017 at 8:09 AM Craig Russell  > wrote:
> Dear Eric Dalquist,
> 
> We are reviewing our records to be sure that all submitted ICLAs are on file.
> Unfortunately, we are unable to locate the ICLA that you submitted earlier.
> 
> Can you please resubmit to secret...@apache.org 
> ? http://apache.org/licenses/#submitting 
> 
> Please do *not* use an apache email as your E-Mail address.
> You can send the original ICLA (if the email address is still valid) or a new 
> one.
> 
> Best regards,
> 
> 
> Craig L Russell
> Secretary, Apache Software Foundation
> c...@apache.org  http://db.apache.org/jdo 
> 
> 

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