github_exp_9245
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| github_exp_9245 [2022/07/20 20:50] – created jmahoney | github_exp_9245 [2026/02/12 05:44] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| [[https:// | [[https:// | ||
| - | ===== High-Level Summary | + | ==== High-Level Summary ==== |
| * Process | * Process | ||
| * forked https:// | * forked https:// | ||
| Line 14: | Line 14: | ||
| * everything else as PRs or issues | * everything else as PRs or issues | ||
| + | ==== Lessons Learned ==== | ||
| + | |||
| + | This process requires a more knowledgeable GitHub user on the RPC side. There were many suggestions about "good GitHub practice." | ||
| + | |||
| + | Author preference for: | ||
| + | * improve subject lines | ||
| + | * consider whether external parties should be allowed to close issues | ||
| + | * close out all issues/PRs once they' | ||
| + | * improve " | ||
| + | |||
| + | |||
| + | ====RPC Lessons Learned==== | ||
| + | |||
| + | This process requires a more knowledgeable GitHub user on the RPC side. There were many suggestions about "good GitHub practice." | ||
| + | |||
| + | Author preference for: | ||
| + | * improve subject lines | ||
| + | * consider whether external parties should be allowed to close issues | ||
| + | * close out all issues/PRs once they' | ||
| + | * improve " | ||
| + | |||
| + | Forking the repository can be confusing. I found myself looking at both to compare things and sometimes found myself confused about whether I was in the right repo. If we fork, we should consider whether/how to clear all earlier branches. | ||
| + | |||
| + | ==== Author Feedback ==== | ||
| + | |||
| + | * What were the advantages of using GitHub during AUTH48? | ||
| + | * Lars Eggert (author): Easier review of proposed changes; compartmentalized discussion | ||
| + | |||
| + | * What were the disadvantages of using GitHub during AUTH48? | ||
| + | * Lars Eggert (author): RPC needs to fine-tune their GitHub use a bit more | ||
| + | |||
| + | * Was communication clear and easy to follow? | ||
| + | * Lars Eggert (author): Yes | ||
| + | |||
| + | * Were there any aspects of communication that were challenging? | ||
| + | * Lars Eggert (author): No | ||
| + | |||
| + | * How may we improve the README.md? | ||
| + | * Lars Eggert (author): (no response) | ||
| + | |||
| + | * Were the issues appropriately " | ||
| + | * Lars Eggert (author): No | ||
| + | |||
| + | * Were the issue labels helpful (e.g., rfced, question, editor-ready)? | ||
| + | * Lars Eggert (author): Yes | ||
| + | |||
| + | * In particular, did you find the process more efficient than the current email-based process? | ||
| + | * Lars Eggert (author): Yes | ||
| + | |||
| + | * What parts of the process would you like to see changed in a future experiment? | ||
| + | * Lars Eggert (author): Use more of GitHub' | ||
| + | |||
| + | * ADs and WG Chairs: Was it easy to track the discussion and resulting updates? | ||
| + | * (no response) | ||
| + | |||
| + | * Please provide any other comments and suggestions for improvement here. | ||
| + | * Lars Eggert (author): (no response) | ||
| + | |||
| + | * May we quote your replies on a public page documenting the experiment? | ||
| + | * Lars Eggert (author): Yes | ||
github_exp_9245.1658350251.txt.gz · Last modified: (external edit)
