github_auth48_experiment
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
github_auth48_experiment [2021/02/05 12:02] arusso |
github_auth48_experiment [2021/02/05 12:22] arusso |
||
|---|---|---|---|
| Line 5: | Line 5: | ||
| ^ ^ RFC 8446 | ^ ^ RFC 8446 | ||
| | I-D | [[https:// | | I-D | [[https:// | ||
| + | | I-D approved | ||
| | AUTH48 start | | AUTH48 start | ||
| | Publication | | Publication | ||
| | GitHub repo | https:// | | GitHub repo | https:// | ||
| + | ^ AUTH48 details | ||
| + | | Time in state | 8.2 weeks | 28.3 weeks | | ||
| + | | # questions at start | 58 | 60\\ (yielded [[https:// | ||
| + | |||
| ==== Process Plan in 2018 ==== | ==== Process Plan in 2018 ==== | ||
| Line 17: | Line 22: | ||
| * status of this memo | * status of this memo | ||
| * section movement to meet the style guide requirements (e.g., move acks and contribs to appear at the end) | * section movement to meet the style guide requirements (e.g., move acks and contribs to appear at the end) | ||
| - | - RFC Editor goes through the EDIT and RFC EDITOR process states and sends an email with a link to the XML file created in step 2 and the edited XML file at the start of AUTH48. | + | - RFC Editor goes through the EDIT and RFC EDITOR process states and sends an email with a link to the XML file created in step 2 and the edited XML file at the start of AUTH48. |
| - At the start of AUTH48, the author will create a Pull Request (PR) with the changes proposed by the RPC. The authors respond and point to the repository they created. | - At the start of AUTH48, the author will create a Pull Request (PR) with the changes proposed by the RPC. The authors respond and point to the repository they created. | ||
| - The relevant people from the RPC will subscribe to notifications from that repository using the “Watch” button and confirm they are watching. For this test case, Heather, Adam, and Martin will follow along as well. | - The relevant people from the RPC will subscribe to notifications from that repository using the “Watch” button and confirm they are watching. For this test case, Heather, Adam, and Martin will follow along as well. | ||
| Line 29: | Line 34: | ||
| - Final approval for the full document needs to result in an explicit email to the the RPC from each author indicating approval. GitHub will be used for editorial discussion, but the final text approval will be done via email. | - Final approval for the full document needs to result in an explicit email to the the RPC from each author indicating approval. GitHub will be used for editorial discussion, but the final text approval will be done via email. | ||
| - | ==== Relevant Documents ==== | + | ==== Evaluation Criteria in 2018 ==== |
| - | + | ||
| - | * **[[https:// | + | |
| - | * 2018-03-21: approved for publication as an RFC. | + | |
| - | * 2018-06-14: initiated AUTH48. provided XML file as described in step 2 above. | + | |
| - | * 2018-08-10: published as RFC 8446 | + | |
| - | * **[[https:// | + | |
| - | * 2018-03-01: approved for publication as an RFC. (in MISSREF because of normative references that are not yet approved) | + | |
| - | + | ||
| - | ==== Evaluation Criteria | + | |
| === RPC Criteria === | === RPC Criteria === | ||
| Line 67: | Line 63: | ||
| * 8.2 weeks | * 8.2 weeks | ||
| * Number of questions at start of AUTH48: 58 | * Number of questions at start of AUTH48: 58 | ||
| - | [[https:// | ||
| === Notes === | === Notes === | ||
| * future work will require mapping of GitHub account names to Authors, WG Chairs, Document Shepherds, ADs, Stream Managers (possible GDPR implications this information is outside the publishing industry norm for information stored about an individual during a publication process) | * future work will require mapping of GitHub account names to Authors, WG Chairs, Document Shepherds, ADs, Stream Managers (possible GDPR implications this information is outside the publishing industry norm for information stored about an individual during a publication process) | ||
| + | ==== Feedback in 2018 ==== | ||
| === Feedback from Eric Rescorla (author, RFC 8446) === | === Feedback from Eric Rescorla (author, RFC 8446) === | ||
| Line 163: | Line 159: | ||
| </ | </ | ||
| - | === Feedback from RFC Editor | + | === Feedback from RFC Editor === |
| This is the consolidated feedback from the RFC Editor regarding the experiment in using GitHub to process the TLS 1.3 document. Please note that this feedback focuses entirely on the GitHub experience; all comments regarding editorial changes are off topic. Also, the markdown conversation (i.e., editing in markdown, choosing a particular flavor of markdown) is also outside the scope of the experiment and this feedback. | This is the consolidated feedback from the RFC Editor regarding the experiment in using GitHub to process the TLS 1.3 document. Please note that this feedback focuses entirely on the GitHub experience; all comments regarding editorial changes are off topic. Also, the markdown conversation (i.e., editing in markdown, choosing a particular flavor of markdown) is also outside the scope of the experiment and this feedback. | ||
github_auth48_experiment.txt · Last modified: 2021/02/24 00:15 by arusso
Page Tools
