Over the last few days, there have been a few actions taken on Trac and in the WordPress GitHub organization that are aimed at clarifying who is looking after areas of the project, and making it easier for contributors to do their work. Maintainer Cleanup The lists of Core Component Maintainers and Core Bug Gardeners […]
Over the last few days, there have been a few actions taken on Trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. and in the WordPress GitHub 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 by the repository owner. https://github.com/ organization that are aimed at clarifying who is looking after areas of the project, and making it easier for contributors to do their work.
Maintainer CleanupThe lists of Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Component Maintainers and Core Bug Gardeners A contributor who has been given advanced privileges in Trac. have been updated to remove contributors where they have either moved on from contributing to the project, have not contributed regularly to a given component, or have not connected their GitHub and WordPress.org accounts. If you feel that you were removed in error, please DM @desrosj or @jorbin in Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ or comment below and you can be re-added.
As always, anyone is welcome to be a Component Maintainer or Bug Gardener. If you are interested in contributing to the project in these ways, feel free to volunteer in the comments below, share your interest during a Core Dev Chat or in #core, or stop by a component meeting in Slack if the one you’re interested in holds them regularly. Additionally, please ensure your GitHub and WordPress.org accounts are connected.
WordPress Organization GitHub TeamsThe following teams have been added to the WordPress/wordpress-develop repository with triage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.-level access:
Gutenberg: Contributors with multiple PRs merged to Gutenberg 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/. This is roughly the Gutenberg equivalent of Trac bug gardeners.WordPress Core Component Maintainers (newly created): Maintainers have been invited as they are currently listed on the Components page on Make Core.WordPress Core Bug Gardeners (newly created): Existing Trac Bug Gardeners have been invited.Members of the WordPress Core PR Triage team have also been invited to the new WordPress Core Bug Gardeners. Since this group’s permissions and purpose align with the responsibilities of being a Bug Gardener A contributor who has been given advanced privileges in Trac., the old team was unnecessary.
Assigning triage-level access will allow team members to request code reviews from other members of the WordPress organization, assign labels, and generally help garden pull requests.
Efforts have been made to ensure all existing component maintainers and bug gardeners are imported to these groups, but some contributors may have been missed. If you received an invitation, it must be accepted within 7 days. Please comment on this post if you believe you were accidentally missed.
Props @desrosj, @jeffpaul, @lancewillett for pre-publish review.
| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | Proposal: Minor updates to the WordPress Core CSS Coding Standards | 0 | 6.22 | 07-10-2026 |
| 2 | WordPress Contributor Toolkit 1.2: One app for your first Core or Gutenberg contribution | 0 | 9.45 | 25-09-2026 |
| 3 | Call for Code Review Help: Repairing Gutenberg GitHub Actions Workflows for wp/x.y Branches | 0 | 8.13 | 16-10-2026 |
| 4 | WordPress 7.1 Release Candidate Phase | 0 | 11.72 | 05-08-2026 |
| 5 | Changeset [64392]: Tests: Separate theme feature validation tests. Move ... | 0 | 10.65 | 16-10-2026 |
| 6 | WordPress Contributor Toolkit 1.0: A smoother workflow for your first Core contribution | 0 | 10.35 | 14-08-2026 |
| 7 | Performance Chat Summary: 6 October 2026 | 0 | 16.05 | 06-10-2026 |
| 8 | WP Feature Notifications weekly update: 2026-10-16 | 0 | 9.42 | 16-10-2026 |
| 9 | Staying Evergreen: How we automated secure access and repo hygiene in a shared org | 0 | 5.61 | 15-10-2026 |
| 10 | Github Integration Webhook processing delay | 0 | 4.14 | 17-07-2026 |