Dev Chat Agenda for July 1st, 2020

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.

It’s July! Holy smokes.

Here is the agenda for the weekly meeting happening later today: June 30th, 2020 13:00 PDT.

Highlighted/Need Feedback Blogblog (versus network, site) Posts

Meeting Notes

Discussion

WordPress 5.5
- Pending bug scrubs
- Beta 1 next week

Components check-in and status updates

News from components
Components that need help/orphaned components
Cross-component collaboration

Open Floor

Got something to propose for the agenda, or a specific item relevant to our standard list above?

Please leave a comment, and say whether or not you’ll be in the chat, so the group can either give you the floor or bring up your topic for you, accordingly.

This meeting happens in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

#5-5, #agenda

Andrei Draganescu 8:08 am on July 1, 2020

Howdy!

Myself and a bunch of other folks have been working on a new, blockBlock 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.-based, menus page (nav-menus.php) in wp-adminadmin (and super admin) for a while. At the current stage of the project we think it’s time to start syncing with everyone else on how things evolve.

Therefore, we will host a weekly chat in #coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. about the current evolution and state of the new navigation screen.

The meeting will happen in #core every Wednesday at 7AM UTC, starting next week, on Jul 8th.

In general it will be a triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. around issues in 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/ labeled with either `[Feature] Navigation screen` or `[Block] Navigation` but also completely open to exploring any subject around improving the navigation creation process in WordPress, increasing compatibility with the incoming FSE and also maintaining backwards compatibility.

I will _not_ be able to make the meeting so thank you for bringing this up for me 🙂

Comments are closed.