This is the first attempt at a high-level overview of work being done in the WordPress project. It was very hard to accomplish, and I’m not sure this is the right format/organization. Nothing about this format is set in stone, however, it’s a start! You can learn more about each of these teams at make.wordpress.orgWordPress.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/.
From the Development Teams
- Shipped: Feature Flags are merged into 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/ repo!
- Discussion: Scope and timing discussions are underway.
- Discussion: JS is looking for feedback on implementing the npm monorepo declaration in the WordPress npm packages.
- Action: Work has started on getting the block editor into the mobile apps.
- Action: Privacy has narrowed their scope to ten tickets for the release.
From the Design Teams
- Shipped: Widgets ported to Blocks design work is complete.
- Discussion: Navigation block is a large undertaking. Feedback is being collected right now.
- Discussion: AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) discussions around block-specific keyboard navigation controls, and the navigation block.
- Discussion: Groundwork for the section block is ongoing.
- Action: Help is needed to implement automated testing with AxeCore.
- Action: Accessibility has narrowed their scope to 32 tickets for the release.
- Action: Calls for design on PHP upgrade page, Showcase update, and Site Health Check.
From the Community Teams
- Discussions: There are 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 marked with support that could use some feedback (dev, and design).
- Discussion: There is an internationalization ticket in need of feedback around some desired new functionality.
Action: The User Docs for Gutenberg could some fresh volunteers to help it get it shipped! - Action: Training and Meta are preparing updates to learn.wordpress.org site.
- Action: Training team is looking for people who are able to write lesson plans.
From the Operations Teams
- Discussion: Changes to the Gutenberg page have been proposed.
- Action: A plan has been formed to manage re-opening a number of TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets.
Noteworthy Dates
- Feb 21 – Targeted 5.1 release date
- Mar 12 – Targeted 5.1.1 release date (if needed)
- Apr 23 – Proposed 5.2 release date
- May 11 – Global WordPress Translation Day 4