Thanks for getting interested in contributing to one of our projects. To help us the right way, here are some rules to follow.
To report a bug, just open a new issue. Try to:
- Be the more explicit as you can
- Be careful on naming your issue: try to be clear
- Use example, another project hosted on github may be an acceptable example
- Provide a unit test that exposes the bug
Don't open an issue but send an email to [email protected].
You may have a great idea. Do not hesitate to send it to us using the following rules:
- Prefix your issue title by
[RFC]
- Describe your idea
- Illustrate with fake code example what it could be
- Start from the
master
branch - Verify that tests are green
- Comment the code
- Fix the codestyle of your code with the following command
php-cs-fixer.phar fix --config=.php_cs.dist
The release policy of BiiG OSS was originally defined here.
Here it is:
- With every release we should fill the release page
- We should release maximum 1 week after some contribution is merged (except doc)
- We open an issue/milestone for the release so we have a track and date for it
- Every contributor to the project & BiiGer can make a release (others can ask for in a new issue)
- We should apply this to any projects of BiiG
- We must respect semver
It may not be apply correctly so you can open an issue to notice it.
This library is under an MIT license. Any contribution you make on it is under the same MIT license.