Tonya Mork 7:05 pm on December 21, 2020
Tags: ,   

Bug Scrub Schedule for 5.7

With 5.7 officially kicked off, time to schedule the 5.7 sessions. These 5.7 specific ticketticket Created for both bug reports and feature development on the bug tracker. scrubs will happen each week until the final release.

Early Scrubs:

Focus: early tickets, tickets that require more time or early testing.

Alpha Scrubs:

Focus: features and enhancements.

Beta Scrubs:

Focus: issues reported from the previous beta and defects.

RC Scrubs:

Focus: issues reported from the previous RC

Check this schedule often, as it will change to reflect the latest information.

APAC-friendly scrubs will be led by @lukecarbis.

What about recurring component scrubs and triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. sessions?

The above 5.7 scheduled 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. scrubs are separate and in addition.

For your reference, here are some of the recurring sessions:

  • Design Triage: Every Tuesday 14:00 UTC in the #design channel (for both coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and 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/).
  • 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) Scrub: Every Friday 14:00 UTC in the #accessibility channel.
  • APAC-friendly Scrub: Every Tuesday at 05:00 UTC in the #core channel. This scrub will continue during the cycle, alternating focus between core and editor.
  • Testing Scrub: Every Friday 13:30 UTC in the #core channel.

Want to lead a bug scrub?

Did you know that anyone can lead a bug scrub at anytime? Yes, you can!

How? 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 (@hellofromtonya) on 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/. and let me know the day and time you’re considering as well as the report or tickets you want to scrub.

Planning one that’s 5.7-focused? Awesome! We’ll add it to the schedule here. You’ll get well deserved props in the weekly Dev Chat, as well as in the #props Slack channel!

Where can you find tickets to scrub?

  • Report 5 provides a list of all open 5.7 tickets:
    • Use this list to focus on highest priority tickets first.
    • Use this list to focus on tickets that haven’t received love in a while.
  • Report 6 provides a list of open 5.7 tickets ordered by workflow.

Need a refresher on bug scrubs? Checkout Leading Bug Scrubs in the core handbook.

Questions?

Have a question, concern, or suggestion? Want to lead a bug scrub? Please leave a comment or reach out directly to me (@hellofromtonya) on slack.

#5-7, #bug-scrub

annezazu 8:16 pm on January 13, 2021
Tags: , ,   

Editor chat summary: Wednesday, 13 January 2021

This post summarizes the latest weekly Editor meeting (agenda, slack transcript), held in the #coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-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, 13 January 2021, 14:00 UTC.

WordPress 5.7

WordPress 5.7 is now underway with BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 due on 2 February 2021. You can help with this effort by jumping in on the following issues shared by @noisysocks:

https://github.com/WordPress/gutenberg/issues/24965
https://github.com/WordPress/gutenberg/issues/14744
https://github.com/WordPress/gutenberg/issues/24092
https://github.com/WordPress/gutenberg/issues/25983
https://github.com/WordPress/gutenberg/issues/23636

Finally, you can follow this Project board that tracks WordPress 5.7 “must-haves”. Please add issues to this board and/or reach out to (@noisysocks) if there is something you think needs to be included.

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/ 9.7 & 9.7.1

Gutenberg 9.7 & 9.7.1 were released over the last week. Highlights include drag & drop from the inserter for block patterns, updates to the reusable 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., and more.

Gutenberg 9.8 RC

As a reminder, Gutenberg 9.8 RC will be released this week to allow for a 1 week RC period before the stable release next week. Please use this as a chance to test the RC!

Monthly Plan & Key Project Updates

The monthly update containing the high-level items that Gutenberg contributors are focusing on for January are:

  • Global Styles
  • Block-based WidgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. Editor
  • Full Site Editing

For detailed plan check out monthly priorities post.

Full Site Editing Update from @ntsekouras

Testing/feedback/review on Query Pagination block with InnerBlocks
and feedback for possible use cases of a Query Title block would be fantastic. Any thoughts and help are really appreciated!

Global Styles Update from @jorgefilipecosta

The theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. mechanism was merged! There is a proposal for a save time theme.json escaping mechanism. The progress to integrate the font size picker new version advanced nicely and the PR should be merged soon.

Widgets & Navigation Update from @andraganescu

They are both back working in the main branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". after some foundational changes broke them.

