About The Good Docs ProjectThe Good Docs ProjectTGDP_e14d3fe0-21bc-11ef-9d16-ebc32983ea00TGDP Steering CommitteeThe 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:Michael Parkco-chairTina Lüdtkeco-chairAlyssa RockAne TrögerBolaji AyodejiBryan KleinCameron ShorterCarrie CroweDeanna ThompsonErin McKeanGayathri KrishnaswamyLana NovikovaMengmeng TangMichael VallanceValeria HernandezTGDP Community ManagersThis 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: ^ * Handling Code of Conduct incidents. ^ * Moderating our community forums. ^^ The current community managers are:Alyssa RockCarrie CroweCat KellerDeanna ThompsonTGDP Tech TeamThe 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 RockBolaji AyodejiBryan KleinMichael ParkTGDP Template Product Management TeamThe template product management team are responsible for defining the vision of the template suite product and related value streams. ^^ This team: ^^ * Creates the template product roadmap. ^ * Conducts user research and gathers feedback to determine what initiatives should go into the roadmap. ^ * Coordinates with the template working group to put the roadmap into action (by creating issues to track work, defining priorities, and more). ^ * Ensures our templates have a consistent style and voice. ^^ The current template product team members are:Tina LüdtkeleadAlyssa RocksupportAne Trogerstyle guide leadTGDP Template Editorial TeamThe template editorial team reviews templates when they are nearing completion to ensure the template: ^^ * Follows best practices for technical writing. ^ * Has no major organization or structural issues. ^ * Has no obvious gaps or missing content. ^ * Is consistent with our style guide. ^^ This team includes at least one member from each template working group who are both experienced technical writers and experienced in the template contributing process. They are also experts on our project's style guide and parent style guides. They meet at least once a release cycle (or as needed) to review style questions and make decisions, led by our lead style guide editor. They also assist in socializing the style guide with their working group. ^^ The current template editorial team members are:Ane Trogerstyle guide lead, Team AlpacaAlyssa RockTeam DolphinCameron ShorterTeam MacawMichael ParkTeam MacawTGDP Working Group LeadsThe 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:Team Alpaca Templates and Chronologue (US/APAC)Ailine DomineytemplatesDeanna ThompsontemplatesMichael ParkChronologueTeam Macaw Templates and Chronologue (APAC/EMEA) Michael ParkChronologueMichael VallancetemplatesTeam Dolphin Templates and Chronologue (US/EMEA)Alyssa RocktemplatesMichael HungboChronologueDocOps RegistryBryan KleinMichael ParkUX and OutreachCarrie CroweoutreachTina LüdtkeUXPast Team MembersThank you to past team members ~ We are thankful for the hard work and dedication of these past team members: ^^ Previous PSC members:Aaron PetersAidan DohertyAnkita TripathiBecky ToddClarence CromwellFelicity BrandJared MorganJennifer RondeauJo CookMorgan CraftNelson GuyaRyan MacklinViraji OgodapolaWell documented open source software_e14d41d4-21bc-11ef-9d16-ebc32983ea00To improve the quality and impact of open source project documentation_e14d4314-21bc-11ef-9d16-ebc32983ea00Open SourceSoftwareDocumentationVarious doctypes ~ There is no one thing called "Good Docs"; there are multiple doctypes, each with different purposes and needs. Targeting your writing to the purpose will improve the quality and impact of your project's documentation, often significantly.Best PracticesSoftware DocumentationBuild best practice templates and writing instructions for documenting open source software_e14d43e6-21bc-11ef-9d16-ebc32983ea00Goals of The Good Docs Project ~ Within The Good Docs Project, we build best practice templates and writing instructions for documenting open source software. (Which incidentally are useful for all software and related domains.) ^^ Focus on what you're best at ~ Templates enable significant efficiencies by allowing experts to focus only on the bits they do best.TemplatesEmbed best practices in templates_e14d4468-21bc-11ef-9d16-ebc32983ea001Various writing experts can embed best practices into a template.ContentWrite better content, more efficiently_e14d463e-21bc-11ef-9d16-ebc32983ea002Domain ExpertsDomain experts can write better content, more efficiently, when they have a template to work against.CompliancePolish content by reviewing for compliance against templates_e14d46de-21bc-11ef-9d16-ebc32983ea003Writers can polish the content by reviewing for compliance against the template.2024-06-03https://thegooddocsproject.dev/about/OwenAmburOwen.Ambur@verizon.net