This post summarizes the dev chat meeting from August 16th (agenda, Slack archive).
- @johnbillion: as part of ongoing Security focus, planning on several user account security related changes, for example bringing some of the 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 confirmation emails when you change your email address into single site
- @flixos90: Multisite team is working on REST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. endpoints for the multisite objects, like sites and networks, plus improvements to the users endpoint that make it compatible with multisite
- @westonruter: just published 0.2.0 of the codemirror-wp plugin which adds an a11y 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) option to the user profile screen to opt-out of syntax highlighting in the same way that a user can opt-out of the visual editor
- @westonruter: feedback and help welcomed via the CodeMirror repo
- @westonruter: Customizer Tool 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. drafting and scheduling (essentially porting the features from the Customize Snapshots plugin) is currently working through designs with @joshuawold, once that’s set this will move to implementation
- @desrosj: Multisite team using weekly meetings to re-organize the Network (versus site, blog) & Sites component’s roadmap to align with Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress.’s current focuses and the component’s short and long term goals
- @desrosj: We propose using make.wordpress.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//core/roadmap/ as a location for components to house their roadmaps (multisite living at `make.wordpress.org/core/roadmap/multisite`) as roadmap posts on the Make/Core blog (versus network, site) slowly get pushed away as new posts are published
- @desrosj: The roadmap outline (brief descriptions of each item, a timeline, some tickets to focus on immediately) would live on these roadmap pages, and link out to make blog posts with specific details about each item.
- Agreement to proceed with this with Multisite and assess how its working before pushing other components to do the same
- @koenhuybrechts: looking for update on #17268
- @mte90: looking for update on #12955
- @drewapicture: concern with potential performance hit due to the sheer number of times it’s called on a given page load; will leave a comment on the ticket Created for both bug reports and feature development on the bug tracker.
- @mte90: looking for an update on #13657
- No one around related to the Database component, will continue to look for updates via the ticket
- @mte90: looking for an update on #40542 as well as my other patches