Native Mobile Block Editor Update from @hypest

  • We added the ability to move blocks to top/bottom via long-pressing the block mover icons
  • Removed the info popup on start about the block editor being the new default as it’s been quite some time now that Gutenberg rolled out
  • Added block insertion E2E tests
  • Made progress on porting the Audio block

Work will continue on the audio block, the code block and prepare to work on the table block.

Help test full site editing

Today is the final day to respond to the very first call for testing for the FSE outreach program. Feedback is of course always welcomed and appreciated 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/. Expect a post this week on Make Test summarizing the results of this first test and join #fse-outreach-experiment if you’d like to help with future calls for testing. Thank you to all who have already helped test!

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.

@ajlende

  • This PR has now been merged: WordPress/gutenberg#25171 adds srcset for cover images. Looks like there’s a few people who would appreciate it for performance reasons and it’s needed in order to add duotone to the cover block. The primary question in the PR is if it’s worth adding the polyfill for IE.
  • Would love a review for this PR: WordPress/gutenberg#27936 has some light refactoring of the custom gradient picker which also adds some inline documentation and simplifies the code for readability. It also allows me to reuse it for the duotone picker. 

@joen

@youknowriad

  • Landed the removal of the auto-drafts in Full Site Editing, an important low-level work.
  • Fixed a number of small bugs and tweaks here and there
  • A number of reviews and discussions.
  • Going forward, would like to focus a bit more on FSE, maybe the template mode in the post editor in the next days.

@ntsekouras

  • PR for Query Pagination with InnerBlocks.
  • Display matching variation icon in Block Switcher.
  • Various small 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 reviews.

@itsjonq

  • Continue the efforts of updating our Component Systems, starting with the FontSizeControl integration.
  • Working through final details/adjustments to make sure things conventions are compatible with Gutenberg.

@annezazu

@paaljoachim

  • Triaging older issues from 2018 and 2019. As well as triaging needs design feedback issues.
  • Docs: Working on (again) improving the Local WP Development Environment setup.
  • Taking part in Learn/Training team meetings to see where Gutenberg can improve to help make things easier there.
  • Docs: Working on Improving the intro Block Editor Handbook page. Issue 27400.

Open Floor

Should we implement a “stale bot” on the GitHub Repo? Raised by @mkaz.

The full question can be seen in this comment. A stale bot essentially automatically goes through issues after X timeframe and can be programmed to share a message before handling closing out the issue/PR. By implementing some version of a stale bot to sweep through the repo, it can ideally help keep the open issues/PRs more relevant and up to date while handling out of date items. Here are key points from the discussion:

  • We’d want a long timeframe for closing. ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. uses 90 days but we’d be looking at 120+ days.
  • Important to keep in mind, closed tickets are still searchable, still exist, and still make up the archive. They don’t disappear, and can be reopened.
  • A label could be added to keep something from being auto-closed for particular items.
  • It would be important to get the messaging right in whatever comment left by the stalebot so it’s clear what action needs to be taken to keep an issue or PR open, the reasoning for such a bot, etc.
  • It’s unclear what kind of approval/agreement is needed for this change. TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. currently doesn’t have this policy but it’s unclear if that’s due to tooling limitations.

Next steps: @mkaz and @annezazu will collaborate on a Make Core post to propose this change, draft a suggestion for the messaging, and get feedback to make sure this is an okay direction to go in.

Help review a restructuring change to the Gutenberg Developer Handbook. Raised by @justinahinon.

Work is underway in this PR about Gutenberg developer handbook homepage as part of the handbook restructuring project. This PR should ideally help give a better experience with more clarity for users who first enter the handbook. The first experience matters immensely so this is a great thing to get right! Give your feedback in the PR.

What’s the best way to allow my block users to edit attributes for every display (desktop, tablet, mobile)? Raised by @louis.

Here’s an expanded version of the question for clarity:

As I understand, iframing the editor is finally coming round (really great stuff). I’ve been looking at different ways to allow my block users to edit attributes for every display (desktop, tablet and mobile), but does the Gutenberg team have an idea worked out on how these attributes will be edited responsively? And if so, is it planned for WordPress 5.7.

@joen kindly jumped in to share some great thoughts:

  • This is really tricky to get right and the team likely won’t have something for 5.7.
  • The current approach is to first and foremost build as good a responsiveness as you can, right into the block. For example, having smart defaults, like how the Media & Text block collapses when responsive.
  • Right now, you can actually hook into the preview dropdown, and leverage that to create your own responsive system right now. This is what the Layout Grid block does, feel free to look at the source there.
  • Even implementing what the Layout Grid does, the experience is still lacking: How do you edit the desktop breakpoint on a physical mobile device?  How do you customize, or add additional breakpoints? All of this is TBD.

Ideally, going forward work started in this Gutenberg issue and improvements to Global Styles can enable this to work better in the editor.

#core-editor-summary

Ebonie Butler 8:29 pm on January 12, 2021
Tags: , ,   

Dev Chat Agenda for January 13, 2020

Here is the agenda for this week’s meetings to occur at the following times: January 13, 2021 at 5:00 UTC and January 13, 2021 at 20:00 UTC.

Blogblog (versus network, site) Post Highlights

Next Releases

  • WordPress 5.6.1 (Release to be scheduled)
  • WordPress 5.7 (Upcoming BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 Release on February 2nd)

Components check-in and status updates

  • Check-in with each component for status updates.
  • Poll for components that need assistance.

Open Floor

Do you have 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-7, #agenda, #dev-chat

Ajit Bohra 7:28 pm on January 12, 2021
Tags: , , , , , ,   

Editor chat summary: Wednesday, 6 January 2021

This post summarizes the latest weekly Editor meeting (agenda, slack transcript), 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, January 6, 2020, 14:00 UTC.

Thank you to all of the contributors who tested the 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. releases and gave feedback. Testing for bugs is a critical part of polishing every release and a great way to contribute to WordPress.

WordPress 5.7

WordPress 5.7 is now underway with Beta 1 due on 2 February 2021. Now’s the time to be thinking about what 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 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 we want to ensure are in the release. Project board to track WordPress 5.7 “must-haves” is available. Please add issues to this board and/or reach out to (@noisysocks) if there is something you think needs to be included.

Gutenberg 9.6

Gutenberg 9.6 was released on 23rd december. The big focuses throughout this release cycle were Full Site Editing and Global styles. This release also includes many fixes and some nice new features and enhancements.

Gutenberg 9.7

Gutenberg 9.7 was released on 6th january. First release of 2021 🎉. A number of contributors enjoyed some well earned time off but it didn’t stop them from shipping exciting features for the 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. editor.

Monthly Plan

The monthly update containing the high-level items that Gutenberg contributors are focusing on for January are:

  • Global Styles
  • Block-based WidgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. Editor
  • Full Site Editing

For detailed plan check out monthly priorities post.

Updates on the key projects

@jorgefilipecosta

  • On the Global Styles side, the work to include the new version of the components is ongoing. Starting with the font size picker. Our end to end tests was improved To not be as markup dependent And work with both versions of the components. There were some end-to-end tests that were legitimately failing And fixes were submitted. Besides that, the discussions on theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. continued to happen. But all the feedback was applied and I think is ready to merge.
  • Another big chunk of the work saves time escaping the theme.json structure to align with what happens with other WordPress data saved in custom post types. This work is proving a little bit more complex than I anticipated. But a part should be ready very soon
  • Currently, we are blocked on an issue regarding transpiling. zustand is not being transpiled and the build is not ECMA compliment. I am not really sure how to force the transpiling of that specific lib. All the solutions I tried failed. But I have a considerable lack of babel knowledge So any help here is appreciated

@annezazu

  • The Full Site Editing Outreach program is underway with the very first call for testing
  • While you can leave feedback anytime 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/, this call for testing will be open until January 13th.
  • If you don’t have time to test right now, no worries—another way to help would be to share the call for testing with others.
  • If interested in joining the fun in general, please :dance: your way over to #fse-outreach-experiment

@paaljoachim

  • In regards to widgets screen update Every Wednesday UTC there is a block-based widget editor chat in the #feature-widgets-block-editor
  • The first meeting after the holiday was earlier today.

@noisysocks 

  • Going through various customizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. issues. A new technical method is on its way check the main issue

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.

@get_dave

@ntsekouras

  • Add block transforms preview
  • Display Block Information by matching block variations is merged. This includes the addition of a property (isActive) in Block Variation’s settings. This optional property is a function to match block variations after their creation.
  • Add new post link to Query Block.
  • I have a PR for new block ‘Archive Title’.

