Meta Team Goals 2024

On January 10, 2024, MetaMeta 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. Team Members met to review the goals for 2024. As this was a collaborative session, we opted to use Zoom. Below is a meeting recording, timestamps, and an AI-generated outline of the discussion.

00:04 Meta team discussing goals and challenges

  • Zoom meeting being first for Meta team
  • Discussion about goal planning and management challenges

02:22 Exploring the components section on the meta team site.

  • The speaker discovered the components section at the top of the meta team site.
  • Discussion on managing tabs and accessing the menu on team sites.

07:10 Marketing team has three new leads

  • Marketing team has identified three new leads, one of whom is interested in revamping
  • Collaboration opportunities for the marketing team and user-focused improvements on the site are being discussed.

09:31 Avoiding wasted time and effort in project collaboration

  • Discussion about coordinating work between meta and marketing teams in the same timezone
  • Emphasizing the need to align on project ideas and relevance to avoid rejected work

14:35 Consider displaying project information on the org website or linking to 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. for more details

  • Consider having an explainer that links to something or a dashboard of its own
  • Provide easy access to GitHub repo for relevant information on the website.

17:09 Discussion about organizing GitHub issues and component maintainers.

  • The team is considering putting ideas into GitHub issues and cleaning them up later.
  • There is a discussion about the roles and responsibilities of component maintainers within the teams.

21:29 Dashboards for each component are a good idea

  • Having dashboards on the org site makes sense and provides a solid reference point for more information.
  • Implementing new component-specific tags and ensuring they are used appropriately can improve the usability and clarity of the pages.

23:37 Discussing adding better descriptions to each component

  • They can include links to the GitHub repo or other resources
  • It may be a temporary step to improve the current situation with track tickets

27:50 Improving clarity and guidance for contributors

  • Addressing the need to provide clearer guidance for contributors beyond the initial setup
  • Suggest creating contributor markdown files for individual GitHub repos for easier contribution.

30:00 Centralizing content on and repurposing for the site

  • Using GitHub for repurposing content and adjusting for different repositories
  • Documenting how P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at works with tags and dashboard and making it public for other teams

34:19 Establishing different levels of access and protection to prevent unauthorized access.

  • Discuss the need for protected or intermediate access levels to avoid unauthorized access.
  • Addressing the importance of recording documentation for restricted access and self-service information for contributors.

36:25 Confusion about the meta projects and handbook pages

  • Discussion about the structure and purpose of the project page
  • Consideration of potentially deleting the page until its purpose is clear

40:53 Improving communication and fostering transparency within the community and contributors

  • Discussing the need to address organizational issues before working on meta goals
  • Exploring ways to strengthen the connection between the community and sponsored contributors

43:22 Finding ways to involve contributors effectively

  • Dashboards and project boards could be useful tools for involving contributors

47:54 Lack of clarity on post updates

  • Difficulty in determining current updates and ongoing project management due to outdated posts.
  • Need for clearer tracking of revisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. and updates.

50:09 Improving post visibility and updates

  • Meta team has a clear schedule for meetings and consistent updates
  • Suggests creating a custom post typeCustom Post Type WordPress can hold and display many different types of content. A single item of such a content is generally called a post, although post is also a specific post type. Custom Post Types gives your site the ability to have templated posts, to simplify the concept. with a ‘last updated’ field for improved visibility

54:33 Defining goals for Q2-4 and website redesign for Meta team 2024

  • Discussing foundational stuff and scoping goals for Q2-4, considering time dependencies and community appreciation.
  • Planning to gather ideas for website redesign, addressing the massive website size and post-launch follow-up issues.

56:54 Meta team aims to create a timeline for prioritization

  • A survey will be created to gather ideas and needs from active teams.
  • The survey data will aid in better understanding and incorporating feedback in initial project steps

1:01:09 The importance of mapping connectors and data migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. for new repos

  • The significance of mapping and data migration for new repositories was highlighted, especially to Matt’s recent announcements at the State of the WordState of the Word This is the annual report given by Matt Mullenweg, founder of WordPress at WordCamp US. It looks at what we’ve done, what we’re doing, and the future of WordPress.
  • The collaboration between the marketing and Meta teams was emphasized to outline and scope the implementation.

1:03:16 Team reps for Meta

  • The role of team reps at Meta should be about facilitation.
  • A team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. is important for connecting with new contributors and facilitating Contributor days.