A Month in Core – March 2025

Here’s some aggregate data for March 2025 about WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. contribution on TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/..

Please note:

  • These data only include code contributions to WordPress codebase, not contributions on 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/ repositories such as 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/ (but it still include Gutenberg package merges and related backports).
  • The committers data only includes commits to trunk. Branch backports are not taken into account for now.
  • The raw data for this post are available on this public spreadsheet (opens in a new tab). You might find it easier to read.
  • All the links for the graphics below open a new tab to display them in full size.

General Trac overview

Ticket numbers are based on the Trac timeline for the period above.

In March, the WordPress Core team shipped 226 commits (+104 compared to last month). 173 tickets were opened (+25), 193 tickets were closed (-12), and 36 were reopened (+11).

This month, 190 people contributed to WordPress source code using Trac (-25 compared to last month, which is expected given we entered 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./RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. cycles), and 34 people made their very first contribution to WordPress Core ♥️ (-8).

Components activity

How did March’s commits break out by Core Component?

The most prolific components were:

  • Editor with 19 commits (15%)
  • Coding Standards with 16 commits (13%)
  • Build/Test Tools with 14 commits (11%)
  • Media with 11 commits (9%)
  • Bundled Themes with 10 commits (8%)
  • General with 7 commits (6%)
  • 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/. with 5 commits (4%)
  • Upgrade/Install with 4 commits (3%)
  • Themes with 4 commits (3%)
March 2025 Core commits distribution across WordPress Core components

Contributors data retrieved from WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ profiles

The data below comes from matching contributors’ usernames, as mentioned in Trac props, with their profiles on WordPress.org.

One caveat: this ignores usernames that did not match a profile on dotorg, plus any that had blank or unusable country/company information (“The Universe”, “Unicorn land” or “Planes, Trains, and Busses” are not known countries 🙂).

Countries stats

In March, people from at least 31 countries contributed to WordPress Core.

The next graphs show the number of props received by country and the number of contributors from each country. The top 10 countries, based on the number of props received, are these (evolution since last month is provided between parenthesis):

CountryContributionsContributors
India112 (+49)43 (+7)
USA81 (+7)19 (-8)
France49 (+15)9 (+3)
Italy28 (-6)2 (-3)
Australia25 (+15)3 (+2)
Russia18 (=)3 (+1)
Bangladesh15 (+8)11 (+4)
Sweden14 (-14)1 (=)
Georgia14 (+14)1 (+1)
Switzerland12 (-3)1 (=)
March 2025 Core contributions (props) by country
March 2025 Core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. (people) by country

Five for the Future related stats

In March, people from at least 68 different companies/organizations (-5 since last month, which was expected given we entered beta/RC cycle) contributed to WordPress Core.

The next graphs show the number of props received by organization and the number of contributors from each organization. The top 10 organizations, based on the number of props received, are these (evolution since last month is provided between parenthesis):

CompanyContributionsContributors
10up72 (+22)11 (+4)
rtCamp56 (+20)21 (+5)
Whodunit49 (+15)8 (+5)
Yoast40 (-24)3 (=)
Automattic27 (-13)16 (-4)
Accessible WD24 (+14)1 (=)
Google22 (-8)4 (=)
Human Made17 (-1)1 (-3)
GoDaddy14 (+5)1 (=)
Emilia Capital10 (-5)1 (-1)
March 2025 Core contributions (props) by organization
March 2025 Core contributors (people) by organization

What did March hold for Core Committers?

14 Core Committers committed code to the trunk branch in WordPress SVNSVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https://subversion.apache.org/. repository this month (-4 compared to last month).

Of the 125 commits to the trunk branch (+21 compared to the previous month), 30 (24%) were made by people working at Whodunit, 24 (19%) from employees of 10up, 19 (15%) from people working at Yoast, and 7 (6%) by Bluehost and Google.

AccountCommitsCountryCompanyMember since
audrasjb30FranceWhodunit2011
joedolson23USAAccessible WD2008
sergeybiryukov19RussiaYoast2007
joemcgill13USA10up2008
peterwilsoncc11Australia10up2008
desrosj7USABluehost2009
johnbillion6Human Made2005
adamsilverstein4USAGoogle2012
mamaduka4GeorgiaGoDaddy2009
jorbin22009
timothyblynjacobs2StellarWP2012
flixos902USAGoogle2012
ryelle1USAAutomattic2009
westonruter1USAGoogle2007

