The code base of the ODM project is composed by several different code repositories found on https://github.com/OpenDevelopmentMekong/. Depending on what part of the system the bug report of feature request relates to, Issues should be raised in the corresponding github repostory.
As a rule of thumb, issues relating to the frontend will be reported on https://github.com/OpenDevelopmentMekong/wp-odm_theme/ or https://github.com/OpenDevelopmentMekong/wpckan depending on whether it , CKAN issues on https://github.com/OpenDevelopmentMekong/ckanext-odm_dataset, https://github.com/OpenDevelopmentMekong/ckanext-odm_library or https://github.com/OpenDevelopmentMekong/ckanext-laws depending on the type of dataset.
In order to avoid creating duplicated Issues, the reporter should first check if it has not been reported yet. For that, it is very helpful to use the search function of the Github Issues.
Example search for “data page”…
Keeping a consistent methodology for reproducing bugs is very important. Once a tester identifies an error, the conditions for repeating it need to be gathered in order for developers to reproduce the scenario and be able to test solutions. This process consist on following steps:
Instead of informing of an error on the functionality, a feature request proposes the implementation of a new functionality or the improvement of an existing one.
While creating a github Issue with a feature requests please:
- Add design mockups on how you would like the feature to look like - Provide detailed description on how the new feature should work and how the user is supposed to use it. - Specify links on the pages/modules where the new feature should be implemented.
Once the information specified above has been gathered, open the corresponding github repository. Example: https://github.com/OpenDevelopmentMekong/wp-odm_theme and click on Issues » New Issue, set a descriptive title and add the steps for reproducing the error, the screenshot and further information in the description.