Editor Chat Summary: October 2nd, 2019

This post summarizes the weekly editor chat meeting on 13:00 UTC, October 2nd, 2019 held in Slack.

The agenda can be found here.

WordPress 5.3

Slack transcript.

Gutenberg 6.6 was released and has been included in WordPress 5.3 beta 2.

Weekly Priorities

Slack Transcript.

The main current focus is still WordPress 5.3. Tasks are being tracked in this Github board. Starting work towards the content-block areas.

Task Coordination

Slack Transcript.

Open Floor

Slack Transcript.

@mikeschroder raised that WordPress 5.3 comes with an update to image uploads: if the server sends a HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. 500 error (for example, because it couldn’t finish the thumbnail resizing) the process will be retried. This is implemented in the Media Library and Media Modal, but not in the REST API and Gutenberg yet.

@maximeculea mentioned that the mobile team is running an experiment with styled components (CSS in JS) as a way to learn whether styles can be shared between web and mobile.

@paaljoachim brough up that there is a PR that address some of 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/ float issues. @youknowriad and @joen noted that, currently, this falls in theme-land. We should make progress on some refactorings to the block list that are a better approach, leaving the current behavior as it is.

#core-editor, #editor-chat, #summary

Editor chat summary: 25 September 2019

This post summarizes the weekly editor chat meeting on Wednesday, 25 September 2019 at 1300 UTC held in Slack.

The agenda can be found here.

News

  • WordPress 5.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. 1 is out

Weekly Priorities

  • Weekly Priorities are the remaining important issues and tasks needed for WordPress 5.3: https://github.com/WordPress/gutenberg/projects/34?fullscreen=true
    • still considering 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. content areas related work as a priority for the project

Task coordination

Note: If you’re reading this summary outside of the meeting, please drop a comment if you can/want to help with something!

  • @andraganescu
    • refactored the MediaFlow component to be a drop in component nstead of a HoC. it looks kind of ready https://github.com/WordPress/gutenberg/pull/16200
    • the PR implementing a smarter block appender could use a new review https://github.com/WordPress/gutenberg/pull/16708
  • @youknowriad
    • works on the WP 5.3 board above,
    • also working on dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase.,
    • Trying to help fix bugs
    • Reviewing Block Content areas work as time allows.
  • @mapk
    • I’m watching the project board like a hawk.
    • Testing @getdave’s responsive spacing PR: https://github.com/WordPress/gutenberg/pull/16790
    • Helping with the Inserter Panel Previews. https://github.com/WordPress/gutenberg/pull/17493
    • Keeping movement on the Block Patterns: https://github.com/WordPress/gutenberg/issues/17335
  • @brentswisher
    • will be back to his PRs
  • @getdave
    • works on the DimensionControl component and needs feedback https://github.com/WordPress/gutenberg/pull/16791
    • needs feedback on ResponsiveBlockControl too https://github.com/WordPress/gutenberg/pull/16790
  • @jorgefilipecosta
    • implements the first version of custom Gradient picker
    • needs review on https://github.com/WordPress/gutenberg/pull/17154
    • also working on compiling WordPress 5.3 Gutenprops. If you have not yet associated your GitHubGitHub GitHub is a website that offers online implementation of git repositories that 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/ to your WP.org profile, please do so, to make the props work easier and to make sure props are attributed!
  • @mcsf
    • focusing back on improving remote vs. local autosaves

Open floor

  • @paaljoachim raised some issues for discussion
    • there was a discussion on an option to use text link instead of auto embed ended with needing to clarify more on the issue
    • there was a discussion on the social block features needed for it to make it in WP 5.3 resulted in not having a light version because of the risk that we’d introduce breaking changes in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.
  • @desaiuditd and @youknowriad discussed about https://github.com/WordPress/gutenberg/pull/17311

The next meeting is on 02 October 2019 at 13:00 UTC.

#core-editor, #editor-chat, #summary

Editor Chat Agenda: September 25th

Note taker: @andraganescu.

This is the agenda for the weekly editor chat scheduled for September 25, 2019 at 1300 UTC.

This meeting is held in the #core-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/..

  • WordPress 5.3
  • Weekly Priorities
  • Task Coordination
  • Open Floor

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

As always, 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

Editor Chat Agenda: September 18th

Note taker: @mikeschroder.

This is the agenda for the weekly editor chat scheduled for September 18, 2019 at 1300 UTC.

