In the spirit of fostering an open, innovative, and welcoming environment, we as members, contributors, and leaders of the KindFi community pledge to make participation in our project and our community 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 centered around revolutionizing the 4th Industrial Revolution through AI and Web3 technologies.
KindFi is on a mission to push the boundaries of what's possible with AI and Web3, building a decentralized future where open-source AI organizations can flourish. Our community values:
- Innovation Excellence: We strive for cutting-edge solutions that advance the intersection of AI and Web3.
- Collaborative Spirit: We believe that diverse perspectives and inclusive collaboration drive the best outcomes.
- Quality Craftsmanship: We maintain high standards in code quality, design, and documentation.
- Open Source Commitment: We are dedicated to building transparent, accessible, and community-driven technologies.
- Continuous Learning: We embrace growth, experimentation, and knowledge sharing.
Examples of behavior that contributes to a positive environment for our community include:
- Technical Excellence: Following our established code style and conventions.
- Collaborative Development: Engaging constructively in code reviews, design discussions, and technical decisions.
- Inclusive Communication: Using welcoming and inclusive language that respects diverse backgrounds and experiences.
- Constructive Feedback: Providing helpful, actionable feedback that helps improve code quality and project outcomes.
- Knowledge Sharing: Actively participating in our Telegram community and helping others learn and grow.
- Quality Contributions: Submitting well-tested, documented code that follows our TypeScript, React, and Next.js conventions.
- Respectful Disagreement: Engaging in technical debates with professionalism and focus on ideas, not personalities.
- Community Support: Mentoring newcomers and helping build an inclusive environment for developers of all skill levels.
Examples of unacceptable behavior include:
- 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 their explicit permission.
- Submitting code that intentionally violates our security guidelines or introduces vulnerabilities.
- Plagiarizing code or claiming others' work as your own.
- Spamming issues, pull requests, or community channels.
- Other conduct which could reasonably be considered inappropriate in a professional setting.
As a community focused on technical excellence, we maintain high standards for code contributions:
All contributors must adhere to our comprehensive code style guide. Key requirements include:
- TypeScript Best Practices: Leverage type safety, avoid
any, use appropriateinterfacevstypedeclarations. - React Conventions: Write declarative, functional components following hooks patterns and composition principles.
- Modern JavaScript: Use ES6+ features, meaningful naming conventions, and RORO (Receive Object, Return Object) patterns.
- File Organization: Follow our lowercase-with-dashes naming convention and appropriate file extensions (
.config.ts,.test.ts,.hook.ts, etc.). - No Default Exports: Prefer named exports for better tree-shaking and import clarity.
- Code Review: All contributions undergo automated review by CodeRabbitAI followed by human review from project leads.
- Signed Commits: All commits must be signed for security and authenticity.
- Branch Naming: Follow our convention:
feat-123-feature-name,fix-456-bug-description, etc. - Documentation: Include appropriate JSDoc comments and update relevant documentation.
- Testing: Ensure code coverage meets project standards with proper unit and integration tests.
- Commit Messages: Use lowercase, descriptive messages under 72 characters.
- Branch Workflow: Create feature branches from
develop, rebase regularly, and follow our branching model. - Monorepo Awareness: Clearly indicate which part of the project your changes affect.
- GitHub Issues: For bug reports, feature requests, and technical discussions.
- Pull Requests: For code contributions following our review process
- Telegram Community: Join our community for real-time collaboration, debugging help, and building connections.
- Documentation: Refer to our live docs for comprehensive guides.
- Read Our Guides: Familiarize yourself with our OSS Contribution Guide.
- Follow Our Conventions: Study our Code Style and Conventions
- Join the Community: Connect with other contributors in our Telegram group.
- Start Contributing: Pick an issue, follow our application template, and submit quality code.
For design contributors:
- Use Figma as our primary design tool.
- Follow our design system standards and naming conventions.
- Maintain clear component hierarchy and auto-layout principles.
- Document design decisions within related issues.
Community leaders and 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 that they deem inappropriate, threatening, offensive, or harmful.
Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
This Code of Conduct applies within all community spaces, including:
- GitHub repositories and all related activities (issues, pull requests, discussions)
- Our Telegram community channel
- Official project communications and documentation
- Public representation of the project (conferences, meetups, social media)
- Design collaboration spaces (Figma workspaces)
This Code of Conduct also applies when an individual is officially representing the community in public spaces.
If you experience or witness unacceptable behavior, or have any other concerns, please report it by contacting the project team through:
- GitHub: Create a private issue or contact repository maintainers directly.
- Email: report@kindfi.org.
- Telegram: Reach out to community moderators in our official channel.
All reports will be handled with discretion and confidentiality. We are committed to making the reporting process safe and comfortable for those who experience or witness violations.
When reporting an incident, please include:
- Your contact information.
- Names (usernames) of any individuals involved.
- Description of the incident and any available evidence (links, screenshots).
- Any additional context that may be helpful.
Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
Community Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
Consequence: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
Community Impact: A violation through a single incident or series of actions.
Consequence: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
Community Impact: A serious violation of community standards, including sustained inappropriate behavior.
Consequence: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a 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.
Consequence: A permanent ban from any sort of public interaction within the community.
We believe in celebrating our community members who exemplify our values:
- Technical Excellence: Contributors who consistently deliver high-quality code following our conventions.
- Community Leadership: Members who actively help newcomers and foster inclusive collaboration.
- Innovation: Contributors who bring creative solutions and push the boundaries of our technology stack.
- Mentorship: Community members who invest time in helping others learn and grow.
- Live Documentation: https://kindfis-organization.gitbook.io/development
- Code Style Guide: Code and Design Guide Style and Conventions
- Contribution Guide: OSS Contribution Guide - How to Contribute
- Community Chat: Telegram Community
- Project Architecture: KindFi Architecture Documentation
This Code of Conduct is adapted from the Contributor Covenant, version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
Community Impact Guidelines were inspired by Mozilla's code of conduct enforcement ladder.
Together, we're building the future of AI and Web3. Let's make it inclusive, innovative, and extraordinary. 🚀
Last updated: June 2025