github_experiment_6
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| github_experiment_6 [2023/04/26 22:22] – sginoza | github_experiment_6 [2026/02/12 05:44] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== GitHub Experiment 6 - RFC TBD ====== | + | ====== GitHub |
| + | |||
| + | The following design was discussed at the [[114_github_workshop_followup|GitHub Workshop at IETF 114]] and followed for experiments held between IETF 114 and IETF 117. The design is based on the [[github_exp_9245|experiment with RFC 9245]]. | ||
| + | |||
| + | **Note:** Although the file format was initially limited to RFCXML, a markdown source file is now also acceptable. | ||
| ===== The plan ===== | ===== The plan ===== | ||
| Line 10: | Line 14: | ||
| * not time sensitive | * not time sensitive | ||
| * willing authors and AD | * willing authors and AD | ||
| - | |||
| - | ^Requestor | ||
| - | | [[rlb@ipv.sx|Richard Barnes]] | [[https:// | ||
| - | |[[rjsparks@nostrum.com|Robert Sparks]] | [[https:// | ||
| - | |[[caw@heapingbits.net|Christopher Wood]] | [[https:// | ||
| - | |RFC Editor | [[https:// | ||
| - | |||
| - | < | ||
| - | |||
| - | * From Richard Barnes < | ||
| - | I am all for using GitHub for AUTH48, but we should do it properly, | ||
| - | with all text changes being made by the RPC making pull requests | ||
| - | against the document repo [1]. | ||
| - | |||
| - | [1] https:// | ||
| - | |||
| - | * From Owen Friel < | ||
| - | 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/ | ||
| - | document lives) have to create PRs against the RPC repo to revert any | ||
| - | changes that RPC make. | ||
| - | |||
| - | This is a github anti-pattern, | ||
| - | github like this for any purpose anywhere. Why can the RPC not submit | ||
| - | PRs against the document' | ||
| - | |||
| - | If trialing github for AUTH48 means we have to follow that crazy process, | ||
| - | then I am not in favor of that at all. | ||
| - | |||
| - | * From Michael Richardson < | ||
| - | I don't want a github process :-) | ||
| - | |||
| - | I want a *GIT* process, that starts from our existing repos. I think that | ||
| - | RPC should run it on their own gitlab. | ||
| - | |||
| - | At the end of the day, if the authors are using github, they can take the git | ||
| - | repo back from the RPC and merge it, or not. | ||
| - | </ | ||
| - | |||
| - | |||
| The RPC will fork the author' | The RPC will fork the author' | ||
| Line 58: | Line 21: | ||
| The RPC will add open questions as issues. | The RPC will add open questions as issues. | ||
| - | The RPC and author will work in this fork during AUTH48. | + | The RPC and author will work in the RPC fork during AUTH48. |
| The RPC will make formatting edits only after the author has approved copy edits. | The RPC will make formatting edits only after the author has approved copy edits. | ||
| + | |||
| + | ---------------- | ||
| + | ^Requestor | ||
| + | | [[rlb@ipv.sx|Richard Barnes]] | [[https:// | ||
| + | |[[rjsparks@nostrum.com|Robert Sparks]] | [[https:// | ||
| + | |[[caw@heapingbits.net|Christopher Wood]] | [[https:// | ||
| + | |RFC Editor | [[https:// | ||
| + | |||
| ----- | ----- | ||
github_experiment_6.1682547759.txt.gz · Last modified: (external edit)