65298f767e
- Add comprehensive MLX engine implementation with Python MLX bindings - Implement MLX model discovery, loading, and native inference pipeline - Add MLX feature flag compilation and Apple Silicon hardware detection - Create dedicated GitHub Actions workflow for MLX testing on macos-14 ARM64 - Add MLX documentation to README and wiki with capability descriptions - Implement pre-commit hooks enforcing cargo fmt, clippy, and test validation - Fix GPU backend tests to properly force specific backends instead of auto-detection - Resolve property test race conditions with serial test execution - Update release workflow validation and platform-specific test expectations - Add MLX implementation plan and cross-compilation toolchain support 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
3.1 KiB
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, religion, or sexual identity and orientation.
Our Standards
Examples of behavior that contributes to a positive environment:
- Being respectful and inclusive in discussions
- Focusing on technical merit and project goals
- Providing constructive feedback on contributions
- Accepting criticism gracefully and learning from mistakes
- Focusing on what is best for the community and project
Examples of unacceptable behavior:
- Harassment, trolling, or discriminatory language
- Personal attacks or inflammatory comments
- Publishing others' private information without permission
- Spam, off-topic discussions, or promotion of unrelated projects
- Any conduct that would be inappropriate in a professional setting
Project Focus
This project maintains a clear focus on technical excellence:
- Stay on topic: Discussions should relate to Shimmy's development
- Respect the philosophy: Contributions should align with lightweight, zero-config principles
- Quality over quantity: We value thoughtful contributions over high volume
- Technical merit: Decisions are made based on technical merit and project goals
Enforcement Responsibilities
The project maintainer is responsible for clarifying and enforcing standards of acceptable behavior and will take appropriate corrective action in response to any behavior deemed inappropriate, threatening, offensive, or harmful.
Scope
This Code of Conduct applies within all project spaces, including:
- GitHub repository (issues, PRs, discussions)
- Project communications
- Public representation of the project
Enforcement
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to michaelallenkuykendall@gmail.com.
All complaints will be reviewed and investigated promptly and fairly. The maintainer is obligated to respect the privacy and security of the reporter.
Enforcement Guidelines
The maintainer will follow these Community Impact Guidelines:
1. Correction
Community Impact: Minor inappropriate behavior or technical disagreement. Consequence: Private clarification about the nature of the violation and explanation of why the behavior was inappropriate.
2. Warning
Community Impact: Moderate violation or pattern of inappropriate behavior. Consequence: Warning with consequences for continued behavior.
3. Temporary Ban
Community Impact: Serious violation of community standards. Consequence: Temporary ban from project interaction.
4. Permanent Ban
Community Impact: Sustained inappropriate behavior or severe violation. Consequence: Permanent ban from all project interaction.
Attribution
This Code of Conduct is adapted from the Contributor Covenant, version 2.0.