Devchat meeting summary: July 1st, 2020

@whyisjake led the chat for this agenda

Highlighted/Need Feedback Blogblog (versus network, site) Posts

A few blog posts and announcements were shared by @whyisjake

@azaozz recently published a plan to update the version of jQuery that is shipped with WordPress: ‬Updating jQuery version shipped with WordPress‬‬

@sergey‬ published this proposal last week to change some of the closure statuses in TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.: Proposal: Rename “invalid”, “worksforme”, and “wontfix” ticket resolutions. ‪@sergey‬‪ shared that he is waiting on more feedback and will summarize this weekend or so.‬‬

@audrasjb recently published ‬WordPress 5.5: Better fine grained control of redirect_guess_404_permalink()

@desrosj recently published External Library updates in 5.5: call for testing

What’s new in GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/

@whyisjake noted the amazing new image editing capabilities (with gifs!) : What’s new in Gutenberg (24 June)

As a follow up, ‪@Andrei‬ posted the editor chat summary earlier today: Editor chat Summary: 1st July, 2020

@whyisjake pointed out that for anyone interested in contributing to closing some 5.5 tickets, ‪@ella‬ has a GithubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ board tracking issues for the net releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software..

@desrosj wants help to test SimplePie and PHPMailer! All 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 authors that utilize these libraries should receive an email alert. The updates have been in trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. for at least a few weeks now, and no issues have been found yet. @ipstenu has picked it up and just needs a clone.

Upcoming Releases

WordPress 5.5 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 is right around the corner: WordPress 5.5 Development Cycle @whyisjake noted that from this point on, no more commits for any new enhancements or feature requests in this release cycle, only 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. fixes and inline documentation. Work can continue on enhancements/feature requests not completed and committed by this point, and can be picked up for commit again at the start of the WordPress 5.6 development cycle.

Components Check-in and Status Updates

APAC Scrub @davidb‬‪ provided an update on the ‬APAC scrub last night. With Beta 1 approaching, the deadline for Feature Requestfeature request A feature request should generally begin the process in the ideas forum, on a mailing list, as a plugin, or brought to the attention of the core team, such as through scope meetings held for each major release. Unsolicited tickets of this variety are typically, therefore, discouraged. and Enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. type tickets is at that point.@audrasjb congratulated everyone on bringing the number down this past week. @whyisjake ‪asked what the process would look like between now and ~next Tuesday for these tickets? @davidb said ‬triaging while pinging owners/maintainers as much as possible for updates. Monday and Tuesday will probably see a lot of punting though, if these tickets don’t move between now and then‪. @whyisjake then asked if a ticketticket Created for both bug reports and feature development on the bug tracker. doesn’t see movement, do we normally move to Future Release or 5.6? @davidb said mostly Future Release with a comment that the owner/maintainer/committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. can update to the current milestone when they assume ownership to avoid the “kick the can down the road” issues of the past.@whyisjake gave major props to @davidb and everyone else that takes the time to keep the ticket garden tidy.‬‬

@francina mentioned that there has been a lot of discussion in 5.3 and 5.4 about what bug fixes can be fixed. Group asked if we should revisit or continue as we did until she finds the time to write the proposal?

@audrasjb noted that ‪#48751 was intentionally punted to 5.6 and not Future release and should be left in its current milestone‬‬

@marybaum team is on track to attach rough layout and copy for the About page to the ticket on track with Beta 1 and then commit by RC1, so polyglots can have the full period to translate. She gave props to ‪@estelaris‬, ‪@yvettesonneveld‬ and ‪@abhanonstopnewsuk‬ for art direction, help with the message brief and outreach to the marketing team.

@francina gently reminded all the component maintainers that we are 6 days away from Beta 1 and ask for help if needed.

@whyisjake provided a link for the list of components, with the maintainers: Component Pages – Makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.

@whyisjake mentioned that WordPress 5.5 introduced a new sitemap component.

@Carike mentioned that there is still a significant difficulty that some components have a large number of maintainers, while only one is currently active. It prevents people from volunteering. @francina and ‪@yvettesonneveld‬ talked about the possibility of mentoring new contributors to avoid burnout.