Thanks to @francina for proofreading this post.

#core

Test Team Update: 7 April 2025

Test Ticket Queue 🎟

 👉🏻 “(change: N)” represents changes from prior week (unless noted).

 📊 Current totals (since March 31, 2025):

  • Need testing info: 18 (change: +2)
  • Need reproduce issue: 2042 (change: +5)
  • Need patch testing: 193 (change: +1)
  • Need unit tests: 104 (change: -2)
  • Need review (have patch and unit tests): 258 (change: +6)

🟢 New/Changed two weeks:

  • Need testing info: 3 (change: +3)
  • Need reproduce issue: 6 (change: -3)
  • Need patch testing: 4 (change: 0)
  • Need unit tests: 0 (change: -3)
  • Need review (have patch and unit tests): 8 (change: -3)

 🟣 Closed two weeks:

  • Need testing info: 0 (change: -1)
  • Need reproduce issue: 1 (change: 0)
  • Need patch testing: 0 (change: -3)
  • Need unit tests: 1 (change: +1)
  • Need review (have patch and unit tests): 3 (change: -14)

To discuss queries used in this report, please comment below, or connect with the Test Team over in #core-test.

+make.wordpress.org/test/

#test

Plugin Review Team: 17 March 2025

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 Status Change Stats

  • Plugins requested : 234
  • Plugins rejected : 135
  • Plugins closed : 136
  • Plugins approved : 121

Plugin Queue Stats (current)

  • Plugins in the queue (new and pending)* : 1502
    • (older than 7 days ago)** : 1202
    • (2025-03-10 – 2025-03-16) : 232
    • (new; not processed or replied to yet)* : 309
    • (pending; replied to)* : 1193
    • (pending; waiting on author)* : 1063
    • (pending; waiting on reviewer)* : 121
    • (pending; waiting on reviewer, email not yet sent)* : 9

Help Scout Queue Stats

  • Total Conversations: 883
  • New Conversations: 551
  • Customers: 718
  • Conversations per Day: 110
  • Busiest Day: Monday
  • Messages Received: 574
  • Replies Sent: 1323
  • Emails Created: 359

* : Stat reflects current size of queue and does not take into account ‘date’ or ‘day’ interval
** : Stat reflects activity only within the ‘recentdays’ from today

#plugins

Test Team Update: 17 March 2025

Test Ticket Queue 🎟

 👉🏻 “(change: N)” represents changes from prior week (unless noted).

 📊 Current totals (since March 10, 2025):

  • Need testing info: 16 (change: 0)
  • Need reproduce issue: 2031 (change: +8)
  • Need patch testing: 196 (change: -4)
  • Need unit tests: 105 (change: 0)
  • Need review (have patch and unit tests): 250 (change: -5)

🟢 New/Changed two weeks:

  • Need testing info: 1 (change: 0)
  • Need reproduce issue: 12 (change: +7)
  • Need patch testing: 7 (change: 0)
  • Need unit tests: 1 (change: -5)
  • Need review (have patch and unit tests): 15 (change: +4)

 🟣 Closed two weeks:

  • Need testing info: 0 (change: -2)
  • Need reproduce issue: 0 (change: -3)
  • Need patch testing: 1 (change: -5)
  • Need unit tests: 1 (change: +1)
  • Need review (have patch and unit tests): 13 (change: +1)

To discuss queries used in this report, please comment below, or connect with the Test Team over in #core-test.

+make.wordpress.org/test/

#test

Themes team update April 30, 2024

i) 🎟 Theme directory stats

Currently,

  • 0 new ticket is waiting for review.
    • 0 tickets are older than 4 weeks
    • 0 tickets are older than 2 weeks
    • 0 tickets are older than 1 week
    • 0 tickets are older than 3 days
  • 40 tickets are assigned.
    • 4 ticket is older than 4 weeks
    • 6 ticket is older than 2 weeks
    • 9 tickets are older than 1 week
    • 25 tickets are older than 3 days
  • 1 is approved but is waiting to be made live.

In the past 7 days,

  • 757 tickets were opened
  • 770 tickets were closed
    • 749 tickets were made live.
      • 45 new Themes were made live.
      • 704 Theme updates were made live.
      • 1 more were approved but are waiting to be made live.
    • 20 tickets were not approved.
    • 0 tickets were closed-newer-version-uploaded.

