All contributions are welcome! 😃 First day in Open Source? Perfect! You belong here!
We're not looking for perfection - we're looking for people who care. If you love these classic games and want to help preserve them, you're already qualified! 💚
We're just gamers who want to keep enjoying the games we love, learning and growing together along the way. Nobody here knows everything, and that's what makes it fun!
Remember: No question is too small, no contribution too minor!
- Join our community discussions and say hello! 👋
- Read through some existing issues to get a feel for things
- Don't understand something? Ask! We love questions!
- Look for issues labeled
good first issue🏷️ - Found something interesting? Comment on it!
- Want to work on something not listed? Propose it!
- Fork the repository
- Create your feature branch (
git checkout -b my-awesome-feature) - Make your changes (take your time!)
- Commit with a clear message (see below for tips)
- Push to your branch
- Open a Pull Request - we'll guide you from there!
Our team is mostly active on weekends 🗓️, so:
- Weekday submissions: Expect responses by the weekend
- Weekend submissions: Usually get same-day attention
- Urgent security issues: We'll prioritize these!
Found a bug? Have an idea? Awesome! Here's how to share it:
- Use our templates - they're there to help you!
- Describe what you expected vs. what happened
- Include steps to reproduce (if it's a bug)
- Screenshots are super helpful! 📸
- Not sure about something? Just do your best!
Your report helps us improve! 🌟
- No perfection required! We'll help you polish it
- Describe what you changed and why
- Tell us how to test your changes
- First PR? Add "First PR" to your description - we'll give extra guidance! 🎓
- Made a mistake? No worries! PRs are conversations, not tests
- A friendly contributor will review your PR
- They might suggest some tweaks (it's all about learning!)
- You make the changes (or discuss alternatives)
- We merge and celebrate! 🎉
We use Conventional Commits - it's simpler than it sounds! Here are examples:
feat:Adding something new- Example:
feat: add dark mode toggle to settings
- Example:
fix:Fixing a bug- Example:
fix: correct database connection timeout
- Example:
docs:Documentation changes- Example:
docs: update installation instructions
- Example:
chore:Maintenance tasks- Example:
chore: update dependencies
- Example:
- Keep it short and sweet (under 50 characters)
- Use present tense ("add" not "added")
- No period at the end
- Explain the "why" in the PR description
We can fix it together! 🤝
- GitHub's Hello World Guide
- First Contributions
- Our community is here to help - just ask!
- Conventional Commits
- How to Write a Git Commit Message
- Pair with a community member on your first PR!
- Code - Features, bug fixes, optimizations
- Documentation - Tutorials, clarifications, translations
- Testing - Bug reports, test cases, gameplay testing
- Ideas - Feature requests, brainstorming, feedback
- Community - Helping others, answering questions, being kind
- Art & Design - Icons, screenshots, improving UI/UX
- We'll treat you with respect and kindness
- We'll help you learn and grow
- We'll celebrate your contributions
- We'll make this a safe space for everyone
And remember, we're here to help every step of the way! 🚀