The WordPress coreCoreCore 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 bugbugA 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.
Gutenberg 15.9.1 is the latest release following on from 15.9.0.
The RCrelease candidateOne of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). wasn’t released yet.
Check out the Issue for backporting the PHP changes from the Plugin for the WordPress 6.3 release. Please check whether you’ve received a pingPingThe act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” and if you have please take time to help get your changes ready.
Updates based on updated scope for site editing projects
Currently working on the release process for GutenbergGutenbergThe 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/ 16.0 RC1 and part of that is going through all of the PRs attached to the milestone to make sure each has a [Type] ... label. These are used to auto-generate the changelog.
Wanted to request that when folks create/review a PR, to please make sure they add a type label (i.e. [Type] Bug, [Type] Enhancement etc.).
Focusing on the Contributor Guide sections of the BlockBlockBlock 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 Handbook. The goal is to get each page updated and accurate as well as adding missing info.
Adding focus mode for Navigation Menus as part of work to add Navigation section to the Browse Mode sidebarSidebarA sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme..
Open Floor
It was a quiet meeting due to WCEU…
New Contributor review requests
@jeffchi introduced himself as a new contributor coming over from TYPO3.
The WP Feature Notifications project will be at WordCampWordCampWordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe Contributor DayContributor DayContributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/, led by @sephsekla. We are a small, focused team, and always on the lookout for new contributors, so we would encourage anyone to get involved!
WP Feature Notifications is a feature pluginFeature PluginA plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins, with a proposal to modernise the way in which WordPress handles emails, adminadmin(and super admin) notices and user notifications. We are working towards the MVPMinimum Viable Product"A minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future product development." - WikiPedia version of a new, centralised system, with both PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher and REST-based APIs.
Contributing
The project has something for everyone, and all new contributors are very welcome!
For developers and other more technical contributors, we have several areas to focus on:
In-progress PHP work for the MVP
JavaScriptJavaScriptJavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser.
https://www.javascript.com improvements to make better use of WordPress components
A provisional TypeScript rewrite of the JavaScript UIUIUser interface
We also have a number of areas to cover which are less technically focused:
Testing and feedback on our current proof of concept (version 0.2.0)
Feedback and pain points on the current WordPress notices and emails
Discussion and ideas for future requirements
No setup ahead of the event or prior knowledge is needed to get involved, but for more technical work we would recommend bringing a laptop with Docker, npm and Composer installed.
Additional information is included in this agenda to assist new and potential contributors to CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. preparing for WordCampWordCampWordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe’s Contributor DayContributor DayContributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/ this week.
Gutenberg 15.9.1 available. This minor releaseMinor ReleaseA set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. provides two fixes: custom fonts are back again visible on the editor and social icon colors now correctly reflect changes in Global Styles. Thanks to everyone involved in this release.
3. Highlighted posts
Preparing to join the WordCamp Europe 2023 core tables at Contributor Day?Information to help you get started and set up a local environment in advance.
Update on the Developer Blogblog(versus network, site) from @webcommsat: If you are looking to contribute through writing blog posts, check out the summary from the June 2023 Developer Blog editorial meeting for articles that are under discussion or in need of a writer. There are editors who support the posts through the process of being published, so don’t worry if you have not contributed to the Developer Blog previously. You can also suggest posts that you would like to read or contribute to for the Developer Blog. New posts this month are also available.
4. Tickets or Components help requests
There are a couple of requests for help in the open floor section of the core-editor meeting from May 31, 2023 including on a writing flow issue for accessibilityAccessibilityAccessibility (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) relating to switching blocks, a proposal on The registerBlockSupportAPI.
Please add any items for this part of the agenda to the comments. If you can not attend dev chat live, don’t worry, include a note and the facilitator can highlight a ticketticketCreated for both bug reports and feature development on the bug tracker. if needed.
5. Open floor
To start off open discussion, we would like to welcome questions from contributors attending WCEU.
If you have any additional items to add to the agenda, please respond in the comments below to help the facilitator highlight them during the meeting.
WordCampWordCampWordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe contributor dayContributor DayContributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/ Thursday June 8 – how to get involved!
Beta 1 for WordPress 6.3 is in 3 weeks, on Tuesday June 27
https://github.com/WordPress/wordpress-develop/pull/4500 is a big one. It will take 7% off the server response time for blockBlockBlock 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. themes
This past week I worked on reducing the amount of calls to _wp_array_get() in GutenbergGutenbergThe 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/ (see PR). Awaiting a review, so if anyone has some time to spare to review that, it would be appreciated
This is a follow up to a patchpatchA special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. that we merged in CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. (see related ticket) a couple of weeks ago, to improve that function’s performance
JavaScriptJavaScriptJavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser.
https://www.javascript.com & CSSCSSCascading Style Sheets.
@10upsimon Enhancing The WP Scripts APIAPIAn API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. with Loading Strategy continues to progress nicely:
Continued work on better handling of deferred inline scripts to be strict CSP compliant (in final stages of review)
Ongoing work against core PR related to script strategies and the script dependency tree
Re-visitation of documentation updates required following recent changes to the body of work introduced via a handful merged PR’s
@joemcgill Re Script Loading API: The aim of the current approach is to fully support the Script Loader API, including attached inline styles, while maintaining loading order for backward compatibility so that current blocking scripts can more easily adopt one of the more performant loading strategies. Even though the PR now meets CSP best practices, there is still disagreement about whether this should be included. @westonruter is finishing up some improvements that should finalize the “full” approach. Meanwhile, I’m prepping a path to remove delayed inline handling in order to unblock the main functionality from being committed prior to BetaBetaA pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1.
Latest delayed inline scripts approach is happening here
Issue to remove delayed inline support for a core merge (if needed) is here
I think the main question is whether we end up merging the full implementation or a reduced scope version while continuing to decide on the right approach for supporting inline scripts attached to async/defer scripts.
@flixos90 I have been reviewing the fetchpriority support PR https://github.com/WordPress/wordpress-develop/pull/4495 that @thekt12 has been working on. It’s getting close to the finish line in terms of core implementation. Once that is sorted out, we’ll have to make sure tests pass and add test coverage for the new functions
So that’s not quite ready for a full review yet (mostly due to tests), but feel free to take a look at the main code already
@joemcgill No new updates on automated tests, but we’re hoping to add some documentation about how to perform measurements to the Performance Team handbook in the coming weeks (maybe even in time for contributor day at WCEU)
@joegrainger For the Plugin Checker, we have completed Milestone 1 and started working on the second phase. This is implementing the initial checks that will be part of the plugins first release. You can follow the progress on the GitHub repo here. Thanks!
@flixos90 Still awaiting approval of the Dominant Color Images pluginPluginA plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. in the plugin repo
Open Floor
@spacedmonkey One thing I want to look into after WCEU, is inlining styles. WordPress has ability to inline styles since 5.8. Functionality was added in 5.8 for block styles. But there are other small styles that use this improvement.
If you don’t know, in-line styles means outputting css inline in a style tagtagA directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) over a link tag with an external request. This saves a httpHTTPHTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. request and faster because of none blocking requests.
I am going to create a ticketticketCreated for both bug reports and feature development on the bug tracker. and I will share it on this channel if anyone is interested.
I also want to document this functionality better for plugin / theme developer are aware of it and start to use it.
@10upsimon Curious to hear your thoughts/opinion on potentially also supporting deferred styles @spacedmonkey I know this has come up once or twice in discussions relating to the script loading strategy work. Is this something you feel is worth exploring? Critical CSS is generally inlined, but I feel that non critical css could benefit from deferral in certain situations?
@spacedmonkey This is something the team at XWP was looking into a while back. There is a benefit, but you have to know what you are doing. For many plugins and themes, it hard to know when a style is needed. Adding this functionality into core makes sense to me and should works the same way as deferring scripts works.
@westonruter Perhaps only feasible to have an API for plugins and themes to register styles that should be delayed.
@spacedmonkey The developer api should be the same imo
@westonruter Doesn’t seem feasible to do it automatically
@joemcgill Finding use cases to defer styles from core would be very helpful to justify a first-party API support
@spacedmonkey On a similar note, block themes have ability to load on block styles for blocks core knows are on the page. Would love somehow if that functionality came to classic themes as well. Maybe by parsing all blocks before headers are sent…
@westonruter Block themes could actually open up possibilities for automatic delayed styles, come to think of it. If we can determine the blocks that would be in the first viewport, then block styles identified for the page but below the first viewport could be delayed (basically ditto Jonny)
@spacedmonkey I haven’t pushed for defer styles as I wanted to see deferred scripts in first. Once scripts is in, we should work on style defer. Even if it is just for constancy
Here is the agenda for this week’s performance team meeting scheduled for June 6, 2023 at 15:00 UTC.
Announcements
WordCampWordCampWordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe contributor dayContributor DayContributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/ Thursday June 8 – how to get involved!
WordPress 6.4 will be the third major release of 2023. The following release team and its cohorts are contributors who answered the call for leadership volunteers and interest. This release aims to galvanize participation and shared ownership for those that identify as gender-underrepresented in the WordPress open sourceOpen SourceOpen Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. project.
This post is shared earlier than in past releases to encourage new contributors to engage now and shadow the 6.3 release and consider whether you, too, would like to join the merry 6.4 cohort of contributors.
Release team
Release LeadRelease LeadThe community member ultimately responsible for the Release.: Josepha Haden Chomphosy
Core TriagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Leads: Nicole Furlan, Olga Gleckler
All release decisions will ultimately be this release team’s to make and communicate while gathering input from the community.
Release Cohort
The Release Cohort are those contributors who committed to assisting the release team and supporting the goal of the gender-underrepresented lead release by spearheading efforts in their respective focuses. All contributions from all community contributors are welcome, whether you are part of a cohort or can contribute to a single PR.
Alpha Begins, TrunktrunkA directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. is opened.
September 26, 2023
BetaBetaA pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1. From this point on, core contributorsCore ContributorsCore contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac.
https://core.trac.wordpress.org will focus on testing and fixing bugs discovered during beta testing. Begin writing Dev Notesdev noteEach important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. and the About page (SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ archive, ZIP download).
October 3, 2023
Beta 2. Test the beta release, fix bugs discovered during beta testing, and continue writing Dev Notes and the About page (Slack archive, ZIP download).
October 10, 2023
Beta 3. Test the beta release, fix bugs discovered during beta testing, and continue writing Dev Notes and the About page (Slack archive, ZIP download).
October 17, 2023
Release candidaterelease candidateOne of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 1. Publish the Field GuideField guideThe field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. with Dev Notes, commit the About page, begin drafting the release post, hard string freeze, and branchbranchA directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". for the release. (Slack archive, ZIP download).
October 24, 2023
Release candidate 2. Update the About page images and continue drafting the release post (Slack archive, ZIP download).
November 1, 2023
Release candidate 3. Update the About page images and continue drafting the release post (Slack archive, ZIP download).
November 6, 2023
Dry run for release of WordPress 6.4 and 24-hour code freeze (Slack archive).
November 7, 2023
WordPress 6.4 is released (Slack archive, ZIP download)!
How to contribute
To get involved in WordPress core development, head over to TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., and shadow a 6.3 ticket by subscribing to and watching how contributors patchpatchA special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing., test, comment, and commit as part of the release cycle. Need help? Check out the Core Contributor Handbook.
If you want to dive deeper into the upcoming WordPress versions, join the weekly meetings in the #core Slack channel, which occur every Wednesday at 20:00 UTC, and the editor-focused meetings in the #core-editor Slack channel, every Wednesday at 14:00 UTC.
(Update June 6, 2023 – posts on 6.4 and GutenbergGutenbergThe 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/ added to section at the end of this post.)
Notes from the weekly WordPress developers chat which took place in the core channel of Make WordPress Slack. All are welcome.
Note: The agenda includes information links for releases and some related content to coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress., especially this and next week to help new contributors to core going to WordCampWordCampWordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe. To allow time for more discussions on tickets, all the links may not always be highlighted during the actual dev chat, and attendees are encouraged to check the full link list in the agenda itself.
Details on the latest Gutenberg pluginPluginA plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. release: What’s new in Gutenberg 15.9? (31 May).
The next phase of initiatives to promote and increase sustainability in the WordPress community and wider is the Proposal: establishment of a formal WordPress Sustainability Team. The sustainability initiative meets weekly on Fridays in the #sustainability channel on the Make WordPress Slack. All welcome to attend or view the discussions asynchronously.
4. Updates on releases
Next major releasemajor releaseA release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.
#6-3-release-leads channel on Slack is a good way to keep up with what is happening with the release.
Last minor releaseMinor ReleaseA set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. for reference
6.2.2 Security release – this came out on May 20, 2023. It addresses 1 bug and 1 security issuesecurity issueA security issue is a type of bug that can affect the security of WordPress installations. Specifically, it is a report of a bug that you have found in the WordPress core code, and that you have determined can be used to gain some level of access to a site running WordPress that you should not have.. As it is a security release, it is recommended that sites are updated immediately if you have not done so already.
4. Help requests relating to tickets or from Component Maintainers
If you have any tickets you would like to raise, you can share them in comments too. If you can not attend live, you can still add a ticketticketCreated for both bug reports and feature development on the bug tracker. and your query in the comments, and the facilitator will be able to share it in the meeting.
Volunteers are also needed to help run bugbugA 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. scrubs.
@oglekler requested feedback on ticket #58354 in the Help/About component.
@kebbett requested review and test the PR for ticket #57893. This ticket is in the 6.3 milestone.
@petitphp requested a second opinion on ticket #58312.
@webcommsat shared the link to a draft post to be shared with WCEU team once published.
Post dev chat posts
Preparing to join the WordCamp Europe 2023 core tables at Contributor DayContributor DayContributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/? Information to help you get started and set up a local environment in advance.
GutenbergGutenbergThe 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/ 15.9.1 has been released and is available for download!
This minor version includes two fixes.
Custom fonts are back again visible on the editor (51178)
There was a regressionregressionA software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. on Gutenberg 15.9 that prevented the fonts to be loaded on the editor.
Social icon colors now correctly reflect changes in Global Styles (51020)
Social Icons colors where not changing with styles variations.
What does the CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. team do?
Core is made up of contributors from many different areas and teams across WordPress.orgWordPress.orgThe 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/. Because Core is made up of many different components and parts, there is a ton of overlap with the other Make teams (polyglots, themes, plugins, metaMetaMeta 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., etc.). It is an exciting and dynamic place to observe or contribute.
The team holds a weekly developer chat in the Make WordPress #core channel on SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ every Wednesday at 20:00 UTC.
New Contributor Meetings are held in the same channel on the 2nd and 4th Wednesdays just prior to the weekly developer chat at 19:00 UTC.
What areas of Core will I be able to work on at WordCampWordCampWordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe 2023?
The Core team and the Core WordPress software is segmented in a number of ways. While there will be some community leaders present representing some specific parts of the Core team, you can contribute to any of these segments at Contributor DayContributor DayContributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/ and there will likely be several contributors experienced in these areas. These are the most common ways that you’ll see Core divided.
Components
Currently, there are 62 components and sub-components within Core. These represent overarching categories of functionality within the code base. Some examples of these are Database, External Libraries, TaxonomyTaxonomyA taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies., Feeds, etc. A handful of components also have sub-components. For example, Embeds, Gallery, and Upload are sub-components of the Media component.
Focuses
In TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., there are also several focuses. Focuses are disciplines or concepts that span many components, or even the entire Core code base. Some examples of these are accessibility, coding-standards, rest-api. Contributors that specialize in these focuses often work with many different component maintainers.
Sub Teams
There are also a few contributor groups that are still technically under Core, but operate as their own team. Some examples of this are Editor, Performance, AccessibilityAccessibilityAccessibility (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). These sub teams will each be represented by table leads at contributor day.
Preparing for Contributor Day before leaving home
Register for a WordPress.org profile and the WordPress.org Slack instance
The large majority of the communication around contributing to the WordPress open sourceOpen SourceOpen Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. projects happens on WordPress.org or in the WordPress Slack instance. Your first step should be to register for both in that order.
A majority of the Core components and sub teams also have their own channels within the WordPress Slack instance.
Install required software to contribute to the code
For those who would like to contribute by way of writing or checking code, the most popular method is by having a local development environment installed on your system.
Installing local environments are likely to be easier and quicker before you arrive at the conference venue. Conference WiFi can often be unreliable or be over-burdened. Getting set up before the event can help reduce the time you will spend installing and setting up the software on the day. You can then get onto more interesting things when you are at the conference!
In order to contribute to Core from a development perspective, you will need the following software installed on your machine:
GitGitGit is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance. Most modern plugin and theme development is being done with this version control system.
https://git-scm.com/ or SVNSVNSubversion, the popular version control system (VCS) by the Apache project, used by WordPress to manage changes to its codebase. (whichever you prefer)
NodeJS (WordPress currently requires NodeJS 14.x)
npm (comes bundled with NodeJS)
Composer (optional, but highly recommended)
Additionally, you will need to choose one of the following:
For those who would like to contribute by way of writing or checking code, the most popular method is by having Vagrant & VVV (Varying Vagrant Vagrants) installed on your system.
Once you are ready, move on to https://varyingvagrantvagrants.org/docs/en-US/installation/ where you will find all the relevant information on how to get set-up and ready to run a local version of WordPress. Where you will be able to edit plugins, themes and core WordPress files.
Note: There are other tools that can be used to set up a local development environment (such as Local), but the two above are the ones maintained and have official support.
Decide how you’re going to work with the codebase
There’s a few options for you to work with the wordpress-develop codebase.
Note: if you chose the Vagrant/Virtualbox/VVV option above, the default is the third option below, but you can change that later.
Forking WordPress/wordpress-develop on GitHubGitHubGitHub 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 by the repository owner. https://github.com/
This option will allow you to submit and work within a pull request on GitHub. When using this option, all of the configured automated testing will run on your code to help verify your change. You can read more about this option in the Core Handbook.
Using WordPress/wordpress-develop directly
With this option, you’ll clone the wordpress-develop repository locally and use that as your codebase. You won’t be able to push any changes or submit pull requests, but you will be able to create patches with your changes to submit on Trac.
Using SVN to check out WordPress
With this option, you’ll checkout the `trunktrunkA directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision.` branchbranchA directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". of the develop.svn.wordpress.org repository to use as your local WordPress site. Any changes you make need to be submitted as patches.
Docker Option
Below are the basic steps to get started with the local Docker environment:
Clone your repository of choice from the previous section. If you’re using a fork that you created, the command will look like this: git clone git@github.com:{your GitHub username}/wordpress-develop
Run cd wordpress-develop to move into the directory created by the git clone.
Run npm install to install dependencies
Run npm run env:start to start the development environment
Run npm run env:install to set up clean installation with the user adminadmin(and super admin) and the password password
Running npm install, vagrant up, or npm run env:start can be networknetwork(versus site, blog) intensive. Run these at home before you leave for the event and confirm everything’s working as expected. Depending on what you work on during Contributor Day, you may need to run these commands again. But having dependencies, virtual boxes, and containers cached locally will greatly decrease the time they take to run at the event.
Try creating patches or a PR ahead of time. If you’re able to start working on a ticketticketCreated for both bug reports and feature development on the bug tracker. before the event, contributors at the event can give you feedback on your work so far.
Many thanks to all the contributors who helped with materials for this post – as ever with WordPress, it is a real team effort! Special thanks to @desrosj who collected much of the preparation information, to @wpscholar for sharing his more detailed document from a previous WordCamp, and to @webcommsat who pulled together the material from different editions. Thanks also to @sergeybiryukov, @jeffpaul and @webcommsat for review and contributions, and to @audrasjb, @paulbearne, @mark99, @vimes1984, @meher, @oglekler for contributions and review for material used from previous editions of this post. Thanks to @davidbaumwald, @joemcgill for review of the checklist.
After WordCamp Europe, a version of this post will be added to the Core Team Handbook.
You must be logged in to post a comment.