chore(deps): bump actions/checkout from 4 to 6

.github/FEEDBACK_REVIEW_PROCESS.md

@@ -0,0 +1,331 @@
+# Feedback Review Process
+
+This document outlines the process for reviewing and acting on user feedback for the Fairness Pipeline Development Toolkit.
+
+---
+
+## Overview
+
+The feedback review process ensures that user input is:
+- Acknowledged promptly
+- Categorized appropriately
+- Prioritized based on impact and feasibility
+- Tracked and addressed systematically
+- Communicated back to the community
+
+---
+
+## Process Steps
+
+### 1. Submission and Acknowledgment
+
+**Timeline**: Within 48 hours
+
+**Actions**:
+- All feedback submissions (issues, discussions, etc.) are acknowledged
+- Initial triage label is applied
+- Feedback is added to tracking system
+
+**Responsible**: Maintainers
+
+### 2. Triage
+
+**Timeline**: Within 1 week
+
+**Actions**:
+- Categorize feedback:
+  - Bug
+  - Feature Request
+  - Documentation
+  - Usability
+  - Performance
+  - General Feedback
+- Assign priority:
+  - **Critical**: Security issues, data corruption, major functionality broken
+  - **High**: Significant bugs, highly requested features, major usability issues
+  - **Medium**: Moderate bugs, useful features, documentation gaps
+  - **Low**: Minor issues, nice-to-have features, edge cases
+- Add appropriate labels
+- Link related issues/discussions
+
+**Responsible**: Maintainers
+
+### 3. Review and Assessment
+
+**Timeline**: 1-2 weeks (depending on priority)
+
+**Actions**:
+- Technical feasibility assessment:
+  - Implementation complexity
+  - Dependencies and conflicts
+  - Performance implications
+  - Breaking changes
+- Impact assessment:
+  - Number of users affected
+  - Workflow disruption
+  - Alignment with project goals
+- Community input:
+  - Gather feedback from discussions
+  - Check for duplicate requests
+  - Assess community support
+
+**Responsible**: Maintainers + Community
+
+### 4. Decision
+
+**Timeline**: 2-4 weeks
+
+**Outcomes**:
+
+**For Bugs**:
+- **Critical/High**: Scheduled for next patch/minor release
+- **Medium**: Added to backlog, addressed in next minor release
+- **Low**: Tracked, addressed when resources available
+
+**For Features**:
+- **High Priority**: Added to next minor/major release roadmap
+- **Medium Priority**: Added to roadmap for future consideration
+- **Low Priority**: Tracked for future releases
+
+**For Documentation**:
+- Updated in next documentation cycle
+- Added to documentation backlog if extensive
+
+**For Usability/Performance**:
+- Investigated and optimized in next release
+- Added to improvement backlog
+
+**Responsible**: Maintainers
+
+### 5. Implementation Planning
+
+**Timeline**: Before release planning
+
+**Actions**:
+- Create implementation plan
+- Assign to release milestone
+- Break down into tasks
+- Estimate effort
+- Identify dependencies
+
+**Responsible**: Maintainers
+
+### 6. Implementation
+
+**Timeline**: Per release schedule
+
+**Actions**:
+- Implement changes
+- Write tests
+- Update documentation
+- Create pull request
+- Review and merge
+
+**Responsible**: Maintainers + Contributors
+
+### 7. Follow-up
+
+**Timeline**: After release
+
+**Actions**:
+- Notify original submitter
+- Update issue/discussion with resolution
+- Credit contributors in release notes
+- Close issue/discussion
+
+**Responsible**: Maintainers
+
+---
+
+## Priority Guidelines
+
+### Critical Priority
+
+**Criteria**:
+- Security vulnerabilities
+- Data corruption or loss
+- Major functionality completely broken
+- Blocks all users from using core features
+
+**Response Time**: 24 hours
+**Resolution Time**: Next patch release
+
+### High Priority
+
+**Criteria**:
+- Significant bugs affecting many users
+- Highly requested features (5+ upvotes)
+- Major usability issues
+- Performance degradation > 50%
+
+**Response Time**: 48 hours
+**Resolution Time**: Next minor release
+
+### Medium Priority
+
+**Criteria**:
+- Moderate bugs with workarounds
+- Useful features with community support
+- Documentation gaps
+- Minor usability issues
+- Performance improvements
+
+**Response Time**: 1 week
+**Resolution Time**: Next minor/major release
+
+### Low Priority
+
+**Criteria**:
+- Edge cases
+- Nice-to-have features
+- Minor documentation improvements
+- Cosmetic issues
+
+**Response Time**: 2 weeks
+**Resolution Time**: Future releases
+
+---
+
+## Feedback Categories
+
+### Bug Reports
+
+**Review Focus**:
+- Reproducibility
+- Impact on users
+- Workarounds available
+- Root cause analysis
+
+**Decision Factors**:
+- Severity of impact
+- Frequency of occurrence
+- Ease of reproduction
+- Fix complexity
+
+### Feature Requests
+
+**Review Focus**:
+- Use case clarity
+- Community support
+- Alignment with project goals
+- Implementation feasibility
+
+**Decision Factors**:
+- Number of users who would benefit
+- Implementation complexity
+- Maintenance burden
+- Fit with project scope
+
+### Documentation
+
+**Review Focus**:
+- Clarity of issue
+- Impact on user experience
+- Scope of changes needed
+
+**Decision Factors**:
+- User confusion level
+- Documentation gaps
+- Update complexity
+
+### Usability
+
+**Review Focus**:
+- User experience impact
+- Frequency of issue
+- Workflow disruption
+
+**Decision Factors**:
+- Number of users affected
+- Improvement potential
+- Implementation effort
+
+### Performance
+
+**Review Focus**:
+- Performance degradation
+- Scalability concerns
+- Resource usage
+
+**Decision Factors**:
+- Impact on typical use cases
+- Optimization potential
+- Implementation complexity
+
+---
+
+## Tracking and Communication
+
+### Issue Tracking
+
+- All feedback is tracked in GitHub Issues
+- Labels indicate category and priority
+- Milestones track release planning
+- Projects organize related work
+
+### Communication
+
+- Regular updates in issue comments
+- Status updates in discussions
+- Release notes for completed work
+- Roadmap updates for planned features
+
+### Metrics
+
+Track:
+- Time to acknowledgment
+- Time to resolution
+- Feedback categories
+- Priority distribution
+- Community engagement
+
+---
+
+## Review Schedule
+
+### Weekly
+
+- Triage new submissions
+- Update issue status
+- Respond to questions
+
+### Monthly
+
+- Review priority assignments
+- Assess community feedback
+- Update roadmap
+- Plan next release
+
+### Quarterly
+
+- Review feedback trends
+- Assess process effectiveness
+- Update review guidelines
+- Community retrospective
+
+---
+
+## Escalation
+
+If feedback is not addressed in expected timeframe:
+
+1. **Check Status**: Review issue comments and labels
+2. **Ask for Update**: Comment on issue requesting status
+3. **Discuss**: Use GitHub Discussions for broader questions
+4. **Contribute**: Consider contributing a fix or implementation
+
+---
+
+## Continuous Improvement
+
+The feedback review process itself is subject to improvement:
+
+- Regular process reviews
+- Community input on process
+- Metrics-driven improvements
+- Adaptation based on project needs
+
+---
+
+**Last Updated**: 2025-01-24  
+**Next Review**: 2025-04-24

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,45 @@
+---
+name: Bug Report
+about: Create a report to help us improve
+title: '[BUG] '
+labels: bug
+assignees: ''
+---
+
+## Description
+A clear and concise description of what the bug is.
+
+## Steps to Reproduce
+1. 
+2. 
+3. 
+
+## Expected Behavior
+A clear and concise description of what you expected to happen.
+
+## Actual Behavior
+A clear and concise description of what actually happened.
+
+## Environment
+- **OS**: [e.g., Ubuntu 22.04, macOS 14.0, Windows 11]
+- **Python Version**: [e.g., 3.10.5]
+- **Package Version**: [e.g., 0.5.2]
+- **Installation Method**: [e.g., pip, conda, from source]
+
+## Code Sample
+```python
+# Minimal code sample that reproduces the issue
+```
+
+## Error Messages
+```
+Paste any error messages or tracebacks here
+```
+
+## Additional Context
+Add any other context about the problem here.
+
+## Checklist
+- [ ] I have searched existing issues to ensure this bug hasn't been reported
+- [ ] I have provided all relevant environment information
+- [ ] I have included a minimal code sample that reproduces the issue

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,11 @@
+blank_issues_enabled: true
+contact_links:
+  - name: GitHub Discussions
+    url: https://github.com/SvrusIO/fAIr/discussions
+    about: Ask questions, share ideas, and discuss with the community
+  - name: Documentation
+    url: https://github.com/SvrusIO/fAIr/blob/main/README.md
+    about: Check the documentation for usage examples and guides
+  - name: Security Issues
+    url: https://github.com/SvrusIO/fAIr/security
+    about: Report security vulnerabilities privately