Guillaume B.B. Van Hemmen
ddad91c367
Introduce a custom Kaniko-based image for OCI container builds, including a wrapper script (`build.sh`) for flexible execution. Added Forgejo CI workflows for PR, branch, and tag builds, along with detailed documentation in the updated README. Licensed under Apache 2.0. Reviewed-on: #1 Co-authored-by: Guillaume B.B. Van Hemmen <GuillaumeHemmen@noreply.git.van-hemmen.com> Co-committed-by: Guillaume B.B. Van Hemmen <GuillaumeHemmen@noreply.git.van-hemmen.com>
87 lines
2.9 KiB
Markdown
87 lines
2.9 KiB
Markdown
# Code of Conduct
|
||
|
||
Thank you for helping make this project a welcoming, friendly, and productive place for collaboration. All community members—maintainers, contributors, and users—are expected to follow this Code of Conduct (CoC) whenever they interact in official project spaces (issues, pull requests, discussions, chat channels, events, etc.).
|
||
|
||
---
|
||
|
||
## 1. Purpose
|
||
|
||
The purpose of this CoC is to:
|
||
|
||
1. Foster a collaborative and respectful environment.
|
||
2. Clarify expectations for behavior.
|
||
3. Provide a mechanism for reporting, addressing, and resolving unacceptable behavior.
|
||
|
||
---
|
||
|
||
## 2. Expected Behavior
|
||
|
||
Project participants are expected to:
|
||
|
||
| Behavior | Examples |
|
||
| -------- | -------- |
|
||
| Be respectful | Use welcoming and inclusive language; be polite in disagreements. |
|
||
| Be considerate | Acknowledge and value different viewpoints. |
|
||
| Be constructive | Offer helpful feedback and focus on solutions. |
|
||
| Be responsible | Take ownership of contributions and mistakes. |
|
||
| Be professional | Communicate in a courteous, positive, and dignified manner. |
|
||
|
||
---
|
||
|
||
## 3. Unacceptable Behavior
|
||
|
||
Examples of behavior that **will not be tolerated** include, but are not limited to:
|
||
|
||
* Insults, threats, or personal attacks.
|
||
* Harassment, bullying, intimidation, or stalking.
|
||
* Public or private disclosure of someone’s confidential information.
|
||
* Excessive profanity or sexually explicit content.
|
||
* Malicious software, spam, self-promotion unrelated to the project.
|
||
* Any illegal activities or encouragement thereof.
|
||
|
||
---
|
||
|
||
## 4. Scope
|
||
|
||
This CoC applies within all official project spaces as well as public spaces when an individual is representing the project. Examples include using an official e-mail address, posting on official social media, or acting as a designated representative at an event.
|
||
|
||
---
|
||
|
||
## 5. Reporting Violations
|
||
|
||
If you observe or experience any behavior that violates this CoC:
|
||
|
||
1. **Privately report** it to the maintainers via:
|
||
`conduct [at] van-hemmen.com`.
|
||
2. Provide as much detail as possible (links, screenshots, timestamps, involved parties).
|
||
3. All reports will be handled **confidentially**.
|
||
|
||
---
|
||
|
||
## 6. Enforcement
|
||
|
||
Upon receiving a report, the maintainers will:
|
||
|
||
1. Acknowledge receipt as soon as possible.
|
||
2. Review and investigate the incident.
|
||
3. Decide on an appropriate action, which may include:
|
||
|
||
* A private warning.
|
||
* Temporary or permanent removal from project spaces.
|
||
* Reversal of contributions (e.g., reverting PRs).
|
||
* Escalation to relevant authorities if required.
|
||
|
||
Decisions of the maintainers are final. Appeals may be considered at the maintainers’ discretion.
|
||
|
||
---
|
||
|
||
## 7. Responsibilities of Maintainers
|
||
|
||
* Uphold and enforce this CoC consistently and fairly.
|
||
* Protect reporters’ confidentiality.
|
||
* Keep records of any incidents and outcomes.
|
||
* Update this document as needed.
|
||
|
||
---
|
||
|
||
Thank you for helping keep this community open, respectful, and productive.
|