Table of Contents

Hacking on the Ushahidi Platform

We use Phabricator for all project management, issue tracking, and code review. You can find our instance of "phab", as we call it internally, at https://phabricator.ushahidi.com/ After you have signed up for an account, please read the help guide and follow the instructions for setting up arc.

The master branch of Lamu is considered "stable" in that the build should be passing and all tests should complete successfully. All development is done locally or through feature branches. All changes must be code reviewed through the Differential tool on phab. Each modification should be a complete unit of change and not break any test. Any new feature should come with a spec test, unit test, or feature test.

...

Ushahidi practices the Agile method of development, with a continuously changing master branch and timed releases. New releases of Ushahidi are made on the 1st and the 15th*, or the next business day after. You are packaged bi-weekly on Thursday afternoons (US/Eastern time). You can check what tasks are currently being worked on by following the project workboard on phab. Any task that is planned, but not yet being worked on, will be in the Backlog column. Tasks in the Next Release column are to be completed before for the next release. Anything that has been shelved for a later date, or has very low priority, will be in the Bike Rack._{* The 1st and 15th release cycle will not begin until the first non-alpha release!}

Bug Reports and Features

Bug reports should include:

...