PHP Meeting Recap – December 18th

This recap is a summary of our previous PHP meeting. It highlights the ideas and decisions which came up during that meeting, both as a means of documenting and to provide a quick overview for those who were unable to attend.

You can find this meeting’s chat log here.

Chat Summary

  • After asking for feedback last week, we got told that our weekly recaps are valuable to some readers, so we keep writing them. We removed the attendees’ list because it takes a substantial amount of time to complete, with little added value.
  • Due to the upcoming holidays, we are skipping the meetings for December 25nd and January 1st. Next meeting will be held on January 8th.
  • Regarding plugin testing, we reasserted that we’ll still recommend PHP Compatibility Checker for now, even though Tide (Team Home | GitHub) is on the horizon. As long as Tide is not open source and hasn’t been properly integrated into the WordPress ecosystem, it just isn’t a valid option.
  • As we’ve finished the content for the page, we are now discussing the overall strategy of moving forward with the project:
    • produce preliminary deliverables (site mockup, admin dialog mockup)
    • create/update (Meta) Trac ticket(s) to make sure we have a clear set of goals, a proper roadmap and a timeline
    • raise awareness through dev-chat meetings and news portals to get feedback and buy-in
  • Ask a precise question to get a precise answer: “Is that something worth pursuing within wordpress.org scope?”
  • We plan to discuss the project in dev-chat on January 10th. By then, we expect to have the deliverables ready.
  • Two tickets that currently track the progress: Trac 41191 (admin notice) and Meta Trac 2996 (external servehappy page).

Next week’s meeting

  • Next meeting will take place on Monday, January 8th, 2018 at 16:00 UTC in #core-php (Note: We are skipping two meetings because of Christmas and New Year’s Day).
  • Agenda: Discuss latest progress and our approach for the dev-chat meeting on January 10th.
  • If you have suggestions about this but cannot make the meeting, please leave a comment on this post so that we can take them into account.

#core-php, #php, #servehappy, #summary

Dev Chat Summary: December 6th (4.9.2 week 1)

This post summarizes the dev chat meeting from December 6th (agenda, Slack archive).

4.9.2 ticket triage + timing

  • 41 tickets already marked for 4.9.2, minus fixed-major there are 39 tickets
  • #42586 is the only high priority ticket in the milestone
  • Aiming for 4.9.2 release toward the end of January 2018

Plan for 4.9.x minor releases

  • Will look to do 6-8 weeks for a release window with 4-6 weeks of work, week and a half of beta, half week of RC
  • From past experience, its best to have someone who isn’t the major release lead handle a minor release as it (1) gets the major release leads some rest and (2) gets more folks familiar with the release process
  • @kadamwhite @joemcgill @desrosj interested in helping as a minor release lead, but unavailable in January. @obenland available to lead a minor release, @sergey available as a backup lead.
  • If you have interest in being a minor release lead, please ping @jbpaul17 or mention in #core. Self-nominations are accepted and encouraged, you don't have to be an engineer, and commit access is not required but helpful.
  • We need to make sure we have people with WP.org access available for the builds, but anyone with the knowledge can organize/follow up on tickets in the lead up to a release and be a decision maker.
  • No rush to find someone with WP.org access to package a release until the week leading up to a release
  • Would be good to add a “next-minor” milestone to Trac so we could pull things into the 4.9.x milestone once they are actually resolved instead of mass punting

Definition of "minor" release

  • Bugfixes and minor enhancements/features that do not add new deployed files and are at the discretion of the release lead with suggestions/input from component maintainers.

Weekly updates from leads

  • Focus leads to provide weekly updates including:
    • what big things happened this week?
    • what needs eyes/testing?
    • what big challenges could the team use help with?
    • what decisions need feedback before being made?
  • Component leads to provide updates as necessary, though not required weekly, and focused mainly on big things or areas where we need coordination

#4-9-2, #dev-chat, #summary

PHP Meeting Recap – December 11th

This recap is a summary of this week’s PHP meeting. It highlights the ideas and decisions which came up during that meeting, both as a means of documenting and to provide a quick overview for those who were unable to attend.

The meeting’s chat log.

Attendees: @afercia @clorith @drewapicture @drivingralle @flixos90 @jdgrimes @joostdevalk @jorbin @ottok @overclokk @paulstonier @pross @ptasker @spacedmonkey @vizkr

