From nobody Mon Apr 19 12:37:31 2021 Return-Path: X-Original-To: wgchairs@ietfa.amsl.com Delivered-To: wgchairs@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBE583A4076 for ; Mon, 19 Apr 2021 12:37:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.002 X-Spam-Level: X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 MzXrYueli5lY for ; Mon, 19 Apr 2021 12:37:28 -0700 (PDT) Received: from jays-mbp.localdomain (unknown [158.140.230.105]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id EF5DE3A4078 for ; Mon, 19 Apr 2021 12:37:27 -0700 (PDT) From: Jay Daley Content-Type: multipart/alternative; boundary="Apple-Mail=_308DDBBF-02B9-4204-9DAE-FAE8BEBEF528" Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) Subject: Re: GitHub management Date: Tue, 20 Apr 2021 07:37:24 +1200 References: <9E5C7729-F839-4136-89BC-812B9A5A8DD5@ietf.org> To: Working Chairs In-Reply-To: <9E5C7729-F839-4136-89BC-812B9A5A8DD5@ietf.org> Message-Id: X-Mailer: Apple Mail (2.3608.120.23.2.4) Archived-At: X-BeenThere: wgchairs@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Working Group Chairs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Apr 2021 19:37:30 -0000 --Apple-Mail=_308DDBBF-02B9-4204-9DAE-FAE8BEBEF528 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 To follow up on this - the GitHub enterprise account has now been = created and we are in the process of transferring over existing GH = organisations to this new account as previewed below. The central = licensing that I referred to below is not quite as it was explained to = us and so is not being implemented just yet. Please let me know if you have any questions. Jay > On 31/03/2021, at 9:48 AM, Jay Daley wrote: >=20 > Hi >=20 > RFC 8875 sets out a plan for how GitHub repositories should be managed = and gives the Secretariat and Tools Team various tasks and = responsibilities. As it stands there are two issues with this. One is = the high administrative of multiple organisations and repositories. The = second is the limited access to features provided by the free tier, such = as the Audit API, which are useful for tools integrations. >=20 > To address this we are in the process of taking up a GitHub Enterprise = license. An enterprise account gives the following features: >=20 > - access to the Audit API that let=E2=80=99s us pull records of = everything for archiving > - allows the creation of unlimited organisations and public = repositories under this account. We can assign whoever we want to = manage those without them requiring a license while the Secretariat = remains an owner for when an admin change is needed. > - existing organisations can be included under this account if they = choose to move to the account > - all the repositories under the account switch from having their own = local licensing terms to central licensing terms, which will be = https://trustee.ietf.org/license-for-open-source-repositories.html to = comply with RFC 8875 (when that link is fixed) >=20 > This basically provides the features the Secretariat and Tools Team = need to deliver RFC 8875. It is also quite cheap as we can use the = minimum 10 user license pack provided that we don=E2=80=99t do anything = with private repositories, which would change the licensing = dramatically. =20 >=20 > Please let me know if you have any questions. >=20 > Jay >=20 > --=20 > Jay Daley > IETF Executive Director > jay@ietf.org >=20 --=20 Jay Daley IETF Executive Director jay@ietf.org --Apple-Mail=_308DDBBF-02B9-4204-9DAE-FAE8BEBEF528 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 To = follow up on this - the GitHub enterprise account has now been created = and we are in the process of transferring over existing GH organisations = to this new account as previewed below.  The central licensing that = I referred to below is not quite as it was explained to us and so is not = being implemented just yet.

Please let me know if you have any questions.

Jay
On = 31/03/2021, at 9:48 AM, Jay Daley <jay@ietf.org> wrote:

Hi

RFC 8875 sets out a plan for how GitHub = repositories should be managed and gives the Secretariat and Tools Team = various tasks and responsibilities.  As it stands there are two = issues with this.  One is the high administrative of multiple = organisations and repositories.  The second is the limited access = to features provided by the free tier, such as the Audit API, which are = useful for tools integrations.

To address = this we are in the process of taking up a GitHub Enterprise license. =  An enterprise account gives the following features:

- access to the Audit API that let=E2=80=99s = us pull records of everything for archiving
- allows the = creation of unlimited organisations and public repositories under this = account.  We can assign whoever we want to manage those without = them requiring a license while the Secretariat remains an owner for when = an admin change is needed.
- existing organisations can be = included under this account if they choose to move to the account
- all the repositories under the account switch from having = their own local licensing terms to central licensing terms, which will = be https://trustee.ietf.org/license-for-open-source-repositories.h= tml to comply with RFC 8875 (when that link is fixed)

This basically provides the features the = Secretariat and Tools Team need to deliver RFC 8875.  It is also = quite cheap as we can use the minimum 10 user license pack provided that = we don=E2=80=99t do anything with private repositories, which would = change the licensing dramatically.  

Please let me know if you have any questions.
Jay

--
Jay = Daley
IETF Executive Director
jay@ietf.org

=
-- 
Jay Daley
IETF = Executive Director
jay@ietf.org

= --Apple-Mail=_308DDBBF-02B9-4204-9DAE-FAE8BEBEF528--