We covered a handful of things in yesterday’s meeting. 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 office hours are held every Tuesday at 20:00UTC in #core-multisite.
Work continues to clarify our primary objectives and the order in which they should be approached. Here’s the current list:
- Solidify mixed domain/path support. This involves UX User experience and related work in #22383 first. We need help testing what is supported, providing clear docs, and making sure things are working in general.
- Define open/closed networks and the words used to describe them. We’ve had some good discussion on this in the past. We need to find the right place to continue this discussion—likely a P2 A free theme for WordPress, known for front-end posting, used by WordPress for development updates and project management. See our main development blog and other workgroup blogs. thread of its own.
- Identify areas where featured plugins can be used to rapidly build out features over multiple releases.
Areas discussed:
- The future of activating multisite and the steps involved. Some things could be done to simplify the process overall, but we want to make sure its ready for the the accidental enabler.
- #30202 – storage space used is calculated incorrectly on the main site. @earnjam is working on building out the patch A 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. some more to support an array of excluded directories and unit tests. It’s possible work here could help with #26135.
- Hunt through old tickets in the multisite focus to look for staleness. There are always some good charms from the past.
- It seems like we can close #16990 as invalid A resolution on the bug tracker (and generally common in software development, sometimes also notabug) that indicates the ticket is not a bug, is a support request, or is generally invalid., a custom
db-error.php is supported in multisite. We should take care of #30002 though.
We’re expanding multisite office hours to include a bug A 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 in #core-multisite immediately after the meeting. Mark 20:00 UTC on your calendars for office hours and 21:00 UTC for bug scrub and join us in #core-multisite.
Tickets mentioned: #22383, #31217, #31148, #22251, #30202, #26135, #16990, #30002
#meeting, #multisite
