Dev chat summary: June 26

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.

Another relatively quiet devchat, with folks returning from WCEU and getting into holiday mode here in the US.

We had one announcement: 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/ 6.0! Props @karmatosed and all the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-editor and Gutenberg contributors. It looks amazing!

@desrosj led a brief discussion of when and how we might release a 5.2.3. Two tickets in TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. have that milestone, but one of them, #47561, is a layout issue and not a functionality issue.

So over the next few weeks, we (you the reader, the community, the component maintainers and I the copywriter) will see how the scheduling for 5.3 shakes out and let that inform the point-release decision.

Meantime, @desrosj suggests we all just keep working on our tickets until we learn more about the specifics of 5.3.

In open floor, @joyously noted that there are a lot of metaMeta 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. tickets to improve the SEO of the .org site. She suggests that some of those be incorporated into WP, to fix it for everyone.

@garrett-eclipse asked for a committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. to review ticketticket Created for both bug reports and feature development on the bug tracker. #37782.

@davidb will lead next week’s devchat.

I’ll be back July 10, and @chanthaboune will be back after that!

Welcome!

Communication

Share this: