Tag Archives: core

David Baumwald 9:50 pm on October 9, 2019
Tags: , core, ,   

Dev Chat: 10/9/2019

@davidbaumwald served as facilitator and note taker for this week’s chat held in the #core Slack channel. To view the chat from the beginning, click on this Slack Archive.

Announcements

WordPress version 5.3 Beta 3 was released on Tuesday. Congratulations to everyone involved in inching 5.3 closer to the finish line.

5.3 Updates

With 5.3 Beta 3 now release, focus turns to Release Candidate 1(RC1) is next on the schedule just a few days from now. A “soft string freeze” is now in effect.

@francina called for volunteers for next week’s RC1 release session. Both Mission Control(MC) and a Core Committer will be required. @azaozz and @sergeybiryukov raised their hands.

@karmatosed provided a quick update on 5.3’s About page, saying that everything is on track and copy is being finalized.

@jeffpaul inquired about the progress on compilation of Dev Notes for 5.3. @justinahinon pointed to a Google Sheet that he’s using to organize them and coordinate volunteer authors.

This discussion led to a call for more volunteers and ticket owners to draft Dev Notes. @desrosj mentioned that he’s “… started a page for the handbook collecting the learnings from the last three releases for this.”

@ianbelanger brought a Twenty Twenty update to the group. A PR has been opened to address WPCS violations in the Beta Twenty Twenty patch, and a call for testing was announced. @karmatosed added that testing on mobile is a great help to the team.

Open Floor

@azaozz mentioned that there are, as of writing, only 37 open tickets in the 5.3 milestone, and everything should be closed out as RC1 is released. This was a great reminder of the tremendous work done by Core Contributors during the course of the 5.3 cycle, as over 350 tickets were initially open when the cycle was kicked off!

These notes were drafted by @davidbaumwald and proofread by @justinahinon.

#5-3, #dev-chat, #summary

Anthony Burchell 2:37 pm on September 19, 2019
Tags: core, , , ,   

Media Meeting Recap – September 19, 2019

The following is a summary of the weekly media component meeting that occurred on Thursday, September 19, 2019. Weekly media meetings are held every Thursday at 13:00 UTC. A full transcript can be found here in the #core-media room in the Make WordPress Slack.

Attendees: @anevins, @joemcgill , @FahimMurshed, @mikeschroder, @antpb, @afercia

Media Focus update: @mikeschroder has been hard at work on a 5.3 intro post. In it will be a focus on calling for testing.  Coming soon!

Add width and height attributes to <img> elements – https://github.com/WordPress/gutenberg/issues/6652
Discussion is taking place in this Slack thread. Maintainers in attendance all agreed that this would be great to be considered a bug and a potential impactful improvement to the editor experience. @joemcgill said, “Realistically, I think a first step is just adding a proof of concept that modifies the save attribute of the image block so the h/w attributes are always saved and then see what breaks.”

5.3 Ticket Triage

#47120 – Media modals: Upload errors and field information are not associated with their control : @antpb has taken ownership of the ticket and will investigate how we would best inject the recommended code into the various buttons/views.

#47137 – Insufficient form semantics : This issue was split into two issues (the other below) to allow the overall problem to improve in pieces. Ownership for this one is needed. It’s a bit of a tough issue that no one has yet to see an immediate solution.

#48028 – Media Library ‘featured image’ dialogue missing link text that describes ‘opens in new tab’. – @afercia said “I think there’s the need to check how editState is implemented in the post frame and what is intended for. That implementation completely lacks in other frames. I think this is for historical reasons because the post frame was the only frame supposed to be used in the “edit post” context.” and @joemcgill responded “The classic editor used the Post frame in most places, rather than the Select frame. Now that most of Gutenberg is using the Select frame, some odd bits aren’t working the same—just like that other featured image bug you (@antpb) just fixed” @antpb assigned the issue to himself given his recent exposure to the featured image frames. A github issue is needed also to track this change in the Gutenberg plugin @antpb is working on that. More to come!

#47144 – Text inadvertently rendered by assistive technologies – Was mentioned at end of meeting but discussion was not able to be had. This issue is in need of ownership for the 5.3 release.

#47611 – Media views: hide the “file upload button” from assistive technologies – Was mentioned at end of meeting but discussion was not able to be had. This issue is in need of ownership for the 5.3 release.

Bug Scrubs next week!

@mikeschroder and @antpb have offered to lead two bug scrubs in #core-media next week to find ownership for the remaining accessibility issues planned for the 5.3 milestone:

Feedback

If you have any feedback on the above, please feel free to leave a comment, join in #core-media for a chat, or attend the next meeting on September 26, 2019 at 1300UTC!

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

Mary Baum 6:42 pm on September 14, 2019
Tags: , core, , twenty-twenty   

Dev chat summary: September 11

Announcements

@Francina asked the group for announcements, and @jbaudras highlighted this Make/Design post:

https://make.wordpress.org/design/2019/09/06/discussion-higher-contrast-form-fields-and-buttons/
There are 3 tickets waiting for final decision in order to land in WP 5.3

Then she added two more:

Make WordPress Core
Introducing Twenty Twenty
The Block Editor will soon celebrate its first birthday in Core and with every update it grows more capable. The promise of the block editor is to give users the freedom to design and structure the… https://make.wordpress.org/core/2019/09/05/defining-content-block-areas/

Make WordPress Core
Defining Content–Block Areas
One of the major projects from this year’s focuses is to expand the block editor beyond the content area and into other parts of the site. This included, so far, explorations to bring blocks into o…
Sep 5th

Media component maintainer Anthony Burchell told the group he’s been sharing that link around and getting great feedback.
@francina praised the video in the post. She added, “Personally I’m looking forward to seeing all the possibilities that blocks are giving us!”
After @afercia mentioned some accessibility feedback, @francina moved the discussion forward, inviting everyone (you too, dear reader!) to leave comments on the relevant posts.

Upcoming releases: 5.3

Bugscrubs: @davidb opened with this news: we still had 314 tickets milestoned for 5.3.

The discussion that followed surfaced a general preference to focus on enhancements and features between now and Beta 1, when features freeze, and on bug fixes between Beta 1 and release.

As of devchat, 120 features and enhancements are milestoned for 5.3 on Trac.

