Umbraco Community Teams: The Core Collaborators

Note: this team was previously known at the PR Team and has now been renamed to better reflect the activities of the team.

Focus areas

To communicate effectively about contributions and surrounding processes by improving contributing guidelines on GitHub and making them friendly for first-time contributors.
Managing the Umbraco CMS Issue Tracker - triaging, labeling, assisting in prioritization and escalation.
Engaging with, onboarding, and coaching new contributors to the CMS
Providing support to Hackathons in a number of ways:

Page about Hackathons with guidelines and resources on Our as well as a GitHub page providing info (similar to meetups.md).
Hackathon organizer's guide on Our.
Use meetups and panel discussions/festival events to inform the community about the structure of the team, achievements and future goals, as well as reaching out for input.

Create a workspace for PR team and contributors to allow community members to receive answers in real-time.
Set out a minimum standard for documentation for pull requests and issues. Create an automated reply to a label we create that informs the contributor that we’re requesting more information and why.
Flesh out the PR and issue templates with more to-the-point information guiding the contributor.
Refining the process for dealing with incoming pull requests to the Umbraco CMS in a predictable and reliable way.
Managing the issue tracking - triaging, labeling, assisting in prioritization and escalation.
Appointing and empowering new members to the team.
Organizing and holding bi-weekly follow-up online meetings - Discuss the current state of the Umbraco CMS repository, potential improvements, and plans going forward.
Writing and publishing follow-up and updates blog posts on umbraco.com, including reporting on relevant metrics.
Open up the bi-weekly HQ meeting to PR team to have a community presence.
Promoting ‘up for grabs’.

Supporting hackathons to ensure that contributions at events such as those are valuable to the CMS and to reduce disappointment for contributors.
Redefine the purpose of Hackathons in order to focus on first-time contributors, providing them with the support and guidance they could use while attending while maintaining support for repeat contributors.
Shift focus during hackathons to onboarding contributors as opposed to the number of contributions being the measure of success.
A commitment to attendance/presence from HQ or team in order to provide the above support.

Create a chatbot that answers FAQs on the PR team and community channel.
Creating webinars focusing on success stories and harnessing the experience of the community to reach out to new contributors and existing.

To ensure the pull requests related to the Umbraco CMS documentation get handled in a timely manner
To provide and maintain clear structure and contribution guidelines
To help and encourage new and returning contributors to the Umbraco CMS
To ensure a transparent and open collaboration and exchange with the HQ dev team and the other community teams
To encourage recurring contributors through the fostering of the friendly experiences on the repository.
To onboard new contributors by making the contributing process as friendly and enjoyable as possible.

The team is ideally organized as a group of no more than 6 members:

With a team lead, Steward, in the center, the team is organized around fulfilling different roles according to the skillset and preferences of each.

Ensure transparency and visibility
Provide coaching and training
Provide financial support for travel and accommodations to participate in meetings and events

managing the team,
providing the necessary support to the different members,
and coordinating with the HQ dev team and the stewards of the other community teams.

The team uses a dedicated Slack workspace to communicate and the issue tracker to comment and follow-up on tasks.

In-person meetings are scheduled twice a year: at Codegarden in May and in a team visit to HQ in November.

We're happy to connect with you on Twitter, see "Current team members" below.
We'll soon create a Slack channel which will be available specifically for contributors to ask questions or share remarks.

An online application will be open once a year, typically in September. (A Google form with a link in the corresponding blog post and on Our)
Ad hoc appointments can be made in case a team member chooses to step down.

Terms of agreement

All Community Team members must abide by the Community Teams Agreement.