Add Contributor Covenant Code of Conduct

[atong01]

Added Contributor Covenant Code of Conduct to outline community standards and enforcement guidelines.

Summary by Sourcery

Documentation:

• Introduce CODE_OF_CONDUCT.md describing community standards, reporting procedures, and enforcement guidelines for project participation.

[sourcery-ai]

Reviewer's Guide

Adds a standard Contributor Covenant Code of Conduct document to the repository to define community standards, reporting channels, and enforcement guidelines.

Flow diagram for Code of Conduct reporting and enforcement process

flowchart TD
  A[Incident occurs
  in community] --> B[Report sent to
  community leaders
  at alexandertongdev@gmail.com]
  B --> C[Leaders review
  and investigate]
  C --> D{Community impact
  assessment}

  D -->|Minor issue| E[Correction
  private written warning]
  D -->|Single or series
  of violations| F[Warning
  with conditions]
  D -->|Serious violation| G[Temporary ban]
  D -->|Pattern of violations
  or harassment| H[Permanent ban]

Loading

File-Level Changes

Change	Details	Files
Introduce a formal, documented code of conduct for project contributors and community members.	Added a new CODE_OF_CONDUCT.md file containing the Contributor Covenant v2.0 text. Defined expected positive and unacceptable behaviors within the community. Documented enforcement responsibilities, scope, and incident reporting process including a contact email address. Outlined graduated enforcement guidelines (correction, warning, temporary ban, permanent ban) and their associated consequences. Included attribution and reference links to the Contributor Covenant homepage, FAQ, and translations.	CODE_OF_CONDUCT.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've found 2 issues, and left some high level feedback:

• Consider using a project- or organization-level contact address (e.g., a shared alias) instead of a personal email for enforcement to make future maintainer changes easier.
• You may want to clarify in the Enforcement section who specifically counts as "community leaders" for this project (e.g., core maintainer list or role description) to make the reporting process more concrete for contributors.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Consider using a project- or organization-level contact address (e.g., a shared alias) instead of a personal email for enforcement to make future maintainer changes easier.
- You may want to clarify in the Enforcement section who specifically counts as "community leaders" for this project (e.g., core maintainer list or role description) to make the reporting process more concrete for contributors.

## Individual Comments

### Comment 1
<location path="CODE_OF_CONDUCT.md" line_range="108-110" />
<code_context>
+
+### 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.
+
</code_context>
<issue_to_address>
**issue (typo):** Fix double space before "harassment" in the "Permanent Ban" description.

There are two spaces between "behavior," and "harassment" in this line; please change to a single space.

```suggestion
**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.
```
</issue_to_address>

### Comment 2
<location path="CODE_OF_CONDUCT.md" line_range="34-43" />
<code_context>
+* Publishing others' private information, such as a physical or email
</code_context>
<issue_to_address>
**nitpick (typo):** Consider using a consistent spelling for "email" vs "e-mail".

You use "email" in "such as a physical or email address" and "e-mail" in "using an official e-mail address". Please standardize on one spelling for consistency across the document.

Suggested implementation:

```
* Publishing others' private information, such as a physical or email address,
  without their explicit permission

```

Search the rest of `CODE_OF_CONDUCT.md` for "e-mail" and replace it with "email" to maintain consistent spelling throughout the document. For example, change "using an official e-mail address" to "using an official email address".
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

nitpick (typo): Consider using a consistent spelling for "email" vs "e-mail".

You use "email" in "such as a physical or email address" and "e-mail" in "using an official e-mail address". Please standardize on one spelling for consistency across the document.

Suggested implementation:

* Publishing others' private information, such as a physical or email address,
  without their explicit permission

Search the rest of CODE_OF_CONDUCT.md for "e-mail" and replace it with "email" to maintain consistent spelling throughout the document. For example, change "using an official e-mail address" to "using an official email address".

[atong01]

Make this change to use email

[sourcery-ai]

Sounds good. To apply this consistently, update the remaining instance so it reads:

Examples of representing our community include using an official email address,

That will align with the earlier usage:

such as a physical or email address,

Once that change is in, the spelling of "email" will be consistent across the document.