@Carike mentioned that one couldn’t triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. tickets properly without maintainer status. @clorith said anyone can triage tickets, it’s also possible to have gardener capabilities without being a maintainer. @johnbillion seconded this and said maybe the status is not set on Trac @whyisjake posted the link to some docs around bug gardening: Bug Gardening @sergey also posted the link to a good overview for anyone interested in triaging/gardening @‬desros ‬has a new related post in his drafts and will try to wrap that up and get it published next week!‬

@audrasjb gave a few updates from the components he’s working on:

  • Everything is fine from Widgets and Menus components. The biggest remaining ticket is #48170 and it’s only waiting for review.
  • Everything is fine from Plugins and Themes auto-updates. We have few remaining tickets but no blockerblocker A bug which is so severe that it blocks a release..
  • From the 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) focus: we’ll start punting to Future soon. We still have two remaining bug scrubs to handle the remaining tickets.

New 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.-based menus page: @Andrei‬ and a bunch of other folks have been working on a new, block-based, menus page (nav-menus.php) and think it’s time to start syncing with everyone else on how things evolve. They will host a weekly chat in #core about the current evolution and state of the new navigation screen. The meeting will happen in #core every Wednesday, July 1, 2020, 12:00 AM PDT, starting next week, on Jul 8th. In general it will be a triage around issues in GitHub labeled with either [Feature] Navigation screen or [Block] Navigation but also completely open to exploring any subject around improving the navigation creation process in WordPress, increasing compatibility with the incoming FSE and also maintaining backwards compatibility.

@sabernhardt mentioned that #50120 could benefit from more attention

Open Floor

@Hareesh asked, with regards to ticket #50503 (linked #40039), if it is conventional to make such changes for all bundled themes all the way up to Twenty Ten? @williampatton @whyisjake @audrasjb agreed it was and @whyisjake said the team normally coordinates with ‪@ianbelanger‬ who pushes those same changes to the non-bundled versions that are the in the theme repo.

@enrico.sorcinelli raised ticket #21676, based on the analysis ‪@sergey‬ he thinks that is definitively the time to take a decision for this 8-year old ticket and long awaited simple feature. ‪@sergey‬ asked everyone to read the recent comments on the ticket and share their thoughts

#5-5-2, #dev-chat-2, #summary

CSS Chat Summary: 25th June 2020

Full meeting transcript on Slack: https://wordpress.slack.com/archives/CQ7V4966Q/p1593118837002500

I (@notlaura) facilitated the meeting.

CSSCSS Cascading Style Sheets. audit updates

I added a summary comment with remaining items to the main CSS audit ticket, and confirmed with the group that we were in agreement to remove auditing CSS comments from the list. I also added property counts for letter-spacing and font-family to go along with the other typography-related properties.

There was general agreement that the “Determine methodology recommendations” sub-task ticketticket Created for both bug reports and feature development on the bug tracker. is complete since we have been using @ryelle excellent CSS audit tool. The next step will be determining how to automate the results, and @isabel_brison suggested that be a separate ticket. In addition to an automation ticket, I added that we will want to have a ticket to determine the display of audit data.

Color scheming updates

@ryelle mentioned the merged PR to GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ that successfully applied the adminadmin (and super admin) color scheme using a single base color with accompanying Sass mixin vs using the post-css themes approach we’ve looked at previously.

@danfarrrow mentioned the possibility of computing the color values in native CSS using custom properties. There was agreement that this would be ideal, but that Sass or PostCSS would be required at least in part, and we would need to test out some approaches, including something like outlined in this blog post. @youknowriad mentioned an issue with the approach outlined in the blogblog (versus network, site) posts ties the colors APIAPI 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. to HSL values, and we would want to have the colors available in a more generic form. Still, some experimenting is in order before we fully rule out the possibility!

CSS Latest and Greatest Link Share

I shared the gap property that can be used for horizontal and vertical spacing between elements for both flexbox and CSS grid. While support is not green across the board yet, recent versions of Chrome have full support, so we are getting close and this blog post of mine gives an overview of using the gap property with a fallback.

#core-css, #summary

Media Meeting Recap – June 25, 2020

