Ever wondered how far your project meets OSS (Open-Source Software) criteria?
Does your project have a proper commit history?
A license and a readme?
Are your pull requests up to the mark?
We wondered about it too, and we ended up with OSSmosis, a chance for you to flex your OSS projects and win exciting schwags from GitHub Community SRM!
All you need is to submit your best OSS project done till date and stand a chance to be awarded the honour of 'Best OSS Project' by the community.
- Your project must be hosted over GitHub and the visibility must be public.
- Your project should be your own. If it is a collaboration project, your contribution must be sufficient to qualify for the prize.
- Your project should not promote any illegal purpose or action.
- You agree to give GitHub Community SRM the rights to showcase your project over our channels (with the proper credits to you) by participating in this contest.
- A proper readme and an appropriate license file are required for all OSS projects.
- A regular and clear commit history is the marker of a good OSS project.
- Issues are a great tool to maintain the track of a project. They are also an excellent way of letting the maintainers know about a bug in the project.
- PRs (Pull Request(s)) are the backbone of any OSS project. A detailed PR helps the maintainers a lot.
- It is a bonus (but is not required) if you have a CI/CD (Continous Integration/Continous Deployment) pipeline set up in your project.
- It would also help (but is not required) to have a good track record of Contributions in your GitHub account.