Editor Chat Agenda: February 13th

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found a 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.? Create a ticket in the bug tracker.
Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.
Other questions? Here is a detailed handbook for contributors, complete with tutorials.

Andrew Duthie 9:29 pm on February 12, 2019
If time permits, I’d like to discuss one or both of the following workflow-related items:
- Another round of prompting feedback for the code owners implementation. It was discussed last week, but only very shortly after it was first introduced and before people had had a chance to settle into the workflow. It’s also undergone many iterations and at least a few of my own shared reflections [1] [2]
- I’d like to propose / solicit ideas about introducing a Probot integration for the 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/ repository. There’s some prior art already for this in the WordPress/WordPress GitHubGitHub 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 (example), and I’ve been experimenting and ideating about ways we can automate workflows in the Gutenberg repository.
designsimply 3:36 am on February 13, 2019

We discussed how to handle support requests in 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/. in last week’s meeting on Feb 6 (see notes).

As a result of that discussion, the following is a proposed update to the #coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-editor channel topic. We should review and approve this change in the Core Editor Weekly Chat on Feb 12.

WordPress core editor development and design. Weekly meetings held Wednesdays at 14:00 UTC.

For support requests, please ask at https://wordpress.org/support/forum/how-to-and-troubleshooting/ or https://wordpress.stackexchange.com/

For reference, the current topic for #core-editor is set to:

Editors, 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/ and editing UXUX User experience. https://make.wordpress.org/core/components/editor/ – weekly meeting 14:00 UTC

For comparison, here is what the #core channel topic is currently set to:

WordPress core development. NOT for support or general chatting.

In addition, following is a short snippet that can be used as a guideline to reply to help requests you see posted in Slack that you do not have time to answer. Our main goal is to optimize Gutenberg development productivity, but that should not prevent contributors and others from answering questions time-permitting. If you do spot a help request that you can answer, consider redirecting the person to the proper channel and then also helping them there if you have time because forums are the appropriate place for help requests. If you find something that you feel would be good to document and that could help many others, please consider opening a documentation PR as a result! We should also keep in mind that some questions which appear to be help requests on the surface can sometimes turn out to be bugs in disguise! We should be quick to recover those when we find them and help people understand how to write a solid 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. report because that will be the best way to make the problem become clear and actionable, a goal that’s helpful for everyone.

Hi there! Note that this channel is for WordPress core editor development and design discussions. For support requests, please ask at https://wordpress.org/support/forum/how-to-and-troubleshooting/ or https://wordpress.stackexchange.com/

Please adjust the wording to fit each situation as needed!

Thank you for being thoughtful about these discussions in our weekly meetings. It’s cool that you are bringing up these questions and wanting to organize work on the editor in ways to improve productivity while also setting good expectations.
- pbrocks 2:48 pm on February 13, 2019
  
  Love this:
  
  Hi there! Note that this channel is for WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor development and design discussions. For support requests, please ask at https://wordpress.org/support/forum/how-to-and-troubleshooting/ or https://wordpress.stackexchange.com/

Comments are closed.

Welcome!

Communication

Share this: