Thank you so much for your interest to contributing to Killgrave. We are so happy that you are interesting on our project, so we want to offer some guidelines before that you start.
Be kind and respectful to the members of the community. Take time to educate others who are seeking help. Harassment of any kind will not be tolerated.
If you have questions, or you want to share knowledge about Killgrave, feel free to join our #killgrave slack channel. Also, we share announcements related with the tool on this channel.
Before filing an issue, please check the existing issues to see if a similar one was already opened. If there is one already opened, feel free to comment on it.
If you believe you've found a bug, please provide detailed steps of reproduction, the version of Killgrave, the imposters that are involved and anything else you believe will be useful to help troubleshoot it (e.g. OS environment, config file, flags, etc...). Also, state the current behavior vs. the expected behavior.
If you'd like to see a feature, or an enhancement please open an issue with a clear title and description of what the feature is and why it would be beneficial to the project and its users. Remember that you could also comment with the community about the new features on the #killgrave slack channel.
Killgrave releases work using milestones, if you see that some issue doesn't have any milestone is possible that the issue has not been reviewed yet by any maintainer or the issue could be integrated in master without any impact, ie. a typo fix on the README.
Each milestone have his own branch, so you will need to wait until the issue have a release assigned to start your work, because you will need based your change on that branch.
So please until to start, ask on the issue if you can take it this issue and request for a milestone if there any declared.
Now, you are ready to contribute to do Killgrave the best mock tool on the world, fork killgrave and start!!