This meeting is held in the #core-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/..

  • 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/ 6.5 Release
  • Weekly Priorities
  • Task Coordination
  • Open Floor

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

As always, 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

Editor chat summary: Wednesday, 28 August 2019

This post summarizes the weekly editor chat meeting on Wednesday, 28 August 2019, 14:00 WEST held in Slack.

Weekly Priorities

  • Inline tips #16582 was closed until #16592 gets resolved.
  • Edit MediaFlow #11952 received feedback and needs to be updated).
  • Regarding the architecture work preparing the editor to handle multiple entities, @epiqueras shared that the framework changes and everything up to the site 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. is done. Now we need designs for template selection/creation, and post block save flows, etc.
  • Background color for the cover block was merged and release.
  • Regarding the gradient backgrounds, @jorgefilipecosta proposed a PR implementing gradient functionality. @jorgefilipecosta shared that we need to decide if the predefined gradients created by themes should use a class or an inline style. And asked: Is there an expectation that when a theme switch happens, the gradients should change? If you have any thoughts on this subject, please share them!
  • Screen height image expand has been updated and just about to cross the finish line. 

Task coordination

Note: If you’re reading this summary outside of the meeting, please drop a comment if you can/want to help with something!

  • @swissspidy is looking at support non-consecutive block multi-selection and would like a helping hand.
  • @nadir is going to revisit some blocked PRs he has made so he can advance them.
  • @kjellr is working on:
  • @jorgefilipecosta will continue the work on gradients, continue the block style improvements (is hoping to merge theme default block styles soon), and other smaller improvements like button block styles.
  • @joen is helping PR #16897 for a new social links block.
  • @mapk is looking to:
    • Spend time triaging and reviewing PRs.
    • Create some more structured mockups for dragging and dropping blocks next to each other: #13202.
    • The PR that adds resizing image to full-height, and also the gradients PR.
  • @brentswisher worked on a demo of using a full-screen modal for publishing #17225. This week will work on moving some old PR’s along. If time allows will come up with something for PR “Block inserter doesn’t show that some blocks are disabled” (would like some help).
  • @gziolo revisited a PR which stop showing errors and warnings when blocks get successfully updated from deprecated version (#16862). Plans to update WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. packages and fully automate the way we maintain script dependencies.

Open floor

@paaljoachim would like some feedback on the last comment he made on PR #16682. Asked if anyone can take over PR #16490, @mcsf said he was hoping to grab the referred PR in the next days. And to conclude @paaljoachim said PR #14367 is almost ready for a final review.

@welcher would like some feedback on PR #17198 (headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. toolbar).

#core-editor, #editor-chat, #summary

Editor Chat Summary

This post summarizes the weekly editor chat meeting on August 21, 2019 at 1300 UTC held in the core-editor Slack channel.

The agenda can be found here.

Note: If you’re reading this summary async, please drop a comment if you can/want to help with something!

Priorities for the week

Slack transcript.

Merged:

Being worked on / Needs more work:

Task Coordination

Slack transcript.

@youknowriad Refresh to reusable blocks that closes multiple issues, triagged issues and reviewed PRs.

@karmatosed Triagged, mainly issues/PRs that need design feedback.

@kjellr Improvements to the inserter help panel (1, 2), changes to NUX tips, and tidying up animations (1, 2).

@jorgefilipecosta Explored mobile viewport in the editor (1, 2). To work on text color formatting, gradient backgrounds, cover 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. resizing.

@mapk Looking into improving the sibling block inserter, helping on widgets work and @retrofox on a UIUI User interface solution for screen height PR.

Components package reorganization and bundle sizes

Agenda | Slack Transcript | Issue

The issue created by @nerrad sparked a conversation on how to control bundle size and offer options to bundle “what you need”:

  • The `wp_enqueue_script` model encourages people to use the whole bundle for a package, not the specific pieces you want.
  • There are concerns over creating too many packages that make discoverability difficult.
  • Overrall, this ties into how to make WordPress play nicely with dynamically loading dependencies as you need them (the SPA model).

To be discussed more in the issue and/or in future coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-js chats.

e2e test and block deprecations

Agenda | Slack Transcript | Issue

  • @isabel_brison raised the issue that e2e tests fail due to block deprecations triggering a `console.warning`.
  • The restriction have been very valuable when it came to deprecate APIs, as to make sure core wasn no longer using them. It is not that useful in other contexts.
  • There is a draft PR to address the deprecation issue.

#core-editor, #editor-chat, #summary

Editor Chat Agenda: August 14th

Note taker: @andraganescu

This is the agenda for the weekly editor chat scheduled for August 14, 2019 at 1300 UTC.

This meeting is held in the #core-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/..

  • 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/ 6.3
  • Tasks Coordination
  • Open Floor

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

As always, 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

Editor Chat Agenda: August 7th

Note taker: @mikeschroder

This is the agenda for the weekly editor chat scheduled for August 7, 2019 at 1300 UTC.

This meeting is held in the #core-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/..

  • Tasks Coordination
  • Open Floor

Last week it was suggested to post items for Tasks Coordination as comments on posts so that it’s easier to follow for folks that can’t attend the regular meeting.

So, let’s give it a try! If you have anything to share for the Tasks Coordination section, please leave it as a comment on this post.

As always, 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

Editor chat summary: Wednesday, 24 July 2019

This post summarizes the weekly editor chat meeting on Wednesday, 24 July 2019, 14:00 WEST held in Slack.

The agenda followed can be found here.

The meeting started with @youknowriad noting that we postponed this week’s 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/ release 6.2 to the next week due to a lot of AFKs and not enough shipped features/enhancements for a proper release. Next week we will resume the regular release schedule.

Task coordination

Note: If you’re reading this summary outside of the meeting, please drop a comment if you can/want to help with something!

@tellthemachines

  • Working on the settings page. It’s not finished yet, but @tellthemachines created a PR up to get feedback: https://github.com/WordPress/gutenberg/pull/16626
  • Started working on a caption for the gallery block: https://github.com/WordPress/gutenberg/issues/9342
  • Looking at http://gutenberg.run/ and other possibilities such as https://tugboat.qa/ for setting up preview environments for our PRs.

@youknowriad

  • Worked mainly on “A11yAccessibility 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) Navigation mode” and “Live Drag and Drop experimentation”.
  • Reviewed: new PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. to register style variations and some small reviews here and there (Gutenberg experiments settings page, Text alignments in 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. heading, Improved preview component…).
  • Started thinking about Full Site Editing and what does it mean for Gutenberg to support editing the full site/page even outside post content.

