What’s next in Gutenberg? (June)

This is a monthly update containing the high-level items that 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/ contributors are focusing on for the next month. Please join us in our efforts and let us know in the comments if anything is blocking you from doing so. As a reminder, here’s an overview of different ways to keep up with Gutenberg and the Full Sitesite (versus network, blog) Editing project. 

Full Site Editing (FSE)

Work on this major focus is ongoing and is expected to continue iterating over the next months. Right now, we’re wrapping up the major work needed to build the technical foundation of this project and are soon moving towards expanding the UX & UI:

We’re watching the Theme Experiments repo as well to see how themers are attempting to build 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 themes. Thank you to everyone participating there as it’s a super useful way for us to determine prioritization. 

Follow along:

The high level, important tasks have been split into sections and highlighted on this overview issue.

Global Styles

As a reminder, Global Styles refers to the system that defines and manages global aesthetics allowing overall site styles, theme styles, and blocks to work well together. The Global Styles work remains a major focus for this month. The important tasks for the month are:

Follow along:

You can follow the progress of this focus in this overview issue.

Navigation Screen

The new Navigation Menu screen and Navigation block will continue to be iterated on and polished. In particular, work is being done to create a true drag and drop experience and to explore improving the selection/focus experience (feedback welcome). In an effort to expand the functionality allowed within navigation, work is being done to explore adding different kinds of blocks other than links.

Follow along:

You can follow the progress of this project on this project board.

Refining the interface

The previous releases saw a big UI update for the editor canvas and the inserter. The team will continue to iterate based on the remaining tasks and the user feedback. The remaining tasks here include:

Follow along:

You can follow the progress of this focus in this overview issue

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

As part of expanding the block editor to other screens in the adminadmin (and super admin), work continues to improve the widget screen including finding bugs in the legacy widget block, ensuring synchronization, and more. Depending on the work done here, the screen should be ready to leave the experimental state and receive additional feedback soon. 

Follow along:

You can follow the progress of this focus by reviewing issues with the [Feature] Widgets label.

Areas to be aware of:

Block & PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party Developers

@aduth just merged this pull request to update default block categories which should be available in next week’s plugin releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software.. This could be particularly impactful for block implementers, since the default categories have changed. For now, please review this drafted devnote here as a point of reference for this change. 

Theme Developers

@epiqueras recently broke down all template tags alongside their block equivalent in order to lay the groundwork for Full Site Editing: 

“The idea is for everyone in the community, especially those very familiar with traditional theme development, to contribute to this list. There might be things we are missing. There might be things we could lose.”

Please check out this overall issue and share what might be missing. 

Ways to Help:

While the above items are our focuses, don’t forget that you can always help with triage, needs testing issues, good first issues and reviewing PRs. If there’s anything we can do to makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). contributing easier, let us know in the comments or in #core-editor chats. While we can’t promise to fix everything, we’d appreciate being aware of any blockers.

#core-editor #gutenberg-next

WordPress 5.4.2 RC 1

WordPress 5.4.2 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). 1 (RC 1) is now available for testing!

There are two ways to test the WordPress 5.4.2 release candidate: try the WordPress Beta Tester 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 (you’ll want to select the point releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. nightlies option), or you can download the release candidate here (zip).

What’s in this release candidate?

5.4.2 Release Candidate 1 features 20 bug and regression fixes on both coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and default themes.

WordPress Core updates

  • #49956 – Spammers able to share unmoderated comments
  • #49749 – Registering rest routes with a slash-prefixed namespace give inconsistent results
  • #49798 – Default WordPress favicon in dark mode browsers
  • #49808 – WordPress 5.4: Deprecated: tag_row_actions is deprecated since version 3.0.0
  • #50121 – About page: correcting the order of headings
  • #50131 – Absent custom favicon triggers wp-adminadmin (and super admin) .htaccess/.htpasswd prompt on frontend in FIrefox
  • #49353 – button padding issue in edit plug on small device

Theme updates

