From 2c1d7fefb0199b6f751036b3c84c246514c61443 Mon Sep 17 00:00:00 2001 From: Alex Bozarth Date: Mon, 26 Jan 2026 17:31:34 -0600 Subject: [PATCH 1/4] docs: add code of conduct Signed-off-by: Alex Bozarth --- CODE_OF_CONDUCT.md | 131 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 131 insertions(+) create mode 100644 CODE_OF_CONDUCT.md diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md new file mode 100644 index 00000000..699b570f --- /dev/null +++ b/CODE_OF_CONDUCT.md @@ -0,0 +1,131 @@ +# 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 by contacting the project team via the [organization members](https://github.com/orgs/generative-computing/people) or by opening an issue on the [GitHub repository](https://github.com/generative-computing/mellea/issues). +All complaints will be reviewed and investigated promptly and fairly. + +All community leaders are obligated to respect the privacy and security of the +reporter of any incident. + +## Enforcement Guidelines + +Community leaders 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. + +## Attribution + +This Code of Conduct is adapted from the [Contributor Covenant][homepage], +version 3.0, available at +[https://www.contributor-covenant.org/version/3/0/code_of_conduct.html][v3.0]. + +Community Impact Guidelines were inspired by +[Mozilla's code of conduct enforcement ladder][Mozilla CoC]. + +For answers to common questions about this code of conduct, see the FAQ at +[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at +[https://www.contributor-covenant.org/translations][translations]. + +[homepage]: https://www.contributor-covenant.org +[v3.0]: https://www.contributor-covenant.org/version/3/0/code_of_conduct.html +[Mozilla CoC]: https://github.com/mozilla/inclusion +[FAQ]: https://www.contributor-covenant.org/faq +[translations]: https://www.contributor-covenant.org/translations From ceab7502d9e05b38c0d26277677c36b04efc5e62 Mon Sep 17 00:00:00 2001 From: Alex Bozarth Date: Mon, 2 Feb 2026 10:58:28 -0600 Subject: [PATCH 2/4] docs: add contact email Signed-off-by: Alex Bozarth --- CODE_OF_CONDUCT.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md index 699b570f..f945b4e4 100644 --- a/CODE_OF_CONDUCT.md +++ b/CODE_OF_CONDUCT.md @@ -59,7 +59,7 @@ representative at an online or offline event. ## Enforcement Instances of abusive, harassing, or otherwise unacceptable behavior may be -reported by contacting the project team via the [organization members](https://github.com/orgs/generative-computing/people) or by opening an issue on the [GitHub repository](https://github.com/generative-computing/mellea/issues). +reported by contacting the project team at Melleaadmin@ibm.com. All complaints will be reviewed and investigated promptly and fairly. All community leaders are obligated to respect the privacy and security of the From 1893b0ce02657eb318ca895a6c005dd70629a070 Mon Sep 17 00:00:00 2001 From: Alex Bozarth Date: Mon, 2 Feb 2026 16:13:40 -0600 Subject: [PATCH 3/4] docs: address review Signed-off-by: Alex Bozarth --- AGENTS.md | 2 ++ CODE_OF_CONDUCT.md | 33 ++++++++++++++++++++++++++++++++- README.md | 1 + 3 files changed, 35 insertions(+), 1 deletion(-) diff --git a/AGENTS.md b/AGENTS.md index b19152ff..748e7b18 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -6,6 +6,8 @@ AGENTS.md — Instructions for AI coding assistants (Claude, Cursor, Copilot, Co > **Which guide?** Modifying `mellea/`, `cli/`, or `test/` → this file. Writing code that imports Mellea → [`docs/AGENTS_TEMPLATE.md`](docs/AGENTS_TEMPLATE.md). +> **Code of Conduct**: This project adheres to a [Code of Conduct](CODE_OF_CONDUCT.md). All contributors, including AI assistants, are expected to follow these community standards when generating code, documentation, or interacting with the project. + ## 1. Quick Reference **⚠️ Always use `uv` for Python commands** — never use system Python or `pip` directly. diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md index f945b4e4..3cffe387 100644 --- a/CODE_OF_CONDUCT.md +++ b/CODE_OF_CONDUCT.md @@ -48,6 +48,10 @@ 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. +### Who Are Community Leaders? + +Community leaders include project maintainers, core contributors with commit access, and individuals explicitly designated by the Mellea project team to moderate community spaces. + ## Scope This Code of Conduct applies within all community spaces, and also applies when @@ -56,15 +60,42 @@ 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. +### Community Spaces + +This Code of Conduct applies to all Mellea project spaces, including but not limited to: + +* GitHub repository (issues, pull requests, discussions, code reviews) +* Discord server +* Project mailing lists and email communications +* Official social media accounts +* In-person and virtual events, meetups, and conferences +* Any other forums created by the project team which the community uses for communication + ## Enforcement Instances of abusive, harassing, or otherwise unacceptable behavior may be -reported by contacting the project team at Melleaadmin@ibm.com. +reported by contacting the project team at melleaadmin@ibm.com. All complaints will be reviewed and investigated promptly and fairly. All community leaders are obligated to respect the privacy and security of the reporter of any incident. +### How to Report + +When reporting a Code of Conduct violation, please include: + +* **What happened**: A clear description of the incident +* **When and where**: Date, time, and location (e.g., GitHub issue #123, Discord channel) +* **Who was involved**: GitHub usernames, Discord handles, or other identifiers +* **Evidence**: Links to relevant conversations or screenshots (if available) +* **Impact**: How this affected you or others + +**Response Timeline**: You will receive an acknowledgment within 48 hours. The project maintainers will review your report and communicate the outcome within 5 business days, or provide an update on the expected timeline for more complex cases. + +**Confidentiality**: All reports are kept confidential. Information will only be shared with those who need to know to investigate and resolve the issue. + +**Appeals**: If you believe an enforcement decision was made in error, you may request a review by emailing melleaadmin@ibm.com with "Appeal" in the subject line. Reviews will be handled by a different maintainer where possible. + ## Enforcement Guidelines Community leaders will follow these Community Impact Guidelines in determining diff --git a/README.md b/README.md index 3a2305cc..599cfb2a 100644 --- a/README.md +++ b/README.md @@ -15,6 +15,7 @@ with structured, maintainable, robust, and efficient AI workflows. [![Ruff](https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/astral-sh/ruff/main/assets/badge/v2.json)](https://github.com/astral-sh/ruff) [![pre-commit](https://img.shields.io/badge/pre--commit-enabled-brightgreen?logo=pre-commit&logoColor=white)](https://github.com/pre-commit/pre-commit) [![GitHub License](https://img.shields.io/github/license/generative-computing/mellea)](https://img.shields.io/github/license/generative-computing/mellea) +[![Contributor Covenant](https://img.shields.io/badge/Contributor%20Covenant-3.0-4baaaa.svg)](CODE_OF_CONDUCT.md) [![Discord](https://img.shields.io/discord/1448407063813165219?logo=discord&logoColor=white&label=Discord&color=7289DA)](https://ibm.biz/mellea-discord) From e0202a14a409154520567395f7599c09bcf911d4 Mon Sep 17 00:00:00 2001 From: Alex Bozarth Date: Wed, 4 Feb 2026 11:12:11 -0600 Subject: [PATCH 4/4] docs: address review Signed-off-by: Alex Bozarth --- CODE_OF_CONDUCT.md | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md index 3cffe387..2beb7568 100644 --- a/CODE_OF_CONDUCT.md +++ b/CODE_OF_CONDUCT.md @@ -50,7 +50,9 @@ decisions when appropriate. ### Who Are Community Leaders? -Community leaders include project maintainers, core contributors with commit access, and individuals explicitly designated by the Mellea project team to moderate community spaces. +Community leaders include project maintainers, core contributors with commit access, +and individuals explicitly designated by the Mellea project team to moderate community +spaces. ## Scope @@ -90,11 +92,16 @@ When reporting a Code of Conduct violation, please include: * **Evidence**: Links to relevant conversations or screenshots (if available) * **Impact**: How this affected you or others -**Response Timeline**: You will receive an acknowledgment within 48 hours. The project maintainers will review your report and communicate the outcome within 5 business days, or provide an update on the expected timeline for more complex cases. +**Response Timeline**: You will receive an acknowledgment within 2 business days. The project maintainers +will review your report and communicate the outcome within 5 business days, or provide an update on +the expected timeline for more complex cases. -**Confidentiality**: All reports are kept confidential. Information will only be shared with those who need to know to investigate and resolve the issue. +**Confidentiality**: All reports are kept confidential. Information will only be shared with those who +need to know to investigate and resolve the issue. -**Appeals**: If you believe an enforcement decision was made in error, you may request a review by emailing melleaadmin@ibm.com with "Appeal" in the subject line. Reviews will be handled by a different maintainer where possible. +**Appeals**: If you believe an enforcement decision was made in error, you may request a review by +emailing melleaadmin@ibm.com with "Appeal" in the subject line. Reviews will be handled by a different +maintainer where possible. ## Enforcement Guidelines