-
Notifications
You must be signed in to change notification settings - Fork 31
document EasyBuild governance #374
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
base: develop
Are you sure you want to change the base?
Changes from all commits
3278a3d
4f5f9c4
cb3d3ad
3640351
fe534ba
8cf0d84
128d7d4
7939969
ebfa58c
00c3bf3
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,46 @@ | ||
| <!-- | ||
| A project charter discusses _what the open source project is and why it exists_. Governance discusses _how the open source project operates_. | ||
|
|
||
| Examples | ||
|
|
||
| https://docs.clearlydefined.io/docs/community/charter | ||
| https://openssf.org/about/charter/ | ||
| https://github.com/cncf/foundation/blob/main/charter.md | ||
| https://github.com/mochajs/mocha/blob/main/PROJECT_CHARTER.md | ||
| https://github.com/nodejs/TSC/blob/main/TSC-Charter.md | ||
| Combined charter - governance https://github.com/camaraproject/Governance/blob/main/ProjectCharter.md | ||
| blog about charters https://opensource.org/blog/what-is-open-governance-drafting-a-charter-for-an-open-source-project | ||
| --> | ||
|
|
||
| # Project Charter | ||
|
|
||
| ## 1. Mission | ||
| <!-- Describe the project's purpose and the problem it addresses. Include a short mission statement. --> | ||
|
|
||
| [EasyBuild](https://easybuild.io) is a tool to facilitate the installation of scientific software, | ||
| along with the dependencies it requires. | ||
|
|
||
| The project focuses on collaboration, automation, and software performance. | ||
|
|
||
|
|
||
| ## 2. Scope | ||
| <!-- Define what is within the scope of the project and what is explicitly out of scope. --> | ||
|
|
||
| EasyBuild automates the build and installation process of scientific software. | ||
|
|
||
| Installing software with EasyBuild is usually done from source code, so that the installed software can be optimized | ||
| for the CPU (and GPU) architecture of the system on which it will be used. | ||
|
|
||
| EasyBuild's primary focus is on High-Performance Computing (HPC) infrastructure (a.k.a. [supercomputers](https://en.wikipedia.org/wiki/Supercomputer)). | ||
| As such, it is intended to be used on systems running [Linux](https://en.wikipedia.org/wiki/Linux) as operating system. | ||
|
|
||
|
|
||
| ## 3. Membership | ||
| <!-- Who can join or participate? Are there any requirements (e.g., code contributions, voting eligibility)? --> | ||
|
|
||
| There is currently no registered membership. Any individual or institution may participate by using EasyBuild, contributing to EasyBuild, etc. | ||
|
|
||
|
|
||
| ## 4. Review and Amendment | ||
|
|
||
| Changes to the charter require approval by the Steering Committee. See the [relevant section of the Governance](governance.md#voting-by-sc). |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,125 @@ | ||
|
|
||
| # Contributor Covenant Code of Conduct | ||
|
|
||
| ## Our Pledge | ||
|
|
||
| We as members, contributors, and leaders pledge to make participation in our | ||
| community a harassment-free experience for everyone, regardless of age, body | ||
| size, visible or invisible disability, ethnicity, sex characteristics, gender | ||
| identity and expression, level of experience, education, socio-economic status, | ||
| nationality, personal appearance, race, caste, color, religion, or sexual | ||
| identity and orientation. | ||
|
|
||
| We pledge to act and interact in ways that contribute to an open, welcoming, | ||
| diverse, inclusive, and healthy community. | ||
|
|
||
| ## Our Standards | ||
|
|
||
| Examples of behavior that contributes to a positive environment for our | ||
| community include: | ||
|
|
||
| * Demonstrating empathy and kindness toward other people | ||
| * Being respectful of differing opinions, viewpoints, and experiences | ||
| * Giving and gracefully accepting constructive feedback | ||
| * Accepting responsibility and apologizing to those affected by our mistakes, | ||
| and learning from the experience | ||
| * Focusing on what is best not just for us as individuals, but for the overall | ||
| community | ||
|
|
||
| Examples of unacceptable behavior include: | ||
|
|
||
| * The use of sexualized language or imagery, and sexual attention or advances of | ||
| any kind | ||
| * Trolling, insulting or derogatory comments, and personal or political attacks | ||
| * Public or private harassment | ||
| * Publishing others' private information, such as a physical or email address, | ||
| without their explicit permission | ||
| * Other conduct which could reasonably be considered inappropriate in a | ||
| professional setting | ||
|
|
||
| ## Enforcement Responsibilities | ||
|
|
||
| Community leaders are responsible for clarifying and enforcing our standards of | ||
| acceptable behavior and will take appropriate and fair corrective action in | ||
| response to any behavior that they deem inappropriate, threatening, offensive, | ||
| or harmful. | ||
|
|
||
| Community leaders have the right and responsibility to remove, edit, or reject | ||
| comments, commits, code, wiki edits, issues, and other contributions that are | ||
| not aligned to this Code of Conduct, and will communicate reasons for moderation | ||
| decisions when appropriate. | ||
|
|
||
| ## Scope | ||
|
|
||
| This Code of Conduct applies within all community spaces, and also applies when | ||
| an individual is officially representing the community in public spaces. | ||
| Examples of representing our community include using an official email address, | ||
| posting via an official social media account, or acting as an appointed | ||
| representative at an online or offline event. | ||
|
|
||
| ## Enforcement | ||
|
|
||
| Instances of abusive, harassing, or otherwise unacceptable behavior may be | ||
| reported to the EasyBuild Steering Committee via direct message to one of the | ||
| EasyBuild Steering Committee Members on the EasyBuild Slack channel. Please indicate | ||
| clearly that your message is about a (possible) breach of the code of conduct. | ||
| All complaints will be reviewed and investigated promptly and fairly. | ||
|
|
||
| The EasyBuild Steering Committee Members are obligated to respect the privacy and | ||
| security of the reporter of any incident. | ||
|
|
||
| ## Enforcement Guidelines | ||
|
|
||
| The EasyBuild Steering Committee will follow these Community Impact Guidelines in | ||
| determining the consequences for any action they deem in violation of this Code | ||
| of Conduct: | ||
|
|
||
| ### 1. Correction | ||
|
|
||
| **Community Impact**: Use of inappropriate language or other behavior deemed | ||
| unprofessional or unwelcome in the community. | ||
|
|
||
| **Consequence**: A private, written warning from community leaders, providing | ||
| clarity around the nature of the violation and an explanation of why the | ||
| behavior was inappropriate. A public apology may be requested. | ||
|
|
||
| ### 2. Warning | ||
|
|
||
| **Community Impact**: A violation through a single incident or series of | ||
| actions. | ||
|
|
||
| **Consequence**: A warning with consequences for continued behavior. No | ||
| interaction with the people involved, including unsolicited interaction with | ||
| those enforcing the Code of Conduct, for a specified period of time. This | ||
| includes avoiding interactions in community spaces as well as external channels | ||
| like social media. Violating these terms may lead to a temporary or permanent | ||
| ban. | ||
|
|
||
| ### 3. Temporary Ban | ||
|
|
||
| **Community Impact**: A serious violation of community standards, including | ||
| sustained inappropriate behavior. | ||
|
|
||
| **Consequence**: A temporary ban from any sort of interaction or public | ||
| communication with the community for a specified period of time. No public or | ||
| private interaction with the people involved, including unsolicited interaction | ||
| with those enforcing the Code of Conduct, is allowed during this period. | ||
| Violating these terms may lead to a permanent ban. | ||
|
|
||
| ### 4. Permanent Ban | ||
|
|
||
| **Community Impact**: Demonstrating a pattern of violation of community | ||
| standards, including sustained inappropriate behavior, harassment of an | ||
| individual, or aggression toward or disparagement of classes of individuals. | ||
|
|
||
| **Consequence**: A permanent ban from any sort of public interaction within the | ||
| community. | ||
|
|
||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. How can we enforce such a ban?
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We can only enforce such a ban the best we can. PRs can be closed, users can be blocked from submitting new PRs in github project settings. Of course they could create a new account and use that, but then it would be an untrusted user, and if found out make it even worse. Let's hope we never get there, it's hard to imagine with the current community doing this in conjunction with their day jobs (as it would look very bad to their employer too), but we need to cover the worst case scenario. |
||
| ## Attribution | ||
|
|
||
| This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/), | ||
| version 2.1, available at | ||
| [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html](https://www.contributor-covenant.org/version/2/1/code_of_conduct.html). | ||
|
|
||
| Community Impact Guidelines were inspired by | ||
| [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity). | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it possible/useful to be a bit more explicit here about the privacy of the reporter.. by adding something like "No information that could identify the reporter, or details of the report, will be communicated outside the Steering Committee without the reporter’s explicit consent, except where disclosure is required by law or necessary to address an immediate risk of harm."
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree, something like: 'these reports will be treated with strict confidentiality within the law', might be useful.
The problem with 'the law' could be as different countries have different law.
As EasyBuild originates in Belgium, maybe we explicitly should put down Belgium, or European Law?