github_experiment_6
This is an old revision of the document!
GitHub Experiment 6 - RFC TBD
The plan
Select a document with the following characteristics:
- has a GitHub repo with the following features used: issue tracking, PRs
- XML source
- 25 pages or less
- not part of a cluster
- not time sensitive
- willing authors and AD
| Requestor | I-D | Pages | Experiment | Date Requested |
|---|---|---|---|---|
| Richard Barnes | draft-ietf-tls-subcerts-15 | 17 | Markdown & GitHub | 4 Oct 2022 |
| Robert Sparks | draft-ietf-sipcore-multiple-reasons | 4 | XML & GitHub | 2 Nov 2022 |
| Christopher Wood | draft-irtf-cfrg-hash-to-curve | 175 | XML & GitHub | |
| RFC Editor | draft-ietf-acme-subdomains | 22 | n/a; authors declined to participate.From Owen Friel (author):I just got wind of the current RPC github process, where RPC creates a new repo that they control and makes their changes there, and then the document authors/editors (with their own repo where the original document lives) have to create PRs against the RPC repo to revert any changes that RPC make.This is a github anti-pattern, and I have never heard of anyone using github like this for any purpose anywhere. Why can the RPC not submit PRs against the document's original repo?If trialing github for AUTH48 means we have to follow that crazy process, then I am not in favor of that at all. |
The RPC will fork the author's document repo.
The RPC will create PRs for copy edits and questions with suggested text.
The RPC will add open questions as issues.
The RPC and author will work in this fork during AUTH48.
The RPC will make formatting edits only after the author has approved copy edits.
github_experiment_6.1682537768.txt.gz · Last modified: (external edit)