The Eventum project welcomes all contributions under a GPL license.
Submission of a patch implies that the submmitter acknowledges that they are the author of the code (or have permission from the author to release the code) and agree that the code can be released under the GPL. The copyright for the changes will then revert to the Eventum Development Team - this is required so that any copyright infringements can be investigated quickly without contacting a huge list of copyright holders. Credit will always be given for any patches through a AUTHORS file in the distribution.
Bugs should be reported to issue tracker.
Before opening new issue, first check that the bug is not already fixed by
testing with master branch, then check that your problem is not already
reported, by looking at open issues.
- Fork it.
- Create your feature branch (
git checkout -b fixing-blah), please avoid working directly on themasterbranch. - Check for unnecessary whitespace with
git diff --checkbefore committing. - Commit your changes (
git commit -am 'Fixed blah'). - Push to the branch (
git push -u origin fixing-blah). - Create a new pull request.
Commits follow good practices for message and content
- Write good commit messages
- Strive for atomic commits whenever you can
How to update forked repository to be up to date with the master:
- Check remotes
git remote -v - Add Eventum as upstream
git remote add upstream https://github.com/eventum/eventum.git - Switch to master
git checkout master - Fetch latest changes
git fetch upstream - Rebase for clean pull requests
git rebase -i upstream/master - Do not make commits on your
masterbranch
For asset compilation laravel-mix is used.
You will need node and yarn installed.
// Run all Mix tasks and watch for file changes
yarn run watch
The webpack.mix.js file is the entry point for all asset compilation.