We welcome contributions to the project. Please read the following guide on how you can contribute.
A bug is a demonstrable problem that caused by the code in the repository. Good bug reports are extremely helpful, so thankes!
Guidelines for bug reports:
- Use the Github issue search function - check if the issue has already reported.
- Check if the issue has been fixed - try to reproduce it using the latest
masterordevbranch in the repo. - Isolate the problem - So the developers doesn't have hard times finding the possible bug.
A good bug report shouldn't have leave others needing to chase up for more information.
Please try to be detailed as possible in your report. What steps ill reproduce the issue? etc..
All these details will help people to fix potential bugs.
- Feature requests first need to be discussed and accepted through an issue before sending in a pull request.
- Pull requests will be merged after being reviewed.
- Please be respectful to other contributors and hold to The Code Manifesto
- Everything submitted to the repository must be in source.That meaning any soft of obfuscated files, binary files, passworded files, and/or encrypted files will immediately removed (unless the file is a representation of the latest compiled compatible AND working version of which this file must only be binary source and include a virustotal scan).
- DO NOT RENAME a resource. Retain the authenticity of it. Everything is designed the way it is for a reason. Do not go behind someone else and redo what someone took the time and effort to do to make everything work.
- Contributions are made to this repository as a goodness of heart and a record kept of the contributor's contributions history for their work.
- Violating any of the above hereby informs you that you will be removed from this community and branded as a leech.