@itsjonq

  • I had a break in December, so I’m catching up on all the things.
  • My primary focus is to continue work on the new Component System (aka. “G2 Components”).
  • As @jorgefilipecosta had mentioned earlier, we’re working on integrating things with the ‘FontSizePicker’ component. I’ll be helping with all integration efforts on that front. We’ll then have the UIUI User interface set up to start improving the UI for Global Styles.

@priethor

I’ve just started working on this issue, my first contribution Navigation Block: Add support for a dynamic home URL

@paaljoachim

  • I am working on various documentation such as updating Setting up a Local Dev environment. I also made a video for it. How to test a PR issue. Etc.
  • Widget screen Using the Move to option. 

@youknowriad

I took the time where everyone was away as an opportunity to solve two of the long-standing issues we had:

  • Reusable blocks to use controlled inner blocks (multi-entity save flow)
  • Refactor FSE templates and template-parts to avoid auto-drafts for theme provided template files.

One is shipped and I’ll continue with the second one

@adamsilverstein

  • I’ve been working on improving the Combobox controls we added for the post author and page parent selector and could use some help/review on when someone has a chance.

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

Francesca Marano 6:39 pm on January 12, 2021  

Recap and proposal: align the WordPress release cycle with the industry standard

Following a lively conversation that happened in this blog in October 2020, here is the recap of the different ideas that were brought up and the proposal to move forward.

Rename phases

There is a consensus here.

NowChange to
Phase 1: Planning and securing team leadsPhase 1: Preliminary Planning
Phase 2: Development work beginsPhase 2: Alpha
Phase 3: 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.Phase 3: Beta (stays the same)
Phase 4: 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).Phase 4: Release Candidate (stays the same)
Phase 5: LaunchPhase 5: General release

Restructure Beta

The main point of discussion is what is allowed and what is not allowed during Beta.

Reserving Beta for testing and fixing bugs discovered by testing respects the efforts of the beta-testers by not introducing new bugs in areas they’ve already tested.

@azaozz

The wider software industry has done this work [how a release cycle is structured] for us. A mature software project is one that has a beta period during which the focus is on testing changes made during this release cycle to ensure its stability. Our current workflow means a random bugfix can go in ten minutes before RC 1.

@johnbillion

However, there are concerns specific to our project

I worry that we aren’t allowing space for older bugs that aren’t specific to the planned features in the release. I also worry that by calling hard freeze earlier in the process we narrow the window for feature inclusion too much. I think Matt agrees with my thoughts there, as well.

@chanthaboune

My concern here is to not shorten the time allowed for fixing older bugs, which I see as an essential part of the project.

@sergeybiryukov

Proposed solutions

Adding a “Feature Freeze” period came up from multiple parties and it seems to be the most popular solution to allow contributors to focus on features first and defect work later, without doing the defect work in Beta, which should be reserved for testing.

Easier said than done… @hellofromtonya presented us with two solutions

Proposal 1: feature freeze and then do defect work

This proposal is for a feature freeze 2-3 weeks before Beta 1 and then allocation of this time period for defect work.

Pro

This proposal has a clear definition in the 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. cycle after the major release is kicked off and when the release squad is in place. 

Concerns

  • It does not capitalize on the overlap between releases.
  • It does not provide a way to reduce the overall release cycle.
  • Does the major release squad need to be focused on the continuous defect work (i.e. defects not directly caused by the release)?

Proposal 2: defect work during release overlap

This proposal front-loads the defect work to overlap the previous release’s Beta and RC.

Pros

  • Work continues with purpose and focus while the previous release is in its testing and release phases. It capitalizes on the time between major releases while keeping the momentum rolling forward.
  • It provides an opportunity to shorten the overall major release cycle.

Cons:

  • Do we need the current release squad to be involved in this early phase or even in the defect cycle?
  • Could the component maintainers and CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Team work together to help prioritize and escalate defect work?

Branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". at Beta

In both solutions, 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. gets branched at Beta

Length of Beta

Both solutions beg the question: is Beta long enough? For 5.7 it’s three weeks. If the leadership of the project decides to move forward with one of the above-proposed solutions, WordPress 5.8 will have to account for a longer Beta probably. See:

Concern: We already have feedback that it’s hard to keep up with changes for our 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/theme authors. While a change like this is possible, it would require some paradigm shifts that I don’t think have been fully explored.

@chanthaboune

Call to action

  1. Discuss this during the next dev-chat (January 13) and leave comments open for an additional week (January 20)
  2. Present any additional evidence gathered to Josepha and Matt for final saying.

