-
Notifications
You must be signed in to change notification settings - Fork 12
Home
This is the hub for development of the Ushahidi instance set up in support of the Christchurch 2011 earthquake.
Great! But to prevent an abundance of cooks from spoiling the broth, please read this wiki page.
To get started, you should get the software running locally.
- Fork the Ushahidi_Web repository into your own Github account.
- Download the repository onto your local LAMP/WAMP/MAMP development webserver. If you don't have a development webserver, XAMPP is a reasonably good option for those of you with Windows & Mac computers.
- Run the installer to set up an empty database with the appropriate code. Make sure the ccnz theme is selected, rather than the default.
If you're new to Git and Github, this page is a good introduction to the fork & pull-request development process.
There are a couple of communication channels that we are using to discuss the project. If you want to help out, please join these, as we're working at a frenetic pace and can't all be in the same room.
- IRC: #eqnz-dev on Freenode.
- Mailing list: eqnz-dev@groups.google.com
In addition to the group communication channels, these people are helping to coordinate volunteer developers and are good people to talk to if you're flummoxed.
- Rob Coup (roup on irc)
- Nigel McNie (waawaamilk on irc)
- Sam Minnee (sminnee on irc)
- Penny Leach (Mjollnir` on irc)
With the flurry of activity surrounding github.com/ccnz/Ushahidi_Web, we are running into problems with having multiple people working on the same issue. To deal with this, can we please use the Github Issue Tracker to consistently track what is being worked on. In other words, follow these 3 rules:
- Before fixing a bug, look to see if there is an issue already for it. Also look to see if someone has posted a message saying that they're working on it. There's no need to have 2 people fixing the same issue.
- If there is an issue for it, post a message on that issue saying that you're working on the issue, and add the "claimed" tag.
- If there isn't an issue for it create a new issue and add a message saying that you're working on the issue, and add the "claimed" tag.
Generally speaking, each developer has their own fork, and works on their changes there. However, if a number of you are working on the same major feature and would like to collaborate more closely, you may want to set up a fork that you all have commit access to.
Once you are a ready to have your code promoted to the main development site, please submit a pull request. The core team with commit access will review and merge your work.
The work will appear initially on dev.eq.org.nz, and in the fullness of time at eq.org.nz.