The core team decided to hold a weekly meeting, focusing on answering questions from new contributors, helping with patches and tickets and going through the good-first-bugs tickets.
Takeaways from Paris
During the WordCamp Europe, the Accessibility team learned a few important things. So, for example, they do not have to try to do every a11y related ticket on their own but show how it should be resolved and let other devs do the patches.
More about this and the other learnings in the post »Takeaways from Paris« by Rian Rietveld.
Weekly meeting for new contributors
From the next week on, there will be a weekly meeting with a focus on new contributors, starting on Wednesday, July 5, at 21:00 a clock. There will optionally be alternative time slots for contributors from other time zones. If you would be interested in another slot, comment below Adam Silverstein’s »Announcing a weekly new contributors meeting« post.
Adam writes: »The new contributors meeting is the perfect place to come if you are new to contributing to WordPress core and have questions!«. More information about the new meeting can be found in his article.
- »Media meeting recap – June 22, 2017«. Among other things, the team discussed the 4.9 focus — one item should be the optimization of full-size images.
- »Dev Chat Summary: June 28th (4.8.1 week 2)«.
- »Multisite Recap for the week of June 26th«.
- »Media meeting recap – June 29, 2017«. Among other things, the team focused on »getting a better understanding of the current product vision for working with media in Gutenberg in order to coordinate priorities and ensure future improvements to the media component align with the needs of the new editor experience.«
- »What’s new in Gutenberg? (June 30)«.
Theme review team
- »Theme Review Meeting Summary: June 27, 2017«. Among other things, the team will not accept newly added Unsplash images as of June 9 because of license changes.
Notes from the Community Summit 2017
Mika Epstein summarizes the topics of the plugin team on the community summit and contributor day in her post »2017 Community Summit Notes«. A few items from the list (partly quoted from the post):
- The team wants to open reviews to everyone with a .org account.
- »Determine the best way to track ‘dependancies’ […] so frameworks and add-on plugins can be clearly indicated and reduce errors«.
- »Design a ‘dashboard’ for people to check the status of their plugins (and themes)«.
More on that can be found in her post.