@mapk

  • Working on 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. screens
  • Exploring some Block Template flows
  • Reviewing PRs

@jorgefilipecosta

  • Plans to finish the work related to block style variations, some PR’s will need an update to avoid PHP anonymous functions.
  • Will submit some fix for issues opened affecting the blocks widget screen.

@karmatosed

  • Plans on reviewing anything design stuck in the backlog.
  • Has been dipping into the ‘needs testing’ label a bit to keep that moving along.

@brentswisher

  • Is working on ideas for “updating the publishing flow”. A PR https://github.com/WordPress/gutenberg/pull/16715/ is available, and feedback is welcome.

@kjellr

  • This week: Worked on improvements to the Gutenberg Starter Theme.
  • Next week: Will focus on the Patterns API + Tips.

@getdave

  • Worked on a PR to add basic spacing/dimensions controls to the Group Block. https://github.com/WordPress/gutenberg/pull/16730
  • Improved BlockPreview component:
    • Autosizing / scaling previews – https://github.com/WordPress/gutenberg/pull/16113/
    • Updating the API of the component to accept multiple blocks as arguments – https://github.com/WordPress/gutenberg/pull/16033

Growing list of open PR’s

@youknowriad made a remark saying:

The list of open PRs is growing. That’s great, I’d like to thank you all for your contributions. This also means we’re having some trouble to keep-up with reviews… I’d like to ask everyone creating PRs / working on Gutenberg to help as much as needed with PR reviews (it doesn’t matter if you think you have the required knowledge or not, all reviews are helpful and help move things forward).
So please review PRs as much as you can and again thanks all for your work/help. If you’re hesitant for any reason, my DMs are open, happy to address your uncertainty.

@karmatosed flipped the question and asked if there are any hurdles to people reviewing.

@brentswisher pointed out that his hesitation (maybe shared with other contributors) is a fear of uncertainty about what would happen after something is reviewed and made the following questions:

  • Does it just get merged?
  • Does someone with more experience look at it again before merging?
  • Am I supposed to merge it?

@karmatosed  and @youknowriad answered that since @brentswisher is a member of the GithubGitHub GitHub is a website that offers online implementation of git repositories that 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/ Gutenberg team, he can merge a PR after the review or review it anyway but not merge it right away and ask for a second opinion.
Both also mentioned that maybe there is space to iterate the docs and make that more clear.

Open Floor

@paaljoachim is wondering if other have some comments on PR https://github.com/WordPress/gutenberg/pull/16557 (Try: Always collapse block alignments), for @paaljoachim the PR seems a no brainer by placing alignment into a dropdown.

@karmatosed said that she would say “yes” to the PR if discoverable, but her concern is hiding usefulness.
@mapk said he liked it, adding that we have other items that work this way already.
@paaljoachim asked for comments on the previously referred PR and PR https://github.com/WordPress/gutenberg/pull/16682 (“added alignment to the toolbar for consistency”).
@karmatosed said we could add the comments and thanked @paaljoachim for championing these PRs.

@desaiuditd asked for comments on PR https://github.com/WordPress/gutenberg/pull/16244 (“Allow changing Block attributes dynamically in InnerBlocks template”.).
@jorgefilipecosta said:

The idea of the template is to provide a set of blocks that prefill a given InnerBlocks when it is empty.
If I pass a template when a block contains a given set of attributes, and later I pass a template where blocks contain different attributes, nothing should happen because the block is not empty anymore and there is no need to prefill it.

The discussion continued on the reason why sometimes the template updates the blocks. @jorgefilipecosta explained that it only happens when templateLock=all and only for cases where blocks changed positions or were removed/added because for this locking we know the user would not have made these actions.

@chrisvanpatten and @mcsf both pointed to a PR that may bring more control to templateLock https://github.com/WordPress/gutenberg/pull/16678 (Template Locking: read-only / disable editing attributes)

@jorgefilipecosta concluded that for now if there is a need to update the attributes of a child, from the parent, the best solution is the usage of updateBlockAttributes action in the parent, and not use the template mechanism.

#core-editor, #editor-chat, #summary

Editor chat summary: Wednesday, 3 July 2019

This post summarizes the weekly editor chat meeting on Wednesday, 3 July 2019, 14:00 WEST held in Slack.

The agenda followed can be found here.

Task coordination

Note: If you’re reading this summary outside of the meeting, please drop a comment if you can/want to help with something!

@nerrad

Implemented the first pass at a potential solution for the element interpolation 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. problem https://github.com/WordPress/gutenberg/pull/16374.

@youknowriad

  • Worked on some performance related PRs. Mostly tried to make the getBlock selector more performant as it’s the bottleneck in terms of typing performance.
  • Reviewed a bunch of PRs. One of the most important is 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. Panel to edit blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.-based 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. areas PR by @epiqueras.
  • Plans to land the block reordering animation soon.

@aduth

Made a few small pull requests, reviews, focusing mostly on “custom” sources for blocks (reimplementing 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 start)
https://github.com/WordPress/gutenberg/pull/16402.
Referred that the issue with the publish button https://github.com/WordPress/gutenberg/pull/16303 has a significant impact and might be easy to review if someone wants to take a look.

@danr

Continues working on table block tasks. Has a couple of PRs ready for review:

Has a PR which changes the way the blocks.registerBlockType 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. works. Would be happy for more testing on it: https://github.com/WordPress/gutenberg/pull/16348

@welcher

Worked on some PRs related to SlotFill with https://github.com/WordPress/gutenberg/pull/13361 being the highest priority, followed by https://github.com/WordPress/gutenberg/pull/16384, in his opinion.

@kjellr

Has been posting some work on revised, less-intrusive tips:
https://github.com/WordPress/gutenberg/issues/16315.

He is hoping to get PR https://github.com/WordPress/gutenberg/pull/14961 merged, once we can figure out the mysteriously-failing test.

Did some initial work on the Patterns 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., and hopes to get that posted until the end of the day: https://github.com/WordPress/gutenberg/issues/16283

@getdave

Has been working to allow any Block to be registered to handle “Grouping” interactions. Received non-consensual feedback some people think that it is a good idea while others think the opposite.
Additional feedback is welcome:
https://github.com/WordPress/gutenberg/pull/16278.

Has been working on Block Previews component along with @joen to allow it to dynamically resize and handle scale a lot better: https://github.com/WordPress/gutenberg/pull/16113.

