Re: Tooling for: Your Apache ICLA has gone missing

2017-04-16 Thread 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

2017-04-16 Thread 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=DwIFaQ=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10=DKWhdZdh69Kb6XA85A6vmYASgWIRD5RAywexyAJQArI=u29WDved3LSsHM8E1RYtvELY463RxF5Lehe_Xi8C1zc=P21mBvHTRxHD8i--NFC7vNrm4TvhTc6Gf81QpxiiINM=
>>  
> 
> +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=DwIFaQ=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10=DKWhdZdh69Kb6XA85A6vmYASgWIRD5RAywexyAJQArI=u29WDved3LSsHM8E1RYtvELY463RxF5Lehe_Xi8C1zc=0x9hY6QUQlsexxFxnFpmkY0MM1ALXTbH1HTk94PXuFY=
   
 
 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=DwIFaQ=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10=DKWhdZdh69Kb6XA85A6vmYASgWIRD5RAywexyAJQArI=u29WDved3LSsHM8E1RYtvELY463RxF5Lehe_Xi8C1zc=hyS7i2_csMmPtIcRUOZ0bB56UYCJyFzSeY5mhiI-JkY=
   
 
 
>>> 
>>> Craig L Russell
>>> Secretary, Apache Software Foundation
>>> c...@apache.org  
>>> https://urldefense.proofpoint.com/v2/url?u=http-3A__db.apache.org_jdo=DwIFaQ=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10=DKWhdZdh69Kb6XA85A6vmYASgWIRD5RAywexyAJQArI=u29WDved3LSsHM8E1RYtvELY463RxF5Lehe_Xi8C1zc=hyS7i2_csMmPtIcRUOZ0bB56UYCJyFzSeY5mhiI-JkY=
>>>   
>>> >>  >

Craig L Russell
Architect

Re: Tooling for: Your Apache ICLA has gone missing

2017-04-16 Thread 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 
>>

RECOVERY: whimsy.apache.org (whimsy.apache.org (https)) is back up!

2017-04-16 Thread Ping My Box 
Hi there!
The service at whimsy.apache.org (whimsy.apache.org (https)) seems to be back 
in working order.

With regards,
Ping My Box - https://www.pingmybox.com/

ALERT: whimsy.apache.org (whimsy.apache.org (https)) is DOWN!

2017-04-16 Thread Ping My Box 

Hi there!
The service at whimsy.apache.org (whimsy.apache.org (https)) appears to be down 
from multiple locations around the world.

The exact error is:

Error component: response
Error code: Internal Server Error or equivalent bad message received: HTTP/1.1 
400 svn iclas ["svn: E175002: Unexpected HTTP status 400 'Bad Request' on 
'/repos/private/!svn/rvr/76125/documents/iclas'", "", "svn: E175009: Additional 
errors:", "svn: E175009: XML parsing failed: (400 Bad Request)"]
Debug output:
[Sun Apr 16 17:51:18 2017]: Initialising socket
[Sun Apr 16 17:51:18 2017]: Looking up hostname whimsy.apache.org...
[Sun Apr 16 17:51:18 2017]: Connecting to 207.244.88.137:443
[Sun Apr 16 17:51:18 2017]: Connected, sending HTTPS payload.
[Sun Apr 16 17:51:18 2017]: Analyzing server certificate
[Sun Apr 16 17:51:18 2017]: Saving certificate data
[Sun Apr 16 17:51:18 2017]: Reading response header from server
[Sun Apr 16 17:51:22 2017]: Caught exception: Internal Server Error or 
equivalent bad message received: HTTP/1.1 400 svn iclas ["svn: E175002: 
Unexpected HTTP status 400 'Bad Request' on 
'/repos/private/!svn/rvr/76125/documents/iclas'", "", "svn: E175009: Additional 
errors:", "svn: E175009: XML parsing failed: (400 Bad Request)"]





With regards,
Ping My Box - https://www.pingmybox.com/