Documentation: mention workflow and high priority labeled issues #13362
Conversation
This file contains 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
Workflow labels are important for interacting with contributors at all levels and should be encouraged. We should also make sure to communicate well with other groups to ask them to use these workflows, such as the Design Team for the `Needs Design Feedback` label, the Gutenberg Team for the `Needs Decision` label, and all contributors or Support Team members who are developers for the `Needs Technical Feedback` label. This PR adds a note about workflow labels and also mentions that high priority issues should have an assignee and/or be in an active milestone. I also updated the `Accessibility` label to `Needs Accessibility Feedback` as it makes more sense for the description in this document.
designsimply
added
the
[Type] Developer Documentation
1 task
jorgefilipecosta
deleted the
update/mention-workflow-and-priority-labels
branch
youknowriad
pushed a commit
that referenced
this pull request
Mar 6, 2019
) Workflow labels are important for interacting with contributors at all levels and should be encouraged. We should also make sure to communicate well with other groups to ask them to use these workflows, such as the Design Team for the `Needs Design Feedback` label, the Gutenberg Team for the `Needs Decision` label, and all contributors or Support Team members who are developers for the `Needs Technical Feedback` label. This PR adds a note about workflow labels and also mentions that high priority issues should have an assignee and/or be in an active milestone. I also updated the `Accessibility` label to `Needs Accessibility Feedback` as it makes more sense for the description in this document.
youknowriad
pushed a commit
that referenced
this pull request
Mar 6, 2019
) Workflow labels are important for interacting with contributors at all levels and should be encouraged. We should also make sure to communicate well with other groups to ask them to use these workflows, such as the Design Team for the `Needs Design Feedback` label, the Gutenberg Team for the `Needs Decision` label, and all contributors or Support Team members who are developers for the `Needs Technical Feedback` label. This PR adds a note about workflow labels and also mentions that high priority issues should have an assignee and/or be in an active milestone. I also updated the `Accessibility` label to `Needs Accessibility Feedback` as it makes more sense for the description in this document.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Workflow labels are important for interacting with contributors at all levels and should be encouraged. We should also make sure to communicate well with other groups to ask them to use these workflows, such as the Design Team for the
Needs Design Feedbacklabel, the Gutenberg Team for theNeeds Decisionlabel, and all contributors or Support Team members who are developers for theNeeds Technical Feedbacklabel.This PR adds a note about workflow labels and also mentions that high priority issues should have an assignee and/or be in an active milestone.
I also updated the
Accessibilitylabel toNeeds Accessibility Feedbackas it makes more sense for the description in this document.https://wordpress.org/gutenberg/handbook/contributors/repository-management/