In the design weekly meeting a few weeks ago, discussion happened about how to align keywords in trac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. (core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and meta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress.) and labels from Gutenberg 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/ GitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ for design.
Why make changes?
Currently there are a wide range of keywords across meta and core trac for design, along with a lack of consistency. This also sees ui and ux feedback split, which often sees a confusion over what to use when.
The goal of this is to unify the workflow and making it easier for designers to follow and contribute. As triage is a focus for 2019, this also should make it easier for anyone work ing on that.
The proposal being put forward is to distill down to 2 keywords across both tracs and this aligns with current GitHub use:
- ‘Needs design feedback’: ‘ux-feedback’ and ‘ui-feedback’ will now merge into this one keyword.
- ‘Needs design’: this will be specific to require a design.
What do you think? Please leave a comment to discuss this change.