community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Roman Shaposhnik <>
Subject Re: ASF for Google Code-In
Date Mon, 31 Oct 2016 23:26:25 GMT
On Mon, Oct 31, 2016 at 4:19 PM, Mark Thomas <> wrote:
> On 31/10/2016 22:53, Roman Shaposhnik wrote:
>> Hi!
>> thanks for the positive feedback. As Mark said -- time is tight
>> so please respond to the following ASAP.
>> I went through the registration process on behalf of ASF and
>> two statements stood out:
>>    1. Google is asking whether we'd be comfortable supplying
>>     ~200 small'ish tasks. I think we are.
> We should be able to do that.
>>     2. There's an Organization Agreement that I'm expected to click
>>     through. I'm attaching it bellow. It looks pretty bare bones to me,
>>     but if anything jumps at you -- please let me know ASAP.
> Two issues jump out at me.
> You don't have the authority to sign it. You need to be an officer of
> the foundation to do that and as I recall you aren't currently a V.P..

I don't think that's required. At least not on the Google side. They
defined who can sign up an org on the first screen and it was "any
active member..."

Now, as a board member you may have a take on whether that's
ok from ASF side, but its ok with Google.

> I'm not comfortable with the Indemnities section. Our liability to
> Google is unlimited with no control over the expenses that Google could
> rack up. There are various scenarios that are well within the bounds of
> possibility that could trigger a liability for us. That exposes that ASF
> to a massive potential risk.
> Google's liability to us is limited to a mere $1,000.
> Putting on my director hat, V.P. Legal (Bcc'd) needs to sign off on this
> before anyone commits the ASF to this agreement.

Hm. Ok. That could be a deal breaker. Well, if V.P. Legal can chime
in one way or the other ASAP -- that'd be highly appreciated.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message