via make.wordpress.org => original post link
Meeting agenda here and the full chat log is available beginning here on Slack.
Announcements
@flixos90: multiple announcementsTeam Rep nominations reminderIf you are contributing to the WordPress/performance GitHub repository (or any WordPress GitHub repository FWIW), please link your WordPress.org and GitHub accounts if you haven’t done so. You can do so at https://profiles.wordpress.org/profile/profile/edit/group/1/If you have been contributing to the team’s efforts (e.g. GitHub, discussions, conversations in this chat, …) but don’t have the “Performance Contributor” badge on your profile, you may request to have it added by requesting to join the group at https://profiles.wordpress.org/associations/performance-contributor/If you are contributing to the WordPress/performance GitHub repository, please be aware of a new rule to avoid naming your regular temporary coding branches something like feature/. That feature/ prefix will be reserved for special protected feature branches going forward@adamsilverstein: other than the ‘feature/’ prefix, are there any other conventions we want to follow / is that documented somewhere?@flixos90: Only feature/ and release/ must not be used for regular coding branches (a pull request to document this has since been opened)Focus group updates