Our team

This page lists the people who currently contribute in key roles in the Good Docs Project and what their responsibilities are.

The Good Docs Project is powered by a great community and a team of dedicated folks who keep our project moving forward. We are always looking for more people to help with:

  • Running and participating in working groups.

  • Onboarding and welcoming new community members.

  • Assisting with the project’s IT needs.

If you’re interested in helping out, get in touch with someone from the team you’re interested in. The best way to contact these team members is on our Slack workspace, which you can get invited to by attending one of our Welcome Wagon meetings.

List of teams

Project steering committee

The Project Steering Committee (PSC) is the official managing body for our project.

This team:

  • Has a duty to define and uphold the project’s mission, goals, and plans.

  • Nominates and votes to approve individuals to key community roles and teams.

  • Discusses and votes on project business and major project initiatives, such as requests-for-comment (RFCs).

  • Is chaired by 1-3 individuals, who act as tie-breaking votes and who help ensure the efficiency and effectiveness of the PSC.

The current project steering committee members are:

  • Alyssa Rock, co-chair

  • Michael Park, co-chair

  • Ailine Dominey

  • Bolaji Ayodeji

  • Bryan Klein

  • Cameron Shorter

  • Carrie Crowe

  • Deanna Thompson

  • Lana Novikova

  • Michael Hungbo

  • Michael Vallance

  • Valeria Hernandez

The committee is drawn from members of the community and is based on merit and interest.

The project steering committee:

  • Aims to attract a diverse mix of personal characteristics, reflective of the community we represent.

  • Avoids having employees of any one organization representing a controlling proportion of the PSC.

  • May retire any time. If a PSC member becomes inactive for multiple quarters, it may be time to retire. (Ex-members will typically be welcomed back if they become active again.) An inactive member may be invited to retire. If unresponsive, they may be removed by the existing PSC.

If you are interested in serving on the PSC, let a current member of the PSC know about your interest.

Community managers

This community managers ensure our community is healthy, vibrant, and safe for all who want to participate.

This team is responsible for:

  • Fostering a positive community culture.

  • Growing our community.

  • Onboarding, mentoring, and training community members.

  • Ensuring our community is safe and supported by:

The current community managers are:

  • Alyssa Rock

  • Carrie Crowe

  • Cat Keller

  • Deanna Thompson

If you are interested in serving as a community manager, let one of the community managers know. You can also join the bi-weekly community onboarding and training sync to start volunteering to assist the community managers.

If you experience an incident which makes you feel less safe in our community or less able to be your authentic self, contact the community manager with whom you have the most comfortable relationship and let them know.

The best way to contact these team members is on our Slack workspace in the #ask-a-community-manager channel or through a private direct message. You can get invited to our Slack workspace by attending one of our Welcome Wagon meetings.

For more information, see:

Tech team

The Tech team helps with the project’s IT services and tooling needs, including repository access.

This team:

  • Maintains access to all the project’s IT services and tools.

  • Enforces and maintains our security policies.

  • Consults on IT related requests and needs.

The current Tech team members are:

  • Alyssa Rock

  • Bolaji Ayodeji

  • Bryan Klein

  • Melissa Mergner

  • Michael Park

  • Rachel Estilo

If you are interested in joining the Tech team, let one of the members of this team know. You can also join the bi-weekly DocOps Registry working group, which acts as an entry point for this team.

The best way to contact the team is on our Slack workspace in the #tech-requests channel. You can get invited to our Slack workspace by attending one of our Welcome Wagon meetings.

Template editorial team

The template editorial team has three focus areas:

  • Reviewing templates that are nearing completion to ensure the template:

    • Follows best practices for technical writing.

    • Has no major organizational or structural issues.

    • Has no obvious gaps or missing content.

    • Is consistent with our style guide.

  • Resolves style guide decisions as they arise.

  • Creates the template product roadmap.

The current template editorial team members are:

  • Alyssa Rock (Team Dolphin)

  • Ailine Dominey (Team Alpaca)

  • Cameron Shorter (Team Macaw)

  • Michael Park (Team Macaw)

Chronologue canon editorial team

The Chronologue canon editorial team reviews new Chronologue example proposals to evaluate whether each proposal:

  • Fits in well in the current Chronologue canon and won’t cause conflicts in the world of the Chronologue.

  • Is a good fit for the template being used and the content type being documented. For example, they might help guide the Chronologue member to make the documentation for the right Chronologue publication based on whether that content type would make sense for a commercial or an open source organization.

  • Needs any additional internal documentation in our knowledge base tracking the Chronologue lore.

This team also reviews Chronologue examples as they are nearing completion to make sure that the final documentation still matches the canon and won’t cause conflicts in the Chronologue canon.

This team includes at least one member from each Chronologue working group who are familiar with the Chronologue world and canon. They also assist in socializing Chronologue canon updates with their working group.

The current Chrononologue canon editorial team members are:

  • Alyssa Rock (support)

  • Elliot Spencer (Team Dolphin)

  • Michael Park (Team Macaw, Team Alpaca)

  • Michael Hungbo (Team Dolphin)

  • Ogunkelu Shola (Team Dolphin)

  • PJ Metz (support)

  • Rachel Estilo (Team Dolphin)

  • Venkat Sai (Team Dolphin)

Working group leads

The working group leads help manage our project’s various working groups. They typically chair working group meetings and act as light project managers that keep GitLab issues up to date and communicate the status of open issues to the project maintainers. They help working group members when they are blocked on tasks and coordinate reviews or other resources as needed.

The current working group leads for each working group are:

Working group Lead(s)

Team Alpaca Templates and Chronologue (US/APAC)

  • Ailine Dominey (templates)

  • Deanna Thompson (templates)

  • Michael Park (Chronologue)

Team Macaw Templates and Chronologue (APAC/EMEA)

  • Michael Park (Chronologue)

  • Michael Vallance (templates)

Team Dolphin Templates and Chronologue (US/EMEA)

  • Alyssa Rock (templates)

  • Elliot Spencer (Chronologue)

  • Michael Hungbo (Chronologue)

DocOps registry

  • Bryan Klein

  • Michael Park

UX and outreach

  • Alyssa Rock (outreach)

  • Carrie Crowe (outreach)

  • Lana Novikova (UX)

  • Valeria Hernandez (UX)

To join any of these working groups, see the Community Calendar for meeting times.

Thank you to past team members

We are thankful for the hard work and dedication of these past team members:

Previous PSC members:

  • Aaron Peters

  • Aidan Doherty

  • Ane Tröger

  • Ankita Tripathi

  • Becky Todd

  • Clarence Cromwell

  • Erin McKean

  • Felicity Brand

  • Gayathri Krishnaswamy

  • Jared Morgan

  • Jennifer Rondeau

  • Jo Cook

  • Mengmeng Tang

  • Morgan Craft

  • Nelson Guya

  • Tina Lüdtke

  • Ryan Macklin

  • Viraji Ogodapola