Weekly Chats

Performance weekly chats are held on Tuesdays and the current meeting time is always up-to-date on the Meetings calendar. Chats are held in the #core-performance channel and last for one hour.

All are welcome to attend the weekly chats to share updates, ask questions, and learn more about the Team’s work. An agenda is posted to Make WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. on Mondays and a meeting summary is posted there after the chat. Both agendas and summaries are viewable in the #performance-chat tag.

Running the chat

Top ↑

Creating the agenda

The weekly chat agenda should be posted on Monday, at least 24 hours before the chat on Tuesday. NOTE: Posting agendas and meeting summaries requires that your 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/ account has permissions to access and edit content on https://make.wordpress.org/wp-admin/. If you do not have this access, you can request it in the #meta channel

  • Clone the most recent agenda from https://make.wordpress.org/core/wp-admin/edit.php
  • Update the meeting date in the title, post content, and URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org slug in the right Post sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme.
  • Modify the agenda as needed. Our regular agenda is for announcements, focus areas updates, and Infrastructure updates, but additional agenda items may come up via 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/ (e.g. module proposals) or from discussions in previous chats.
  • Publish the agenda
  • Add a comment with +make.wordpress.org/performance/ to cross-post the agenda to the Make Core Performance blog

Top ↑

Facilitating the chat

  • At the start time, use /here command to signal the meeting start
  • Request updates for each focus area by tagging the POCs for each group. The Performance Lab CODEOWNERS file is an up-to-date list of focus areas and their current POCs.
  • Give POCs a few minutes to respond, and if there’s no reply, move on to the next focus area
  • If there is still time after updates
  • End the meeting at the top of the hour with </end meeting>

Top ↑

Taking notes

It’s easiest to take notes during the meeting by cloning the most recent summary from https://make.wordpress.org/core/wp-admin/edit.php and updating as the meeting takes place. You can always “clean up” in advance of posting.

Note that users’ display names in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. do not necessarily match their wordpress.org usernames. You can use the URL https://profiles.wordpress.org/SLACKMEMBERID to easily find a Slack user’s wordpress.org username. You can easily and find copy a user’s Slack Member ID by clicking on their name in Slack, selecting the three dots next to Huddle, and selecting Copy member ID.

Top ↑

Sharing the meeting summary

  • On the cloned summary post, update the meeting date in the title, post content, and URL slug in the right Post sidebar
  • Update the “meeting agenda here” to link to this week’s agenda and “beginning here on Slack” to your /here message in Slack
  • For the links in each “Feedback requested” section, click through and update the number of issues for each as needed
  • Publish the summary
  • Add a comment with +make.wordpress.org/performance/ to cross-post the summary to the Make Core Performance blog

Last updated: