User Tools

Site Tools


github_auth48_experiment

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision Both sides next revision
github_auth48_experiment [2021/02/05 12:12]
arusso
github_auth48_experiment [2021/02/05 12:22]
arusso
Line 9: Line 9:
 | Publication    |  2018-08-10 |   2021-01-20 | | Publication    |  2018-08-10 |   2021-01-20 |
 | GitHub repo    |  https://github.com/tlswg/tls13-rfc |  https://github.com/rtcweb-wg/jsep | | GitHub repo    |  https://github.com/tlswg/tls13-rfc |  https://github.com/rtcweb-wg/jsep |
 +^ AUTH48 details  ^^^
 +| Time in state  |   8.2 weeks |   28.3 weeks |
 +| # questions at start  |   58 |    60\\ (yielded [[https://github.com/rtcweb-wg/jsep/issues?q=is%3Aissue+is%3Aclosed+assignee%3Aajeanmahoney|78 issues]] in GitHub) |  
 +
  
 ==== Process Plan in 2018 ==== ==== Process Plan in 2018 ====
Line 30: 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. 
  
-==== Evaluation Criteria (defined in 2018====+==== Evaluation Criteria in 2018 ====
  
 === RPC Criteria === === RPC Criteria ===
Line 63: Line 67:
   * 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 154: Line 159:
 </code> </code>
  
-=== Feedback from RFC Editor (in 2018) ===+=== 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