Note: These stats include both the new theme tickets and updated theme tickets as well.

Number of reviewers: 5 (@acosmin@kafleg@fahimmurshed@vowelweb@bijayyadav)

ii) 💻 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. Theme Stats

  • 15 Block themes are currently being reviewed
  • 12 Block theme has been live in the last 7 days

iii) 💡HelpScout Stats

In the past 7 days,

Email Conversations 12Messages Received 17
Replies Sent 15Emails Created 0
Resolved 13Resolved on First Reply 77%

iv) 📊Extras

  • Create Block Theme 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 now has 10000+ active installs. There are 55 active issues and 4 Pull requests in GitHub.
  • Theme Check Plugin has 6 PRs and 38 issues.

v) 📝Handbook Stats

#themes, #weekly-updates

A Month in Core – February 2025

Here’s some aggregate data for February about WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. contribution on TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/..

Please note:

  • These data only include code contributions to WordPress codebase, not contributions on 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/ repositories such as 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/ (but it still include Gutenberg package merges and related backports).
  • These data only includes commits to trunk. Branch backports are not taken into account for now.
  • The raw data for this post are available on this public spreadsheet (opens in a new tab). You might find it easier to read.
  • All the links for the graphics below open a new tab to display them in full size.

General Trac overview

Ticket numbers are based on the Trac timeline for the period above.

In February, the WordPress Core team shipped 104 commits. 148 tickets were opened, 205 tickets were closed, and 25 were reopened.

This month, 215 people contributed to WordPress source code using Trac, and 42 people made their very first contribution to WordPress Core ♥️

Components activity

How did February’s commits break out by Core Component?

The most prolific components were:

  • Coding Standards with 15 commits (14%)
  • Editor with 14 commits (13%)
  • Administration with 9 commits (9%)
  • General with 8 commits (8%)
  • Build/Test Tools with 8 commits (8%)
  • Bundled Themes with 7 commits (7%)
  • Security with 6 commits (6%)
February 2025 Core commits distribution across WordPress Core components

Contributors data retrieved from WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ profiles

The data below comes from matching contributors’ usernames, as mentioned in Trac props, with their profiles on WordPress.org.

One caveat: this ignores usernames that did not match a profile on dotorg, plus any that had blank or unusable country/company information (“The Universe”, “Unicorn land” or “Planes, Trains, and Busses” are not known countries 🙂).

Countries stats

In February, people from at least 31 countries contributed to WordPress Core.

The next graphs show the number of props received by country, and the number of contributors from each country. The top 10 countries, based on the number of props received, are these:

CountryContributionsContributors
USA7427
India6335
France386
Italy345
Sweden281
Greece194
Russia182
UK167
Switzerland151
Australia104
Germany107
February 2025 Core contributions (props) by country
February 2025 Core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. (people) by country

Organizations stats

In February, people from at least 73 different companies/organizations contributed to WordPress Core.

The next graphs show the number of props received by organization, and the number of contributors from each organization. The top 10 organizations, based on the number of props received, are these:

CompanyContributionsContributors
Yoast643
10up507
Automattic4020
rtCamp3616
Whodunit343
Google304
Human Made184
Emilia Capital152
Accessible WD101
Bluehost91
GoDaddy91
February 2025 Core contributions (props) by organization
February 2025 Core contributors (people) by organization

What did February hold for Core Committers?

18 Core Committers committed code to the WordPress SVNSVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https://subversion.apache.org/. repository this month.

Of the 104 commits, 26 (25%) were made by people working at Whodunit, 20 (19%) from people working at Yoast, 14 (13%) from employees of 10up, and 13 (12%) by Human Made employees.

AccountCommitsCountryCompanyMember since
audrasjb26FranceWhodunit2011
sergeybiryukov18RussiaYoast2007
johnbillion13Human Made2005
peterwilsoncc1010up2008
joedolson7Accessible WD2008
desrosj6USABluehost2009
flixos905USAGoogle2012
joemcgill4USA10up2008
mamaduka3GeorgiaGoDaddy2009
jorbin22009
adamsilverstein2USAGoogle2012
poena2SwedenYoast2008
karmatosed12006
bernhard-reiter1Automattic2008
swissspidy1SwitzerlandGoogle2008
spacedmonkey1UKSpacedmonkey2009
westonruter1USAGoogle2007
davidbaumwald1USADream Encode2016

