This post is a proposal to start weekly Editor Bug Scrubs in #core-editor the week of June 28th. The scrubs will have a singular focus on issues in the 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/ repository. If you have feedback, please comment by June 24th, 2022.
Overview
New in the WordPress 6.0 release cycle, the role of Editor Triage Lead triages 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/ issues in the release and, to that end, runs weekly bug 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. scrubs in #core-editor.
As the release progressed, it became clear just how valuable these weekly meetings were in moving issues forward. And as the launch drew near, George Mamadashvili (@mamaduka) suggested continuing the scrubs a weekly, regardless of the release schedule.
Gutenberg right now has more than 4,200 open issues, and the number grows faster by the month.
And that number, especially out of context, makes a fairly convenient data point for observers to cite as evidence the project is not production-ready. Now, the same records that show the issues also show that dozens of contributors regularly and actively triage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. these issues.
But the process for working through any set of issues on GitHub or tickets on Trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. is informal — that is the nature of open source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL.. Which also means, therefore, that the process utterly depends on the interests and skillsets of those contributors who show up and do the work.
The result is an ad-hoc process that has produced hundreds of stale issues. Many of those are no longer relevant, but they stay open because nobody formally closes them. And truly important issues are at a nontrivial risk of slipping through the cracks.
Weekly bug scrubs will not single-handedly solve these problems. But they will dedicate a solid hour every week when team members (including you, who are reading this now!) get together, review issues, and make concrete plans to resolve them.
And during release cycles, the structure will give Editor Triage Leads a ready structure and a team of contributors to get more done, and produce a better experience, with every new version of WordPress.
Proposal
- What will happen? An Editor Weekly Bug Scrub meeting, in #core-editor Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/., every Tuesday at 1400 UTC.
- When will they start? The week of June 28, 2022.
- How will people know they’re happening? The scrubs will be on the Meetings Calendar.
- What will they cover? Bug scrubs will follow the normal process in the Handbook — but address only Gutenberg issues on GitHub.
- Who will run these scrubs? Members of the Gutenberg Triage Team. Nick Diego (@ndiego) and George Mamadashvili (@mamaduka) will run the first several. Then other team members will get onboarded for future sessions.
- How will they work with the release cycle?
- As soon as the release squad has a designated Editor Triage Lead, that person will lead the meetings and tailor triage efforts to he release in progress.
- At launch, meeting leadership will go back to the Gutenberg Triage Team. Ideally, Editor Triage Leads will have come from the Gutenberg Triage Team, so that transition should be seamless.
Next Steps
So what do you think?
Please share your comments by June 24th. If the community agrees Editor Bug Scrubs would be a good thing, the first scrub will be Tuesday, June 28, 2022, at 1400 UTC.
Props to George Mamadashvili (@mamaduka), Justin Tadlock (@greenshady), Héctor Prieto (@priethor), and Birgit Pauli-Haack (@bph) for their help in putting this proposal together.
(Ed. note: Also, did you know that anyone can lead a bug scrub, for any reason? That means you! And you can focus your scrub on any tickets you like, or any Gutenberg issues. (The difference: most of Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. runs on Trac, which uses tickets and patches. The block Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor runs on GitHub, which uses issues and pull requests. – @marybaum)
#bug-scrub, #editor, #gutenberg
