During Contributor Day Contributor 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://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. at WordCamp WordCamps 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 2019, the newest WordPress Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. component was created, Site Health. After many months being tested as a feature plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins., Site Health was merged into WordPress core in versions 5.1 and 5.2. Below are several changes that were made during Contributor Day to help organize tasks and efforts around Site Health moving forward.
New Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. Room
The Site Health feature is just one tool that is empowering site owners and hosts to upgrade to more modern versions of PHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher. Because of this, most of the discussions around Site Health have happened in #core-php to this point.
However, now that Site Health is in WordPress Core, it’s time to give that Slack room back to the folks discussing how PHP is used in Core (upgrades to patterns, discussing guidelines, style guides, etc.).
All Site Health discussion moving forward will be held in the new #core-site-health channel.
Component Maintainers
The following people have played incredibly important roles in the Site Health project so far and were asked to be component maintainers. All accepted:
Action Summary
Here is a brief summary of the actions taken to facilitate this change:
- A Site Health component was created in Trac.
- A Site Health component was created and added to the Make WordPress Core Components page.
- All open tickets with the
site-health keyword were moved into the Site Health component (tickets effected). - All open tickets with the
servehappy keyword were moved into the Site Health component (tickets effected). - All closed tickets with the
site-health keyword were moved into the Site Health component (tickets effected). - All closed tickets with the
servehappy keyword were moved into the Site Health component (tickets effected). - The site-health tag A 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.) has been created for this blog (versus network, site). All Site Health related posts will utilize this tag.
Note: The site-health and servehappy keywords are now obsolete and should not be used moving forward. but they will remain on old tickets.
#site-health
