Devchat meeting summary – May 20, 2020

@francina facilitated the chat on this agenda.
Meeting recap by @audrasjb and @marybaum.

Full meeting transcript on Slack

Announcements

Just a few hours before the chat, the hardworking team behind the plugins and themes auto-updates feature committed it to Core! Congrats to all!

Check out this related ticketticket Created for both bug reports and feature development on the bug tracker. that adds Help Tabs text to update-core, themes and plugins WP-Adminadmin (and super admin) screens: #50215

If you’d like to be part of the Full Site Editing outreach experiment, the sign-up deadline is now May 22. @chanthaboune noted that’s just to show interest, not a commitment yet.

Highlighted posts

Upcoming releases

WordPress 5.5

The next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope. of WordPress is in active development (Alpha cycle).

@francina noted the team is not quite complete, but it’s confirmed that @matt will return as release leadRelease Lead The community member ultimately responsible for the Release.@davidbaumwald as co-lead in the role of Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. PM and @sergeybiryukov as Core tech lead. The 5.5 team will also mentor the 5.6 team.

WordPress 5.4.2

@audrasjb shared that there are 20 tickets in the milestone. Of those, 17 are closed as fixed.

@whyisjake leads this point releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality., and the group firmed plans for a release candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). on June 3 and a final 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. June 10.

Components check-in and status updates

@whyisjake was exuberant that the core team was able to merge the auto-updates code today. This is going to do a great deal to help people stay on top of updates for a safer WordPress ecosystem.

The merge is just the latest significant step toward the master plan for 2020. Lazy-loading of images merged a few weeks ago, and XML sitemaps is making great progress as well.

On 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) side, @audrasjb shared that most of the accessibility team’s main projects for 5.5 are moving forward. Alternate views for posts, users, and comments lists should be ready for review soon.

@johnbillion wanted to note that weekly meetings for Multisitemultisite 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 have restarted, on Tuesdays at 17:00 UTC in #core-multisite. Come join them!

In Sitesite (versus network, blog) Health, @clorith pointed out that the Theme Review Team has implemented requirements for PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 headers in themes. That move should push users in the right direction for updates.

As well, the Site Health component team has had discussions with hosting about bumping the version for Servehappy dashboard nags.

Open floor

@dlh wanted to highlight #48416. He recently encountered a use for it again. If you’re interested in the taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies. component, please give it a look.

@sippis reminded everyone to register for WCEU 2020 Online 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/., which is Thursday, June 4, 2020 at 13:00 UTC. If you don’t register, you won’t get the emails you’ll need in advance, so don’t forget to register.

#5-4-2, #5-5, #dev-chat, #feature-autoupdates, #fse, #summary, #wceu, #wceu-2020

Core-Editor Dev Chat May 20, 2020

This post summarizes the latest weekly Editor meeting, held in the #core-editor Slack channel, on Wednesday, May 20, 2020, 10:00 AM EDT. These meetings coordinate collaboration in the development evolution of the 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/ project. You can find today’s agenda here. Facilitator: @pbrocks

Recap

CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 5.5 — Checkout the Planning Roundup here

Gutenberg items to ship:

  • 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. UIUI User interface Redesign
  • Block Patterns
  • Hundreds of small improvements and  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

Gutenberg items we hope will ship but we’re not certain yet due to the deadlines:

  • Navigation screen and block
  • Widgets screen block-based
  • Global styles

Gutenberg version 8.1

Released last week containing:

  • Pattern searching
  • Copy block
  • Iterations on experimental screens
  • Embed transform to paragraph block.

Monthly Plan

What’s next in Gutenberg outlines the goals for May. There was no additional discussion around the current goals.

Task Coordination

@sageshilling

  • working with core-media data flow, design gallery, image block, gallery patterns…block_id

@mkaz

  • Diving into docs and addressing needs highlighted here Issue 22151

@karmatosed  

  • My main priority right now is navigation, navigation and oh yes navigation! I am working with some awesome peeps there.
  • I have a side order of triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. and ensuring any tickets I touched have feedback.

@andraganescu

  • As part of the ongoing work on the experimental navigation screen, I have added a _delete_ functionality for core data entities. If you are someone who uses entities this is interesting to get right so any feedback is welcome:

@youknowriad 

  • I’ve worked on a new CLICLI Command Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress. command to automate performance tests across branches/versions
  • Fixing some bugs related to Color palettes
  • Looking at some UI parity work between edit-post and edit-sitesite (versus network, blog)

@q

  • I’m continuing to help improve the Cover block, mostly around customization and the UI/UXUX User experience of those controls.
    • Adding Padding Controls
    • Improving Color controls
    • Improving Background controls

@ajlende 

  • I’m working on getting the first pass / rough draft of rich image editing now that it’s unblocked again. Still need to know how best to limit for testing as experimental and where it should live. 

@michaelarestad

  • I’m working on template part flows, how they could fit with a site-wide column grid, and hopefully flows for setting up a new template.

@nrqsnchz

  • Merged the new Welcome Guide design, which includes support for prefers-reduced-motion
  • Worked on and merged a couple of block patterns
  • Fight Travis tests, as I usually do

@nosolosw

  • My main focus was the managed CSSCSS Cascading Style Sheets. PR. It’ll remain my main focus for next week.
  • 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. docs generation: audited & updated the list of packages (some are up for grabs, pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” me if you’re interested in helping and don’t know how to do it) and documented the steps.
  • A bunch of other things: help with reviews, enable only stage-4 JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. syntax, etc.

@nfmohit 

  • I’m still working on a vertical style for the Buttons block.

@isabel_brison (tellthemachines)

  • working on a prototype for moving blocks between nesting levels with the keyboard and would love some feedback and testing on it! Also addresses the inability to move between nesting levels in navigation mode.

Open Floor

@zeb asks for review of the PRs listed in the agenda comments 

@annezazu The form for the Full Site Editing outreach project is open until May 22nd now: 

@mkaz

I’ve got one with regards to documentation I think we should revisit the idea of publishing off 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. tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.), and instead be versioning at the unit level. For example, the core docs include the version and changelog for each function. 

@nickthegeek

Looking for comments/help with this Issue 22332 Add screen reader only text format

@noisysocks asked for comments and review on Navigation

`A few of us (@talldanwp @andraganescu @isabel_brison @zieladam @karmatosed) have been building out a rudimentary replacement for nav-menus.php which is based on the Navigation block UI. This new screen is in a semi functional state and you can see it by switching on the Navigation experiment in the latest Gutenberg.

A new [Feature] Navigation Screen label tracks issues to do with this new screen, and the Navigation in 5.5 project board tracks work that we think is important for this feature to land in WordPress 5.5. If you’re interested in helping out with this project, please feel free to pick up one of the tasks in the project board. You can also ping me (@noisysocks) if you have questions or need guidance! `

@zeb expressed concerns with the current navigation interface, specifically referencing wanting to see the following issues addressed;

  • Issue 22089 Navigator iterations: ellipsis and movers
  • Issue 22297 Block Navigator/Navigation: Drag & Drop

The in-depth conversation can be followed in Slack archives. With the team in agreement to continue the conversation in 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/ with @karmatosed noting the navigation feature is still under an experimental flag and is in an iterative design process.

#meeting-notes #core-editor-summary

Chat Summary: 14th May 2020…

Chat Summary: 14th May 2020

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

I (@notlaura) facilitated the meeting.

CSSCSS Cascading Style Sheets. audit updates

@isabel_brison ran a check for dead code using Purge CSS (and there’s not too much of it!) and added results to the Google Doc.

We discussed running checks on CSS in wp-includes as well as in wp-adminadmin (and super admin), and that seems like a good idea. @isabel_brison mentioned there is some inline CSS in PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 and JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. files – including some inline !importants 🥺. It seems like a useful data point for the audit to include a list of non-CSS files that contain CSS so we can flag those instances for improvement later, and I added that to the Google Doc.

Color Scheming Updates

I added a comment to the Iterating on Color Schemes Trac ticket with some details on how design systems handle theming with abstractly named tokens, and added a few comments to @ryelle‘s Gutenberg PR that contains a prototype for color schemes using PostCSS themes. We discussed the importance of determining an approach for browser support and getting some experiments started early.

wordpress/postcss-plugins-preset

@kburgoine asked about a default PostCSS setup for WordPress which led nicely into this agenda item. The coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor team requested feedback on this PR adding support for building CSS in the wp-scripts package.

WCEU Online 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/.

WordCampWordCamp 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. Europe contributor day will be held online on June 4. It is an opportunity to contributors know about #core-css since it is a new group, and we could create a short list of tasks new contributors can help with on the CSS audit, or perhaps point them to the 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/ CSS tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.). I volunteered to find out some next steps for this.

That was all for this (last…) week!

#summary #core-css

Dev Chat Agenda for May 20, 2020

Here is the agenda for the weekly meeting happening later today: Wednesday, May 20, 2020, at 20:00 UTC.

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

Discussion

Should we have a point releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. based on the list of milestones tickets?

Components check-in and status updates

  • News from components
  • Components that need help/Orphaned components
  • Cross-component collaboration
  • Updates from XML Sitemap, Lazy Loading, 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 and Themes auto-updates, 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/ features and everything else planned for 5.5

Open Floor

Got something to propose for the agenda, or a specific item relevant to our standard list above?

Please leave a comment, and say whether or not you’ll be in the chat, so the group can either give you the floor or bring up your topic for you, accordingly.

This meeting happens in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

#5-5, #agenda, #devchat

REST API Meeting Agenda for May 21

The 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/. weekly component chat will occur this week at May 21, 2020 18:00 UTC in the #core-restapi 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.

Agenda Items:

  • Menus 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. Batch Requests
  • Authentication Update
  • 5.5 Updates
  • Open Floor

All agenda items are welcome, from all teams and contributors; please post them as comments below or let us know by joining the meeting.

#agenda, #rest-api

Dev chat summary: May 13, 2020

@chanthaboune led the chat on the standard agenda.

Announcements/Highlighted Posts

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.1

@youknowriad announced the minutes-old release of Gutenberg 8.1 and linked to the changelog.

Check out the full release post here.

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/.

@jeffpaul pointed the group to this WCEU Contributor Day post and asked for volunteers to help on the day and beforehand.

@marybaum volunteered to do a video about contributing to CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. in ways other than code, and the group asked her to please keep it brief. She promised it will be no more than a minute long.

@clorith is doing a video that focuses directly on code contributions.

@sippis posted this link to the full Contributor Day P2 and has made herself available for questions. @jeffpaul and @chanthaboune did as well.

Core Rep Elections

@jeffpaul reminded the group that May 14 is the deadline for nominating prospective Core Reps. These are very specifically not lead developer roles — they are roles that represent the work and interests of the Core team to other teams working on the project and to folks outside it as well.

See more in Jeff’s post here, including nominations and how voting will work.

Full-sitesite (versus network, blog) editing outreach 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.

Because the best things come in sets of three, @chanthaboune announced that May 14 is also the deadline to join the Full-Site-Editing outreach beta that she’s putting together.

Fill out the form and get all the details here.

Auto-Updates Feature PluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins.

@audrasjb and @azozz updated the group on the status of Auto-Updates for Themes and Plugins, which as a feature plugin is at v.0.8.

The big news is the Core merge ticket, which is #50052, and its first 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., courtesy of @pbiron. As @audrasjb put it, “It’s a pretty big patch!”

Then he laid out the plan for the feature plugin:

Now, we’ll update 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 with a PR that will deactivate the plugin when running the WordPress 5.5 / 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. to avoid conflicts.
Then, we’ll 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. version 0.8 of WP Auto-updates Feature plugin.

@audrasjb

Upcoming Releases

Major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: WordPress 5.5

@chanthaboune told the group she had a few more things to add to a 5.5 planning post; it is up here, and as of today we are kicking off the Countdown to Beta.

Pending further input, beta will be July 7, eight weeks from right now.

@chanthaboune noted in the chat that she’s still pulling together the Release Squad, adding, “But I wanted to see if anyone had volunteered for the release squad already that I might have missed.”

@marybaum and @whyisjake each, as they said, “volunteer formally, if not implicitly, . . ” to fulfill the roles they have in the immediate past.

With a wry emoji smile, @sergeybiryukov volunteered to reprise his tech-lead role as well.

Minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.: WordPress 5.4.2

@audrasjb referred to this list of 14 tickets in the 5.4.2 milestone. One ticketticket Created for both bug reports and feature development on the bug tracker. in particular caused concern in the group (Which one? You’ll see when you click on the list!)

So @whyisjake volunteered to lead a point releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. for mid-June. @audrasjb volunteered to help with all the things.

Open Floor

There were no specific calls from component maintainers, so the group moved on into Open Floor.

A request for eyes on a ticket

@apedog asked for some feedback on ticket #48223.

@jeffpaul noted almost immediately the ticket touches a component—Rewrite Rules—that at the moment has no formal maintainer. But then he wondered aloud if @sergeybiryukov and @asif2bd, who maintain the parent component Permalinks, could take a look.

Of course, @sergeybiryukov agreed.

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) plans for 5.5

@audrasjb transitioned from that ticket into his accessibility update. Here’s what he and his squad are planning for 5.5:

Alternative WP List Tables views (work started on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.)

Accessible color schemes (work started on 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/)

Refine/replace the upper-right WP-Adminadmin (and super admin) fly-out menu (work started on Trac)

And of course all the other tickets/bugs in the milestone

@chanthaboune: sabbatical planning

Josepha reminded the group she’s heading out on June 8, and we won’t see her back until September.

She pointed to a post that shows who to ask which questions, based on the topic and people’s areas of expertise.

A forum post about HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. entities

@joyously brought this forum post to the group, starting a lively discussion about sanitizing and escaping HTML in blocks and the Classic editor.

Finally …

Remember those May 14 deadlines. By now, that’s today! And watch this space for news on Core reps, the release squad and more.

#devchat

Privacy Office Hours Minutes 14 May 2020 Plans for WCEU Contributor Day

Mission 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/.:

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). Privacy Actionable.

Working groups:

There will be two working groups:
– Coding working group (coordinated by @garrett-eclipse);
– Non-coding working group (coordinated by @carike).

Pre-event office hours:

– 3 June 2020 at 10:00 UTC;
– 3 June 2020 at 19:00 UTC.

Pre-event office hours are to help onboard new contributors.
This primarily involves making sure that they have access to the tools necessary for the day.

Tools:

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/.:
Privacy Policy: region-specific at https://slack.com/intl/en-us/privacy-policy
Terms of Service: region-specific at https://slack.com/intl/en-us/terms-of-service/user

StreamYard:
Privacy Policy: https://streamyard.com/resources/docs/privacy/
Terms of Service: https://streamyard.com/resources/docs/tos/
We will be using StreamYard, as a number of experienced contributors in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-privacy have expressed an unwillingness to use Zoom due to privacy considerations.

YouTube:
Privacy Policy: https://policies.google.com/privacy
Terms of Service: https://www.youtube.com/t/terms

Core TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. (coding working group):
Privacy Policy: https://wordpress.org/about/privacy/

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/ (coding working group):
Privacy Policy: https://help.github.com/en/github/site-policy/github-privacy-statement
Terms of Service: https://help.github.com/en/github/site-policy/github-terms-of-service

How to participate:

As a host:
If you are interested in hosting one or more topics, please comment below.
You can contact @carike on Slack if you would like more information.

As a guest via StreamYard:
You DO NOT need to register a StreamYard account in order to enter the stream as a guest.
You DO NOT need to download any program in order to use StreamYard. It is an in-browser solution.
You DO NOT need to appear on-screen if that is not something you are comfortable with. An audio-only option is available. We’re going to be using a very practical approach, so I’m going to be screen-sharing most of the time anyway.
We will provide new contributors with instructions on joining StreamYard as a guest via e-mail.
Instructions can also be found here: Guest Instructions: https://streamyard.com/resources/docs/guest-instructions/
We will provide new contributors with a link to join the stream via Direct Message (DM) on Slack, as there can only be six contributors “onscreen” (or via audio) at any one time (i.e. two hosts and four new contributors), with up to four additional new contributors in the “waiting room”.

As a guest via YouTube:
You DO NOT need to register an account with YouTube in order to watch the stream.
You DO need to register an account and be logged in to YouTube in order to participate in the live chat.
StreamYard supports integrating live chat messages from YouTube.
This will allow for more real-time input and also allow participation among those who do not want to use audio, or appear onscreen.
We are trying to recruit experienced contributors to help moderate the YouTube live chat to ensure compliance with the WCEU Code of Conduct, as well as to highlight any questions, comments and suggestions to the hosts.
Please comment below if you are able to help with YouTube live chat moderation.
You can find a copy of the WordCampWordCamp 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. Europe Online 2020 here: https://2020.europe.wordcamp.org/code-of-conduct/

Via Trac (coding working group):
You DO need to register an account with WordPress.orgWordPress.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/ in order to comment on Trac tickets.

Via GitHub (coding working group):
You DO need to register an account with GitHub in order to create / comment on issues or to create / comment on Pull Requests (PRs).

On the day:

Coding working group:

13:00 – 16:00 UTC (coding working group)
Garrett will be available on Slack during this time.

The coding working group will participate via Slack, Core Trac and GitHub.
@garrett-eclipse is going through the list of privacy-related tickets to mark them with the “good first 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.tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) where applicable.
For the more adventurous, there is the option to contribute to “help wanted” tickets for the next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope. (WordPress 5.5.).
An overview of current privacy tickets can be found here:
https://make.wordpress.org/core/components/privacy/

Non-coding working group:

The non-coding working group will have two two-hour sessions.

13:30 – 15:00 UTC
How to market without destroying user privacy (working title only).
Hosts: @carike and @jonoaldersonwp
During this session, we hope to identify online marketing best-practices that can be implemented even when users have opted-out (or not opted-in, depending on the jurisdiction) to being tracked with the view of creating actionable Trac tickets and / or to provide a resource for content marketing.
Topics will include:
– What is informed consent in a marketing context?
– Which digital marketing strategies were employed pre-the-ability-to-track-across-platforms and how may we able to adapt these?
– Which data points may still remain available for analytics if a user opts out of / does not opt in to the collection of their PPI.
Jono is “special ops” at Yoast SEO and we are very excited to have him participate.

16:00 – 18:00 UTC
A case study in the application of the Privacy Workflow Document and the Disclosures and Permissions (DPT) tabs.
Hosts: @carike and @pepe
In this session, we will be attempting to harmonize the Privacy Workflow Document and the Disclosures and Permissions (DPT) tabs and apply them practically to the WP Job Manager 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.
The desired outcome for this session is an action plan for an education drive among plugin and theme authors regarding the proposed disclosures.json file.
Pepe has previously presented at WordCamp, is very involved with the #core-privacy team and was helped to create the draft Privacy Workflow Document. His insight will be invaluable to this session.

License:

We will be using the Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license for the non-coding work group:
https://creativecommons.org/licenses/by-sa/4.0/legalcode

Contributions to the WordPress.org code are licensed in terms of the General Public License (GPLGPL GNU General Public License. Also see copyright license.) version 2 or later:
https://www.gnu.org/licenses/old-licenses/gpl-2.0.html

Slack logs:

You can view the Slack logs here:
https://wordpress.slack.com/archives/C9695RJBW/p1589396619341400
In order to view the logs, you will first need a WordPress.org account: https://login.wordpress.org/register
You will then need to register a Slack account: https://make.wordpress.org/chat/

Change log:
14 May 2020 at 14:15 UTC – @carike added GitHub information.
14 May 2020 at 17:45 UTC – @carike updated formatting in the Slack links.
16 May 2020 at 11:35 UTC – @carike switched out the non-coding session starting at 16:00 UTC, as Pepe has agreed to co-host.
18 May 2020 at 18:05 UTC – @carike added the times Garrett will be available on Contributor Day.
1 June 2020 at 13:55 UTC – @carike changed the start time for the first non-coding session in order to accommodate the WCEU introductions.
3 June 2020 at 19:40 UTC – @carike added details for the workgroup sessions and removed the third session.

#contributor-day, #privacy, #wceu-2020, #wordcamp-europe-online-2020

Editor Chat Summary: 13th May, 2020

This post summarizes the latest weekly Editor meeting (agenda, slack transcript). This meeting was held in the #core-editor 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 on Wednesday, May 13, 2020,14:00 UTC and was moderated by @andraganescu.

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.1.0

Gutenberg 8.1 RC was released on May 11th and is on track for a final 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.. 8.1 is focused on performance improvements, 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 multiple enhancements around several areas of the editor and the experimental screens/features. Outside of those focuses, there are also new features like new transforms, pattern search, and a new testimonials pattern.

Weekly Priorities

There was limited discussion on weekly and monthly priorities@andraganescu noted that the new navigation menuNavigation Menu A theme feature introduced with Version 3.0. WordPress includes an easy to use mechanism for giving various control options to get users to click from one place to another on a site. screen is coming together! Overall though, Full Sitesite (versus network, blog) Editing (FSE) is a major focus right now and can be followed here with the overall plan shared here.

Task Coordination

Note: Anyone reading this summary outside of the meeting, please drop a comment in the post summary, if you can/want to help with something.

@nosolosw

  • Main focus has been “Global Styles”. Currently, iterating on some framework tasks that need to be to unlock before resuming work on the UIUI User interface. This will be the focus for this week too.

@aduth

  • Working on some documentation and framework-level improvements, largely summarized in this slack convo.
  • Refreshing and splitting off work around renaming 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. categories.
  • Next up, continuing work on renaming block categories plus follow-up work around block context.

@youknowriad

  • Did two zoom chats to help contributors (one in #core-editor, one in French WordPress slack).
  • Trying to land categories support for patterns.

@nrqsnchz

@retrofox

  • Made progress in the Tips approach. It’s now possible to register tips defining the scope, descriptions, and other parameters.

@earnjam

  • Handling some PR reviews to help with triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. starting with the list of non-draft PRs with no review, less than 2 comments, and sorted by least recently updated to try to find anything that has slipped through the cracks.

@mapk

  • Spent time triaging issues.
  • Search block enhancements.

@itsjonq

  • Continuing to add features to Cover block via new control UIs (“Design Tools”). In doing so, also building a set of incredibly robust and feature rich control primitives (e.g. Input).
  • Longer termer goal would be to (hopefully) refactor/replace existing controls within Gutenberg with these ones. These components would of course be available for block/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 as well, enriching the UI experience of the Gutenberg ecosystem as a whole.

@vindl

  • Working on allowing extensions/replacements of editor close button which is part of this issue. It’s already merged for the site editor, and now I’m looking to expand it to the post editor too.
  • After the above work wraps up, will return to site editor UI tasks

@michael-arestad

  • Working on template part creation/manipulation design patterns. Right now, exploring how they might work as sections. This could be really slick when building templates.
  • Continuing on this path this week and will likely spin up some zooms if anyone wants to help or just watch! Links will be shared in #design.

@sageshilling

  • Working on the image and gallery blocks.

@andraganescu

  • Working on the navigation screen– just merged menu location management.
  • Will continue to work on various issues on this project for the next week.

@zieladam

Working on the experimental navigation screen, in particular:

Open floor

Do we instead of listing packages and versions, need to list components and versions? Raised by @paaljoachim.

This discussion point was raised in reaction to a comment from @clorith in this trac ticket on adding Gutenberg plugin version information to the Site Health section. Right now, this tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. issue needs feedback to keep the issue moving. It was agreed that there’s no easy solution to this partially because WordPress versions includes features and bug fixes of various versions of Gutenberg. This makes handling bug reports tricky for example.

Next step: Taking the discussion back to the track ticket!

Do we need to apply a max height for the style placeholders in the inspector? Raised by @munirkamal.

The problem right now is that placeholders need to have a preview so if the block is quite large the the preview is too. @matveb chimed in to say that previews are loading example content now so this decision is up to the block author. However, if an example is not provided it falls back to actual block content which is where a max-height could be useful.

Next step: A “Needs Design” Label was added to the issue for design to explore further.

What time and day would work for the discussion about full-site editing and the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. customize component? Raised by @dlh.

The original proposed date and time was 20:00 UTC on May 25th but this time may not work well for the people working on Full Site Editing. @youknowriad suggested meeting more around 15UTC/16UTC but wants to hear from others. Tied to this, @aduth noted that May 25th is Memorial Day in the United States which

Next step: If you’re interested in attending this meeting, please share in the comments below what time might work best. Notes will be taken and posted either way if you can’t 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). it.

Can we add a block ID to each block that is unique and stable to help connect server data to client data? Raised by @sageshilling.

This came up as part of work done on the image and gallery blocks (full context here). There have been various discussions about this historically in the early days of Gutenberg. These discussions always concluded that while there is a need for this from time to time we don’t want to pollute markup and/or we don’t want to keep two separate things in sync. Before discussing anything technically, it was agreed that a case needs to be made for why it should go in core and why extension-based solutions are not apt.

Next step: @sageshilling will collect use cases and details in a post 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. to propose this idea.

#meeting-notes, #core-editor, #editor, #gutenberg

CSS Chat Agenda: 14th May…

CSSCSS Cascading Style Sheets. Chat Agenda: 14th May 2020

This is the agenda for the upcoming CSS meeting scheduled for Thursday, May 14, 2020, 5:00 PM EDT.

This meeting will be held in the #core-css channel in the Making 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/..

If there’s any topic you’d like to discuss, please leave a comment below!

#agenda, #core-css

Auto-updates feature meeting summary: May 12, 2020

These are the weekly notes for the WP Auto-updates team meeting that happened on Tuesday May 12, 2020. You can read the full transcript on the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-auto-updates 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.

Reminder, WP Auto-updates Feature PluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. is developed on GitHub and is available for testing on WordPress.org plugins repository.

Update on core 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.

@pbiron is in charge of the core patch. It should be ready around the middle of this week. Paul asked whether it’s better to do a pull request against wordpress-develop 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/ repository or a diff file on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress..

@azaozz answered both would work, and have different pluses and minuses:

  • Pull requests can be reviewed in inline comments, but are harder to modify by different people.
  • A diff file would need to be applied to a svn checkout before testing, but easier to iterate (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). new diffs)

Paul will send a diff file.

WP auto-updates version 0.8.0

Here are the expected steps for the core merge:

  1. Publish the diff file on the related Trac ticketticket Created for both bug reports and feature development on the bug tracker. (#50052)
  2. After merge details are known, update Pull request #123 – Self-deactivate the plugin after the functionality has been merged to core
  3. 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. WP Auto-updates version 0.8
  4. Commit the Trac diff file to WordPress Core

@azaozz noted that releasing version 0.8 after the diff is available on Trac is needed to make sure 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 can self deactivate once the diff file is merged into WordPress core. The check in version 0.7 doesn’t actually work with the patch, because the name of the function it is checking changed in the patch

The plugin’s options should also be deleted from WordPress installs once the plugin is uninstalled by sites owners. @audrasjb opened pull request #125 to handle that.

The team noted the feature plugin reached 900+ active installs. 77% are running version 0.7, 12% are running version 0.6 and 11% are running versions 0.6.0 or less.

@whyisjake also implemented prettier on the plugin. It allows to run CSSCSS Cascading Style Sheets./JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. lint check, using npm test , and to fix linting issues using ESLint --fix option.

Open floor

@azaozz shared some thoughts about keeping some stats on successful/failed autoupdates, on the WordPress.orgWordPress.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/ 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. side. It’s not a blockerblocker A bug which is so severe that it blocks a release. for merging and can be added later. The idea is to potentially have anonymous/aggregated stats per plugin/theme. This is also related to the Tide project, which can use those stats to determine how “safe” an update may be.

@audrasjb asked if it’s directly related to this feature or if it should be handled in a separate ticket/project. For @azaozz, it is part of plugins and themes auto-updates, but it can be a separate Trac ticket.

@pbiron asked if we were talking about stats on the results of auto-updates, or about user preferences for what should be auto-updated (since whether an auto-update is attempted can be controlled by other plugins, such as Easy Updates Manager, etc). Andrew answered that it may be both.

@audrasjb asked what would be the main benefit for the end user? Having prompts to alert on “not recommended” updates? @azaozz doesn’t think it would be a direct communication but an auto-update may be eventually stopped/postponed if there are many failures.

@apedog wanted to mention a version-rollback feature for plugins. For them, it would become relevant as more installations start using WP Auto-updates feature plugin. @audrasjb answered it should eventually be introduced independently of auto-updates feature as it’s not only related to this type of updates mechanism. @apedog pointed out that breakage occurring from a manual update gives the user immediate feedback. An over-night auto-update (especially if multiple plugins/themes were updated) could make debugging much harder. @audrasjb added that the best way to move this independent project forward is to open a ticket on Trac if it doesn’t exists yet. @sergeybiryukov added that WP Core do perform a rollback if a background core update fails (enabled for minor versions by default), that might be helpful when looking into implementing this for plugins and themes too.

@apedog also asked whether WP Auto-updates log the previous version vs new version? For example, for a user encountering breakage from an auto-update. Sitesite (versus network, blog) breakage can occur even on successful updates – simply due to conflictconflict A conflict occurs when a patch changes code that was modified after the patch was created. These patches are considered stale, and will require a refresh of the changes before it can be applied, or the conflicts will need to be resolved.. @audrasjb answered there is no such log mechanism in core, even for manual updates.

@pbiron asked @audrasjb if Pull request 121 – Add help tabs on update-core, plugins, and themes admin screens is going to be ready on time for version 0.8.0. @audrasjb is on it, but it will probably needs copy review.

The team agreed Help Tabs will be handled separately from the initial core patch, to give it time for copy review.

#auto-update, #core-auto-updates, #feature-plugins, #feature-projects, #feature-autoupdates