The Community Team uses the 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/ repository @WordPress/Community-Team
All team-wide tasks, projects, and tracking start and branch out from our main repository dedicated to the Community Team. We currently manage Community Team focused task and project management covering Issues tracking:
- Vetting of Event Applications, which currently covers our 2 event types:
- WordCamps and Events Applications
- MeetupsMeetup Meetup groups are locally-organized groups that get together for face-to-face events on a regular basis (commonly once a month). Learn more about Meetups in our Meetup Organizer Handbook. Applications
- A General Master Board to track current repetitive, role-specific, tasks of the Community Team and its members (soft-usage, currently mostly in use for 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. and Administrative team tasks.)
Purpose
This documentation is designed to facilitate the WordPress Community Team’s adoption, onboarding, and usage of GitHub Project Management tools starting with Event application tracking.
This is aimed as a first step towards enhancing operational practices within the WordPress ecosystem.
Its key purposes include:
- Simplifying Onboarding: To ease the Community Team into GitHub, offering a straightforward guide for tracking events in a transparent and focused workflow fostering accountability.
- Boosting Efficiency: Streamline event applications by leveraging GitHub’s tools, aiming for a more organized, visually driven, people-focused process – allowing easier identification of available tasks for contributors with availability to claim.
- Enhancing Transparency: Increase transparency, accountability, and Contributions through better tracking, attribution, metrics, organization-wide visibility and collaboration opportunities between projects and across-team.
- Recognizing Contributions: Improve the visibility, acknowledgement, and attribution of team member contributions for roles and tasks previously not tracked or logged to users’ 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/ profiles.
- Insightful Decision-making: Utilize new available metrics, analytics, and insights allowing iterative continuous process improvement, decision-making, and data-informed status updates.
- Standardizing Operations: lead and encourage the Standardization of tools, workflows, automation, and processes across the WordPress.org project from cohort, projects, to the x-team level, setting a precedent for best practices.
- Encouraging Improvement: Adopt an iterative approach to enhance processes, beginning with event application vetting management, setting the stage for ongoing enhancements. Constant Improvement becoming a more integral part of Team and Contributor culture.
This guide serves as a concise blueprint for the Community Team’s transition to GitHub, aiming to streamline project and task management, beginning with the tracking of Event Application Vetting, as we foster a culture of continuous improvement and collaboration within the WordPress community.
The GitHub Event Tracker
Start at the official Community Team’s repository here: @WordPress/Community-Team
The GitHub Event Tracker is currently used to organize and manage applications vetting by Event Supporters and Program Supporters.
The GitHub issues allow the those contributing to the vetting of an application more visibility and also a good overview of the status of who is doing the vetting, if a review is needed and if the vetting is complete.