Thanks to @benjamin_zekavica, @francina for proofreading this post.

#core

Test Team Update: 3 March 2025

Test Ticket Queue 🎟

 👉🏻 “(change: N)” represents changes from prior week (unless noted).

 📊 Current totals (since Feb 24, 2025):

  • Need testing info: 18 (change: -1)
  • Need reproduce issue: 2018 (change: +1)
  • Need patch testing: 205 (change: -8)
  • Need unit tests: 105 (change: +5)
  • Need review (have patch and unit tests): 259 (change: -5)

🟢 New/Changed two weeks:

  • Need testing info: 2 (change: +2)
  • Need reproduce issue: 4 (change: -7)
  • Need patch testing: 14 (change: +4)
  • Need unit tests: 2 (change: +1)
  • Need review (have patch and unit tests): 21 (change: +8)

 🟣 Closed two weeks:

  • Need testing info: 2 (change: +2)
  • Need reproduce issue: 21 (change: +18)
  • Need patch testing: 1 (change: -2)
  • Need unit tests: 0 (change: -1)
  • Need review (have patch and unit tests): 8 (change: 0)

To discuss queries used in this report, please comment below, or connect with the Test Team over in #core-test.

+make.wordpress.org/test/

#test

Plugin Review Team: 17 February 2025

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 Status Change Stats

  • Plugins requested : 207
  • Plugins rejected : 103
  • Plugins closed : 18
  • Plugins approved : 96

Plugin Queue Stats (current)

  • Plugins in the queue (new and pending)* : 1403
    • (older than 7 days ago)** : 1154
    • (2025-02-10 – 2025-02-16) : 165
    • (new; not processed or replied to yet)* : 246
    • (pending; replied to)* : 1157
    • (pending; waiting on author)* : 991
    • (pending; waiting on reviewer)* : 155
    • (pending; waiting on reviewer, email not yet sent)* : 11

Help Scout Queue Stats

  • Total Conversations: 761
  • New Conversations: 409
  • Customers: 548
  • Conversations per Day: 95
  • Busiest Day: Sunday
  • Messages Received: 552
  • Replies Sent: 1019
  • Emails Created: 216

* : Stat reflects current size of queue and does not take into account ‘date’ or ‘day’ interval
** : Stat reflects activity only within the ‘recentdays’ from today

#plugins

Our Strengths and Challenges

Hello all, and thanks for welcoming me so warmly. I’m new to this role of Executive Director, but this is my third year helping our wonderful community work together. During that time, I’ve worked with a lot of teams and have been able to see what seems to be working well for most of us.

For the most part, the WordPress contributors excel at:

  1. Sharing knowledge freely, for the common good
  2. Seeking efficient and effective solutions to complex problems
  3. Communicating courteously in our shared public spaces
  4. Pointing out exceptions and possible risks in implementation
  5. Raising concerns about fairness and possible conflicts of interest
  6. Jumping in to help when the need is great

Working with multiple teams across the project has also given me the chance to identify some things we all struggle with. I’ve received feedback from contributors, too, about where they feel more support is needed. Here are some of the places where I see we (contributors of all types) can have the most impact over the course of the year.

For the most part, WordPress contributors need help with:

  1. Coordinating on collaborative work between teams
  2. Aligning our work better to project goals/values
  3. Understanding team roles, leadership structures, and decision making
  4. Clarifying the differences between 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. and open commit
  5. Tracking conversations and progress across the project
  6. Raising project-wide concerns more easily
  7. Improving how we recognize and celebrate success

We can start solving some of these things right away (please join me in using this P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/. for talking about project-wide work for starters). Others will take some exploration and planning.

What is missing from this list? What kind of support do you need to do your best work? Which of the above do you think is most urgent? Share your thoughts in a comment on this post

After people have had a chance to weigh in, I’ll follow up with some next steps!

Addressing Overlapping Initiatives and Improving Collaboration Across Teams

An in-person meeting during 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. Europe was convened to address the overlapping initiatives among various WordPress contributor groups and explore ways to enhance collaboration and streamline efforts. The primary goal was to avoid duplication of work and ensure that all teams were aligned and working efficiently towards shared objectives.

