Proposal: cancel core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor chat
The core editor chat is a 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/. meeting that takes place every week on Wednesdays in the core-editor channel of the WordPress Slack instance, focused on discussing topics related to the 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/ 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 development.
This meeting has served in time as a place for the following types of communication:
- general announcements about Gutenberg or WordPress
- Gutenberg project updates, on various features in development
- task coordination between the various people contributing
- community introductions and help during open floor
- issue escalation – bringing attention to specific issues
- requests for help or reviews, a place to ask for an extra pair of hands or eyes
The meeting has served us well over the years, but in the past two years several developments occurred:
- the post pandemic speed of people picking up these meetings was suboptimal
- the 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/ project management has been considerably better
- there are people managing tracking and overview issues, updating them with project status
- the project features of GitHub itself have been significantly upgraded
- several other efforts picked up steam:
- there is a new learn section on wordpress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/
- there is a revamped developer blog (versus network, site) on wordpress.org
- developer experience and outreach programs improved
- we have a constant stream of events like hallway hangouts on varied topics
Considering the above, I suggest that the meeting has now become an inefficient use of the time for those organizing it.
It’s not only that the attendance is low, but the topics discussed and the lack of interest in the meeting itself point to the fact that the other avenues are doing a better job at keeping people engaged and updated with the progress of Gutenberg in WordPress, as well as providing much better avenues for getting support to contribute to or implement the core editor.
Therefore we propose discontinuing the meeting.
What do you think? You’re all invited to chime in with pros and cons, ideas and anything related for the duration of a three week comment time for this proposal to cancel the core editor chat for an indeterminate duration of time.
Many thanks to the following list of people who have been helping across the years with running, summarizing and managing the agenda of the core editor chat:
@ajitbohra @annezazu @paaljoachim @fabiankaegy @jorgefilipecosta @get_dave @zieladam @bph
For the duration of the comment time (three weeks) there will be no more core editor chats (meetings).