Thank you @hellofromtonya for peer review

annezazu 5:59 pm on January 12, 2021
Tags: ,   

Editor Chat Agenda: 13 January 2021

Facilitator and notetaker: @annezazu

This is the agenda for the weekly editor chat scheduled for Wednesday, 13 January 2021, 14:00 UTC.

This meeting is held in the #coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-editor 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/. and all are welcome to join!

Even if you can’t make the meeting, you’re encouraged to share anything relevant for the meeting in the comments below:

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

#core-editor #core-editor-agenda

Jb Audras 10:01 pm on January 11, 2021
Tags: , ,   

A Week in Core – January 11, 2021

Welcome back to a new issue of Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Let’s take a look at what changed on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between January 4, 2021 and January 11, 2021.

  • 10 commits
  • 19 contributors
  • 64 tickets created
  • 6 tickets reopened
  • 41 tickets closed

Ticketticket Created for both bug reports and feature development on the bug tracker. numbers are based on the Trac timeline for the period above. The following is a summary of commits, organized by component.

Code changes

Bootstrap/Load

  • Add missing <p> tags to error message in wp-load.php – #52254

Customize

  • 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): Add an empty alt attribute to the <img> 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.) used as a hidden placeholder in the CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. preview when no logo is chosen – #51846

Docs

  • Correct description for wp_parse_list() – #51800

Editor

  • Support filtering arguments in 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. type registration from metadata – #52138

Help/About

  • Accessibility: Use more descriptive link text for the Privacy Policy link on the Privacy screen – #52233

Login and Registration

  • Introduce the lostpassword_user_data filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. which allows for the user data object during a password reset request to be filtered – #51924

Posts, Post Types

  • Introduce the wp_list_table_show_post_checkbox filter which allows the visibility of the bulk edit checkbox on the post list table to be controlled separately from the edit_post capability of the current user – #51291

Privacy

  • Clarify the “Contact information” heading in default privacy policy content – #52272

Quick/Bulk Edit

  • Aaaand our best commit message of the week so far, by @johnbillion (read the full commit message here) 😂
    By the power vested in me, I hereby declare the top bulk actions and the bottom bulk actions joined forever in MatrimonyScript – #46872

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

  • Fix fatal error on 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 when calling the single item 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 routes – #52205

Props

Thanks to everyone who contributed to WordPress Core on Trac last week:

@audrasjb (4), @mukesh27 (2), @shital-patel (1), @marcelo2605 (1), @carike (1), @hareesh-pillai (1), @pbiron (1), @garrett-eclipse (1), @subrataemfluence (1), @clayray (1), @sabernhardt (1), @swissspidy (1), @TylerTork (1), @laxman-prajapati (1), @alexstine (1), @coreyw (1), @oakesjosh (1), @TimothyBlynJacobs (1) and @johnjamesjacoby (1).

Please welcome our 2 new Core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. of the week ♥️
@TylerTork and @coreyw.

Core committers: @sergeybiryukov (5), @johnbillion (3), @timothyblynjacobs (1), @and @gziolo (1).

#5-6-1, #5-7, #week-in-core

annezazu 6:07 pm on January 8, 2021
Tags: ,   

Core Editor Improvement: Drag & Drop Blocks and Patterns from the Inserter

With the launch of Gutenberg 9.6 and Gutenberg 9.7 comes the ability to drag and drop blocks and 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. patterns from the Block Inserter. This new feature might be easy to miss if you’ve grown used to relying on the current ways to add blocks! Here’s a quick video showing how it’s done for both blocks and block patterns:

Video showing drag & drop from the inserter for first a block and then a block pattern.

Important Note: you need to use a theme with registered block patterns (ex: the current default theme and the prior 4 years) .

With this new addition, there are now seven ways to quickly add blocks to your content, whether it’s to write a compelling post, build out a fancy sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. with the in progress Widgets Editor, or create a site using the site editing experiment:

  • Drag and drop from the inserter.
  • Select from the inserter. 
  • Type a forward slash followed by the block name: /image or /paragraph.
  • Click the black + icon at the side of an empty block.
  • Using the + icon at the top left of the editor which opens Block Inserter.
  • Hit the Enter/Return key from a currently selected block to create a new block underneath it. 
  • Click on the three dots just above a selected block and choose to add a block above or below the current block.

