This post summarizes the weekly dev meeting on June 15th, 2016.
Update on WordPress 4.5.3
Still targeting Tuesday, June 21st 2016 at 14:00 UTC.
Feature project updates
Font Natively
@helen updated the system fonts ticket Created for both bug reports and feature development on the bug tracker. with screenshots of the test page. The ticket still needs a few more screenshots and a 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. for font-weight.
Directly after the meeting @coderste submitted a patch for the remaining font-weight issues.
Shiny Updates
The results of Monday’s Shiny Updates meeting gave a partial merge approval. The commit was made today [37714]. Congratulations to the Shiny Updates team and all who were involved in any way. @swissspidy is going to lead the project for the rest of the cycle.
Dev notes Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. and initial field guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. planning
The Field Guide is an effort that the Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team make each release to inform developers about important changes in the release. The Field Guide is made up of links to individual posts known as dev notes. Dev notes include things like new features, changes to watch for, and potential areas for breakage. As an example, here is the Field Guide for 4.5: https://make.wordpress.org/core/2016/03/30/wordpress-4-5-field-guide/
Please note: dev notes do NOT need to be written by committers. Someone can work with first time authors to help them feel comfortable writing a post. If you would like to contribute to the 4.6 Field Guide please speak up in the #core Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel and someone will help you on your way.
Topics that need dev notes and their potential authors:
- Bootstrap – @jorbin
- Summary – @jorbin
- Font Natively – ????
- Shiny Updates V2 – @swissspidy
- 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 – @jeremyfelt
- Editor – @iseulde/@azaozz?
- Customizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. – @westonruter?
- Requests/HTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. – @rmccue?
- dbDelta – @pento?
- i18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill. – @ocean90?
- Widgets – @westonruter?
- WP_Term_Query – @boonebgorges
For the #core group there are currently ~140 signups. 20%-40% of these signups are new or not an experienced contributor (yet 🙂). Contributor days are meant to change that.
Review handbook pages and good-first-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. report
In order to effectively help those seeking to begin contributing to WordPress, both the contributor handbook pages and the good-first-bug report need to be reviewed and refined. These help guide new contributors in finding something to work on and properly submitting a patch.
@lukecavanagh showed interest in helping with reviewing the handbook pages.
Workshop about preparing a dev environment for core
The core group is going to be huge and it will be way more productive for everyone if there was someone experienced to help new people set up their dev environments. The WCEU team is looking for someone (with a backup) to lead a workshop about preparing a dev environment for core. @adamsilverstein volunteered to help with the workshop. @jeremyfelt is going to help if any issues come up with VVV.
If anyone else is interested please contact @_dorsvenabili or @petya.
Component announcements/updates
None.
Open discussion
- #12706 needs some eyes and an architectural decision before it can move forward. It may be a good candidate for a feature project.
- In 4.5, the login <
title>Â structure was fixed, but the admin (and super admin) pages were missed. #35774 aims to fix that.
- #34923 is seeking feedback for accessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility), design, code review, docs, and general comments.
#4-6, #dev-chat, #summary