The following updates were made to the default themes. You will not receive these updates if updating using the WordPress Beta Tester plugin. You must download the RC 1 package directly.

  • #37926 – Twenty Eleven & Twenty Twelve: Dropdown categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. 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. exceeds parent div when strings are long enough
  • #45865 – Twenty Nineteen: Consider decreasing the font size for widget titles
  • #48803 – Twenty Twenty: Custom post typeCustom Post Type WordPress can hold and display many different types of content. A single item of such a content is generally called a post, although post is also a specific post type. Custom Post Types gives your site the ability to have templated posts, to simplify the concept. that doesn’t support author, shows author
  • #48916 – Twenty Twenty: anchor links don’t work in mobile menu
  • #49088 – Twenty Twenty: Add icon for g.page links (Google business profile)
  • #49316 – Twenty Twenty missed license for images.
  • #49320 – Twenty Twenty: aligncenter>figcaption missing text-align: center; feature
  • #49322 – Twenty Twenty: Submenu items disappear underneath the 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.
  • #49435 – Twenty Twenty: inconsistent top and bottom margins for .alignwide and .alignfull on Chrome vs Safari (cross browser issue)
  • #49699 – Twenty Nineteen: Center- and right-aligned heading accents appear broken
  • #49793 – Twenty Twenty: Images in list blocks are not positioned correctly
  • #49893 – TwentyTwenty: TikTok and ResearchGate Social Icons
  • #49932 – Small Typo in Twenty-Twenty

What’s next?

Committers: The dev-reviewed workflow (double committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. sign-off) still applies when making any changes to the 5.4 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"..

The official 5.4.2 releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. is still scheduled for Wednesday, June 10, 2020. Happy Testing!

#5-4-2, #minor-releases

Dev Chat Summary: June 3, 2020

@whyisjake facilitated on this agenda. @sageshilling is the author of this summary, and @marybaum is your marginally faithful editor.

Announcements

@chanthaboune had three: 

  1. CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. has two brand-new team reps – @francina and @audrasjb! See more here.
  2. @chanthaboune will host office hours with Matt at WordCamp Europe this weekend.
  3. Release squads for the rest of 2020 are pretty close to final, with one update outstanding.

@whyisjake pointed the group to the latest Gutenberg news, which included a near-weekly releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software.–this time to version 8.2.

Upcoming releases: 5.4.2

@whyisjake shared the status of the next minor.

After a smooth release-candidate launch just hours before devchat, he confirmed, “We are looking really great for a release on the tenth.” Check the Trac milestone here and you’ll see for yourself!

Component Updates

@swissspidy expects to share a merge proposal for sitemaps next week 🙂 based on this pull request. He commented that folks are “adding the finishing touches here and there until we have something we believe is ready to merge.”

@audrasjb reminded the group that two weeks ago the Plugins and themes auto-update feature got merged, and so far the feedback is pretty good.

The coders on the ticketticket Created for both bug reports and feature development on the bug tracker. are adding a few more hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same., and @audrasjb pointed to two relevant tickets that need copy review by Friday, when @audrasjb will submit them for final review. @m_butcher, @yvettesonneveld and @marybaum are on the task.

The two tickets are #50215 and #50268. If you’re reading this, you too can look at the copy and add your suggestions!

Open Floor

(Ed. note: Got a pressing topic for Open Floor? Add it to the agenda post as a comment, and come to the chat. It’s in 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/., so you don’t even have to comb your hair! )

From comments on the agenda:

@glorialchemica asked for an update on the full-sitesite (versus network, blog)-editing, or FSE, for short, project.
@chanthaboune responded.

So, the form to show interest has been closed, and I believe that the process of reaching out to everyone has started. The point at which actual feedback outreach and processing begins is a little fluid, since it’s tied to development timelines but it should get going in the next month or so if I recall correctly. In my absence, @annezazu will be driving the bulk of that work.

@chanthaboune

@annezazu announced that she was in the process of inviting everyone who’d signed up to a private Slack chat where folks could try things out and communicate efficiently; a lively discussion followed, with several keepers of WordPress history reminding the group of relevant incidents in the history of the project.

The result: @annezazu immediately made a public space for FSE and will take the private one down shortly.

@timothyblynjacobs asked for feedback from the Build/Test Tools maintainers on #50251. @jorbin took a look and said, Looks good. I’m going to commit it

@francina reminded the group about Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. at WCEU!

