- Umbraco CMS pull requests
- Responsiveness and recognition
- Structure, process, guidelines
- Input, promotion and content creation
- Guidance for hackathons
- Contribution grooming, standard-setting and providing feedback.
- 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.
Meet the team
- Busra Sengul (Turkey)
- Emma Garland (United Kingdom)
- Georgina Bidder (United Kingdom)
- Jason Elkin (United Kingdom)
- Kyle Eck (United States of America)
- Laura Neto (The Netherlands)
- Michael Latouche (Belgium)
- Sebastiaan Janssen (Umbraco HQ - Denmark)
Main Activities (Short term and ongoing)
- To communicate effectively about contributions and surrounding processes by improving contributing guidelines on GitHub and making them friendly for first-time contributors.
- 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. 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 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.
- Appointing and empowering new members to the team.
- Organizing and holding monthly 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 monthly HQ meeting to PR team to have a community presence.
- Promoting ‘up for grabs’.
Long Term Activities
- 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.
The team is ideally organized as a group of HQ steward and community members:
- 1 HQ employee - steward
- 5-8 community volunteers
With a team lead, Steward, in the center, the team is organized around fulfilling different roles according to the skillset and preferences of each.
HQ support and role
- Ensure transparency and visibility
- Provide coaching and training
- Provide financial support for travel and accommodations to participate in meetings and events
The Steward's role is focused on
- 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 the dedicated Discord channel #contributing to communicate and the CMS issue tracker to comment and follow-up on tasks.
In-person meetings are scheduled once a year at a team visit to Umbraco HQ in November.
Getting in touch with the Team
- We're happy to connect with you on Twitter or Mastodon, see "Current team members" above.
- The #contributing Discord channel is available specifically for contributors to ask questions or share remarks.
Joining the Team
- An online application will be open once a year (a form with a link in the corresponding blog post and on Our Umbraco)
- 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.