Add Contributor Covenant Code of Conduct

[twangodev]

This document outlines the Code of Conduct for community members, detailing pledges, standards, enforcement responsibilities, and consequences for violations.

[coderabbitai]

Warning

Rate limit exceeded

@twangodev has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 3 minutes and 7 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 116ffe7 and 713bcdb.

📒 Files selected for processing (2)

• CODE_OF_CONDUCT.md (1 hunks)
• CONTRIBUTING.md (1 hunks)

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch code-of-conduct

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull Request Overview

Adds a Contributor Covenant Code of Conduct document to establish community standards, enforcement, and attribution.

• Introduces Contributor Covenant content (v2.0) with standards and enforcement guidelines
• Provides a reporting contact email
• Includes attribution and reference links

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

Pull Request Overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 7 comments.

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

The security reporting email is missing, which prevents responsible disclosure. Please provide a valid contact (for example, security@ogis.dev) or link to a SECURITY.md; alternatively, reuse the existing conduct@ogis.dev inbox for security reports.

Suggested change

	> You must never report security related issues, vulnerabilities or bugs including sensitive information to the issue tracker, or elsewhere in public. Instead sensitive bugs must be sent by email to .
	> You must never report security related issues, vulnerabilities or bugs including sensitive information to the issue tracker, or elsewhere in public. Instead, sensitive bugs must be sent by email to [conduct@ogis.dev](mailto:conduct@ogis.dev).

[Copilot]

Use American English consistently; change 'licence' to 'license' to match the rest of the document's US spelling (e.g., 'behavior').

Suggested change

	> When contributing to this project, you must agree that you have authored 100% of the content, that you have the necessary rights to the content and that the content you contribute may be provided under the project licence.
	> When contributing to this project, you must agree that you have authored 100% of the content, that you have the necessary rights to the content and that the content you contribute may be provided under the project license.

[Copilot]

This section is left as a TODO. Either provide initial setup and contribution steps (environment setup, build/test commands, how to run linters) or remove the section from the ToC until it’s ready.

Suggested change

	<!-- TODO
	include Setup of env, IDE and typical getting started instructions?
	-->
	### Improving The Documentation
	<!-- TODO
	Updating, improving and correcting the documentation
	-->
	## Styleguides
	### Commit Messages
	<!-- TODO
	-->
	## Join The Project Team
	<!-- TODO -->
	To get started with contributing code to ogis, follow these steps:
	1. **Fork the repository** and clone it to your local machine.
	2. **Install dependencies**:
	```bash
	npm install

3. Set up your development environment:
   You can use any IDE or editor of your choice (e.g., VS Code, WebStorm).
4. Run the project locally:

   npm start

5. Run tests before submitting changes:

   npm test

6. Lint your code to ensure style consistency:

   npm run lint

7. Create a new branch for your feature or bugfix.
8. Make your changes, commit them, and push to your fork.
9. Open a Pull Request on GitHub and fill out the PR template.

Improving The Documentation

To update, improve, or correct the documentation:

1. Edit the relevant markdown files in the docs/ or root directory.
2. Ensure your changes are clear, concise, and follow the existing style.
3. If adding new documentation, update the Table of Contents as needed.
4. Commit your changes with a descriptive message (see Commit Messages below).
5. Open a Pull Request and describe the documentation improvements.

Styleguides

Commit Messages

Please follow these guidelines for commit messages:

• Use the present tense ("Add feature" not "Added feature")
• Start with a short summary (max 50 characters)
• Separate subject from body with a blank line
• Explain the motivation for the change in the body, if necessary
• Reference issues and pull requests when relevant (e.g., "Fixes chore(deps-dev): bump svelte from 5.47.0 to 5.51.5 #123")

Join The Project Team

If you are interested in joining the ogis project team:

• Reach out via GitHub Discussions or open an issue expressing your interest.
• Tell us about your background and how you'd like to help.
• We welcome maintainers, reviewers, and contributors of all experience levels!

[Copilot]

The 'Improving The Documentation' section is a placeholder. Add concrete guidance (doc structure, style guide, how to run docs build/preview, where to file doc issues) or omit it from the document for now.

Suggested change

	### Improving The Documentation
	<!-- TODO
	Updating, improving and correcting the documentation
	-->

[Copilot]

Commit message conventions are marked TODO. Consider adding the project's standard (e.g., Conventional Commits), with examples and scope rules, or remove this section until defined.

Suggested change

	<!-- TODO
	-->
	This project uses the [Conventional Commits](https://www.conventionalcommits.org/) standard for commit messages. Please format your commit messages as follows:

[optional scope]:

**Types**:
- `feat`: A new feature
- `fix`: A bug fix
- `docs`: Documentation only changes
- `style`: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
- `refactor`: A code change that neither fixes a bug nor adds a feature
- `perf`: A code change that improves performance
- `test`: Adding missing tests or correcting existing tests
- `chore`: Changes to the build process or auxiliary tools and libraries such as documentation generation

**Scope** (optional): Use to specify the part of the codebase affected, e.g. `api`, `docs`, `core`.

**Examples**:
- `feat(api): add user authentication`
- `fix(core): handle null pointer exception`
- `docs: update contributing guide`

For more details, see [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/).

[Copilot]

This section is empty. Either document the process (roles, expectations, how to apply) or remove it to avoid confusing contributors.

Suggested change

	## Join The Project Team
	<!-- TODO -->

[Copilot]

Capitalize the proper name 'Node.js' correctly.

Suggested change

	- Provide project and platform versions (nodejs, npm, etc), depending on what seems relevant.
	- Provide project and platform versions (Node.js, npm, etc), depending on what seems relevant.