@joyously mentioned there was a meeting about the editor and 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., and FSE.  She asked if there will be another one? 

@desrosj I think that meeting was more to help the Customizer maintainers shape their expectations of where their expertise would be needed throughout the FSE process. 

@whyisjake ended the meeting at the top of the hour.

If you’d like more depth about anything the Core team discussed, you can read the full chat transcript here.

#chat, #core, #dev, #summary

WordPress 5.5: Call for Tickets

With 5.4 released, let’s officially kick-off 5.5! As we do with each releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software., we want to fix bugs, add new tools and makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). WordPress the best user experience. 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 (and full sitesite (versus network, blog) editing) are still at the top of the WordPress goals list, but what other tickets do you think need some attention in this release cycle?

Share Your Feedback!

  • What do you want to see included in 5.5?
  • What are current UXUX User experience pain points?
  • What features can we add or iterate on?
  • Component Maintainers: what tickets of yours do you think will be ready to ship in 5.5 and need some review/feedback/approval/etc?

Note: Adding your ticketticket Created for both bug reports and feature development on the bug tracker. here won’t necessarily guarantee inclusion. But no one can fix things they can’t see, so bravely share your thoughts!

Deadline April 30, 2020

#5-5

Core Team Reps for 2020+

Now that voting for CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team Reps has concluded, I’m pleased to announce that the new Core Team Reps for 2020 (and beyond) are Francesca Marano (@francina) and Jb Audras (@audrasjb)!

Francesca Marano

Francesca is the WordPress Community & Partnerships Manager at SiteGround, one of the largest independent web hosting companies where the quality of service stands above it all. Francesca is also part of the global WordPress Community Team and co-led the releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. of WordPress 5.3 and 5.4. One of the things she is most proud of is her blogblog (versus network, site) C+B, which helped many creative female entrepreneurs find their path throughout the years. As an accomplished educator, community leader, and public speaker, you can find her around the world talking about hosting, WordPress, community, open-source, women in tech, and small businesses.

Jb Audras

Jb hails from Ardèche, France and is currently CTO at Whodunit, a well-known French WordPress agency. He started using WordPress in 2007 and became Widgets and Menus components maintainer a few years ago. Jb served as the AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. over the last 2 years, took the role of release leadRelease Lead The community member ultimately responsible for the Release. on half a dozen of minor releases, and helped as focus lead on WP 5.3, WP 5.4 and now on WP 5.5. When he’s not contributing to WordPress, Jb loves to listen over and over to the same good ole Neil Young songs, learn new cool diabolo tricks and to practice bouldering.

From myself and @helen (the outgoing Core Team Reps), we’re excited to see these two wonderful contributors step up to their new role and are looking forward to a fruitful and productive year ahead for the team!

#team-reps

Dev Chat Agenda for June 3rd, 2020

👋 Howdy, y’all. Here is the agenda for the weekly coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. dev chat happening tomorrow: Wednesday, June 3, 2020, 1:00 PM PDT

Announcements

  • 2020 WordPress Release Squads
  • Core Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. Announcements

Recent Makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility)./Core Posts

WordPress 5.4.2

  • RC planned for June 3rd, releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. June 10th.

Component Check-In and Status Updates

  • News from components
  • Components that need help/Orphaned components
  • Cross-component collaboration
  • Featured 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 Updates for 5.5.
    • Core Auto-updates
    • XML Sitemaps

Open Floor

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

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

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

2020 WordPress Release Squads

Excellent progress has been made on WordPress 5.5 so far, and I’m here to do some updates! One of the big things missing from that post was some clarity around who was joining the releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. squad to help makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). sure this is a success. This post has the names we know, and I’m happy to take corrections or suggestions as well. 🙂

  • Release leadRelease Lead The community member ultimately responsible for the Release.: Matt Mullenweg @matt
  • Release coordinator: Jake Spurlock @whyisjake
  • Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. PM: David Baumwald @davidbaumwald
  • CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech: Sergey Biryukov @sergeybiryukov
  • Editor Tech: Ella van Durpe @ellatrix
  • Editor Design: Michael Arestad @michael-arestad
  • Media Tech: Andrew Ozz @azaozz
  • 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) Tech: JB Audras @audrasjb
  • Docs coordinator: Justin Ahinon @justinahinon
  • Marketing/Release Comms: TBD

