This post summarizes the dev chat meeting from March 15th (agenda, Slack archive).
- Additional dev chat earlier today on topic of Browser support (Slack archive)
- After some discussion, we arrived at the following strategy.
- A “text” editor available to everyone is the best fallback – the new visual editor will leave old browsers behind.
- Some form of the current version of the editor can be packaged into a plugin 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. Sites with users requiring a more advanced editor experience for older browsers can install this plugin.
- The WordPress admin (and super admin) screen will display a notice of some sort to users with older browsers explaining the changes and how they can install the plugin for the experience they were used to (possibly utilizing BrowseHappy).
- The editor team will use their research for the new editor to determine which buttons need to remain in the “text” editor with support for older browsers.
- A more general discussion about browser support policies is slated to be had at the Community Summit before WordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. EU. But this discussion can start before that (@jorbin is working on a Make post to start that conversation).
- Any additional feedback from anyone who could not attend then is welcomed!
Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team reps
- Last week we had nominations for @jorbin and @afercia.
- Core team reps need to plan to be at the Community Summit and can take on organizing topics and people
- @afercia not currently scheduled to be at summit, but would like to
- Please comment or contact @jbpaul17 directly if you’re planning to attend the summit and can help organize topics/people for Core
- Core Media Widgets are in a good place for testing now, specifically the image widget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user.
- Development & current version tracked via GitHub repo
- Day of REST event was successful, but delayed continuing 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. triage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors., will pick back up on 4.7.4 to make sure we keep solving the critical pieces
- @jnylen0 & others resolved issue with tests & daylight savings time
- due to bandwidth the existing 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/. contributor group is fully occupied with the API An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. itself
- existing REST API contributor group have neither the bandwidth nor the domain expertise to also be leading the WP Admin implementations that will consume the REST API
- @adamsilverstein lead the charge with Quick Draft, and work has begun in several parallel channels, but as of right now there’s nothing that appears to have momentum
- We need help to drive adoption of the REST API within WP Admin, please come chat in #core-restapi any time
- We need more explicit awareness of how the other feature teams want to use the REST API, or volunteers to lead separate implementations to move away from admin-ajax where it introduces inconsistency
- If you’re not able to lead the separate implementations, then please chime in on component tickets as they’re opened to help us triage the pain points
- PHPunit tests (#39265: Missing @covers and @uses in the comments block 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. in phpunt test for wordpress)
- @pbearne: I am trying to do is get support to have
@uses required for PHPunint tests
- @pbearne: Willing to work through the old tests to add the missing comments
- @pbearne: I would like to propose that we require for all new / updated tests and that the code committers commit updates with these added ASAP
- How would we use that information going forward?
- @pbearne: add to 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/ as way of show code quality and tell how well we are doing
- What would be a realistic number we’d want to achieve?
- @pbearne: anything over 80%
- If you use the editor, please look to complete the Editor Experience Survey.