The WordPress core development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:
This post summarizes the dev chat meeting from August 16th (agenda, Slack archive).
The agenda for this office hours meeting was to discuss the format of the multisite roadmap that will be compiled from many of our recent conversations.
The meeting’s chat log
Attendees: @desrosj, @flixos90, @spacedmonkey, @vizkr, @jeremyfelt
Chat Summary:
make.wordpress.org/core/roadmap/ structure under which make.wordpress.org/core/roadmap/multisite/ can exist as well as pages for other components or focuses.The next office hours will take place on Tuesday 16:00 UTC. An agenda for it will be posted in advance.
The agenda for this ticket scrub was to discuss approaches for better clarifying site statuses, and then have an open floor for further tickets.
The meeting’s chat log
Attendees: @flixos90, @sergey, @ina2n, @afragen, @pmbaldha, @paaljoachim, @desrosj, @spacedmonkey, @jeremyfelt
Chat Summary:
wp-admin/network/site-info.php don’t convey any real information about their meaning or a workflow.get_blog_count() and get_user_count() return an integer. Specifically—Can the return type be safely changed without issue and/or should we deprecate get_blog_count() in favor of get_site_count(). We aren’t too worried about changing the return type as this function doesn’t appear to be used much outside of core.The next ticket scrub will take place on Monday 17:00 UTC. An agenda for it will be posted in advance.
If you were unable to attend one of these meetings but have feedback, please share your thoughts in the comments on this post. In case there’s a need for further discussion we will ensure to make time for it in one of next week’s chats. See you next week!
This is the agenda for the weekly dev meeting on August 16, 2017 at 20:00 UTC / August 16, 2017 at 20:00 UTC:
If you have anything to propose to add to the agenda or specific items related to the above, please leave a comment below. See you there!
This is the agenda for the weekly office hours meeting on Tuesday 16:00 UTC in #core-multisite.
This is the agenda for the weekly ticket scrub meeting on Monday 17:00 UTC in #core-multisite.
Please join the chat if you’re interested in one of the topics. In case you cannot make the respective meeting, we will be working on publishing a recap post afterwards. If you have some thoughts beforehand or would like something related to be part of the agenda, feel free to share your ideas in the comments for this post. See you in the chat!
The agenda for this office hours meeting was to discuss whether a function to retrieve a site by specific details should be introduced as a successor to the legacy-bloated get_blog_details().
The meeting’s chat log
Attendees: @desrosj, @drewapicture, @earnjam, @flixos90, @jeremyfelt, @jmdodd, @spacedmonkey, @stephdau, @stevenkword
Chat Summary:
get_site_by() function proposed in #40180 should be introduced. It might need to get a more suitable name though. While it can work similar as other existing functions like get_term_by(), a significant difference is that it can also accept an array of multiple fields to query by, which makes the name a bit confusing.get_site_by( 'id', 2 )get_site_by( 'slug', 'subsite1' )get_site_by( array( 'domain' => 'mainsite.com', 'path' => '/subsite1/' ) )get_site_by( 'domain', 'subsite1.mainsite.com' ) (only works in a subdomain install)get_blog_details() will wrap the new function, and apply some tweaks to remain backward-compatible.*_blog_details() functions were further discussed in regard of a possible deprecation. They are still widely used, so that should probably not happen any time soon. It was however decided that, once the changes in #40364, #40180, #40228 and #40201 have been completed, a new ticket should be opened to further discuss the path towards deprecating get_blog_details(), update_blog_details() and refresh_blog_details(), all of which will be unnecessary at that point.wp_blogs table as well as setting up the individual site tables are ready as well. It should be clarified that the CRUD functions do not actually set up the site’s database tables and should not be used on its own in most cases.get_content_url( $blog_id = null, $path = '' ) function that could help with this. @drewapicture will have a closer look at the ticket.The next office hours will take place on Tuesday 16:00 UTC. An agenda for it will be posted in advance.
The agenda for this ticket scrub was to finish reviewing multisite tickets assigned to the 4.9 milestone, and then have an open floor for further tickets.
The meeting’s chat log
Attendees: @desrosj, @flixos90, @jeremyfelt, @mista-flo, @sergey, @spacedmonkey, @vizkr
Chat Summary:
wp/v2/sites endpoint for the REST API by implementing a full CRUD API for sites. A particular focus for the new functions was to only deal with the wp_blogs table and have all connected functionality be handled by hooks. @jeremyfelt has since reviewed the ticket and patch and left a comment.*_site_option() and *_network_option() calls once the *_network_meta() functions are in core. In the discussion it was decided that the network meta functions cannot be a direct replacement for the network option functions, as meta functions have always required passing an ID and should continue to do so. They can still replace them in several areas, however a solution needs to be found for the hooks that the *_network_option() functions trigger, but the *_network_meta() functions wouldn’t.The next ticket scrub will take place on Monday 17:00 UTC. An agenda for it will be posted in advance.
If you were unable to attend one of these meetings but have feedback, please share your thoughts in the comments on this post. In case there’s a need for further discussion we will ensure to make time for it in one of next week’s chats. See you next week!
Gutenberg is about to reach a milestone of having the technical and design vision in place. I know that we’re a little off from the existing roadmap, so I’d like to suggest an update to the milestones going forward.
The milestones below are based on information from the focus leads about who will be available and when. As with all things in open source, these are best guesses and I encourage everyone to join us in being flexible as we keep creating:
It should be clear this is not set in stone. Gutenberg is not ready to merge and as a result giving it this time is important to iterate and respond to feedback. Beyond the merge proposal it’s also difficult to predict, so the roadmap to 5.0 isn’t being predicted here, that will depend on the proposal.
This one includes a few new blocks.
We welcome all your feedback and contributions on the project repository, or ping us in #core-editor. Follow the “gutenberg” tag for past updates.
This post summarizes the dev chat meeting from August 9th (agenda, Slack archive).
