LogoLogo
  • CHAOSS Community Handbook - Table of Contents
  • Handbook Usage
  • ABOUT
    • CHAOSS History
    • Values
    • Roadmap
    • Roles and Responsibilities
    • Community Guidelines
    • Path to Leadership
    • Terminology
      • CHAOSS Specific Terms
      • CHAOSS Committees
      • CHAOSS Community Working Group Terminology
      • CHAOSS Community Mentorship Terminology
    • Terminology Usage
    • General FAQ
  • COMMUNITY
    • Working Groups
      • WG Repository Structure
    • Metrics
      • Releases
      • Translation
      • Metrics FAQ
    • Community Report
    • CHAOSScon
    • CHAOSScast
    • CHAOSS Meetings
  • CONTRIBUTING
    • Development
      • Contributing Workflow
    • Documentation
      • Style Guide
    • Design
      • Design Workflow
      • Design Contribution
      • CHAOSS Visual Identity
    • Outreach
  • MENTORSHIPS
    • Google Summer of Code
    • Google Season of Docs
    • GSoC/GSoD Roles & Responsibilities
    • Outreachy
  • D&I BADGING
    • Overview of the D&I Badging
    • How to contribute
    • Apply for a badge
      • Apply for an In-Person Event
      • Apply for a Virtual Event
    • Reviewing for CHAOSS
      • Apply to Review
      • The Review Process
      • Conflict of Interest Policy
    • Badging Roles
      • Applicant
      • Reviewer
      • Moderator
      • Maintainer
    • The badging-bot
    • D&I Badging Code of Conduct
Powered by GitBook
On this page
  • Naming Convention
  • Base Files
  • Focus areas
  • Metrics
  • General conventions

Was this helpful?

Export as PDF
  1. COMMUNITY
  2. Working Groups

WG Repository Structure

Working Groups that define metrics need to follow the repository structure outlined here

The goal of this document is to describe a uniform structure that CHAOSS Working Groups are currently using for developing metrics. The outcome of this standardizing Working Group repository structure is less overhead for community members moving between WGs and a consistent expectation for new members.

Naming Convention

Below mentioned is the standard naming covention followed by all Working Group repositories -

Base Files

  • /README.md - describes WG, informs about getting engaged, shows off work, meeting information

  • /LICENSE.md - default always MIT in accordance with Charter

  • /CONTRIBUTING.md - describes the technicalities of engaging with the WG through GitHub; explain the DCO sign-off

  • /code-of-comnduct.md - copy of CHAOSS’s Code of Conduct

  • /.gitignore - for system files like .DS_Store

  • /.github/FUNDING.yml - information for where to donate to CHAOSS

  • Other files may exist in the base of WG repositories

Focus areas

  • /focus-areas/ - directory for all metrics work

  • /focus-areas/README.md - a table of focus areas and their goals, linking to the next level

  • /focus-areas/<focus-area-name>/ - directory for metrics in a focus area

  • /focus-areas/<focus-area-name>/README.md - table of metrics in this focus area with questions the metrics answer; linking to specific metrics

Metrics

  • /focus-areas/<focus-area-name>/images/<metric-name>_<image-name>.png - images included in a metric; file-ending can be png/jpg/gif/svg

General conventions

  • DO NOT use spaces in names

  • Use hyphens “-” instead of spaces within names

  • Use underscore to separate different names (e.g., between metric-name and image-name)

  • Use lower case for all file and folder names, except README, LICENSE, CONTRIBUTING, FUNDING which are standard across open source always capitalized

  • Images are always in a sub-directory “images” under the markdown file that references the image

  • The WG repos should have only released and under-review metrics

  • In cases where the metric name is also a descriptor, please use this convention:

    "specific thing being measured"-"further description if needed"

    EX: pull-requests-open.md EX: issues-first-response.md

PreviousWorking GroupsNextMetrics

Last updated 4 years ago

Was this helpful?

/focus-areas/<focus-area-name>/<metric-name>.md - metric detail page, must conform to the standard

template