Meeting Subject: Addressing Overlapping Initiatives and Improving Collaboration Across Teams
Teams/Groups Involved: Sustainability Team, DEIB Working Group, Five for the Future Working Group, Contributor Mentorship Working Group, Community Team, 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. Team, Dashboards Working Group
Facilitator: Angela Jin – Head of Programs & Contributor Experience
Attendees:

  • Josepha Haden Chomphosy @chanthaboune – Executive Director of the WordPress project
  • Chloe Brinkmann @cbringmann – Operations/Communication
  • Naoko Takano @naoOpen 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 Manager / Five for the Future initiative
  • Patricia Brun Torre @patricia70 – Facilitator of the Contributor Mentorship Group
  • Courtney Robertson @courane01 – Meta Team and Project Health Working Group
  • Isotta Peira @peiraisotta – Community 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.
  • Nora Ferreirós @noradriana, Nahuai Badiola @nahuai, Thijs Buijs @yellowlime – Sustainability Team
  • Birgit Olzem @coachbirgit – DEIB Working Group

The meeting took place in person during WordCamp Europe on June 14th, 2024.

Key Discussions

Introduction and Purpose

Angela Jin opened the meeting by expressing excitement about the gathering and emphasizing the importance of understanding each group’s focus areas to prevent duplication of efforts and improve collaboration.

Team Introductions and Project Overviews

Sustainability Team

The Sustainability Team, represented by Nora Ferreirós, Nahuai Badiola, and Thijs Buijs, has focused primarily on environmental projects like the WP Sustainability Plugin, and the Sustainable Events Handbook due to time constraints. They aim to expand their work to include socio-economic and environmental pillars, with ongoing projects like making WordPress events more sustainable and developing a 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 to measure website environmental impact.

Project Health Dashboard

Courtney Robertson discussed the Project Health Working Group’s involvement in exploring dashboard options to gather better statistics and metrics for contributors and the need for better documentation to support team reps during turnover. They are considering whether to build their systems or use SaaS solutions.

DEIB Working Group

Birgit Olzem highlighted the DEIB Working Group’s focus for 2024 on extending the contributor handbook to be more inclusive and accessible. They are conducting surveys to assess DEIB status within the WordPress community at both local and international levels. The intended purpose of the DEIB working group is to be a shared resource for all contributor teams on how to apply the DEIB principles into their daily routines.

Contributor Mentorship Program

Patricia Brun Torre explained the mentorship program’s evolution from earlier contributor working groups. The program aims to improve onboarding and create closer connections with initiatives like Five for the Future.

Overlapping Projects and Communication

The attendees recognized significant overlaps in their projects, especially concerning contributor onboarding and sustainability. Discussions highlighted the need for better coordination and communication among teams. There was a consensus on the value of regular cross-team check-ins and hangouts to share current projects and focus areas.

Challenges and Solutions

Several challenges were identified, including the perception of the sustainability team’s role and the need for clear documentation processes within Meta. The group discussed potential solutions like forming a central team for culture and sustainability, while maintaining specific focus areas under this umbrella. Concerns were raised because of the community’s perception of the term “Sustainability.” This term is often perceived as focusing only on environmental sustainability.

Proposed next steps

Forming a Singular Team

The attendees agreed on the potential benefits of forming a singular team to address contributor culture, sustainability, and onboarding comprehensively. This new team would focus on integrating efforts and providing clear resources for new and existing contributors.

Enhanced Communication

To improve communication and avoid duplication, the group proposed regular cross-team hangouts and using existing channels like the Team Reps channel and P2s for updates and collaboration.

Documentation and Awareness

Emphasizing the importance of documentation, the group suggested creating detailed guides and resources to help team reps and contributors navigate their roles and projects effectively. Additionally, raising awareness about each team’s efforts within the community was seen as crucial for fostering a cohesive and informed contributor base.

Conclusion

The meeting concluded with a commitment to continue discussions and refine the proposed collaboration structure. A follow-up meeting will be scheduled to finalize details and ensure all teams are aligned on the next steps.

Rough dates to follow-up with next steps:

  • Follow-up meeting via Zoom Call: mid-July
  • Singular team decision (structure, collaboration protocol, and name/identity): early August

Please leave your thoughts and feedback to this discussion here as a comment before July 12, 2024

Props

Thanks to @nao, @courane01, @cbringmann, @peiraisotta for reviewing and leaving feedback on this post. Thanks also to @patricia70, @noradriana, @nahuai for giving your blessing after reviewing. A special thanks to @courane01 for recording (with consent of all participants) and providing the transcription of the meeting.