Introducing new Core Team Reps for 2023

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, @marybaum and @audrasjb are pleased to announce that the new Core Team Reps for 2023 are Tonya Mork (@hellofromtonya) and Abha Thakor (@webcommsat)!

Both of them will officially be our new Core Team Representatives starting January 1st, 2023.

More info: results of the electiondetailed results (PDF – 314Kb)

Tonya Mork

Tonya is a leader, architect, engineer (software and electrical), coach, and learner. She became hooked on contributing during the 5.5 release cycle as she prepared to join the 5.6 squad. She’s a full-time contributor, Core 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., and Build/Test Tooling co-maintainer. She’s served in various release squad roles including the 5.9 Release Coordinator, 5.9 Core Tech Lead, 5.7 Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Lead, and 5.6 Triage Lead.

Outside of the project, she’s likely best known as a developer educator and for her journey into WordPress (read on HeroPress, and People of WordPress). She lives in a small fishing village on the shores of Lake Michigan (in the US) with her spouse (celebrated their 36th anniversary this year) and their little doggie (who thinks he’s a cat).

Tonya Mork @hellofromtonya

Abha Thakor

Abha Thakor is an experienced communicator, and digital professional, with a speciality in tech and communities, voice technology, research and innovation. She has been actively involved as a volunteer in WordPress core since the 4.8 release. She has been a notable contributor and on a number of release teams, and encouraged cross team collaboration. She is a component maintainer and involved with helping new contributors get involved with core and the wider project.

She is a meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. organizer and been an organizer for local and Europe-wide WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. and core translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. events, with a focus on encouraging contributors globally and supporting inclusion.

She is also involved in the following projects:

  • Core development blogblog (versus network, site)
  • FSE experiment
  • Release documentation and Learn WordPress tutorials
  • Contributed to supporting dev chat for the last 18 months

From @audrasjb and @marybaum (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

Core Team Reps for 2023: Submit Your Votes

Two weeks ago 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 @marybaum and me. Nominations have closed, so now it’s time for voting!

You can find the poll below. Since we’re aiming to elect two reps, you can vote for up to two people.

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/., to help find someone on the Core team who will be at 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.  It’s an administrative role. While people elected as team reps will generally come from the pool of folks that people think of as experienced leaders, the team rep role is designed to change hands regularly.

This role has a time commitment attached to it. Not a huge amount, but it’s at least one or two hours a week.

Here are the main tasks:

Then… let’s get ourselves two new reps!

Where Can I Vote?

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. @marybaum and I will be happy to reply. Thanks!

This poll will remain open until Friday, December 16, 2022 at 23:59 UTC, after which team reps will be chosen based on the votes received.

Co-authored by @audrasjb and @marybaum.

#team-reps

Nominations for Core Team Reps: 2023 Edition

This post kicks off the election process with nominations to replace Jb Audras (@audrasjb) and Mary Baum (@marybaum) as CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team reps. Jb has been in the role for a couple years and Mary for a year, so 2023 marks the time to get new folks to help!

The Role

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.  It’s an administrative role. 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 it’s at least one or two hours a week.

Here are the main tasks:

How the election works

Please nominate people in the comments of this post. Self-nominations are welcome. The deadline is 2 December 2022.

After that, a poll will be opened for voting. It will stay open for two weeks. The new reps will start their role in January 2023.

If you want to nominate someone in private, please reach out to @audrasjb, @marybaum, or @jeffpaul 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/..

Disclaimer: if you get nominated, please don’t feel like you have to say yes. The polls will only include the names of the people that are responding positively to a nomination.  So feel free to reply with a “Thank you, but no thank you”.

If you have any questions, please feel free to ask in the comments. Finally for reference, here are the 2020 and 2021 nomination posts.

Thanks to @marybaum for co-authoring and to @jeffpaul for reviewing this post.
Special thanks to @webcommsat who helped a lot the current team reps on a number of tasks this year.

#team-reps

New Core Team Rep for 2022

After a call for volunteers, I’m pleased to announce that the new CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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. for 2022 (and beyond) is Mary Baum (@marybaum)!

Mary Baum

Mary is the owner of RacquetPress. She is a self-taught developer, and she is a woman of many talents and hobbies: from online fabric, product design, 3D to landscape and macro photography. She is a self-proclaimed tennis bum.

Mary has been part of multiple release squads in different roles since 2019. She is also the maintainer of two components, Help/About and Quick/Bulk Edit.

Headshot of Mary Baum

I, @francina, am stepping down and @audrasjb will continue until another team representative is found. Do not hesitate to reach out to him or ask in #core if you have questions about the role.

I am excited to see Mary stepping into the role and helping Core with all the adminadmin (and super admin) tasks needed to keep the team moving.

#team-reps

Nominations for Core Team Reps 2022

This post kicks off the election process with nominations to replace @audrasjb and @francina as CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team reps. We have been in the role for over a year now, so 2022 marks the time to get new folks!

The Role

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

It is not called “team lead” for a reason. It’s an administrative role. While people elected as team reps will generally come from the pool of folks that people think of as experienced leaders, 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. role is designed to change hands regularly.

This role has a time commitment attached to it. Not a huge amount, it’s at least two hours a week.

Here are the main tasks:

Full details on the Team Rep role is on the Team Update site.

How the election works

Please nominate people in the comments of this post. Self-nominations are welcome. The deadline is 10 November 2021.

After that, a poll will be opened for voting. It will stay open for about two weeks. The new reps will start their role on January 1st, 2022.

If you want to nominate someone in private, please reach out to @francina or @audrasjb 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/..

Disclaimer: if you get nominated, please don’t feel like you have to say yes. The polls will only include the names of the people that are responding positively to a nomination.  So feel free to reply with a “Thank you, but no thank you”.

If you have any questions, please feel free to ask in the comments, we will be happy to reply.

Thanks to @audrasjb for the peer review.

#team-reps

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 release 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, stare at marvelous landscapes, hiking and rock climbing.

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

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 release 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

Nominations for Core Team Reps

Earlier this month I proposed an election format for updating Core team reps, based on the Community Team model, and discussed the concept in yesterdays devchat.  This post kicks off the election process with nominations to replace @helen and myself (@jeffpaul) as CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team reps.

The Role

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 release leads with devchat agenda posts, chats, and summaries

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

The Community Team has been running the following process which makes for a tried and tested model for the Core Team to similarly try out.  Hat tip to @francina for sharing these details!

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

How the election works

Please nominate people in the comments of this post. Self-nominations are welcome. The deadline is 14 May 2020.

After that, a poll will be opened for voting. It will stay open for ~two weeks.

If you want to nominate someone in private, please reach out to @jeffpaul (that’s me!) or @helen 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/..

Disclaimer: if you get nominated, please don’t feel like you have to say yes.  The polls will only include the names of the people that are responding positively to a nomination.  So feel free to reply with a “Thank you, but no thank you”.

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!

#team-reps

Proposal: Core Team Rep Elections

It’s been an eternity since team reps were updated for the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team.  @helen and I (@jeffpaul) have been serving since before 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/ development began, way longer than team reps usually would… so it’s time to talk about how we update Core team reps.

The Role

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 release leads with devchat agenda posts, chats, and summaries

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

The Community Team has been running the following process which makes for a tried and tested model for the Core Team to similarly try out.  Hat tip to @francina for sharing these details!

Nominating

Nominations happen in the comments of a Core Team Reps Election post (here’s a sample Community Team nominating post).  Self-nominations are welcome.  The deadline for nominations should be around two weeks.  

If you want to nominate someone in private, please reach out to @current-team-rep-1 and @current-team-rep-2 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/..

Disclaimer: if you get nominated, please don’t feel like you have to say yes.  The polls will only include the names of the people that are responding positively to a nomination.  So feel free to reply with a “Thank you, but no thank you”.

Once the deadline has passed for nominating, a comment will be added and pinned to the top:

Nominations are now closed and voting is open until <voting deadline>. Voting details and link here: https://make.wordpress.org/core/<voting-link>/

Voting

After nominations have ended, a poll for voting will be opened and linked from a voting announcement post (here’s a sample Community Team voting post).  It will stay open for around two weeks.

Once the deadline has passed for voting, a comment will be added and pinned to the top:

Voting has concluded and the new team reps will be announced on <date> during the Core devchat.

Once the results have been finalized and announced, a comment will be added and pinned to the top:

Selected Core Team reps are announced here: https://make.wordpress.org/core/<results-link>/

Results

After voting has ended, results should be shared in an announcement post (here’s a sample Community Team results post).  Similarly, the new team rep(s) should be updated on the Team Reps page.

The outgoing team rep(s) should plan to be available for questions and consultation from the incoming team rep(s) as there will undoubtedly be a learning curve as new rep(s) get into the role.

Next steps

I will bring this proposal up in the next devchat on <date> and lacking any major concerns, will work to publish a nominating post after that devchat.

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!

#proposal, #team-reps

Dev Chat Summary: October 10 (5.0 Week 2)

This post summarizes the dev chat meeting from October 10th (agenda, Slack archive).

5.0 planning

  • See @pento’s WordPress 5.0 for Contributors and Committers post:
    • “If you’re an experienced contributor or 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. who has time available during the WordPress 5.0 release cycle, and want to be able to make meaningful contributions towards making WordPress 5.0 awesome” … “Please reply to this post with information about your availability, what components of WordPress you have experience in, and (if you haven’t got involved with 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/ yet) what you feel has been getting in the way.”
    • In that post are some direct actions you can take to help contribute to 5.0, otherwise please review and comment if you’ll be around during the 5.0 release cycle… thanks!
  • Also see review @pento‘s 5.0 commit/branch details if you plan to contribute during the 5.0 release cycle
  • @pento: if you have time to help, please review tickets in the 5.0 milestone to determine whether to keep it in 5.0 (Gutenberg-related), or move to 5.0.1 (other 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) or 5.1 (other feature)
  • @kadamwhiterequest for help testing Lazily Evaluate Translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. Strings (#41305) with input requested by the end of this working week to help remove the blockerblocker A bug which is so severe that it blocks a release. to further Gutenberg localization work
  • Plans for an updated readme.htmlHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. to be committed with contributions open until RCrelease 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).
  • @chanthaboune: collecting blocker items and dates across team reps, will post listing to Make/CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., if you have items to add to the listing please 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.” @chanthaboune directly
    • @matt: 5.0 baseline and goal is 4.9.8 + Gutenberg, thus a lot of things that may have been considered blockers in past major releases are probably going to be reclassified as “nice to have”
  • @matveb: last JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. package included in the Gutenberg 4.0 RC, on track and could be ready for end of the week

Updates from focus leads and component maintainers

  • The Gutenberg / Editor team published Gutenberg 4.0-RC
  • The 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/. team posted their meeting notes including Gutenberg-related tickets that are blocked, “next” tickets, and note on review still needed for #39953. Otherwise @kadamwhite @danielbachhuber are looking for folks with bandwidth to assist with REST API development over the coming weeks, so ping them if you have interest and availability
  • The PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher team posted their meeting notes including the Update PHP page and WSOD protection
  • The Media team posted their meeting notes including 5.0 milestoned tickets and related action items
  • The JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. team posted their meeting notes including preparations for 5.0, the annotations 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. in Gutenberg, and a generic data store API

General announcements

  • See @matt‘s post for details on the Gutenberg Phase 2 Leads, @alexislloyd (design and product) and @youknowriad (technical)
    • Phase 2 is about thinking outside the box, namely the post and page box, to allow Gutenberg to handle entire-site layouts. We will replace widgets with blocks, so any 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. will be able to be used in any registered “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.” for legacy themes, and we will upgrade “menus” to a navigation block.
    • Phases 3 and 4 of Gutenberg at WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. US in December.
  • @audrasjb: 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) team reorganizing, will discuss during next week’s meeting
  • @chanthaboune: as teams identify new/updated team reps, please follow notes on team rep orientation

Next meeting

The next meeting will take place on October 17, 2018 at 20:00 UTC in the #core 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. Please feel free to drop in with any updates or questions. If you have items to discuss but cannot make the meeting, please leave a comment on this post so that we can take them into account.

#5-0, #accessibility, #core, #core-editor, #core-js, #core-media, #core-php, #core-restapi, #dev-chat, #gutenberg, #summary, #team-reps