Here’s a summary of the #core-media chat from June 25, 2020. Weekly media meetings happen on Thursdays at 14:00 UTC; see the full transcript here, in the Make WordPress Slack.

Attendees: @paaljoachim, @joemcgill, @desrosj, @chaion07, @cdog, @sageshilling, @antpb, @afercia, @swissspidy, @JJJ, @pbiron

Discuss Media REST APIREST 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/. endpoints

The below post was discussed as an effort to bring visibility to the changes in image editing. Please take a moment if you haven’t to consider any Media implications of the changes. Many great ideas have been documented in the post.

Ticketticket Created for both bug reports and feature development on the bug tracker. #50105: Remove infinite scrolling behavior from the Media grid

#50105 was discussed and there is some help needed testing the most recent patchpatch 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. to remove the infinite scrolling behavior in Media grid. Separately from this issue, a new 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. was found that needs some attention. The unintended consequence of the changes were that the number of items counted for the “Load More” button are incorrect as they calculate images that do not render. The ticket at minimum before 5.5 needs a more accurate count to better represent what is left to load. An issue to track this can be found in #50410.

Media Meeting Continued June 26 at 14:00 UTC

One topic that did not get a chance to be discussed was #16020 “Upload custom avatarAvatar An avatar is an image or illustration that specifically refers to a character that represents an online user. It’s usually a square box that appears next to the user’s name. for user in Dashboard” which was recently commented with a recommendation to remove from the 5.5 scope. Given the timeframe and wide range of complexities, this needs some time to:

  1. Discuss tomorrow at 14:00 UTC to determine next steps
  2. Collaborate with the Privacy team to ensure this is done in the best way for everyone and in a featured 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.

Please feel free to continue the momentum of this issue join in on the discussion tomorrow.

#core, #core-accessibility, #core-media, #media, #summary

Devchat meeting summary – June 24th, 2020

@whyisjake led the chat on this agenda.

Highlighted/Need Feedback Blogblog (versus network, site) Posts

A few blog posts and announcements were shared by @whyisjake and others:

  • GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ 8.4 has been released: What’s new in Gutenberg – June 24, 2020
  • A date/time has been solidified for APAC specific triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. sessions: New date and time for APAC triage sessions
  • @audrasjb announced that @ryokuhi was elected to replace him as 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) Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts., alongside @nrqsnchz.
  • @jorbin has recently published a proposal on moving git repositories away from master as the main branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". name to using trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision.: Proposal: Update all git repositories to use trunk instead of master. This work is already on track.
  • @sergeybiryukov published a proposal to change some of the workflow related keywords to be more inclusive: Rename “invalid”, “worksforme”, and “wontfix” ticket resolutions

Upcoming releases

WordPress 5.4.3

WordPress 5.4.2 has been simmering for a few weeks now, and milestone 5.4.3 is open on Trac.

Right now, the majority of the tickets are related to theme updates, with one regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5.. As there is less than 2 weeks before WordPress 5.5 betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1, the main effort is currently concentrated on milestone 5.5.

WordPress 5.5

WP 5.5 ReleaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. coordinator @whyisjake shared that beta 1 is roughly two weeks away (July 7, 2020), and there are still around 230 open tickets in the milestone.

@davidbaumwald will bump the remaining early tickets at the end of the week. There are currently 13 tickets marked as early in the milestone. He also shared a general reminder: Beta 1 is the deadline for Feature Requestfeature request A feature request should generally begin the process in the ideas forum, on a mailing list, as a plugin, or brought to the attention of the core team, such as through scope meetings held for each major release. Unsolicited tickets of this variety are typically, therefore, discouraged. and Enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. type tickets.

@desrosj shared a list of all feature request and enhancement tickets currently in the 5.5 milestone (88).

@pbiron asked if “enhancements” to the three feature plugins merged in WP 5.5 are allowed to be committed after beta 1. @clorith answered Feature plugins should not need enhancements post-merge. However, small enhancements can be labelled as 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., for example if the enhancement aims to reduce false positives, like #50437 does.

@sergeybiryukov also recommended to branch the next milestone (5.6) right after Beta, so enhancements and other bug fixes could go to trunk for 5.6 and not loose their momentum.

Components check-in and status updates

@antpb shared the Media team next meeting agenda.

@azaozz asked for help with the Test jQuery Updates plugin. Feedback are welcome ont the text/explanations in it, and with the readme file, etc. The 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 is expected to be officially released very soon.

Open Floor

@joyously pointed some tickets that may benefits to plugins and themes auto-updates feature. Her proposal is to add more information to the auto-update email notifications. In the case of themes, adding information from the changelog. @audrasjb to makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). sure to raise those points during the next auto-updates team meeting.

@carike asked to consider removing coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. SlackSlack 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 from the channels that are auto-joined for Slack. It would be less stressful to try to orientate new users in an environment that is less technically-focused and/or not quite as large as core Slack channel. Everyone agreed this proposal makes sense. @aaroncampbell proposed to use a welcome channel that is locked but had a message with the main channels for each group for people to click to join. A ticketticket Created for both bug reports and feature development on the bug tracker. is about to be opened on MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. to handle ad discuss this task.

#5-4-3, #5-5, #core, #summary

CSS Chat Summary: 18th June…

CSSCSS Cascading Style Sheets. Chat Summary: 18th June 2020

Full meeting transcript on Slack: https://wordpress.slack.com/archives/CQ7V4966Q/p1592514070423800

I (@notlaura) facilitated the meeting.

CSS audit updates

@isabel_brison updated the Audit Google Doc with some unique counts of layout and typography related properties with a focus on those than overuse px in a way that effects responsive behavior, and added a list of all properties using px values.

We then discussed @joyously‘s suggestion from a few weeks back that we create a task list for the audit. The doc is useful, but very informal and might be hard to follow for anyone who doesn’t have existing knowledge about the initiative. There was general agreement that a specific task list would be useful. I mentioned that it seems like we are nearing completion of the smaller audit tickets (Create a Report Outline and Determine Methodology Recommendations), and that in a few weeks we will want to discuss what’s next. Exciting! I volunteered to take stock of the remaining work and update the main audit ticket.

Color scheming updates

Last week we discussed naming conventions with the design team, and I mentioned that the notes from that meeting are a good overview of the color scheme initiative for newcomers.

@isabel_brison pointed us to a message that @youknowriad shared a PR adding admin color schemes to Gutenberg. Pretty cool that folks are dropping PRs in our channel!

I mentioned that, in the last meeting, we determined a next step of creating annotated screenshots to start iterating on the color names and abstraction names, and wondered if we should proactively seek out help from the design team for this. @isabel_brison mentioned that whatever the solution, the naming needs to work for designers and devs, and @kburgoine suggested we could propose some names and ask design for feedback. Overall, it will be a collaborative process and doesn’t need to be done by a specific team. We also discussed what exactly would be in an annotated screenshot – a full page? A specific module? I suggested that we start small, maybe with a widgetWidget 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. or the toolbar.

CSS Latest and Greatest Link Share

I shared a new property I learned about that has good browser support: max-inline-size

@kburgoine shared a lovely tool that shows sorted named CSS colors.

That was all for this week!

#summary #core-css

Devchat meeting summary – June 17th, 2020

@davidbaumwald led the chat on this agenda.

Highlighted/Need Feedback Blogblog (versus network, site) Posts

@davidbaumwald shared a few blog posts and announcements:

Meeting notes

@jeffpaul and @timothyblynjacobs called for particular attention to the Experimental Endpoints (REST APIREST 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/. team). It needs a decision, and it could use input from a variety of experienced reviewers who understand what’s at stake:

Other meeting notes:

Upcoming releases

WordPress 5.4.2

WordPress 5.4.2 shipped with the help of our amazing contributors). This version packs six security fixes and lots of 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. fixes. More details about what is inside are on the version page.

@whyisjake took a moment to thank everyone that was part of the releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. team’s huge group of contributors, both on the security front and in bug fixing.

He also called special attention to the fact that the release team decided to backportbackport A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. the changes in how comments are handled to WordPress 5.1/5.2/5.3. See the related dev note for more.

As a reminder, the WordPress project’s security policy is publicly available on GitHub.

WordPress 5.5

WP 5.5 Release coordinator @whyisjake shared that betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 is roughly four weeks away, and there are still around 250 open tickets in the milestone.

Of special note is this GitHub project that the #core-editor team has been working on.

@davidbaumwald reported that he’s added the 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) scrubs to the Bug Scrub Schedule for 5.5.

The Accessibility team needs help and feedback on these tickets:

@marybaum announced that there’s a team assembled to work on the About page. @davidbaumwald has opened ticketticket Created for both bug reports and feature development on the bug tracker. #50416 to handle About page development.

Following up on her announcement, @marybaum suggested promoting WP 5.5 in the current version’s dashboard for a couple of weeks in the release-candidate period in a dashboard widgetWidget 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..

@desrosj answered that if something is important enough to receive its own area on the dashboard of every sitesite (versus network, blog) before it is released, the best way to do that would be in a post on the News blog.

Components check-in and status updates

@flixos90 asked the Media team for feedback on #50367.

@timothyblynjacobs would like feedback on a possible batch-processing endpoint for the REST API: #50244, on the particulars of the patchpatch 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. and on the ergonomics of it.

@mikeschroder requested feedback on whether (and what) filters would be helpful for opcode cache invalidation: #36455.

Open Floor

@paaljoachim pointed out ticket #16020, which aims to introduce custom avatars for user profiles. The ticket has a patch; it needs review and final validation from the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team.

@enrico.sorcinelli called the group’s attention to ticket #21676, and @sergeybiryukov confirmed that ticket is already on his review list.

#5-4-2, #5-5, #core, #summary

CSS Chat Summary: 11th June…

CSSCSS Cascading Style Sheets. Chat Summary: 11th June 2020

Full meeting transcript on Slack: https://wordpress.slack.com/archives/CQ7V4966Q/p1591909237318500

I (@notlaura) facilitated the meeting.

Discussion on color naming with the design team

We started out by reviewing some goals of this color scheme initiative with regards to wp-adminadmin (and super admin):

  1. Easily create full-feature color schemes that apply to the entire wp-admin (e.g. dark mode)
  2. Improve existing wp-admin CSS

@joyously asked if this applies to properties like CSS filters and blend mode, and @kburgoine and I indicated that it would likely be limited to defining a base color palette and color values.

I then asked how the designers currently name colors in designs – @michael-arestad replied that he uses hex codes, and for colors named according to intent, it is only the accent color. @ryelle linked to this WordPress Colors CodePen. @nrqsnchz agreed that we should aim to use names that specify the use of the color vs. the color itself.

@michael-arestad linked to a couple of example projects where colors were organized into “sets”: the main colors (5-10 most common), a primary accent color, additional accent colors. Here is one example with multiple levels of abstraction and an older version.

I mentioned another goal – or perhaps an elaboration of what “easily create color schemes” means – is that creating a new color scheme should be a matter of updating a predefined set of variables with different colors values. One should not have to write any new CSS (save custom property definitions at a high level) to create a new color scheme, and to achieve this, multiple levels of abstraction will be required (e.g. assigning #FFF to --button-color, and thencolor: var( --button-color );).

@michael-arestad noted the importance of providing a range of lighter/darker versions of a colors to ensure folks aren’t coming up with slightly different shades of the same color, even though providing those options is important.

We discussed a next step of annotating some designs with potential color palettes and names – for example, a screenshot of wp-admin with the default color scheme and a screenshot in dark mode, with a Figma palette with the colors used in each. The intent of the annotations is not to determine specific color names yet, but to get an idea of the higher level “color buckets” or categories (e.g. color-primary, color-accent), and the UIUI User interface elements they may be applied to (e.g. --button-text-color, --sidebar-background-color).

Next, we talked about options for naming the variations in the colors – a couple of approaches mentioned were using terms lightest/lighter/light/dark/darker/darkest or using number 100-900 to allow for middle ranges. @ryelle mentioned another approach where 50 was used as a cutoff and above or below 50 indicated contrast with white/black, and we discussed the ideal of a naming system that would help ensure proper contrast ratio between colors. I shared an example of how we are handling our color naming at my job.

To conclude the meeting, I re-iterated / refined the goals of the color scheme initiative:

  • Creating a new color scheme should be similar to filling out a form with color values
  • All colors in the wp-admin should be controlled by the color schemes
  • Reduce the number of colors in use by providing default color palettes with varying shades

Our next steps are to start determining the “color buckets” and categories/mappings of the UI abstractions that will be used to apply the colors. We can start this process by annotating screenshots two screenshots (one of light mode and one of dark mode) with potential color names and corresponding color palettes.

Help Needed
Is someone with design knowledge up for creating these annotations? @michael-arestad offered to provide guidance and access to Figma where needed.

Latest and Greatest in CSS Link Share

@kburgoine shared Hybrid positioning with CSS variables and max() from Lea Verou (who’s website is using the default theme to great effect! 😄).

That was all for this week!

#summary #core-css

Devchat meeting summary – June 10th, 2020

@whyisjake led the chat on this agenda.

Highlighted/Need Feedback Blogblog (versus network, site) Posts

@whyisjake shared a few blog posts and announcements:

Upcoming releases

WordPress 5.4.2

WordPress 5.4.2 was planned to be released Wednesday 10th after the devchat (and successfully shipped with the help of our amazing contributors). This version includes six security fixes and many 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. fixes. More details about what is inside can be found on the version page.

WordPress 5.5

@pbiron reminded that three feature plugins will be included in WordPress 5.5. Lazy loading of images, themes, and plugins, auto-updates, and XML sitemaps.

Some tickets for enhancements/features will need some help, testing, or feedbacks before 5.5 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 (targeted date: July 7th, 2020): #40351, #41750, #33161, #47456, #43738.

@audrasjb mentioned some other tickets on which the 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) team needs help and feedback. #49459 and #49651 need Editor team feedback and #30155, #47120 and #48170 will need feedback and expertise from the Media team.

@paaljoachim said he’s working on #16020 and would need some feedback on it.

Open Floor

@enricosorcinelli mentioned that #21676 got some new attentions, and could be a possible candidate to ship in 5.5.

@adamsilverstein reminded the group that the #core-js team is looking for an additional person to help run the weekly JavascriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. chat. The chats take place Tuesday at UTC-06:00 in #core-js. Feel free to say in the channel in the next meeting if you’re interested in that.

@justinahinon said that he reached out to people interested in helping on hosting APAC devchats proposed here. There is a plan to discuss in the #core channel about the outcomes of the meetings and a possible schedule (a note about that will be published soon on Makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility)./CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blog).

Related to that, @yvettesonneveld shared what they have been doing for marketing coffee breaks and that was very helpful in recruiting and retaining contributors. Updates for this can be found here.

@jeffpaul proposed some additions to the Releasing Major Version and Glossary handbooks. These additions are about the early ticketticket Created for both bug reports and feature development on the bug tracker. definition and how they are handled during the releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. process. This is a result of discussions at WCEU Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. and received helpful feedback from @davidb, @desrosj, and @joemcgill. Some contributors had a discussion about that, and you can rollback to here to follow.

@enricosorcinelli reminded that they are some tickets that have been milestoned for each release since 5.0 but hadn’t received any attention in their life cycle. These are #43516, #43517.

This closed the devchat discussions to leave room for WordPress 5.4.2 release party.

#5-4-2, #5-5, #summary

CSS Chat Summary: 4th June…

CSSCSS Cascading Style Sheets. Chat Summary: 4th June 2020

Full meeting transcript on Slack: https://wordpress.slack.com/archives/CQ7V4966Q/p1591304484223300

I (@notlaura) facilitated the meeting.

Acknowledging Racial Injustice

I didn’t feel comfortable leading our usual meeting without explicitly acknowledging the racial injustices that have lead to the Black Lives Matter protests in the US and around the world. I invited meeting attendees to converse in a thread during the meeting, if they wanted.

CSS audit updates

I update the Google Doc with the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 files that contain CSS, and we discussed how to approach the JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. files that contain CSS, and what specifically to note about the styles in PHP. @kburgoine suggested to focus on any CSS that includes colors and units of measurement that may change in the future.

Color Scheming Updates

Next week, we will have an agenda item to discuss color naming conventions with the design team, but we did have a cursory discussion this week.

@ryelle has been experimenting a PostCSS plugin she mentioned last week that will pull out all colors and replace them with custom properties named according to their selector and property. While it has promise, there will need to be some manual work involved since it creates so many properties and very long property names due to long selectors.

@michael-arestad outlined a couple of alternative approaches that may reduce the amount of the custom properties, but may require selective overrides and may be more difficult to understand. We went back and forth a bit exploring these options and that it would be valuable to have foreground and background colors paired together, and perhaps there is a way with the concept of design tokens to achieve that.

We concluded that a next step would be getting an idea of the scale of actual color values required, and @squarebracket shared a very interesting approach for programming Sass-like color functons with custom properties that would could incorporate into our iteration.

CSS Latest and Greatest Link Share

The clamp() function has very good browser support these days! Here is a great blog post about it – just look at that huge Less/Sass mixin we no longer have to write!

Also, @netweb is doing some work on getting the Stylelint config and tooling into coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. for #wceu Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/.! Very cool.

That was all for this week!

#summary #core-css

Dev Chat Summary: June 3, 2020

@whyisjake facilitated on this agenda. @sageshilling is the author of this summary, and @marybaum is your marginally faithful editor.

Announcements

@chanthaboune had three: 

  1. CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. has two brand-new team reps – @francina and @audrasjb! See more here.
  2. @chanthaboune will host office hours with Matt at WordCamp Europe this weekend.
  3. Release squads for the rest of 2020 are pretty close to final, with one update outstanding.

@whyisjake pointed the group to the latest Gutenberg news, which included a near-weekly releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software.–this time to version 8.2.

Upcoming releases: 5.4.2

@whyisjake shared the status of the next minor.

After a smooth release-candidate launch just hours before devchat, he confirmed, “We are looking really great for a release on the tenth.” Check the Trac milestone here and you’ll see for yourself!

Component Updates

@swissspidy expects to share a merge proposal for sitemaps next week 🙂 based on this pull request. He commented that folks are “adding the finishing touches here and there until we have something we believe is ready to merge.”

@audrasjb reminded the group that two weeks ago the Plugins and themes auto-update feature got merged, and so far the feedback is pretty good.

The coders on the ticketticket Created for both bug reports and feature development on the bug tracker. are adding a few more hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same., and @audrasjb pointed to two relevant tickets that need copy review by Friday, when @audrasjb will submit them for final review. @m_butcher, @yvettesonneveld and @marybaum are on the task.

The two tickets are #50215 and #50268. If you’re reading this, you too can look at the copy and add your suggestions!

Open Floor

(Ed. note: Got a pressing topic for Open Floor? Add it to the agenda post as a comment, and come to the chat. It’s in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/., so you don’t even have to comb your hair! )

From comments on the agenda:

@glorialchemica asked for an update on the full-sitesite (versus network, blog)-editing, or FSE, for short, project.
@chanthaboune responded.

So, the form to show interest has been closed, and I believe that the process of reaching out to everyone has started. The point at which actual feedback outreach and processing begins is a little fluid, since it’s tied to development timelines but it should get going in the next month or so if I recall correctly. In my absence, @annezazu will be driving the bulk of that work.

@chanthaboune

@annezazu announced that she was in the process of inviting everyone who’d signed up to a private Slack chat where folks could try things out and communicate efficiently; a lively discussion followed, with several keepers of WordPress history reminding the group of relevant incidents in the history of the project.

The result: @annezazu immediately made a public space for FSE and will take the private one down shortly.

@timothyblynjacobs asked for feedback from the Build/Test Tools maintainers on #50251. @jorbin took a look and said, Looks good. I’m going to commit it

@francina reminded the group about Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. at WCEU!

@joyously mentioned there was a meeting about the editor and CustomizerCustomizer 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., and FSE.  She asked if there will be another one? 

@desrosj I think that meeting was more to help the Customizer maintainers shape their expectations of where their expertise would be needed throughout the FSE process. 

@whyisjake ended the meeting at the top of the hour.

If you’d like more depth about anything the Core team discussed, you can read the full chat transcript here.

#chat, #core, #dev, #summary