Skip to content

Files

Latest commit

4a76b46 · Dec 20, 2022

History

History
This branch is 324 commits behind chaoss/community:main.

how-to-contribute

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
Dec 16, 2022
Dec 16, 2022
Dec 16, 2022
Dec 20, 2022
Dec 16, 2022
Dec 16, 2022
Dec 16, 2022
Dec 14, 2022
Nov 25, 2022

Contributing to CHAOSS

👍🎉 Thanks for your interest in contributing to the CHAOSS project! 🎉👍

Who can contribute?

Anyone can contribute to CHAOSS. See https://chaoss.community/participate/ to learn more about how to participate. We are excited to meet newcomers, and we are always ready to support you during your contribution journey.

Which channel should I use if I’m a newcomer?

The best place to start is by joining our CHAOSS Newcomers Slack Channel. Go ahead and introduce yourself; we’ll be happy to greet you there.

Other places you can find us online

Ways to Contribute

There are so many ways to contribute to the CHAOSS project. Here is a short list of places that might interest you:

  • Metrics and metrics model development
  • Software development
  • Website management
  • Event management
  • DEI Event Badge reviewing
  • Graphic design
  • Social media

The CHAOSS project is complex and sometimes requires a bit of time to find the ways to contribute that best suit you. Again, we recommend that you join our CHAOSS Newcomers Slack Channel to get things started.

How do we make decisions?

The basic decision-making mechanism for CHAOSS is a lazy consensus. Each of the software projects or working groups will try to reach a consensus on their decisions after giving a reasonable opportunity to people contributing to them to express their opinion. In this, we welcome all people to join and contribute to our conversations.

When the issues under discussion are perceived to be of importance to the whole CHAOSS community, the same process will be carried on at the CHAOSS level, using the general periodic calls and other communication means for discussion.

If consensus is not reached, the issue may be raised to the CHAOSS board, where consensus and voting may be used to get a final decision on the matter.

In any case, all decisions are subject to the CHAOSS Charter.

Note: By "lazy consensus" we mean, as Apache does a decision-making policy that assumes general consent if no responses are posted within a defined period. For example, "I'm going to commit this by lazy consensus if no-one objects within the next three days."