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 our bug tracker.
We use Slack for real-time communication. Contributors live all over the world, so there are discussions happening at all hours of the day.
Our core development meetings are every Wednesday at 05:00 UTC and 20:00 UTC in the #core channel on Slack. Anyone can join and participate or listen in!
Bit of a late entry for agenda posts, apologies for that, it’s been a hectic couple of days… can you say 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?!! We’ll no doubt talk about that, but please also share any items you’d like to include in the comments below.
Announcements – let’s celebrate the release of Beta 1 of 5.6
Highlighted blogblog(versus network, site) posts
Introducing GitHub Actions for Automated Testing – worth a look, this was used to good effect in the release this week. I think there are opportunities to contribute to this if you’re available. Please check it out.
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/ 9.1
@youknowriad reiterated the main points of the release: improvements for theme.jsonJSONJSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. shape and developpers APIs to control the editor, the widgets screen improved and a few nice UIUIUser interface iterations including 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. patterns selection on the inserter.
@isabel_brison drew some attention to the issues in the To do and the Needs Review columns
@cguntur shared the issue tracking 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
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 @youknowriad noticed it could use some updates to remove some of the 5.5 dev notes labels from the PRs
The PR for porting pages selector dropdown to the navigation 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. is ready to be merged once e2e tests are fixed.
The initial PR that adds a basic document settings dropdown to the site editor has been merged. There are ongoing design iterations to determine the right content for it.
The `Query` block now supports Custom Post Types and (soon to be merged) we have a Latest Pages block variation
CustomizerCustomizerTool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings.
there are explorations to make the Customizer work with the new blocks in widgetWidgetA WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. areas functionality
there were also a couplesuggestions on how to best solve it architecturally
I’m focusing on various Social Links issues since the widget screen is going live, social could use some love. The two biggest ones left are Placeholder experience and icon sizing.
Continued work on a Block Editor Release Process doc with @jorgefilipecosta and @isabel_brison, amplifying the widgets screen call for testing, triagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. and testing!
I have been working on refactoring @wordpress/date to move away from momentjs. Tests passing right now, but there are a couple of formatting options that were ported from PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 that are a bit tougher to achieve PR: 25782
Block supports 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.
Reviewing a number of PRs (templateLock, video tracks, usage of block api v2)
Helping with the merge with CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress..
Continued the iterations on some PR’s I have open, namely video tracks, template lock updates
Improved the code samples of the scripts I used that will be shared as part of the Block Editor Release Process doc (these scripts were for personal use and deserved a little bit of polishing to be publicly shared).
Rewrote and clean up the “Package update and core path” and “Cherry picking” sections of the Block Editor Release Process doc.
Update core to be able to use wp-scripts packages-update command to make core 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. creation easier.
Submitted and commit the WordPress core update patch.
Made some improvements to the back-compatibility required for WordPress 5.6.
Iterated and merged the automatic generation of preset classes and the user-editable color palette.
Did Multiple PR reviews and answered pings I had pending.
Monthly Plan for October 2020 and key project updates. With focus on issues, what is being done and help that is needed.
Global Styles.
Widgets screen.
CustomizerCustomizerTool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. screen.
Full Site Editing.
Task Coordination
Open Floor
Even if you can’t make the meeting, you’re encouraged to share anything relevant for the discussion:
If you have anything to share for the Task Coordination section, please leave it as a comment on this post.
If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.
Reminder that @kburgoine will be leading the biweekly coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.CSSCSSCascading Style Sheets.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. scrub next Thursday, October 22, one hour before the CSS Chat meeting.
The generated reports are now accessible as GithubGitHubGitHub is a website that offers online implementation of git repositories that can 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/ pages (here for example). @ryelle observed that eventually this tool should be migrated to the WordPress github repos.
@notlaura mentioned that a comment about report generation should be added to the TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.ticketticketCreated for both bug reports and feature development on the bug tracker., for community reference and put a call out for a volunteer to do this, specifying:
the key items to include in a comment are the link to the generated report (https://ryelle.github.io/css-audit/public/wp-admin) and the next steps, which are to complete the data (missing property values) and to style the template
@ryelle reported that she has kept her reduced-color branch testing site up-to-date with WordPress 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.. There followed a short discussion about the pros and cons of proposing to merge the 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". into the 5.6 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.. @garrett-eclipse suggested seeking a champion from #design, otherwise punting it to 5.7, which, @ryelle observed, would allow us to focus on bug-scrubbing & Twenty Twenty One issues over the coming weeks.
CSS links share + Open floor
@danfarrow (me!) shared a link to a portfolio site ichimnetz.com which has a quirky “adjust CSS” slider feature which demonstrates the effect of using more or less CSS.
Some browsers will limit the number of available colors that can be used to render styles. This is called “forced colors mode” and, if enabled in the browser settings, the user can choose a limited set of colors to use on a page. As a result, the user is able to define color combinations and contrasts that make content more comfortable to read.
And, with that, the meeting was concluded. Thanks everybody!
As of [49162], CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. is now running automated tests using GitHubGitHubGitHub is a website that offers online implementation of git repositories that can 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/ Actions as a runner, in addition to the existing Travis CI and Appveyor runs. This post is to publicize the change, document the reasoning, communicate next steps, and share how people contributing to WordPress Core will benefit.
GitHub Actions allows us to automate software workflows directly in GitHub, triggered by GitHub events. By switching, we are able to take advantage of a unified interface, inline annotations for linting issues in pull requests, the broader 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. ecosystem building and using Actions including existing work in Gutenberg, and free availability for public repositories. Note that private repositories do use the monthly bucket of included minutes.
There is also an additional 7th workflow that is meant to leave a welcome message when it’s the contributor’s first pull request, letting them know how we use GitHub pull requests and how to link them to a TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.ticketticketCreated for both bug reports and feature development on the bug tracker.. There appears to be an issue concerning permissioning when PRs are sent from forks, so this is pending.
Currently, Travis CI and Appveyor will continue to run for a transition period (ending TBD) to allow for any issues to be ironed out, and so that real-world usage data can be collected. So far, even in early testing, runs appear to be completing more quickly and with fewer/no false negatives, e.g. when Travis CI does not see the commit in the mirror yet. @desrosj will be collating run data in a spreadsheet, including but not limited to: overall build time, run time comparison (where 1:1 comparisons can be made), and frequency of false negatives.
Known next steps
Add and configure SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. notifications. In addition to sending the results of the whole build of a core commit into #core, we may also want to consider a firehose channel for PRs.
Move to GitHub badges for build status indicators – note that these are per-workflow, which is different from the single badge for the entire Travis build for a given commit. However, GitHub does report an overall status for a commit/PR, so we may be able to use that information as well.
Switch to ESLint from JSHint, as the latter does not appear to easily support inline annotations, and the former is in broader usage including in core for docs, 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/ and many community projects. See #31823 for more – volunteers very much appreciated here.
BackportbackportA port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. the workflow files to actively maintained older branches.
As always, please report any issues you are seeing with our GitHub Actions, as well as further ideas for use you may have. Major thanks to @desrosj for all the heavy lifting he’s done in just a couple of weeks, and to @ocean90 and @ayeshrajans for their help along the way.
This meeting will be held in the #core-css channel in the Making WordPress SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..
If there’s any topic you’d like to discuss, please leave a comment below!
Posted on behalf of @monikarao since she is not a user yet on this blogblog(versus network, site)
As part of the 5.6 release, we’ll be hosting a widgetWidgetA WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. screen focused test scrub this Friday, October 16, 2020, 13:30 UTC in the #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/..
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/ 9.1 released a new 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.-based widget screen. This new functionality replaces the previous wp-adminadmin(and super admin) > Appearance > Widgets screen.
If you want to contribute to this feature by testing, please join us and share your valuable feedback.
We are particularly looking for design, functional, as well as UIUIUser interface/UXUXUser experience feedback.
APAC based core committercommitterA 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., @peterwilsoncc has taken up a role that will allow him to contribute to core 4 days a week 🎉
A group is gathering around issues that can be moved to a minor release to clear the path for 5.6 and address issues like removing the embed blocks for FB an Instagram due to their withdrawal of support. If you can help, here’s where to dig in https://core.trac.wordpress.org/tickets/minor @whyisjake will be organizing the release, so reach out if you want to get involved.
No Highlighted Blogblog(versus network, site) posts this week
@francina highlighted a PR that will generate a weekly auto post to core to solicit reports from Focus Leads and Component Maintainers, and reminded people that if they’re no longer available for contributing as maintainers.
Open Floor
@mikeschroderobserved some failing tests for some hosts and the 0500 UTC crew dug in to find the cause in a package update – resolution to add an issue to the board to be included for the next 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/ release.
@isabel_brison threw out that if anyone was keen to work on or review editor-related stuff, the 5.6 project board has a few things to pick up in To do and Needs Review columns
The state of PHP8 support in core generated a fair amount of discussion. Rather than summarize here, please review the archive of the conversation in Slack for all the detail. Major takeaways are the 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
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. are in progress in relation to communication around the significant number of breaking changes – Helen called for a deliberate effort towards outreach of this change which has extensive discussion to follow. Furthermore @omarreisssuggests declaring WP incompatible with PHP8 with a useful perspective from@jrf in response. Lots to dig in there, and there will be marketing and outreach efforts to ensure widespread awareness.
@justinahinon opened a discussion with a suggestion regarding pairing existing contributors with new ones to build connection and support newbies.
@helen asked for a rundown on significant issues to complete before 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 is released,
These are the weekly notes for the Updates/Install component meeting that happened on Tuesday October 13, 2020. You can read the full transcript on the coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.-auto-updatesSlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel.
The meeting was focused on the component’s major project for 5.6: an UIUIUser interface for opting in to core auto-updates: #50907.
@audrasjb sent a first 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. for this feature and shared a screenshot of the first workaround:
This approach adds two checkboxes, to provide the ability to enable/disable auto-updates for both minor and major auto-updates.
@pbiron pointed out that disabling auto-updates for minor releases was already discussed during previous meetings, and the decision is that it is not an option the Core team wants to provide to end-users. It needs to be disabled by a 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 or by using the existing hooksHooksIn WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. or PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 constants. @audrasjb will update his patch accordingly, so there will be only one available option: opt-in for major releases auto-update.
@estelaris added that there is already 4 buttons on this screen. It would be nice to avoid adding a new one. She added that we should use a toggle button instead of a checkbox + a submit button. @audrasjb answered that there is no existing toggle component in WordPress Core for now. This eventual new component also would need to be designed, developed, and its 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) would need to be tested and reviewed. It doesn’t look realistic for WP 5.6 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.
@paaljoachim proposed to move the auto-updates opt-in to General Settings. @pbiron and @audrasjb are not enthusiastic about this proposal as for now, the Updates screen seems to be the more natural place to find Core auto-updates settings.
@karmatosed pointed out that this screen is already a very dense interface. She will share some alternative designs this week on this Figma file, to help design decisions. @audrasjb will work on the patch implementation at the end of the week.
For beta 1, the team agreed that a robust technical implementation is needed, so we have a UI basis for this new feature. Then, the team will focus on phrasing and on polishing the interface elements.
@estelaris asked for documentation about plugins and themes auto-updates. The team shared all the existing documentation:
Technical documentation (WordPress 5.5 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
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.):