Joining simultaneously is the WordPress 5.6 release squad! I’ve tagged all of them here, but have left out role assignments. If they make it part way through the ride along process of WP5.5 and decide it’s not what they signed up for after all, then they can step back and someone else can join. 🙂 The WP5.6 release squad will be announced in a roundup/kickoff post of their own.

@afshanadiya @alliennimmons @amandahdm @amykamala @anchenlr @angelasjin @anyssa @annezazu @aurooba @Azhiyadev @bethannon1 @bethsoderberg @breannmcdede @cguntur @chanthaboune @daydah @elmastudio @eringoblog @estelaris @francina @helen @hellofromTonya @isabel_brison @jainnidhi @katiejrichards @laurora @luminuu @m_butcher @marybaum @mbguery @meaganhanes @meher @mekalekahi @melchoyce @metalandcoffee @michelleames @monikarao @newyorkerlaura @planningwrite @poena @rebasaurus @sarahricker @shitalmarakana @sncoker @thelmachido @thewebprincess @tray @trisha_cornelius @whitneyyadrich @yvettesonneveld

#5-5 #5-6 #planning

WordCamp Europe Office and Listening Hours

@matt and I are looking forward to seeing everyone this week, either at Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. or in the great line up of scheduled sessions. One of the highlights of these events is the time to be together and share our stories, and not be able to be in person makes that a little harder.

This year, Matt and I are offering office hours together! If you would like to grab some time with us, please sign up with Calendly. A Zoom link will be added to your calendar invite after booking.

I will also be offering additional office hours on Saturday, June 6th. You can sign up for one of those sessions here. All appointments will be 15 minutes with a 5 minute break to allow for transition time.

See you soon!

Core Team Reps: Submit Your Votes

In April we opened up nominations for new CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team Reps to replace myself and @helen. Nominations have closed so now its time for voting!

You can find the poll below. Since we’re aiming for two reps to be elected this time, you can select up to two people to vote for.

What Are Team Reps?

In the WordPress open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. project, each team has on average one or two representatives, abbreviated as reps.  Some teams have more than two, but for the sake of sanity sticking with two for now keeps things simpler.  And for the historians out there, the role goes way back to 2012.

Historically with the Core team, the team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. duration was around a year, though some reps stuck around longer if there was a particularly good fit.

Anyone who serves as a “team rep” is responsible for communicating on behalf of the Core team to the other contributor groups via weekly updates, as well as occasional cross-team chats.  Reps are also consulted on Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/., helping find someone within the Core team attending an event who can help lead a Core table.  Full details on the Team Rep role is on the Team Update site.

It is not called “team lead” for a reason.  While people elected as team reps will generally come from the pool of folks that people think of as experienced leaders, remember that the team rep role is designed to change hands regularly.

This role has a time commitment attached to it.  Not a huge amount, but in my experience, it’s at least one hour a week.

Here are the main tasks:

  • Writing regular Core team recaps and posting it in Updates
  • Keeping an eye on the moving parts of the team to be able to report for quarterly updates (example)
  • Occasionally helping releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. leads with devchat agenda posts, chats, and summaries

More details on coordinating devchat are available in the Core handbook.

Over the year, the team might decide to add one or two people to help: some teams have up to five, six people, depending on how much work there is. For now, we’re going to be electing two team reps and, if the need arises later in the year, we can elect further people to serve in this role.

Ok then… let’s get us two new reps!

Where Can I Vote?

You can vote in the public poll here. You can vote for up to two people at the same time, but once you have submitted your vote you won’t be able to vote again.

If you have any questions, please feel free to ask in the comments.  I will be happy to reply (or look to past team reps for input)… thanks!

This poll will remain open until Thursday, May 28, 2020, after which team reps will be selected based on the votes received.

#team-reps

Editor Chat Agenda: 3 June, 2020

Facilitator and notetaker: @ajitbohra

This is the agenda for the weekly editor chat scheduled for 2020-06-03 14:00 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/..

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

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

#agenda#core-editor#editor-chat

#agenda, #core-editor, #core-editor-agenda, #gutenberg