@nadir

Continues the work on Snap to grid RFC.

@jorgefilipecosta

Answered & debugged some issues and submitted 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. fix PR’s. Reviewed some PR’s, including the blocks in the customizer and the custom parser options. Proposed a simple mechanism for themes to register styles and did updates to the image Link UIUI User interface refactor PR, which was recently merged.

@chrisvanpatten

Has been doing some light PR reviews and issue replies… Is aiming to schedule a Gutendocs bug scrub session next week; if anyone has specific days/times that work and you want to join, feel free to comment! @chrisvanpatten would love to get good attendance.

Agenda: Non-code contributions

@youknowriad introduced the topic by referring that the idea is that we value code contributions (or PRs more precisely) more than other types of contributions: PR reviews, triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors., discussions in issues… The consequence is a growing list of unreviewed PRs and untriaged issues.

@epiqueras proposed some ideas to explore:

  • draft documentation for what is good triage and reviewing, why it’s important, and where new contributors should start.
  • highlight some good live PRs to review for people to take a look at.
  • recognize these types of contributions so that their value is more obvious.

@karmatosed referred that design / technical feedback should be added to the previous list.

@youknowriad a small first step today was that he tried focusing more on “non-code” contributions during the Task Coordination and tried to highlight this work more.

@karmatosed noted that we could expand beyond ‘did you review PRs’ to say ‘did you leave feedback or offer insights’.

@nadir shared that:

being a new contributor, based on my experience in trying to review PR I would say it was really hard for me because sometimes you really need to understand the codebase, things that are agreed upon, the norms and what’s not.

the only PR that I could review are related to things I already solved issues on or had PR related to, but I felt that I wasted a lot of the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team time reviewing basic problems like how to document eslint disable rules and how to write code that matches the core team theme

@karmatosed made an essential point that every single moment investing in someone as awesome to try and contribute isn’t a waste

@mcsf thanked the share made by @nadir and said:

I think that’s a very real issue for anyone coming to the project. I have a suggestion for easing into reviewing other people’s work: recognise that you can still provide helpful feedback even when you’re not an “expert”. This, to me, means that you could define the scope of your review, or your abilities: “I can only speak about this component”, or “about the overall readability”,
Concluding by saying that a newcomer’s eye can reveal a lot of blind spots in PR’s.

@aduth also thanked the share made by @nadir referring that he is inclined to say that we need more documentation for the things @nadir referred. Followed with a set of questions: Is this documentation as it’s organized today very effective? Do you have any thoughts on what might be an effective way for you to become aware of norms and such?

@karmatosed continued the conversation by stating that: Docs are just docs. It’s surfacing and being in the right place counts.

@nadir added that triaging was also an excellent way for him to contribute since he worked on two components when he started (button & snack bar), filtering issues & PR by those components gave him a good ability to review and understand what is happening

@brentswisher joined the conversation and supported the idea of “draft documentation for what is good triage and reviewing”.

@youknowriad proposed a welcome bot that comments PR’s of new contributors. The discussion went on with people sharing insights regarding that idea and how a concrete bot implementation could like.

@karmatosed shared the following actions points as a discussion summary:

  • Recognize and highlight non-code contributions more during weekly meetings
  • Surface the docs better (how?).
  • Improve the docs. (can we create an issue to discuss what needs to be improved and how)
  • Add thoughts to welcome bot and project board: https://github.com/WordPress/gutenberg/projects/24#card-17518302
  • Consider what role of welcome contributor could be.

And ended with a reminder: “We are all human.”

Open Floor

The open floor started with a question by @joyously: How the editor can better support themes? She added:

The old editor has an easy interface to add “Formats” with a simple PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher filter that makes a button in the editor. When can we have that again? Why change the interface to the theme? (new API)

@youknowriad answered by saying:

I think there’s a difference in the paradigm that makes applying “random classNames” to “random HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers.” not a good fit for the block editor. While in TinyMCE we’re adding content as HTML, in the block editor we’re adding content as blocks which means any markup we add should be meaningful for the block.

So the idea is that we have two use-cases here:
– Apply a style variation to the block (known block) (className + stylesheet)
– Apply an inline style variation (inline class name) in RichText. We don’t have an API for that one because it’s less common, but I think you should feel free to open an issue about this “Custom Format” (talking about the RichText Format API ).

#core-editor, #editor-chat, #summary