FOR ARCHIVAL PURPOSES ONLY

The information in this wiki hasn't been maintained for a good while. Some of the projects described have since been deprecated.

In particular, the "Ushahidi Platform v3.x" section contains information that is often misleading. Many details about this version of Platform have changed since.

This website is an extraction of the original Ushahidi wiki into a static form. Because of that, functions like logging in, commenting or searching will not work.

For more documentation, please refer to https://docs.ushahidi.com

Skip to end of metadata
Comment: Migrated to Confluence 4.0
Go to start of metadata

Currently, all development issues (bugs, feature requests and roadmaps) are tracked on Github and Github Issues.

The developer site is open to anyone who wants to log a feature request or a bug report. However, you need to sign up for an account in order to file a report and receive notifications when the status of issue changes or the report detail is modified.

Bug Reports

Bug reports are used to track glitches in the application. A bug report should always include the following information:

  • Subject/title of the report
  • Description of the bug and if necessary, attach a screenshot of the observed or a patch for the suggested solution
  • Severity/Priority of the issue
  • Version of the platform in which the bug was encountered. Version should always be the current or previous version of the software

To submit patches you can:

  • Submit a GitHub pull requests - this will create an issue for you, so include the same info in a pull request as you would in a bug report
  • Push a commit to your repository and reference the issue number in your commit message
    • ie. "Fixes #259 - Error on Install: missing sharing table"

Feature Requests

Feature requests are filed in the same fashion as bug reports and the same information is collected. Attachments for a feature request may include:

  • Wireframes/mockups for the desired feature
  • A patch that that implements the feature - However, GitHub pull requests are best placed to handle this. If you submit a pull request this will create a Github issue for you.

Feature requests are almost always included in the product roadmap. However, some features are best implemented as plugins in which case they are left out of the roadmap.

NOTE: GitHub Issues sync up with commits and check the commit messages for any issues that have been closed. For example, if a commit message reads Closes #xxxxx, the status of issue no. xxxxx shall be changed to closed.