This is a very new feature so, as you explore, know that feedback 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. reports are always welcome on GitHub. 

If you’re interested in working on features like this, make sure to join #core-editor, check out the current focuses, and attend the Core Editor weekly meeting on Wednesdays @ 14:00 UTC in core-editor. 

#core-editor-improvement #core-editor

Lara Schenck 8:26 pm on January 7, 2021
Tags: ,   

CSS Chat Agenda: 7 January 2021

And we’re back after a couple weeks break!

This is the agenda for the upcoming CSSCSS Cascading Style Sheets. meeting scheduled for Thursday, January 7, at 10:00 PM UTC. 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!

  • Housekeeping
    • Checking in on meeting format
  • Updates
    • CSS Audit (#49582)
    • Color Scheming (#49999) – Visual Regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. Testing (#49606)
  • Open floor + CSS link share

#agenda, #core-css

Nalini Thakor 6:25 pm on January 7, 2021
Tags: , ,   

DevChat Meeting Summary: January 7, 2021

@thewebprincess and @webcommsat led the weekly meetings of the WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team, respectively at 05:00 UTC and 20:00 UTC.

Thanks to @nalininonstopnewsuk and @webcommsat for the notes.
Slack archive for the 20:00 UTC meeting.

Announcements

  1. WordPress 5.7 news

2. Workshop submissions and testing calls

  • Full Site editing update
  • Learn WordPress
    • Got a dev workshop, or thinking of designing one? Submit it to Learn WordPress. Here’s a great example on using tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., that is already there: https://learn.wordpress.org/workshops/.
    • Follow and share promotions for #LearnWP and Meetups on social media too @WordCamp, @WordPressEvents and LinkedIn.

3. Monthly and weekly updates/ bulletins

Updates from the Component Maintainers and Focus Leads

Component maintainers do really important work. More about components at https://make.wordpress.org/core/components/

  • Update from @sergey:
    • Build/Test Tools – These change the frequency of code coverage reporting. A change was made in [49931] to display a relatively accurate code coverage data at https://codecov.io/gh/WordPress/wordpress-develop on any given day of the week.
    • Some other changes include updating several NPM packages and simplifying Composer package caching
    • I18Ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill., Date/Time, Permalinks: No major news this week.
  • Update from @sarahricker on 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)
    • several Accessibility Team members volunteered to stay up to date with accessibility needs for each component/focus
    • if your component doesn’t connect with an Accessibility member soon, let the team know.

Open Floor

  • Update from @Sergey on 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/ 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:
    • After almost a month since WordPress 5.6, for some reason the Gutenberg plugin still shows “Tested up to: 5.5.3” in the Plugin Directory and “Untested with your version of WordPress” when searching from a WordPress 5.6 adminadmin (and super admin), leading to search results that are not exactly great: https://cldup.com/nmU8Bq64U1.png
    • Note how every other plugin is listed as “compatible with your version of WordPress…”, but Gutenberg is “untested”.
    • Could we have an established process for updating the “Tested up to” version for Gutenberg? Boosting exact slug/name matches for plugin search was previously discussed in #meta3327 and some other 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. tickets. Apparently it’s not something that can or should be done at this time, however making sure that the “Tested up to” version is accurate should give us better search results. Ticket #3327: Searching with exact plugin name has it on page 3 of results
  • Promoting guidance for updating plugins to related WordPress versions
    • @webcommsat: Marketing has heard from Meetups and contributor events on intro talks on plugins development or basic talks on installing plugins: uncertainty about how plugins show they update to the current version. Potential to further promote guidance and advice.
    • @audrasjb recommended the Plugin development FAQ

Goals for 2021

Tickets requesting feedback

#5-7, #devchat

#5-7, #core, #devchat

Riad Benguella 9:35 am on January 7, 2021
Tags: , , ,   

What’s new in Gutenberg? (6 January)

First release of 2021 🎉. A number of contributors enjoyed some well earned time off but it didn’t stop them from shipping exciting features for the 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. editor.

Block Patterns Drag and Drop

Similar to blocks drag and drop that shipped in the previous release, 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/ 9.7 allows user to drag block patterns from the inserter right into the desired position in the canvas.

Reusable blocks

The release also so an important change to how reusable blocks are shown and edited in the editor solving some of the old issues around block inspector, and block toolbars for the reusable blocks. Based on these changes, the UIUI User interface for reusable blocks is most likely going to see some iterations on the upcoming weeks.

Matching block variations

Block variations are a great 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. that can be used to build a generic block and ship several variations on top of it. That’s how the embed blocks or social link blocks are built. In Gutenberg 9.7, if you insert a block variation, the editor is going to match the block being used and show the “icon” and “description” of the said block variation in the different elements of the interface. (Block navigation, block inspector…)

9.7 😅

Features

  • Support drag and dropping block patterns from the inserter. (27927)

Enhancements

  • Improve the Reusable Blocks UI by relying on multi entity save flow. (27887) (27885)
  • Show the insertion point indicator bellow the inbetween inserter. (27842)
  • Add block transforms previews. (27861)
  • URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org: RemoveQueryArgs should remove the ? char after removing all args. (27812)
  • Deburr the input of the Post Author and Parent Page controls when filitering results. (26611)
  • Display block icon, description and name by matching block variations. (27469)
  • RSS Block: Add an explicit border-box CSSCSS Cascading Style Sheets. rule. (27767)

New APIs

  • Create block: Allow to list npm packages to be installed in the template. (27880)
  • wordpress/url: Add a maxLength argument to filterURLForDisplay. (27530)
  • Add new package @wordpress/stylelint config. (22777)

Bug Fixes

  • Show all taxonomies in Tag Cloud block. (27930)
  • HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. Block: Fix editor styles. (27627)
  • Don’t ignore extra edits made in the server when saving posts. (27929)
  • Remove the animation of post publish button during autosaving. (27874)
  • Prevent the inserter from closing when switching the pattern categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging.. (27792)
  • LinkControl: Fix horizontal scrollbar within block toolbar. (27777)
  • Create Block: Fix support for external templates. (27776) (27784)
  • Fix text color dropdown not opening. (27596)

Experiments

  • Full Site Editing Framework:
    • Add support for custom templates in FSE themes. (27778)
    • Refactor the edit-site store to clarify the purpose of templateId and templatePartId. (27839)
  • Full Site Editing Blocks:
    • Site Logo: Remove duplicate link. (27924)
    • Post excerptExcerpt An excerpt is the description of the blog post or page that will by default show on the blog archive page, in search results (SERPs), and on social media. With an SEO plugin, the excerpt may also be in that plugin’s metabox. block: Fix incorrect quotes for the class attribute in the wrapper. (27895)
  • Global Styles: Add padding control to the Global Styles sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme.. (27154)
  • Navigation block: Fix the text color for links in the navigation block. (26698)

Documentation

  • Improve documentation for withNotices HOC in components package. (27863)
  • Add ContrastChecker component readme. (25570)
  • Remove default style information from the documentation. (27811)
  • Storybook: Fix broken import statements for DateTime component. (27794)
  • Add additional information about lock inheritance. (27834)
  • Typos and tweaks: (27909), (27799)

Code Quality

  • Use a consistent way to check isRTL. (27838)
  • Update the minimum required WordPress version to 5.5. (27807)
  • Remove unused redux-optimist dependency. (27798)
  • Storybook: Perform cleanup in the Storybook setup. (27786) (27813)
  • Raw handling: Remove duplicate code. (27758)
  • Refactor BlockSwitcher as a functional component. (27674)
  • Rich Text: Replace store name string with exposed store definition. (27820)

Tools

  • Remove overrides for JSDoc rules downgraded to warnings. (27912) (27879)
  • 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 release tool: Fix svn add/rm commands for release tool. (27886)
  • Add types to the wordpress/keycodes package. (19520)
  • end to end tests:
    • Make end to end tests do not rely on font size picker classes. (27825)
    • Remove expect.assertions count from multi-entity-saving tests. (27802) (27818)
    • Testing: Remove axe verification executed after every test case. (26626)
    • Improve font size end to end tests to work with input changes on blur. (27871)

Performance Benchmark

The following benchmark compares performance for a particularly sizeable post (~36,000 words, ~1,000 blocks) over the last releases. Such a large post isn’t representative of the average editing experience but is adequate for spotting variations in performance.

VersionLoading TimeKeyPress Event (typing)
Gutenberg 9.75.41s31.1ms
Gutenberg 9.65.45s28.8ms
WordPress 5.65.45s30ms

Kudos for all the contributors that helped with the release. 👏

#core-editor, #editor, #gutenberg, #gutenberg-new