Labeling Issues in the Gutenberg Project – DocsWP

Hello! I will be working closely with GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc.
https://wordpress.org/gutenberg/ for the next several months and am really pleased to be here!! My WordPress username is designsimply and I go by sheri on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.

Part of my work is centered around bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. gardening where my goal is to scrub bugs to fit the project’s workflow in a way that saves everyone else time by adding screenshots, checking validity, closing inactives, and sane labeling. Labels are important for historical reference too, so any work here should prove useful as the project grows!

Labeling rules I tend to follow:

Each issue should have a focus area and type label.
Each PR should have a focus area and status label.
Priority labels should only be set as needed—just using high and low is 👍.
High priority issues should have an assignee or be in an active milestone.
Action-based labels start with “Needs”.

I’ve made a few small changes to labels so far:

Added [Type] Duplicate (for tracking and so dupes can easily be filtered out of searches).
Combined [Type] Support and [Type] How do I? and renamed to [Type] Help Request.

Have I mentioned I love labels?! Let’s update them together as an iterative process. Deciding labels can be opinionated so open discussions about them will be fun and help us work together in good ways.

My next questions about labels:

Can we move Chrome and UI Components to something like Block Controls?
Can we move [Type] Plugin / Theme Interoperability to [Type] Plugin Conflict and [Type] Theme Conflict?
Should Won't Fix and Works For Me be [Type] labels?
I’d love to add Design Notes label as a way to track design decisions.
What is [Type] WP Core Bug for exactly?
Should Text Mode be changed to Edit as HTML to match the UIUI User interface?
Can we get rid of [Status] Stale in favor of closing?
Let’s use [Status] Needs More Info or close with a comment instead of Works For Me.
Would it be useful for devs to add [Status] Revisit to issues that are not good to keep open now but may be good to look at again in the future?

If you’re keen to help with Gutenberg bug gardening or discuss the inner amazingnesses of labeling 😊, then I would love to talk with you! Please comment here or say hello in #core-editor on Slack.

#gutenberg