The Gutenberg and WordPress core committers have different permissions for different tools… but should this be the case?
Remember that you can listen to this program from Pocket Casts, Spotify, and Apple Podcasts or subscribe to the feed directly.
Program transcript
Hello, I’m Alicia Ireland, and you’re listening to WordPress Podcast, bringing the weekly news from the WordPress Community.
In this program, you’ll find the information from July 15th to 21st, 2024.
WordPress 6.6.1 has been released with 7 core fixes and 9 editor fixes in a version that primarily addresses some CSS style errors.
The Core team has undertaken a process to unify committer permissions across different code repositories (Gutenberg on GitHub and Core on SVN). At WordCamp Europe, it was discussed how committers who have access to one part of the code should have equivalent access in other repositories to avoid bottlenecks and confusion. As a first step, write access and the ability to merge pull requests were granted to Core committers in the Gutenberg repository on GitHub.
It is also proposed that the Gutenberg team on GitHub be a subset of the Core committers in Subversion, requiring the same nomination and approval process, seeking greater alignment between the two groups, and nominating Gutenberg team members who do not have SVN access to obtain it.
In the Developers Blog, a post has been published about new features that allow theme developers to register custom variations of color and typography in WordPress 6.6.
The Accessibility team has opened a call for Team Reps now that their two representatives, after 3 years, must step down.
It is expected that by August 2, the list of interested individuals will be ready for the change.
The Media Corps team has published the results of the survey on the first briefing meeting with a rating of 3.8 out of 5 for effectiveness and 4.3 for organization. Participants appreciated the demonstrations and the ease of asking questions, though they suggested including less technical content and more practical examples of using WordPress.
It was proposed to hold monthly meetings with additional updates via Slack and to provide media kits with shareable resources.
The Community team has updated its venue policy, making some improvements to the current texts that essentially stated that venues with religious or political affiliations were excluded.
It is now explicitly stated that venues with political affiliations are excluded, but for those with religious affiliations, the specific area of worship or with religious iconography is determined, and places where propaganda or promotion of ideas is conducted among organizers or attendees are added. In any case, it is reminded that venues must follow the WordPress Code of Conduct.
Regarding Meetups and the Reactivation Program, the process carried out between April and July is considered closed, and on August 5, the process of closing those groups that have not had events for a while will begin.
And finally, this podcast is distributed under a Creative Commons license as a derivative version of the WordPress Podcast in Spanish; you can find all the links for more information, and the podcast in other languages, at WordPress Podcast .org.
Thanks for listening, and until the next episode!
Leave a Reply