Re: [Ietf-and-github] GitHub Sponsors for Organizations

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 25 May 2020 20:49 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf-and-github@ietfa.amsl.com
Delivered-To: ietf-and-github@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06C653A05A0 for <ietf-and-github@ietfa.amsl.com>; Mon, 25 May 2020 13:49:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p0r4DcqFVdOz for <ietf-and-github@ietfa.amsl.com>; Mon, 25 May 2020 13:48:59 -0700 (PDT)
Received: from mail-pg1-x533.google.com (mail-pg1-x533.google.com [IPv6:2607:f8b0:4864:20::533]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 545813A053F for <ietf-and-github@ietf.org>; Mon, 25 May 2020 13:48:59 -0700 (PDT)
Received: by mail-pg1-x533.google.com with SMTP id p21so9030914pgm.13 for <ietf-and-github@ietf.org>; Mon, 25 May 2020 13:48:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=WaERjQ/JGf/P0UJ9Uk/jsAUSEWrVPHfwqZFfMWb1Xj8=; b=VkVnhKSuodUJ8dEeVEXrJJO+VELO/KRleCH4bsDvnad/wApVMnQJcPPq0ikUEex6W+ IgGJpFEjIMLg0bTAInWKBuWFGuzPVE/sJL9n/FIq1r56NJ2VBh5219b8lFNBp/i/1ccS YEtpGxuNI72FnYSPC8lWCqYGRkBfaLQ34qMbe2yaj6dN/cF1b4CLsPvdG85amBXTtCSl KFBoc0VmzLd5ZZKZeGRYbpjIocfwlj/8q0vNVMGpceJa6YBi55pmTXtV1aDzCpxydv8y Zfwj3xPh293OEPCiG+MJQ65T6KEoQ+WiERVElRpR7F3ZpDPfQrNJMeUEslfrVZp5iUSz 09Ow==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=WaERjQ/JGf/P0UJ9Uk/jsAUSEWrVPHfwqZFfMWb1Xj8=; b=aie1A2qZHQJoEGOT7VWheS9f+9VQpFIXmLS6vspWPPXdRuJoLJwdBSxCDBgGgxX+fe oExcAyAHRdjYxB5EMOp/lm+IdoBIJAtvvqPoXsDBZFPinLo9yNfrtOg12yD7th3nITGi FjHlW3pcizlnQM2JE03EOseGS8yZIJBT50yPnEMesAPNfPwpDuzQ7s7VPMThHoxA0ZUo uXN3l66GmhsKFShE8NY3Dd5yZ8qK0objooE0gcUnF0Ac08DidadPjYIwcUC1q1lTDnF8 vLdLXKrtHTGfSgZt2c5Y8tbaiQHvn0Fw9MxNxpXeD0me0vBD2pqVl/3OT7Vsbn33E+gs gt3g==
X-Gm-Message-State: AOAM533uaSMMVVt0C74OSTyhtabsz8BlcT5Hi2xAma/AVUgu8gkDK7KP z4f3/oiCiBedd31zmmGGnyEOF8Gb
X-Google-Smtp-Source: ABdhPJwG5VDjHy5A3v9MRlcxLRnUt2Bxm53YoVwC9N7LjmqLCTOCswnhh7N/gShI7uNy+SM+IOolcw==
X-Received: by 2002:a05:6a00:46:: with SMTP id i6mr19348422pfk.146.1590439737547; Mon, 25 May 2020 13:48:57 -0700 (PDT)
Received: from [192.168.178.30] ([165.84.12.178]) by smtp.gmail.com with ESMTPSA id f11sm4690987pfk.58.2020.05.25.13.48.54 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 25 May 2020 13:48:56 -0700 (PDT)
To: Mark Nottingham <mnot@mnot.net>
Cc: Lars Eggert <lars@eggert.org>, ietf-and-github@ietf.org, ietf-and-github@ietf.org
References: <3FD4710B-52E4-4D84-A4F2-AC4BA074252D@eggert.org> <13E62784-0343-4E22-AE61-73F33165F8BD@mnot.net>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <bff7ce63-e3c1-d5b7-fc8d-dbf54fffc128@gmail.com>
Date: Tue, 26 May 2020 08:48:52 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <13E62784-0343-4E22-AE61-73F33165F8BD@mnot.net>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/l9mI6XiWNcIA3El11UI37q2gmEc>
Subject: Re: [Ietf-and-github] GitHub Sponsors for Organizations
X-BeenThere: ietf-and-github@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of using GitHub in IETF activities, particularly for Working Groups" <ietf-and-github.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-and-github>, <mailto:ietf-and-github-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-and-github/>
List-Post: <mailto:ietf-and-github@ietf.org>
List-Help: <mailto:ietf-and-github-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-and-github>, <mailto:ietf-and-github-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 May 2020 20:49:02 -0000

On 24-May-20 17:22, Mark Nottingham wrote:
> I don't think this is a good idea -- at least not without a lot more checking / consultation.

Mark, I think that funds directed at a specific draft/solution would be a bad thing for many reasons, not least being that money is not a proxy for technical quality, and the IETF is supposed to choose solutions for their technical merit. So IMHO the funds must not be labelled with "quic" or any other specific technology.

But if the funds are by construction sent to a suitable general account via ISOC or IETF LLC, I don't see an ethical problem, and (IANAL) I doubt there could be anti-trust problems, and they could presumably be treated as 501(c)(3) donations for US tax purposes.

I agree of course that this must be carefully checked by legal/tax experts.

If the LLC stopped accepting donations, I think we'd have much more fundamental problems.

   Brian

> 
> Potential issues:
> 
> - The primary purpose of standards (at least to lawyers) is countering anti-trust concerns. Does allowing sponsorship of individual efforts create a perception of conflict of interest? Especially if the sponsorships are visible to the Chairs, the WG, etc.
> 
> - GitHub appears to require you to create a Stripe account for the funds to be deposited into. Presumably, you'd then forward them to IETF LLC. Does this  create any reporting obligations or potential liabilities for you in the EU, US, etc.?
> 
> - Likewise, as a co-controller of the GitHub account, does it create any obligations for me and Lucas (keeping in mind that I'm a citizen of two countries, one of which is has a notoriously complex tax system)?
> 
> - What measures will we take to make the forwarding of funds (as well as any deducted fees, currency conversions, etc.) transparent to donors?
> 
> - If the LLC stops accepting donations, where will remaining funds go?
> 
> Etc.
> 
> Cheers,
> 
> 
>> On 23 May 2020, at 12:19 am, Lars Eggert <lars@eggert.org> wrote:
>>
>> Hi,
>>
>> so orgs can now set themselves up to receive sponsorships through GitHub Sponsors: https://github.com/sponsors/accounts
>>
>> I'm contemplating a test balloon with the quicwg org, setting it up so that any sponsorship would go to the IETF LLC.
>>
>> Anyone see a downside to this?
>>
>> Thanks,
>> Lars
>> _______________________________________________
>> Ietf-and-github mailing list
>> Ietf-and-github@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf-and-github
> 
> --
> Mark Nottingham   https://www.mnot.net/
> 
> _______________________________________________
> Ietf-and-github mailing list
> Ietf-and-github@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-and-github
>