Refresher: What’s Meta 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. responsible for?
The Meta team makes WordPress.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/, provides support, and builds tools for use by all the contributor groups. If you want to help make WordPress.org better, sign up for updates from the Meta blog.
Attendance
@tellyworth, @sergey, @valentinbora, @clorith, @poena
Facilitator: @tellyworth
Note taker: @valentinbora
Actionable points
- @dufresnesteven local dev setup process and identifying missing components
- @tellyworth to clarify who’s to take a fresher and more complete dump of the live database (pruned and sanitized) for easier local setups
- @tellyworth to reach out for advice on marketing ourselves better to new contributors
- @valentinbora to march forward on tickets #5017, #5018, #5015, #5008
- @clorith to further specify how to optimize the relationship with meta committers
Next meeting
Thursday, February 26, 2020, 22:00 (see all #meta meetings here)
Topic: Contributing to Meta
@valentinbora mentioned he found it very gratifying to work on Meta due to changes potentially going live faster than with Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress., and wanted to find out whether new contributors could be encouraged to consider joining the effort
@sergey shared an interesting WordPress.tv talk he liked on the topic
@tellyworth went on to say that the Meta dev environment is a bit difficult to set up and would like to see the barrier for entry lowered.
@valentinbora confirmed that was the case but not as difficult as it looked at first sight. He suggested simply improving the documentation first, while working on a more fully-blown means of local setup
@poena mentioned they had a theme triage earlier and the attendees didn’t know what the meta environment was or what the Meta team was responsible with
@valentinbora stressed out the goals to be lowering the barrier to entry and increasing motivation for new contributors to join
Topic: Tickets requiring attention
@tellyworth mentioned a decrease in the overall number of Meta tickets, which is commendable
@valentinbora raised awareness to #5017, #5018 and #5015 while emphasizing the last two to cause some friction in the migration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. process. See more details about it by checking the Summary for Docs Team Meeting: February 10, 2020
@valentinbora also mentioned #5008 and #5013 to be awaiting feedback from Design
@tellyworth emphasized the Support Forums as being the component with most open tickets and @valentinbora praised @clorith for the helpful Bug Scrub held recently
@clorith stressed the importance of defining a focus area ahead of time for a good scrub in order to avoid getting lost in details and opinions across some of the lengthier tickets
@clorith and @tellyworth agreed that an approach where we’d ask a committer to quickly review and close a well-defined set of tickets would make a lot of sense to improve delivery
Transcript
https://wordpress.slack.com/archives/C02QB8GMM/p1581544979268900
#meeting, #meeting-notes