Chat Summary

The main agenda for this week was to review the copy the marketing team has been working on in regards to the “Before Upgrading PHP” document.

Here is the discussion summary:

  • As WordPress recommends a specific PHP version on the requirements page, it was decided that that same version should be used on the Servehappy page (currently 7.2). Vague version terminology like “PHP 7+” or similar should be replaced accordingly.
  • A few minor changes to the copy were suggested and added to the Google document as a comment.
  • The part about the backup not including the PHP version might need to be clarified, but on the other hand it might unnecessarily scare away site owners from proceeding. This is something that still needs to be figured out.
  • On a side note, the PHP Compatibility Checker plugin should make it easier to run the check after the installation. Currently there’s simply a submenu item added in the admin, but no link or anything to it, so the user has to search for it which is bad UX.
  • There was a discussion regarding the proposal in #42858, to bump the minimum version requirement in PHP 5.0 and make 4.9 some kind of LTS version. The gist of the discussion was that this would be a problematic move as it would leave deliberately leave users behind which is against WordPress’ principles. An eventual version bump should be announced well in advance, and there should be enough time to educate site owners on the topic and prepare them for the upgrade instead of forcing them to either upgrade immediately or be left behind. The Servehappy page should be a major contributor to that education, but before it is in place, no measures in regards to a minimum version bump should be taken. Once it is live, #40934 and #41191 will be the two main tickets that need to be worked on for core so that site owners can actually be made aware of the problem.

The rest of the meeting focused on a few organizational items:

  • Writing the weekly recap posts is an extra maintenance burden that may possibly not be worth the effort. A regular update would still be valuable though, so a good alternative would be to write a monthly update post or just an update post when something major was decided. If you have been reading these weekly recaps and find them particularly useful, please leave a comment on this post, otherwise the team will move over to writing decision-dependent update posts.
  • Once Servehappy is set in stone, one of the next major goals of the initiative will be to discuss and come up with more patterns and standards in core, in order to at least in the future prevent rather random decisions by individual developers, causing an inconsistent codebase. As of now however, Servehappy is the sole priority.

Next week’s meeting

The next meeting will take place on December 18th, 2017, 16:00 UTC as always in #core-php. The agenda will be to plan spreading the word more, particularly by asking for more feedback in the weekly development chat. If you have suggestions about this but cannot make the meeting, please leave a comment on this post so that we can take them into account. See you next week!

#core-php, #php, #summary

Dev Chat Summary: November 29th (4.9.1 week 2)

This post summarizes the dev chat meeting from November 29th (agenda, Slack archive).

4.9 feedback + 4.9.1 timing

WordPress 4.9.1 was released last week. It's a security and maintenance release for all versions since WordPress 3.7, users are strongly encouraged to update their sites immediately.

Notable bug fixes include:

  • Issues relating to the caching of theme template files.
  • A MediaElement JavaScript error preventing users of certain languages from being able to upload media files.
  • The inability to edit theme and plugin files on Windows based servers.

This post has more information about all of the issues fixed in 4.9.1 if you'd like to learn more.

Gutenberg usability testing + contributions

There are new usability tests for Gutenberg.

There was also a usability testing table for Gutenberg at WordCamp US this weekend, as well as a dedicated Gutenberg section at the Contributor day.

General announcements

@davefx: Looking for feedback on #42669.

#4-9-1, #core, #dev-chat, #gutenberg, #summary

Dev Chat Summary: November 22nd (4.9.1 week 1)

This post summarizes the dev chat meeting from November 22nd (agenda, Slack archive).

4.9 feedback + 4.9.1 planning

  • WordPress 4.9 was released last week, and so far 3 pressing issues have arisen that needs to be addressed in a timely manner:
    • #42573 (template file caching), #42574 (MEJS breaking things for some languages), and #42609 (file editing broken on Windows).
    • As we have a short timeline for this release, focusing on these 3 major issues for now, and planning a future point release for any other regressions appear to be the ideal way forward.
    • @johnbillion has volunteered to run the 4.9.1 release, backed by @sergeybiryukov, we're aiming to have 4.9.1-RC1 on Monday November 27th, with a tentative release date set for Tuesday November 28th.

