Re: GitHub management

Jay Daley <> Mon, 19 April 2021 19:37 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id DBE583A4076 for <>; Mon, 19 Apr 2021 12:37:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 0.002
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id MzXrYueli5lY for <>; Mon, 19 Apr 2021 12:37:28 -0700 (PDT)
Received: from jays-mbp.localdomain (unknown []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (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.\))
Subject: Re: GitHub management
Date: Tue, 20 Apr 2021 07:37:24 +1200
References: <>
To: Working Chairs <>
In-Reply-To: <>
Message-Id: <>
X-Mailer: Apple Mail (2.3608.
Archived-At: <>
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

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.


> On 31/03/2021, at 9:48 AM, Jay Daley <> 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’s 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 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’t 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 Daley
IETF Executive Director