Dev Chat Agenda: April 3rd

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found a bugbug 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.? Create a ticket in the bug tracker.
Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.
Other questions? Here is a detailed handbook for contributors, complete with tutorials.

Gary Pendergast 11:24 am on April 3, 2019

I won’t be around for this meeting, so here are my updates:

WordPress 5.2

The number of open issues hasn’t gone down as much as I would’ve liked since last week. Any assistance folks can offer with triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. would be greatly appreciated. With RC1 two weeks away, we’re going to need to puntpunt Contributors sometimes use the verb "punt" when talking about a ticket. This means it is being pushed out to a future release. This typically occurs for lower priority tickets near the end of the release cycle that don't "make the cut." In this is colloquial usage of the word, it means to delay or equivocate. (It also describes a play in American football where a team essentially passes up on an opportunity, hoping to put themselves in a better position later to try again.) all tickets not related to 5.2 features pretty soon.

Coding Standards Feedback

There’s been a lot of great feedback on the proposed coding standards changes, thank you! I haven’t had a chance to reply to the comments this week, but I’m planning on sorting through it over the next week or so.
Jb Audras 11:38 am on April 3, 2019
Thanks @karmatosed 🙂
Here is some further items:
- New dev notedev note 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. concerning Adminadmin (and super admin) Tabs AccessibilityAccessibility 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):
https://make.wordpress.org/core/2019/04/02/admin-tabs-semantic-improvements-in-5-2/
- also I proposed some help to run a bugbug 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. scrub / triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. session for 5.2 but I’still waiting for any approval on that side.
Cheers,
Jb
Jeffrey Paul 2:04 pm on April 3, 2019

I’m able to assist @audrasjb and any others on running a bugbug 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. scrub this/next week, though I won’t likely make devchat today so will have to coordinate on times async.

Comments are closed.

Welcome!

Communication

Share this: