David Baumwald 4:22 pm on April 29, 2020
Tags: , , , ,   

Dev Chat Agenda for April 29, 2020

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

Announcements

If anyone has any announcement to make, now is the time!

Upcoming Releases

Components Check-in

  • News from components
  • Components that need help/Orphaned components
  • Cross-component collaboration

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-4-1, #5-5, #5-6, #agenda, #devchat

Lara Schenck 4:03 pm on April 29, 2020
Tags: ,   

Chat Summary: 23th April 2020…

Chat Summary: 23th April 2020

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

I (@notlaura) facilitated the meeting.

CSS audit updates

No CSS audit updates this week.

Color Scheming status update

I proposed having this as a recurring agenda item since it is a long term and far reaching initiative – meeting attendees were in agreement that it should be.

@kburgoine created the ticket “Replace wp-admin color schemes with CSS custom properties” #49930 and mentioned there hasn’t been much traction. We discussed possible next steps for the ticket. @ryelle mentioned a need to break down the need for color schemes, and @kburgoine mentioned researching and outline some potential approaches, perhaps with proof of concept Codepens and some prototypes.

@ryelle indicated that the root issue might be that we need a different approach to color schemes and that custom properties might be part of the solution, but not the whole thing. There are currently has 206 unique colors in wp-admin, and the current implementation of color schemes requires any overriding of default colors to be just as specific. To summarize this message, standardizing colors and switching them all to custom properties would remove the need for color scheme authors to write new CSS to override the default colors. So, specificity resulting from the current color scheme handling is an issue. @isabel_brison suggested that a ticket to track the current issues with color schemes would be useful.

@netsassprodsr asked about IE support, and @isabel_brison mentioned that we would need some sort of flagging / indication to users what color schemes are IE friendly.

I outlined a couple of next steps for the color scheme ticket based on the conversation:
1. research/list some problems that are caused due to the current color scheme implementation
2. research/list some approaches for colors schemes in the ticket

@ryelle offered to take on #1 and to create a ticket for it if one doesn’t already exist.

Open Floor

@isabel_brison has created a label in the Gutenberg repo for CSS issues – very cool! This will hopefully be helpful for folks who want to contribute to Gutenberg with their CSS skills.

That was all for this week! @isabel_brison will be filling in for me and facilitating the next CSS chat on 30 April.

#summary, #core-css

Francesca Marano 2:20 pm on April 29, 2020
Tags: , , ,   

Dev Chat Agenda for April 29, 2020

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

Announcements

If anyone has any announcement to make, now is the time!

Upcoming Releases

  • Work continues on WordPress 5.4.1 lead by @whyisjake. WordPress 5.4.1 RC1 is out.
  • All the maintainers have been pinged about 5.5. The information has been collected and expect a further ping for a status update so the schedule for 5.5 can be finalised.

Highlighted/Need Feedback Blog Posts

Components Check-in

  • News from components
  • Components that need help/Orphaned components
  • Cross-component collaboration

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-4-1, #5-5-2, #agenda, #devchat

Paal Joachim Romdahl 11:58 am on April 28, 2020  

Editor Chat Agenda: 29th April, 2020

Facilitator and notetaker: @jorgefilipecosta

This is the agenda for the weekly editor chat scheduled for 2020-04-29 14:00 UTC.

This meeting is held in the #core-editor channel in the Making WordPress Slack.

If you have anything to share for the Task Coordination section, please leave it as a comment on this post.

If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.

#agenda, #core-editor, #editor-chat

Jb Audras 4:51 pm on April 24, 2020
Tags: ,   

WordPress 5.4.1 RC1

WordPress 5.4.1 Release Candidate 1 (RC1) is now available for testing!

There are two ways to test the WordPress 5.4.1 release candidate: try the WordPress Beta Tester plugin (you’ll want to select the point release nightlies option), or you can download the release candidate here (zip).

What’s in this release candidate?

5.4.1 Release Candidate 1 features 11 bug and regression fixes, as well as 6 bug fixes for the block editor. Here’s a detailed list:

  • #49838 – Accessibility: Fix the headings hierarchy on the Freedoms page
  • #49798 – Customize: Give the WordPress logo a white background for dark mode browsers
  • #49853 – Mail: Make the check for empty post title in wp-mail.php more resilient
  • #49753 – Media: Remove display: none; from the (visually hidden) <input type="file"> button used in Plupload to select files for uploading. Fixes selecting files in Edge <= 44 and iOS Safari
  • #49772 – Privacy: Support additional elements (table, ol, ul) in privacy policy guide new styling
  • #49802 – Privacy: Make the deprecated wp_get_user_request_data() function available on front end
  • #49645 – REST API: Fix revisions controller get_item permission check
  • #49648 – REST API: Fix _fields filtering of registered rest fields
  • #49824 – Site Health: Instantiation prevents use of some hooks by plugins
  • #49759 – Taxonomy: Un-deprecate category_link and tag_link filters
  • #49974 – Block Editor updates

What’s next?

Committers: The dev-reviewed workflow (double committer sign-off) still applies when making any changes to the 5.4 branch.

The official 5.4.1 release is still scheduled for Wednesday, April 29, 2020. Happy Testing!

#5-4-1, #minor-releases

Jorge Costa 1:47 pm on April 24, 2020
Tags: , ,   

JavaScript Chat Summary: Tuesday, April 21, 2020

Below is a summary of the discussion from this week’s JavaScript chat (agenda, Slack transcript).

Have a topic for discussion for the next meeting? Leave a suggested edit on next week’s agenda.

Package updates and type checking support

@aduth shared the following announcement:

There was a round of WordPress NPM packages updates published last week. These were the first to include first-party TypeScript types :tada: Unfortunately, there were some unforeseen conflicts with a few of them, and some had to be quickly backed out temporarily and will be republished later.

More about the issues can be found here: https://github.com/WordPress/gutenberg/pull/21613.

Including follow-up tasks: https://github.com/WordPress/gutenberg/pull/21613#issuecomment-615314861

@jonsurrell added that we conflicted with 3rd party types from DefinitelyTyped. In isolation, there was nothing strictly wrong with the new types. In the future, the DefinitelyTyped types would be replaced by packaged (1st party Gutenberg) types, but in the short term, it’s in everyone’s best interest to remain compatible.

The solution to remain compatible with DefinitelyTyped is not yet clear. @jonsurrell created the following issue to discuss it https://github.com/WordPress/gutenberg/issues/21767. Feel free to leave your thoughts there.

Ongoing WordPress packages tasks

@aduth collected and shared the following list of tasks happening around WordPress packages:

@adamsilverstein said that for the underscore to lodash work, the biggest win would be to remove the underscore dependency from the media library. @adamsilverstein volunteered to work on the task.

Regarding the on-demand installation of Puppeteer, @aduth demonstrated great excitement with the change. Saying it will reduce the installation time for new development environments pretty significantly, especially because it’s also part of the general-purpose wp-scripts. @aduth concluded this improvement in new setup time would be useful in contributor days.

#core-js, #javascript, #meeting-notes

Timi Wahalahti 9:52 am on April 24, 2020
Tags: ,   

X-post: WCEU Online 2020 Contributor Day update: times, registration, platforms and team video introductions

X-post from +make.wordpress.org/updates: WCEU Online 2020 Contributor Day update: times, registration, platforms and team video introductions

Timothy Jacobs 5:50 pm on April 23, 2020
Tags:   

REST API: Decision on Introducing a dashboard namespace

In Introduce a dashboard namespace the REST API team proposed introducing a dashboard namespace to house dashboard specific endpoints like Site Health and the Customizer. Based on the feedback received on the post, as well as in the #core-restapi slack channel, the REST API team has decided on giving major features their own namespace. For example, wp-site-health and wp-customize.

Many contributors felt that relegating these endpoints to a dashboard namespace did a disservice to the features and made them harder to discover. Additionally, it may suggest to third-party developers that these endpoints are strictly internal, even though the endpoints would be useful outside of WP-Admin.

The wp/$FEATURE/v1 pattern was suggested a number of times. However, using a wp-$FEATURE prefix allows us to maintain the recommended pattern of <prefix>/v<version>.

Namespaces are prefixed with wp so that plugin developers don’t have to worry that any namespace they pick could eventually be reappropriated by WordPress core.

For any future smaller endpoints that don’t need their own dedicated namespace, for instance Community Events, they’ll use the dashboard/v1 pattern.

#rest-api

Justin Ahinon 4:53 pm on April 23, 2020
Tags: , , ,   

Devchat meeting summary – April 22, 2020

The chat was led by @davidbaumwald based on this agenda.

The full meeting transcript is available on Slack.

Highlighted blog posts

@davidbaumwald shared some posts from the Make Core blog.

5.4 Retrospective – Call for feedback: the deadline is April 30 and everyone is welcome to leave a feedback.

Proposal: Core Team Rep Elections: the deadline for nominations and self-nominations is May 4.

We’re applying to Season of Docs: a new working group that needs help!

WordPress 5.5: Call for Tickets: the deadline is April 30.

Upcoming Releases

WordPress 5.4.1 Release Candidate 1 was supposed to be released yesterday Wednesday, but there were some miscommunication between Core team and Gutenberg team. The RC has then been pushed back to this Friday. The Gutenberg changes that are going to be included in the release are listed in this pull request. The milestone for this point release is also cleared.

@davidbaumwald reminded that for 5.5, all the maintainers have been pinged about potential features and focuses.  If you’re a component maintainer and haven’t replied yet, please do, so scope and schedule can be proposed.

He also said that work for 5.6 release, aka all-women release, continues. All the women that expressed interest have been contacted. @chanthaboune, @angelasjin, @cbringmann and @francina will work on phase 2: identifying missing roles and cohorts to organize the team that will ride along with 5.5.

Components Check-in

@francina has pinged #meta team about having a weekly scheduled post to check Components status; @dd32 expressed some concerns about the noise that it will create. @davidbaumwald suggested to move on with this for a three-month test.

@audrasjb gave an update about plugins and themes auto-update feature. The team released version 0.6.0 of the Feature Plugin yesterday Wednesday.

The Feature Plugin contains all the identified must-have features and the UI was reviewed by several teams. The team is now about to write the Core merge proposal post on Make/Core. More infos here.

Open Floor

@apedog asked a question about routing in WordPress Core. He stated that the WP class having $_SERVER hard-coded into it. And this would require re-writing the methods inside WP class, but without changing its functionality.

@clorith said that he’s generally against the bot idea for a general channel with lots of chatter, and the loss of potential input to backscroll. If it’s going to happen, it should be on Make/* somewhere for consistency and visibility.

@audrasjb pointed out to #16557, a long standing ticket raised by some people in the French WordPress community. It appears it would be a great SEO enhancement to provide proper filters on redirect_guess_404_permalink() function.

He milestoned the ticket to 5.5.0 and refreshed the existing patch against trunk after testing it. This still needs some unit tests, but before writing them, it would be nice to get a quick review on the current proposal.

@netpassprodsr called for review on #49832.

#5-4-1, #5-5, #5-6, #summary

Lara Schenck 9:58 pm on April 22, 2020
Tags: ,   

CSS Chat Agenda: 23nd April…

CSS Chat Agenda: 23nd April 2020

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

This meeting will be held in the #core-css channel in the Making WordPress Slack.

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

  • CSS audit status update
  • Color Scheming status update
  • Open floor

#agenda, #core-css