Proposal for advancing issues while keeping editors in loop#182
Merged
Conversation
Based on the experience in the past milestone, I suggest adding a "best practice" suggestion to the process, in which people submitting proposals are encouraged to notify editors of the progress. The idea is that this will be helpful for editors to feel in the loop, as we lacked this in this round, and that editors will use these notifications to advance issues on the project board. I purposely did not mention the project board though, as editors can be free to organize the work, but I think these phases are fairly universal. I think this proposal matches the discussion we had on the gap call too.
TallTed
reviewed
Dec 23, 2019
TallTed
reviewed
Dec 23, 2019
TallTed
reviewed
Dec 23, 2019
TallTed
reviewed
Dec 23, 2019
TallTed
reviewed
Dec 23, 2019
TallTed
reviewed
Dec 23, 2019
Co-Authored-By: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
Co-Authored-By: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
Co-Authored-By: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
Co-Authored-By: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
Co-Authored-By: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
Co-Authored-By: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
Member
Author
|
Many thanks, @TallTed ! |
Mitzi-Laszlo
added
the
process proposal
csarven
approved these changes
Dec 27, 2019
justinwb
reviewed
Jan 13, 2020
justinwb
left a comment
justinwb
left a comment
Member
There was a problem hiding this comment.
Good addition. Minor adjustments suggested but I'm on board with the overall add.
TallTed
reviewed
Jan 14, 2020
Co-Authored-By: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
timbl
approved these changes
Jan 15, 2020
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Based on the experience in the past milestone, I suggest adding a "best practice" suggestion to the process, in which people submitting proposals are encouraged to notify editors of the progress. The idea is that this will be helpful for editors to feel in the loop, as we lacked this in this round, and that editors will use these notifications to advance issues on the project board. I purposely did not mention the project board though, as editors can be free to organize the work, but I think these phases are fairly universal.
I think this proposal matches the discussion we had on the gap call too.