to @/all the new contributors here :) ... Good job with your contributions in the form of bug reports (or) PRs (or) both ...
Got a few suggestions though
- Write clear meaningful git commit messages (Do read http://chris.beams.io/posts/git-commit/)
- Make sure your PR's description contains GitHub's special keyword references that automatically close the related issue when the PR is merged. (More info at https://github.com/blog/1506-closing-issues-via-pull-requests )
- When you make very very minor changes to a PR of yours (like for example fixing a failing travis build or some small style corrections or minor changes requested by reviewers) make sure you squash your commits afterwards so that you don't have an absurd number of commits for a very small fix. (Learn how to squash at https://davidwalsh.name/squash-commits-git )
- If you're submitting a bug report, make sure you add steps to reproduce it. Especially if that bug is some weird/rare one.
- If you're submitting a PR for a UI-related issue, it would be really awesome if you add a screenshot of your change or a link to a deployment where it can be tested out along with your PR. It makes it very easy for the reviewers and you'll also get reviews quicker.
- If you would like to work on an issue, drop in a comment at the issue. If it is already assigned to someone, but there is no sign of any work being done, please free to drop in a comment so that the issue could be assigned to you if the previous assignee has dropped it entirely.
- Go through the application completely on your local machine. Press on any link/button you can find and see where it leads to. Explore. (Don't worry ... Nothing will happen to the app or to you due to the exploring ;) Only thing that will happen is, you'll be more familiar with what is where and might even get some cool ideas on how to improve various aspects of the app.)
And also, there seems to be some confusion regarding what code is where.
So, any bug-fixes will not be reflected at eventyay until a new release is made in the master branch.
The tentative release policy for now is, (since there is a lot of activity and a lot of bugs), an alpha release every monday and friday. (since we see more activity on weekends).
Thank you for your patience while reading this long message :D