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.
1.4 KiB
1.4 KiB
Description
Please describe what this pull request does. What problem does it solve? What feature does it add?
Closes: #(issue number, if applicable)
Type of Change
- Bug fix (non-breaking change that fixes an issue)
- New feature (non-breaking change that adds functionality)
- Breaking change (fix or feature that would cause existing functionality to change)
- Documentation update
- Refactoring (no functional change)
- Test improvement
How Has This Been Tested?
How did you test your changes? Please describe:
- Existing tests pass
- Added new tests
- Tested manually (describe how)
- Other (describe)
Checklist
- Code follows the project style (
cargo fmt,cargo clippy) - All tests pass (
cargo test) - New tests added for new functionality (if applicable)
- Documentation updated (if applicable)
- Commit messages are clear and follow conventions
- I have read the Code of Conduct
- My changes don't introduce security or accessibility issues
Screenshots or Examples (Optional)
If your change affects the UI or user experience, add screenshots or examples here.
Additional Notes
Anything else reviewers should know? Any trade-offs or decisions you made?
Thank you for contributing! We appreciate your effort. If you have any questions while preparing this PR, don't hesitate to ask in comments.