Request for devchat lead next week

  • @sergeybiryukov has graciously volunteered to help with runnign next weeks Dev Chat, as many of us will be in transit for WordCamp US

Props to @clorith for helping lead devchat and write this summary. 🙌

#4-9, #4-9-1, #core, #dev-chat, #summary

PHP Meeting Recap – November 20th

This recap is a summary of this week’s PHP meeting. It highlights the ideas and decisions which came up during that meeting, both as a means of documenting and to provide a quick overview for those who were unable to attend.

The meeting’s chat log.

Attendees: @flixos90 @jdgrimes @nerrad @overclokk @ptasker @schlessera @uofaberdeendarren @vizkr

Chat Summary

The agenda for this week was to finish the rest of the “Before Upgrading PHP” document that will be handed over to the marketing team afterwards to get their help with writing the copy.

Here is the discussion summary:

  • It was decided that the sections dealing with asking plugin/theme support, the hosting provider and possibly a developer for help should be combined into one help section at the end of the document. The reason for this decision is that all of those resources may or may not be available for a site owner, and the results of a consultation may vary. It should be emphasized that the upgrade steps are intended to be easy enough for the site owner to perform them on their own, but those resources should still be pointed out for those who feel more comfortable that way.
  • Merging those help sections into one has made the document more straightforward to read. It essentially now consists of the following steps:
    • Backup & Rollback Plan
    • Updates
    • Compatibility Check
    • Find replacements for incompatible plugins
  • The third step will hopefully become a lot simpler once the new WP Tide project is available.
  • The fourth step is at this point the least straightforward one. Finding plugin alternatives requires either good knowledge of the WordPress economy or an exhausting search. In addition, migrating from one plugin to the other will likely involve non-trivial tasks that only a developer could take care of. At least in regards to finding alternatives, a dedicated feature for that in the plugin repository could help. @schlessera pointed out that this is apparently already being worked on by the plugin repository team.
  • By the end of the meeting, it was agreed that the draft is now ready to be passed on to the marketing team so that they can build something awesome out of it. @flixos90 has since asked for their help in the #marketing channel.

Next week’s meeting

The next meeting will take place on November 27th, 2017, 16:00 UTC as always in #core-php. There is no scheduled agenda yet this time, as there hasn’t been a response by the marketing team yet. WordCamp US will however provide a good opportunity to talk about the document in person. If you have suggestions about this but cannot make the meeting, please leave a comment on this post so that we can take them into account. See you next week!

#core-php, #php, #summary

Multisite Recap for the week of November 13th

Office Hours Recap

The agenda for this office hours meeting was to discuss adopting Trello as a way to manage status, progress, and ownership on tasks, as well as progress on multisite roadmap with a target to publish an initial version before WCUS.

The meeting’s chat log

Attendees: @desrosj, @flixos90, @jeremyfelt, @spacedmonkey, @vizkr

Chat Summary:

  • The full roadmap draft should be in place by November 21st, in order for the document to be published a week later, on November 28th, so that it is out before WordCamp US. @flixos90 and @jeremyfelt will have another look to complete the remaining sections.
  • After discussing possible usage of Trello in a collaborative way, the conclusion was that what is missing the most is an easy-to-use UI to manage required tasks and assignees for tickets on Trac. However most of the functionality is already in place and could be used through workarounds, so the decision was made not to use Trello for now. Instead the goal is to be more precise with defining tasks when assigning a ticket and generally assign tickets around between the responsible parties for a part of it more deliberately, instead of having a single owner through most of a ticket’s lifecycle. In a perfect world, there would be more possibilities to choose from when assigning a ticket to somebody, such as “update patch” or “write unit tests”, but for now these tasks can also be determined in regular comment text.

Next meeting

The next office hours will take place on November 21th, 2017, 17:00 UTC. Its agenda will be to review the roadmap draft and then discuss #42252.

Ticket Scrub Recap

No ticket scrub took place this week.

Next meeting

The next ticket scrub will take place on November 20th, 2017, 18:00 UTC. Its agenda will be to determine the current state and required tasks of tickets scheduled for 5.0 and assign them accordingly.

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!

#multisite, #networks-sites, #summary

PHP Meeting Recap – November 13th

