Skip to content

Good First Issues

Greeniac edited this page Nov 22, 2025 · 2 revisions

Good First Issues

Welcome to FairMind! These issues are perfect for getting started. They are well-documented, have clear acceptance criteria, and include detailed getting started instructions.

Why Contribute to FairMind?

  • High Impact: Help build ethical AI governance tools
  • Learning Opportunity: Work with modern tech stack (Next.js, FastAPI, TypeScript, Python)
  • Clear Guidance: Every issue includes step-by-step instructions
  • Community Support: Active maintainers ready to help
  • Recognition: Contributors are recognized in releases and documentation

Quick Links

Current Good First Issues

Frontend & UI/UX

  • #99 - UI/UX: Add Loading States & Skeleton Screens
  • #103 - Frontend: Improve Accessibility & Keyboard Navigation
  • #104 - Internationalization: Add Multi-language Support
  • #106 - Mobile: Improve Mobile Responsiveness
  • #115 - Frontend: Improve loading states consistency across pages

Testing

  • #109 - E2E Tests: Add explicit waits for dashboard state transitions
  • #110 - E2E Tests: Add timeout check for loading state
  • #111 - E2E Tests: Add error message assertion for dashboard error state
  • #112 - E2E Tests: Add accessibility checks for data-testid wrappers

Backend & Infrastructure

  • #23 - Backend: Comprehensive API Testing Suite
  • #26 - DevOps: CI/CD Pipeline Setup

AI/ML

  • #63 - Basic ML: Dataset Preprocessing & Feature Engineering
  • #64 - Basic ML: Model Training & Evaluation Pipeline
  • #65 - Basic ML: Data Visualization & Analytics Dashboard
  • #66 - Basic ML: Testing & Quality Assurance

What Makes a Good First Issue?

  • Clear description and requirements
  • Well-defined acceptance criteria
  • Getting started instructions included
  • Low to medium complexity
  • Good learning opportunity
  • Helpful resources linked

How to Get Started

  1. Read the Issue: Understand what needs to be done
  2. Check Prerequisites: Make sure you have the required skills
  3. Set Up Environment: Follow development setup guide
  4. Ask Questions: Comment on the issue if you need clarification
  5. Start Working: Create a branch and begin implementation
  6. Submit PR: When ready, create a pull request

Tips for Success

  • Start small: Pick an issue that matches your skill level
  • Ask questions: We're here to help!
  • Test thoroughly: Make sure your changes work
  • Follow patterns: Look at existing code for examples
  • Be patient: Take your time to understand the codebase

Need Help?

What Happens After You Contribute?

  • Your PR will be reviewed by maintainers
  • You will receive feedback and guidance
  • Once merged, you will be added to our contributors list
  • Your contribution will be recognized in release notes

Ready to Start?

  1. Pick an issue from the list above
  2. Read the issue description carefully
  3. Set up your development environment
  4. Create a branch and start coding
  5. Submit your PR

We are excited to see your contributions!

Happy contributing!