Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Onboarding new persons #87

Open
wants to merge 23 commits into
base: master
Choose a base branch
from
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Create Charter.md
OliverFendt committed Feb 10, 2020
commit aced73dfe471abbae998440f3979fdb3c09a69b7
27 changes: 27 additions & 0 deletions Charter.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@

## Overview

Sharing creates value operates much like a meritocratic, consensus-based community project. Anyone with an interest in the project is encouraged join the community, contribute to the project, and participate in the decision making process. This document describes how that participation takes place and how to set about earning merit within the project community.
Please also check our:
[Code of conduct](./CODE_OF_CONDUCT.md)
[Contribution policy](./CONTRIBUTING.md)

## Structure
Everybody is welcome to join the community of this project. Anyone can use the artifacts developed in this project in accordance to the licenses which are valid to the particular artifact, there are no other constraints.



## Contributions
User contributions are highly welcome since they enable the project team to ensure that they are satisfying the needs of those users.

There are many ways to contribute to the project. Contributions to the documentation, case studies, website content, integration scenarios code and test cases are governed under the contributing guidelines, relevant licensing guidelines and terms of use of our website.

Since the overall purpose of this project is to build an OSS compliance toolchain with open source tools we will not accept contributions, which might put a non open source tool into the toolchain.

## Decisions
Decisions about the future of the project are made with the Developers through discussion with all members of the team who wish to participate in the discussion, from the newest Developers to the most experienced one. All project management discussion takes place in team meetings and on the oss-based-compliance-tooling@groups.io mailing list.
In order to ensure that the project is not blocked by endless discussion and continual voting, the project operates a policy of lazy consensus. This allows the majority of decisions to be made without resorting to a formal vote.


## License policy
We follow a simple and clear approach in regard to licensing. All artifacts which are documentation are to be licensed under CC-BY-SA-4.0. All artifacts which are code (including tests) are licensed under MIT.