@davidb and the focus leads will do a bit of promoting to get more folks to come to bugscrubs.
(Ed. note: Beta 1 should land September 23; final release is slated for November 12.

Default theme focus lead @ianbelanger reported in on the next default theme, Twenty Twenty. has a weekly meeting, on Mondays at 19:00 UTC, and has opened its Github repo to contributors.

Marketing has nominated @miker as its focus lead for the release. It’s started meeting on Fridays at 16:00 in the Marketing channel, to work on copy for the About page. @marybaum and @miker asked for input from maintainers on enhancements they think are important.

In Docs, we have one dev note published and two more under review. Lead @justinahinon is going to all the component meetings, to let their teams know the Docs team is around to help with their notes.

Media: @mikeschroder is the 5.3 focus lead.

Next bugscrub is Thursday at 05:00 UTC. Check the rest of the schedule at https://make.wordpress.org/core/2019/08/27/bug-scrub-schedule-for-5-3/

Maintainers

@antpb reported in on Media, which is also taking the lead on APAC-friendly meeting times. As he said:

“This devchat does not align with normal hours for him, so I will help with updates here. Discussion about the scope of the 5.3 Media will take place tomorrow at 13:00 UTC (agenda to come soon in the #core-media room). I anticipate the scope to largely focus on a11y and image handling improvements. I know of a few on my plate currently that will also fit in line with the release focus of UI improvements.”

@clorith and @jeffpaul will work to get scrubs posted on WordPress 5.3 Development Cycle – Make WordPress Core.

@pierregordon volunteered to become a maintainer for the External Libraries component.

And there was more discussion on getting people to come to bugscrubs.

21:00

As we hit the hour, folks who needed to do other things (like sleep, eat or work) signed off. But the chat was still lively enough that several people stayed on tolerant more about exactly what a component maintainer’s role includes.

@jbaudras referred to this post:

These maintainers are vital to keeping WordPress development running as smoothly as possible. They triage new tickets, look after existing ones, spearhead or mentor tasks, pitch new ideas, curate roadmaps, and provide feedback to other contributors. Longtime maintainers with a deep understanding of particular areas of core are always seeking to mentor others to impart their knowledge.

From https://make.wordpress.org/core/components/ (edited)

Devchat ended at ten minutes past the hour.

#5-3, #core, #devchat, #twenty-twenty

Anthony Burchell 3:59 pm on September 9, 2019
Tags: core, , , ,   

Media Meeting Recap – September 5, 2019

The following is a summary of the weekly media component meeting that occurred on Thursday, September 5, 2019. Weekly media meetings are held every Thursday at 13:00 UTC. A full transcript can be found here in the #core-media room in the Make WordPress Slack.

Attendees: @anevins, @sergeybiryukov, @pstonier , @afercia, @francina, @mikeschroder

Media Focus Lead for 5.3

Much like the 5.0 release, 5.3 will have many designated release leads around each focus/component in the project. 5.3 is right around the corner and now is the time for a decision to be made on a release lead representing the Media component. Previously @antpb had offered to take on the role if no others were interested. In this weeks Media meeting, a volunteer emerged! @mikeschroder has graciously offered to take on this role. Thanks Mike! Mike is in the JST time zone. This brings an awesome opportunity to have global representation in the team. @antpb has offered to help with relaying information or representing where time zones do not conveniently meet for Mike.

5.3 Ticket Triage

#47135 – Drag and drop functionality unavailable to keyboard or touchscreen — It was determined by the team that this issue exists more globally in meta boxes. It was deemed appropriate to document the information from the Media focused instance of this in an existing ticket on the issue: #39074 No method to move meta boxes using keyboard which was also given the keyword wpcampus-report for tracking purposes.

#47137 Insuficient form semantics – @anevins asked “Is there a technical reason why there isn’t a form element being used around that attachments browser code? That would defeat all of the remediation advice.” @afercia had these recommendations: “Ideally it should be a form because that helps in establishing semantic relationships. However, the sidebar is not rendered in all the views, so including the select area, the attachments list and the sidebar within one form might be a bit complicated.
The list of attachments is perceived as a list of checkboxes so it makes sense to wrap it within a fieldset + legend. I’d tend to think it would need more work in the future because yes, it’s a group of checkboxes but it actually works like a mini-application with custom interaction. I’d say fieldset + legend would help, for now.”

Triage on unanswered tickets continued after the meeting closed, and can be followed here.

Feedback

If you have any feedback on the above, please feel free to leave a comment, join in #core-media for a chat, or attend the next meeting on September 12, 2019 at 1300UTC!

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

Josepha 8:46 pm on September 4, 2019
Tags: , , core, ,   

Dev Chat Summary: September 4

@audrasjb was our chat leader today and did an excellent job as usual. (backscroll)

Announcements

JB shared some posts that are currently open for discussion, feedback, or volunteering.

  • About page design: https://make.wordpress.org/design/2019/08/28/discussion-about-the-about-page/
  • New feature plugin proposal: https://make.wordpress.org/core/2019/09/04/feature-plugin-proposal-privacy-data-request-form/

Upcoming Release(s) Update

  • WordPress 5.2.3
    • This is due out today!
    • Right after devchat the plan is to begin the final packaging and release process.
  • WordPress 5.3 has a new batch of focus leads!
    • @miker joined the team as Marketing Focus Lead
    • @ianbelanger joined the team as Default Theme Wrangler
    • @andersnoren joined the team as Default Theme Designer
  • WordPress 5.3 also has an updated timeline posted here: https://make.wordpress.org/core/5-3/
  • All bug scrubs are listed here: https://make.wordpress.org/core/2019/08/27/bug-scrub-schedule-for-5-3/ . The next general bug scrub is Sept 5, 2019 at 14:00 UTC in #core channel.

Call for Component Maintainers

  • @azaozz has put up a challenge to his fellow maintainers for 5.3 (and hopefully beyond!) https://make.wordpress.org/core/2019/08/30/component-maintainers-in-5-3/
  • @chanthaboune shared that the maintainers of the default themes are due for a change
    • @ianbelanger and @williampatton raised their hands to help with that transition.
    • @clorith suggested it’s time to have a clearer support plan for working with default themes

Open Floor

  • If anyone is local to the Orlando area, there’s a community event coming up. https://www.meetup.com/WordPress-Orlando/events/263847409/

Important WP5.3 Dates

  • September 23: Beta 1 (begin writing Dev Notes and About page, and last chance to merge feature projects)
  • September 30: Beta 2 (continue writing Dev Notes and About page)
  • October 7: Beta 3 (continue writing Dev Notes and About page, and soft string freeze)
  • October 15: Release candidate 1 (publish Field Guide with Dev Notes, commit About page, begin drafting release post, and hard string freeze)
  • October 22: Release candidate 2 (update About page images, and continue drafting release post) (also @audrasjb‘s birthday!)
  • October 29: Release candidate 3 (update About page images, and continue drafting release post)
  • November 5: Release candidate 4 (if needed)
  • November 11: Dry run for release of WordPress 5.3 and 24 hour code freeze.
  • November 12: Release Day!

#devchat #summary #5-2-3 #5-3

Mike Schroder 2:31 pm on September 3, 2019
Tags: core, , , ,   

Media Meeting Recap – August 29, 2019

The following is a summary of the weekly media component meeting that occurred on Thursday, August 29, 2019. Weekly media meetings are held every Thursday at 13:00 UTC. A full transcript can be found here in the #core-media room in the Make WordPress Slack.

Attendees: @joemcgill, @anevins, @desrosj, @horttcore, @paaljoachim, @mikeschroder

5.3 Tickets

@azaozz requested review on the latest patches in #43524, #47873, #47872, #32437. He plans to commit them before the end of the week.

Chatting About Sizes

@pierlo asked for a discussion on #43524, which is about adding an additional image size.

Folks seemed to agree that it makes sense to add another one, and that it’d be great if sizes could be backfilled in the future, but that’s likely not for 5.3.

Connected to that, there was a conversation about the direction WordPress could take with sizes in 5.4 and beyond. Things discussed included a feature like add_image_size for attachments, delivering srcset sizes based on file size, and resizing after theme change.

If that sounds interesting, you can read the whole discussion here.

Ticket Triage

  • #47215: The media that is “Unattached” is different in list mode vs grid mode — @desrosj was able to reproduce, and is going to do a bit more testing.
  • #47215: The media that is “Unattached” is different in list mode vs grid mode — @joemcgill notes that this is an intentional behavior, meant to avoid clutter in the media library due to site icons or headers. This may need to be revisited.
  • #47364: Docs: Standardise the description for image size parameters — @joemcgill agreed to review the ticket and clarify the goals.
  • #47444: Deprecate the caption field from the media modal — Folks present noted use-cases for this, and @joemcgill to leave a comment.

Triage on unanswered tickets continued after the meeting closed, and can be followed here.

Feedback

If you have any feedback on the above, please feel free to leave a comment, join in #core-media for a chat, or attend the next meeting on September 5, 2019 at 1300UTC!

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

Andrew Ozz 12:55 am on August 30, 2019
Tags: , , , core   

Component Maintainers in 5.3

On the heels of APAC Triage and Bug Scrub Sessions and Bug Scrub Schedule for 5.3, thanks @pento and @davidbaumwald, I’d like to propose something a little bit different.

The WordPress 5.3 release is shaping up to be substantial. There are tons of fixes and improvements in Gutenberg, for both users and developers. Even if 5.3 only included the Gutenberg update, it would have been a very nice, very desirable upgrade.

There is more to this release! Currently there are 632 tickets on the 5.3 milestone on Trac, both open and closed. A few smaller new features and user facing enhancements are in the works, and a lot of bugfixes and under-the-hood improvements are coming up or already done.

I’d like to propose that component maintainers take more “charge” of the tickets in their components. There is a general expectation that if you moved a ticket to a milestone you are the “lead” for that ticket and will see it through to completion, or move it to a future milestone if not feasible. But that shouldn’t stop component maintainers from helping to keep those tickets moving.

With the scheduled bug scrubs, and the per-component bug scrubs that usually happen at the components’ meetings, the 329 open tickets aren’t that big of a mountain. 

The 5.3 Challenge

During the next few weeks (by beta-1 scheduled for 23 September) join me in making sure all 5.3 tickets in our components will either be resolved or moved to a future milestone. And if there are any hurdles leave a comment on the ticket briefly outlining the difficulties and include a resolution timeline.

It would also be helpful if during this time all component maintainers do a short, concise update about their component on the weekly core dev chats. These updates would typically include the number of open 5.3 tickets and whether there are any difficulties with any of them. This will help people know where help is most needed, especially any newer contributors who are having trouble deciding where to spend their time.

Also, we have a Docs Wrangler for our release! After 5.3.0-beta-1 is out, it would be great if component maintainers review all changes to their component (if not already reviewed), then, if possible, help @justinahinon with writing or editing dev. notes. There are currently 301 fixes and enhancements committed to the 5.3 milestone and they will need documentation.

The proposed change for component maintainers is to act early, before beta-1, and to regularly make updates and bring any difficulties to the core dev chat.

#5-3, #bug-scrub, #components, #core

Francesca Marano 5:03 pm on August 28, 2019
Tags: , , , core,   

Dev Chat Agenda for August 28th 2019 (5.3 week 2)

Here is the agenda for the weekly meeting happening later today: Wednesday, August 28, 2019, 20:00 UTC. Please share any items you’d like to include in the comments below!

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

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

#5-3, #5-2-3, #agenda, #core, #devchat

Gary Pendergast 2:11 am on August 26, 2019
Tags: APAC, , core, , ,   

APAC Triage and Bug Scrub Sessions

Living in APAC timezones can be difficult. From waking up at 3am for meetings, to flying 20+ for WCUS or WCEU (WCAsia is coming to fix that!), to hearing “what’s it like living in the future?” jokes for the millionth time. One thing that shouldn’t be hard is contributing to WordPress, and it’s time to make that even easier, with APAC-friendly triage and bug scrub sessions.

You may have already seen Gutenberg meetings happening every second week for the last few months, but starting Thursday at UTC 0600, we’ll alternate each week between working on WordPress Core, and Gutenberg! This week, join in the fun in the #core Slack channel for a WordPress Core bug scrub. Next week, the party will be in the #core-editor Slack channel, for a Gutenberg bug scrub. 🎉

The meeting lead will pick a report to work through, but if there are particular issues you’d like to get more eyes on, or you have a patch/PR that you’d like reviewed, this is the place to bring it up!

#apac, #bug-scrub, #core, #core-editor, #gutenberg, #triage

Joe McGill 8:18 pm on August 23, 2019
Tags: core, , , ,   

Media Meeting Recap – August 23, 2019

The following is a summary of the weekly media component meeting that occurred on Thursday, August 23, 2019. Weekly media meetings are held every Thursday at 13:00 UTC. A full transcript can be found here in the #core-media room in the Make WordPress Slack.

Attendees: @joemcgill, @anevins, @pbiron, @desrosj

5.2.3 Media Tickets

All relevant tickets have been closed. 🎉 Props @sergeybiryukov on back-porting bug fixes.

5.3.0 Release Media Lead

Following up on the 5.3.0 Release Schedule and Scope, we were asked to identify a Media release lead. To coordinate media related tickets.

  • @antpb has expressed interest in doing this again, but wanted to open up the opportunity to anyone else interested.
  • @joemcgill wondered if this role was redundant with @azaozz role as Core technical lead, since most of the priority Media items are ones he is already working on.

If you’re interested in volunteering for this role, feel free to comment here, in #core-media, or DM @joemcgill or @antpb directly in Slack.

5.3.0 Tickets

  • #47156: Consider a way to clear the wp.a11y.speak() live regions – @anevins followed up and noted that the Drupal a11y team have a similar issue and this might be a limitation of aria-live regions, generally. The plan is to follow up with the #core-accessibility team this week.
  • #44581: users without ‘edit_posts’ capability never get informed that their uploads succeed – @pbiron asked that this get moved into the 5.3 release for review.
  • #47872: Try to create image sub-sizes again when uploading fails with a PHP fatal error – @azaozz asked for review, noting that testing requires the client to re-try creation of image sub-sizes after uploading an image and the server “crashes” with HTTP 500 error.
  • #40439: Save progress of intermediate image creation after upload – @azaozz believes this is complete, but would like more testing before closing.
  • #47873: Introduce handling of “Big Images” – @azaozz added as a new enhancement. Feedback appreciated.
  • #40175: Upload Validation / MIME Handling – @joemcgill noted that this stalled out after 5.2 and with the focus for 5.3 being on improving handling of large image uploads, would need to be punted to a future release unless someone else wants to pick it up for 5.3.
  • #35725: Add mime-type for Webp – @joemcgill doesn’t think #40175 should be a blocker for this ticket, but wasn’t sure if it should be in core without full browser support.

#core, #media, #summary