RFC 8874: Working Group GitHub Usage Guidance
In plain English — editorial summary, not part of the RFC
This document provides a set of guidelines for working groups that choose to use GitHub for their work.
Document record
- Document ID
- RFC8874
- Published
- August 2020
- Authors
- M. Thomson; B. Stark
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- gen
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7282On Consensus and Humming in the IETFCurrent
June 2014
- RFC 7221Handling of Internet-Drafts by IETF Working GroupsCurrent
April 2014
- RFC 5434Considerations for Having a Successful Birds-of-a-Feather (BOF) SessionCurrent
February 2009
- RFC 2291Requirements for a Distributed Authoring and Versioning Protocol for the World Wide WebCurrent
February 1998
- RFC 8875Working Group GitHub AdministrationCurrent
August 2020
- RFC 8721Advice to the Trustees of the IETF Trust on Rights to Be Granted in IETF DocumentsCurrent
February 2020
- RFC 8719High-Level Guidance for the Meeting Policy of the IETFUpdated
February 2020
- RFC 8718IETF Plenary Meeting Venue Selection ProcessUpdated
February 2020
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?