📌 Welcome to Kepler Contributors! Please Read Before Opening an Issue or Pull Request 🚀

[krishkhinchi]

👋 Welcome to Kepler!

Thank you for your interest in contributing to Kepler, an open-source AI-powered autonomous Space Traffic Management platform. Whether you're fixing bugs, improving documentation, enhancing the frontend, optimizing the backend, or building new features, we're excited to have you as part of our community.

To ensure a smooth and fair contribution process, please read the guidelines below before getting started.

---

🚀 Contribution Workflow

1. Browse the list of available Issues.
2. Choose only one issue you'd like to work on.
3. Claim the issue by commenting:

/claim

4. Wait for a maintainer or automation to assign the issue to you.
5. Fork the repository.
6. Clone your fork locally.
7. Create a new branch from the latest main branch.
8. Implement your changes.
9. Test your changes locally.
10. Commit your work with a meaningful commit message.
11. Push your branch to your fork.
12. Open a Pull Request and reference the related issue.

---

📋 Before You Start

• Read the project README carefully.
• Make sure the issue is not already assigned.
• Check if someone is already working on it.
• Keep your branch updated with the latest changes.
• Ask questions if anything is unclear before starting.

---

🚫 Please Don't

• Work on an issue without claiming it.
• Submit multiple Pull Requests for the same issue.
• Open duplicate issues.
• Submit AI-generated code without reviewing and understanding it.
• Copy code from other repositories.
• Submit unrelated changes in a single Pull Request.
• Commit sensitive information such as API keys or credentials.
• Make unnecessary formatting changes unrelated to the issue.
• Force push to another contributor's branch.

---

✅ Pull Request Checklist

Before submitting your Pull Request, make sure:

• Your code builds successfully.
• All existing functionality continues to work.
• Your changes solve the assigned issue.
• No unnecessary files are included.
• Code follows the project's style and conventions.
• Documentation has been updated if required.
• Your Pull Request references the related issue.
• Commit messages are meaningful.
• No merge conflicts exist.
• You have tested your changes locally.

---

💡 Good Contribution Practices

• Keep Pull Requests small and focused.
• Write clean, readable, and maintainable code.
• Follow the existing project structure.
• Add comments only where necessary.
• Reuse existing utilities whenever possible.
• Respect other contributors' work.
• Be open to code review feedback.

---

🤝 Need Help?

If you're stuck or have questions:

• Open a GitHub Discussion.
• Ask questions in the issue comments.
• Reach out to the maintainers before making major architectural changes.

We're happy to help you get started.

---

⭐ Support the Project

If you enjoy contributing to Kepler:

• ⭐ Star the repository
• 🍴 Fork the project
• 🐛 Report bugs
• 💡 Suggest new features
• 📢 Share the project with others

Your support helps the project grow and reach more contributors.

---

Happy Coding and Welcome to the Kepler Community! 🛰️🚀