Contributing to Polymathy¶
Thank you for your interest in contributing to Polymathy! This guide will help you get started.
Ways to Contribute¶
-
:material-bug:{ .lg .middle } Report Bugs
Found a bug? Open an issue with reproduction steps
-
:material-lightbulb:{ .lg .middle } Suggest Features
Have an idea? Start a discussion or open a feature request
-
:material-code-braces:{ .lg .middle } Submit Code
Fix bugs or implement features via pull requests
-
:material-file-document:{ .lg .middle } Improve Docs
Help make our documentation better
Quick Start¶
- Fork the repository
- Clone your fork
- Create a feature branch
- Make your changes
- Submit a pull request
# Fork via GitHub, then:
git clone https://github.com/YOUR-USERNAME/polymathy.git
cd polymathy
git checkout -b feature/your-feature-name
# Make changes...
git commit -m "Add your feature"
git push origin feature/your-feature-name
# Open a PR on GitHub
What We're Looking For¶
High Priority¶
- Bug fixes with test coverage
- Performance improvements
- Documentation improvements
- Test coverage expansion
Welcome Contributions¶
- New features (discuss first)
- Code refactoring
- CI/CD improvements
- Example code
Before You Start¶
For Bug Fixes¶
- Check existing issues
- Create an issue if none exists
- Reference the issue in your PR
For New Features¶
- Open a discussion or issue first
- Wait for feedback from maintainers
- Proceed only after approval
Pull Request Process¶
- Create focused PRs - One feature/fix per PR
- Write tests - Cover new code with tests
- Update docs - Document new features
- Follow style - Run
cargo fmtandcargo clippy - Pass CI - All checks must pass
Code of Conduct¶
- Be respectful and constructive
- Welcome newcomers
- Focus on the code, not the person
- Accept constructive criticism gracefully
Getting Help¶
- Questions: Open a Discussion on GitHub
- Bugs: Open an Issue
- Security: Email maintainers directly
Next Steps¶
- Development Setup - Set up your development environment
- Code Style - Our coding conventions