Based on triaging a few hundred tickets in the General and Multisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site components, we’ve added five components:
- Bootstrap/Load — applies to wp-settings.php, ms-load.php, load.php, ms-settings.php, etc.
- Login and Registration — useful for multisite, but applies to single-site too
- Options and Meta 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. — option.php, meta.php, etc.
- Script Loader — WP_Scripts, WP_Styles, and script-loader.php
- Networks and Sites — multisite only
We also removed two components that (poorly) described the problem rather than the affected area of core Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. “Validation” ranged from from validation tickets to XHTML issues. HTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. validation issues now belong in the affected component, like “Template” or “Administration.” “Warnings/Notices” contained tickets ranging from PHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher warnings to providing feedback to users. The open tickets were moved to more appropriate components. Additionally, the remaining tickets in “AtomPub” were wontfixed and the component was removed.
A new concept: Focuses
We’ve also added seven new “focuses” — ui, accessibility 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), javascript JavaScript 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/., docs, multisite, performance, and rtl. Focuses are about broad concepts and help break tickets down by specialties and skills, rather than functional areas of core. Multisite and RTL are widely general “modes” for WordPress, and each have contributors who focus strongly on those areas, but they are not well-contained “components” of core. Accessibility isn’t an area of core — it permates the entire user experience. A ticket Created for both bug reports and feature development on the bug tracker. about inline documentation should still receive the attention of developers for that area of core (say, comment.php), while those who focus on inline documentation should still be able to do so.
“Focuses” is a new field in Trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.. They’re like tags, and more than one can be assigned to a ticket. It can be queried using custom queries. And they have their own reports which we hope to properly expose and make better really soon — https://core.trac.wordpress.org/focus/accessibility.
Guidelines to help with the transition
The corresponding components for the new focuses have been removed. The “ui-focus” keyword has also been converted over. Overall, we gained five components but lost eight.
This has the potential to be confusing at first and we’ll surely need to make some adjustments. Also, the component cleanup is not done yet — this is just the beginning. Here are some guidelines for how to use the new focuses.
-
The old RTL component — use the rtl focus and assign a relevant component. If it’s RTL issues with the media library, use the “Media” component. If it’s about the RTL build tools, then use the “Build Tools” component. If it’s more general, then use the “I18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill.” component.
-
The old Accessibility component — use the accessibility focus and assign a relevant component. For issues with the media library, use “Media.” For issues with activating a theme, use “Themes.”
-
The old Inline Docs (phpdoc, docblock, xref) component — use the docs focus and assign a relevant component. Hook documentation for user.php belongs in the “Users” component.
-
The old Multisite component — use the multisite focus and assign a relevant component. If it’s related to users, use “Users.” If it’s related to the loading process of multisite (choosing a site based on domain and path, etc.), use “Bootstrap/Load.” If it’s related to the installation process, use “Upgrade/Install.” network_admin_url() goes into the “Permalinks” component. get_site_option() is “Options and Meta.” The Network (versus site, blog) Admin (and super admin) still has its own component. (Choosing that component or “Networks and Sites” automatically assign the “multisite” focus for you.) @jeremyfelt recategorized about 110 tickets into about 15 different components.
-
The old Performance component — use the performance focus and assign a relevant component. Improving the performance of WP_Query belongs in “Query,” improving the performance of get_option() belongs in “Options and Meta,” etc.
-
The old Graphic Design component — use the ui focus and assign a relevant component. (This is probably going to be “Administration”, at least for now.)
-
The old ui-focus keyword — This has been removed. Simply use the ui focus.
-
The old JavaScript and UI User interface components — these have not existed for some time. Use the corresponding focus and assign a relevant component.
We may add more focuses over time. For example, the “Text Changes” component would probably make a better focus, for our wordsmiths.
Any questions, suggestions, or comments?
This is a summary and addendum of one section of this Wednesday’s weekly developer meeting. Logs.
#components, #trac
