Matsubaa
941a9da928
- Added goals for defining personal data categories and retention obligations. - Included exit criteria for user-level moderation, personal collections, and self-service data export. - Expanded Phase 2 goals to include remote actor moderation and shareable block lists. chore: Update flake.nix to specify main program - Set the main program for the project in the flake configuration. feat: Add issue templates for bug reports, feature requests, and questions - Created structured templates to streamline issue reporting and feature suggestions. docs: Add pull request template for consistent contributions - Introduced a PR template to guide contributors on providing necessary information. docs: Establish a Code of Conduct for community behavior - Implemented a Code of Conduct to promote a respectful and inclusive environment. docs: Create Diversity, Equity, and Inclusion (DEI) statement - Outlined commitment to diversity and inclusion within the FeDIY community. docs: Define Code Review Guidelines for constructive feedback - Established guidelines to ensure respectful and effective code reviews. docs: Implement Security Policy for vulnerability reporting - Created a security policy detailing how to report vulnerabilities and our commitment to addressing them.
5.1 KiB
FeDIY Community Code of Conduct
Our Commitment
FeDIY is dedicated to providing a welcoming, respectful, and inclusive environment for everyone—regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, education, socioeconomic status, nationality, personal appearance, race, religion, sexual identity and orientation, or any other dimension of human diversity.
We are committed to making participation in the FeDIY community a harassment-free experience for everyone. We value the diverse perspectives, backgrounds, and experiences that each member brings to our community.
Our Standards
Examples of behavior that create a positive environment include:
- Using inclusive, respectful language — Avoid gendered, ableist, or discriminatory language. Use neutral pronouns (they/them) when uncertain.
- Being welcoming and supportive — Encourage newcomers; help them learn and grow. Remember that not everyone has the same background or expertise.
- Actively listening — Pay attention to others' perspectives and experiences, even (especially) when they differ from your own.
- Acknowledging mistakes gracefully — Apologize sincerely when you make an error and work to do better.
- Focusing on what is best for the community — We are all here to make FeDIY better. Constructive criticism and healthy debate strengthen our project.
- Demonstrating empathy — Try to understand others' experiences and challenges. Be patient and kind.
- Recognizing diverse skill levels — DIY communities thrive on curiosity and learning. Questions are welcome; condescension is not.
Examples of unacceptable behavior include:
- Harassment, intimidation, or discrimination of any kind
- Slurs, insults, or derogatory language
- Deliberate misgendering or use of rejected names
- Sexual harassment, unwanted sexual advances, or inappropriate sexual comments
- Threats of violence or violent language
- Abuse, mockery, or belittling of individuals or groups
- Doxxing (sharing private information without consent)
- Deliberate disruption of discussions or trolling
- Exclusionary behavior based on identity or background
- Pattern of aggressive behavior, even if individual comments seem minor
- Any conduct that violates laws or harms others
Reporting Violations
If you experience or witness behavior that violates this code of conduct, we encourage you to report it. Your safety and comfort matter to us.
How to Report:
- For serious safety concerns: Contact the project maintainers directly at [security@moturpin.com] or open a confidential GitHub Security Advisory.
- For other violations: Report to the FeDIY maintainers via email at [conduct@moturpin.com] or by creating a confidential issue if available.
- In emergencies: Contact local law enforcement or appropriate authorities.
What to Include in Your Report:
- A description of the incident
- Who was involved
- When and where it occurred
- Any witnesses
- Any relevant context or history
Confidentiality:
We will handle all reports with care and confidence. We will not name the complainant without their consent unless disclosure is necessary for safety. Reports will be reviewed promptly.
Enforcement
The FeDIY maintainers will investigate all reports in good faith. Upon finding a violation, we may:
- Issue a warning to the person responsible
- Remove or edit comments/content
- Temporarily or permanently exclude the person from participation
- Report to appropriate authorities if necessary
We are committed to fair, proportional, and constructive enforcement. Our goal is accountability and community restoration, not punishment for its own sake.
Appeal Process
If you believe a moderation decision was unfair, you may appeal to the project maintainers by providing additional context or new information. Appeals will be reviewed within 7 days.
Our Responsibility
Project maintainers are responsible for:
- Clarifying the standards of acceptable behavior
- Responding promptly and fairly to reports
- Enforcing this code of conduct consistently
- Modeling inclusive, respectful behavior
- Being accessible and responsive to community concerns
- Regularly reviewing and updating this code of conduct
Scope
This code of conduct applies to:
- All FeDIY project spaces (repositories, discussions, issue trackers, pull requests)
- Project communication channels (forums, chat, mailing lists, social media)
- In-person events, meetings, or conferences related to FeDIY
- Anywhere someone is representing FeDIY or its community
Acknowledgments
This code of conduct is adapted from the Contributor Covenant, version 2.1, which is widely used in open source communities and emphasizes inclusive, welcoming practices.
We also draw inspiration from CHAOSS (Community Health Analytics in Open Source Software) principles for measuring and improving community inclusion.
Questions?
If you have questions about this code of conduct or how it applies to specific situations, please reach out to the maintainers. We're here to help.
Last Updated: May 2026
Maintained by: FeDIY Project Maintainers