Community Guidelines

Community Guidelines

The Boo the Mummy project welcomes community participation and contributions while maintaining standards that ensure a positive, inclusive, and productive environment for all participants. These guidelines establish expectations for interaction, contribution, and collaboration within the project ecosystem.

Code of Conduct

Core Principles

Respectful Communication - All community interactions must maintain respectful, professional communication standards. Personal attacks, harassment, or discriminatory language will not be tolerated under any circumstances.

Inclusive Environment - The project community welcomes participants from diverse backgrounds, experiences, and skill levels. Contributions and perspectives from all community members are valued and encouraged.

Constructive Feedback - When providing feedback or criticism, focus on specific issues or improvements rather than personal characteristics. Offer suggestions for improvement when identifying problems.

Professional Standards - Maintain professional behavior in all project-related communications, including GitHub issues, pull requests, social media interactions, and documentation discussions.

Prohibited Behavior

Harassment and Discrimination - Any form of harassment, discrimination, or exclusionary behavior based on personal characteristics is strictly prohibited.

Spam and Self-Promotion - Excessive self-promotion, spam, or off-topic content that does not contribute to project goals is not permitted.

Malicious Activities - Any attempts to introduce malicious code, security vulnerabilities, or harmful content will result in immediate removal from the community.

Copyright Violations - All contributions must respect intellectual property rights and avoid incorporating copyrighted material without proper authorization.

Contribution Standards

Technical Contributions

Code Quality - All code contributions must meet established quality standards including proper TypeScript typing, consistent formatting, and comprehensive testing where applicable.

Documentation Requirements - Code changes must include appropriate documentation updates, including inline comments for complex logic and README updates for new features.

Testing Standards - New functionality should include appropriate tests to ensure reliability and prevent regression issues in future development.

Performance Considerations - Contributions should maintain or improve application performance metrics and avoid introducing unnecessary performance overhead.

Content Contributions

Story Guidelines - New story content must align with the established character voice, maintain appropriate humor levels, and avoid content that could be offensive or exclusionary.

Image Standards - Visual content must meet quality standards, include appropriate alt text for accessibility, and respect copyright requirements.

Consistency Requirements - All content additions must maintain consistency with existing narrative tone, character development, and thematic elements.

Design Contributions

Visual Consistency - Design changes must maintain visual consistency with the established design system and color palette.

Accessibility Standards - All design modifications must meet or exceed WCAG 2.1 accessibility guidelines to ensure inclusive user experience.

Responsive Design - Design contributions must function properly across all supported device categories and screen sizes.

Performance Impact - Design changes should not negatively impact loading performance or user experience metrics.

Contribution Process

Getting Started

Repository Setup - Fork the main repository to create a personal development environment for contribution work.

Development Environment - Follow the setup instructions in the main README to establish a proper development environment with all necessary dependencies.

Issue Selection - Review open issues to identify contribution opportunities that match your skills and interests. Comment on issues to indicate your intention to work on them.

Communication - Engage with project maintainers and other contributors through GitHub issues and discussions to coordinate efforts and avoid duplicate work.

Development Workflow

Branch Management - Create feature branches with descriptive names that clearly indicate the purpose of the changes being made.

Commit Standards - Use clear, descriptive commit messages that explain the purpose and scope of changes. Follow conventional commit format when possible.

Code Review Process - All contributions undergo code review to ensure quality, consistency, and alignment with project goals. Be responsive to feedback and willing to make requested changes.

Testing Requirements - Test all changes thoroughly in local development environment before submitting pull requests. Include evidence of testing when relevant.

Pull Request Guidelines

Description Requirements - Provide comprehensive descriptions of changes, including the problem being solved, the solution implemented, and any potential impacts on existing functionality.

Documentation Updates - Include necessary documentation updates as part of pull requests, ensuring that changes are properly documented for future reference.

Breaking Changes - Clearly identify any breaking changes and provide migration guidance for users who may be affected by the changes.

Review Process - Participate constructively in the review process, responding to feedback promptly and making requested changes in a timely manner.

Community Interaction

Social Media Engagement

Platform Guidelines - When engaging with the project on social media platforms, maintain the same professional and respectful standards established for direct project communication.

Content Sharing - When sharing project content, provide appropriate attribution and avoid misrepresenting the project's purpose or scope.

Feedback Channels - Use appropriate channels for different types of feedback, directing technical issues to GitHub and general discussion to social media platforms.