PHP Meeting Recap – January 8th

This recap is a summary of our previous PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 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

The primary focus of this chat was strategizing about our opportunity on January 10th to discuss the servehappy project during the devchat. We discussed a potential roadmap with estimated timeline so that there’s specific information to offer at the devchat.

Decisions arrived at for rough ETA’s on Roadmap

• 1st Quarter 2018 is target for servehappy page on wp.org
• 2nd Quarter 2018 is target for coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. integration (adminadmin (and super admin) notice etc). See Core integration doc recently published.
• 3rd Quarter 2018 possible target for pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party requirements work.

Other discussion

• README.md was updated on the servehappy repository. Pull requests are welcome for keeping it up to date and adding any missing info (such as PHP Compatability Checker mentioned during the meeting)
• For admin notice initial work will be done in the tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker. (and that will be the source for initial wire-framing/discussion) and then we’ll do a feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. (possibly WordPress/servehappy-admin-notice) for iterating on implementation and easier user/usability testing.
• Some discussion around Tide and any potential impact on the servehappy project. General consensus is that Tide doesn’t blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. anything but communication should be kept open between the two teams to be aware of any overlap of documentation or user facing things between the two projects.
• @schlessera will be preparing a blogblog (versus network, site) post outlining a more detailed roadmap that will be published within two days, the intent being using it as a resource ahead of the general WP core dev-chat meeting.

Next Meeting

The next meeting will take place on Monday January 15, 16:00 UTC as always in #core-php.  The agenda will likely cover the results from servehappy presentation at the dev chat meeting and the next steps from that. See you next week!

#core-php, #php, #summary