This recap is a summary of our previous PHP meeting. It highlights the ideas and decisions which came up during that meeting, both as a means of documenting and to provide a quick overview for those who were unable to attend.

The meeting’s chat log.

Attendees: @flixo90 @jdgrimes @jon_bossenger @mikelking @mte90 @nerrad @schlessera

@sergey

Chat Summary

We started the meeting by examining the poll that @flixos90 had made regarding a modified meeting time slot.

As most of the votes went to the 16:00 UTC time slot, and nobody had a specific reason for not using that time slot, we decided to make that new time official from now on.

This means that all subsequent meetings are held at 16:00 UTC from now on.

Then we continued working on the “Before Upgrading PHP” section again, which we are working on in a shared Google Doc.

Here’s a brief summary of the corresponding discussions and decisions:

  • We discussed adding a second “Backup” step after all updates have been done. In case of a rollback further down the line, this would avoid going through all updates again, which incur a big time and bandwidth hit.
  • While discussing how to best add this addition “Backup” step, we came up with the idea of adding small “aside” text boxes to the document, which visually communicate that the content therein is not part of the critical path and should not be considered a blocker in case the user can’t complete that “aside”.
  • We discussed the different animals that Google Docs assigned to the anonymous users, and how they don’t seem to match up everywhere. 😉
  • Regarding the compatibility checker, we discussed whether to include knowledge about the future XWP project that might have an impact here, or not. We decided that we write the content for the current state and context, as there’s no guarantees to when or if any of the WIP projects will be completed and usable.
  • We added an aside to the compatibility checker as well, to warn users against false positives and other detection issues.
  • We acknowledged that our aside might be a bit on the intimidating side, and that we need the help of the #marketing team to rephrase the copy in that regard.
  • We rewrote the “Ask plugin/theme support” topic so that it is clearer and points people to existing resources first before contacting support.

Next week’s meeting

The next meeting will take place on Monday, November 20, 2017 at 16:00 UTC, as always in #core-php, and its agenda will be to finish the rest of the “Before Upgrading PHP” document that we will hand over to the marketing team to get their help with writing the copy. If you have suggestions about this but cannot make the meeting, please leave a comment on this post so that we can take them into account. See you next week!

#core, #core-php, #php, #summary

Dev Chat Summary: November 15th (4.9 week 16)

This post summarizes the dev chat meeting from November 15th (agenda, Slack archive).

4.9 schedule + release timing

  • 4.9 release was delayed from yesterday (Tuesday, November 14th) to today (Wednesday, November 15th)
  • An updated 4.9 build went out earlier today, we still have to rebuild tinymce.min.js, but otherwise please test!
  • @afercia disagrees with patching last minute serious bugs without proper, broad, testing but deferred to decision by release leads
  • 4.9 release scheduled for later today (Wednesday, November 15th) at 3pm PST / 23:00 UTC
  • [Editor note: 4.9 released successfully! 🚀]
  • We’ll discuss post-4.9 / pre-5.0 plans later once we’ve had a chance to gather broader feedback on 4.9.
  • There is currently no timeline or plan for 4.9.x, but there are tickets currently slotted as 4.9.1 in Trac.

Meeting time changes

Gutenberg update

#4-9, #core, #core-js, #core-restapi, #dev-chat, #gutenberg, #summary

Multisite Recap for the week of November 6th

Office Hours Recap

The agenda for this office hours meeting was open floor.

The meeting's chat log

Attendees: @florian-tiar, @spacedmonkey, @desrosj, @flixos90, @mikelking, @jeremyfelt

Chat Summary:

  • There was a loose discussion on the tickets that should be focused on at the beginning of the 5.0 cycle.
  • Caching in WP_Site_Query will be a big focus at first. Tickets #42252, #42280, #42251. There was a brief discussion on some approaches.
  • Implementing new install and update methods in #41333.
  • Using the meta API for network options in #37181.
  • The new multisite roadmap is getting there and should be ready to publish before WordCamp US.

Next meeting

The next office hours will take place on November 14th, 2017, 17:00 UTC. Its agenda will be:

  • Discuss adopting Trello as a way to manage status, progress, and ownership on tasks.
  • Progress on multisite roadmap with a target to publish an initial version before WCUS.
  • Any progress on 5.0 tickets.

#4-9, #multisite, #network-sites, #summary