Return-Path: <mnot@mnot.net>
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 3B8A43A041E
 for <ietf-and-github@ietfa.amsl.com>; Sat, 23 May 2020 22:23:04 -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, RCVD_IN_MSPIKE_H3=0.001,
 RCVD_IN_MSPIKE_WL=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=mnot.net header.b=zkfoOVW8;
 dkim=pass (2048-bit key)
 header.d=messagingengine.com header.b=kE2MGCaG
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 zozar3FCOvze for <ietf-and-github@ietfa.amsl.com>;
 Sat, 23 May 2020 22:23:02 -0700 (PDT)
Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com
 [64.147.123.19])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id C5F9B3A041D
 for <ietf-and-github@ietf.org>; Sat, 23 May 2020 22:23:01 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44])
 by mailout.west.internal (Postfix) with ESMTP id 68F1E7F2;
 Sun, 24 May 2020 01:23:00 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163])
 by compute4.internal (MEProxy); Sun, 24 May 2020 01:23:00 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=
 content-type:mime-version:subject:from:in-reply-to:date:cc
 :content-transfer-encoding:message-id:references:to; s=fm2; bh=w
 ZSSTf2wrIX7hPvSGE9ys8MN8z+ipaf5NMdg6qHo0Co=; b=zkfoOVW8cqMXgXcMp
 uwQbp6V6pZjb04LH5SdwZ0IZvRwU2xUKLaUWIF3hTF8ILONKNjTNpQZCPsZtMUUe
 jCm8kT0we6PySufq/ZjMbnRlBUSt7rbLiOnD7tHCUDLVSIkByhC25YmhXszVfdPQ
 RNAwzcfnmeTG+N7njrEzGex0k1XPEV0l4J6Mi40eNP9FDSrlOJdtmn1mBR/FJo7l
 HdBbcxfkzrGhxV+BDX8/ggsJToQqexGWiUNa6BKRmDrfVEfZZWkx9xSjgE+NDpm0
 rgf0BMTjUs03ztYPYsMuBIHX55FvlWcwsD4os37PGBzPRmcPGquh90PARDKTx5Bk
 TU+1g==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
 messagingengine.com; h=cc:content-transfer-encoding:content-type
 :date:from:in-reply-to:message-id:mime-version:references
 :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender
 :x-sasl-enc; s=fm2; bh=wZSSTf2wrIX7hPvSGE9ys8MN8z+ipaf5NMdg6qHo0
 Co=; b=kE2MGCaGt0aUDTaHt654vpdJ00V9nsyQLDwcw9F3qsWI3H1mnt/f2yAZi
 gA1ZuGNLlstMNvoxbjAeE5i4iH61G79ou2zvQYZ9MaMDudXhSEerkb2RxkFUgHZT
 mEvYOKjfB8xS4/kLMQFyxiJFqbnVaaLeNM+Py5szyhy+Hziw2l66Fj7yvPgMyTbM
 E5yZJ49ERLOu3J/0r3qWRHDdyQGktMK0RGhL5Bd4Qb0w/By4Hg9cy+F8jefjhgru
 5Xy25rJW1+DFvylEogfJSvimWubJGB1dzVHFWUQxYZU5G/fgMZvsca9dD6hDTNtS
 YHgoK9D7OWYwxaQ1HQJ/4MzvdxPWg==
X-ME-Sender: <xms:swTKXhdHuJlDFc5NT7QBhtpjvz2F_tUWKuH1EpvFjbABLLoxepIisg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedruddujecutefuodetggdotefrodftvfcurf
 hrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecuuegr
 ihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjug
 hrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtddvnecuhfhrohhmpeforghrkhcupfho
 thhtihhnghhhrghmuceomhhnohhtsehmnhhothdrnhgvtheqnecuggftrfgrthhtvghrnh
 epieelgfehgffgueeiuedtgeeiiedvleffudelgfeivdethfekvdelveekhfekteevnecu
 ffhomhgrihhnpehgihhthhhusgdrtghomhdpihgvthhfrdhorhhgpdhmnhhothdrnhgvth
 enucfkphepudduledrudejrdduheekrddvhedunecuvehluhhsthgvrhfuihiivgeptden
 ucfrrghrrghmpehmrghilhhfrhhomhepmhhnohhtsehmnhhothdrnhgvth
X-ME-Proxy: <xmx:swTKXvMKf8aemRqbJP0lFd2S8ZrPoSaoVuwIAh9XHdNDy1NiYDvFZA>
 <xmx:swTKXqhTUnHUrgadbUr_9Ds0HAN61aTTG453syy1F8u3FftqVJs1Ug>
 <xmx:swTKXq_6-Uod2_N3S8iXPzr6eZJjU7H9Q4VIoUfGY23J_HK5qLicEw>
 <xmx:tATKXuUMjvQDw1sMVz82T-vaq2X6Owxa1sDCyVIlqq_zRJV1KOZVMw>
Received: from macbook-air.mnot.net
 (119-17-158-251.77119e.mel.static.aussiebb.net [119.17.158.251])
 by mail.messagingengine.com (Postfix) with ESMTPA id A9098306650F;
 Sun, 24 May 2020 01:22:58 -0400 (EDT)
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <3FD4710B-52E4-4D84-A4F2-AC4BA074252D@eggert.org>
Date: Sun, 24 May 2020 15:22:56 +1000
Cc: "ietf-and-github@ietf.org," <ietf-and-github@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <13E62784-0343-4E22-AE61-73F33165F8BD@mnot.net>
References: <3FD4710B-52E4-4D84-A4F2-AC4BA074252D@eggert.org>
To: Lars Eggert <lars@eggert.org>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-and-github/lOXUZJBXoZOTFT-9N-_HeLTT3qk>
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: Sun, 24 May 2020 05:23:05 -0000

I don't think this is a good idea -- at least not without a lot more =
checking / consultation.

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:
>=20
> Hi,
>=20
> so orgs can now set themselves up to receive sponsorships through =
GitHub Sponsors: https://github.com/sponsors/accounts
>=20
> I'm contemplating a test balloon with the quicwg org, setting it up so =
that any sponsorship would go to the IETF LLC.
>=20
> Anyone see a downside to this?
>=20
> 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/

