CONTRIBUTING.md, CODE_OF_CONDUCT.md

Author: philpher0x

CODE_OF_CONDUCT.md

@@ -0,0 +1,55 @@
+# Code of Conduct
+
+## Our Pledge
+
+We as contributors, maintainers, and participants pledge to make participation in this project a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, 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:
+
+- Demonstrating empathy and kindness toward other people.
+- Being respectful of differing opinions, viewpoints, and experiences.
+- Giving and gracefully accepting constructive feedback.
+- Taking responsibility, apologizing to those affected by our mistakes, and learning from the experience.
+- Focusing on what is best for the community and the project.
+
+Examples of unacceptable behavior:
+
+- 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 explicit permission.
+- Other conduct which could reasonably be considered inappropriate in a professional setting.
+
+## Enforcement Responsibilities
+
+Project maintainers are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior they deem inappropriate, threatening, offensive, or harmful.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned with this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all project spaces, and also applies when an individual is officially representing the project in public spaces. Examples include using an official project email address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Reporting
+
+If you experience or witness unacceptable behavior, report it to the maintainers by opening a private security advisory or by contacting maintainers through repository channels.
+
+All reports will be reviewed and investigated promptly and fairly.
+
+## Enforcement Guidelines
+
+Maintainers may follow these Community Impact Guidelines when determining consequences:
+
+1. Correction
+2. Warning
+3. Temporary Ban
+4. Permanent Ban
+
+## Attribution
+
+This Code of Conduct is adapted from the Contributor Covenant, version 2.1:
+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html

CONTRIBUTING.md

@@ -0,0 +1,69 @@
+# Contributing to mppx-go
+
+Thanks for contributing to `mppx-go`.
+
+## Before You Start
+
+- Read [README.md](./README.md) for architecture, examples, and package layout.
+- Review [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md).
+- Check existing issues and pull requests to avoid duplicate work.
+
+## Development Setup
+
+Requirements:
+
+- Go `1.25+`
+
+Install dependencies and verify the project:
+
+```bash
+go mod download
+go test ./...
+```
+
+## Branches and Pull Requests
+
+1. Fork the repository and create a feature branch from `main`.
+2. Make focused changes with clear commit messages.
+3. Add or update tests for behavior changes.
+4. Run formatting, linting, and tests locally before opening a PR.
+5. Open a pull request with:
+   - a short summary of what changed,
+   - reasoning behind the change,
+   - test evidence (command output or explanation),
+   - any migration notes if relevant.
+
+## Code Style
+
+- Keep public APIs clear and documented.
+- Prefer small, composable functions and explicit errors.
+- Preserve backward compatibility unless the change is clearly breaking and documented.
+
+Formatting and linting:
+
+```bash
+gofmt -w .
+golangci-lint run
+```
+
+If `golangci-lint` is not installed, install it first:
+
+```bash
+go install github.com/golangci/golangci-lint/cmd/golangci-lint@latest
+```
+
+## Testing Guidelines
+
+- Add unit tests for all new logic.
+- Add regression tests for bug fixes.
+- Keep tests deterministic and isolated (no hidden network or external state dependencies unless explicitly needed).
+
+Run:
+
+```bash
+go test ./...
+```
+
+## License
+
+By contributing, you agree that your contributions are licensed under the project license in [LICENSE](./LICENSE).

README.md

@@ -254,3 +254,8 @@ func main() {
 go build ./...
 go test ./...
 ```
+
+## Contributing
+
+- [Contributing Guide](./CONTRIBUTING.md)
+- [Code of Conduct](./CODE_OF_CONDUCT.md)