If you wish to contribute to joind.in, please be sure to read/subscribe to the following resources:
- Contributor Code of Conduct: https://github.com/joindin/joindin-web2/CODE_OF_CONDUCT.md
- Contributor's Guide: https://github.com/joindin/joind.in/wiki/How-to-Contribute-Code
- Contributor's mailing list: http://groups.google.com/group/joindin-developers
- Contributor's IRC channel: #joind.in on Freenode.net
You should work on what you want to. Our bug tracker is here: https://joindin.jira.com
Any issues that have the "hackathon" or "easypick" label are ones that we think are a good starting point. This JIRA filter will give you the list of all current issues with the "hackathon" or "easypick" issues.
If you have any problems, ask on the IRC channel or send an email to the mailing list.
If you start working on an issue, please assign yourself to it and mark the issue as "in progress".
If you include the JOINDIN-nnn issue number in the commit message, then JIRA will pick it up and display your branch on the issue.
If you want have your commit messages perform actions in JIRA. JIRA has documentation on their extensive list of commands, but here is an example of what you can use in your commit message:
JOINDIN-<number> #close <message>
An example would be:
JOINDIN-445 #close Fixed.
The current PHP version for joind.in is PHP 5.6.
All PHP code follows psr-2. One way to help ensure that your submitted code is PSR-2 is to run PHP Code Sniffer against PSR-2 and the .editorconfig plugin for your editor before submitting.