How to contribute

Bug reports and feature requests

If you have suggestions of plots you would like to see in this library and are not currently here, you can open an issue describing your suggestion. No previous knowledge of GitHub is needed to do this. Please read already existing issues to check whether someone else has made the same suggestion or reported the same error before creating a new issue.

Contributing through GitHub

If you have graphs you would like to add to this library and are comfortable using GitHub, fork the repository and submit a pull request to the master branch with any additions you want to make. Please read the guidelines below on code, branching and folder structure conventions before opening a pull request.

Contributing via e-mail

If you have graphs you would like to add to this library but you are not comfortable using GitHub, you can send an e-mail to dimeanalytics@worldbank.org. Use the subject "Contribution to Stata Visual Library" and attach a zipped folder containing (1) the de-identified data used to create the plot, (2) the code that creates the plot from such data, and (3) the ado-file for any user-written command not published in SSC.

Please read the guidelines below on code conventions before sending your contribution. We also recommend that you create a GitHub account and include your GitHub handle in the e-mail so you can receive credit for your contribution.

Contribution guidelines

Code conventions

• We recommend following the DIME Analytics Stata style guide, available on the appendix of our data handbook for all styling relevant to the code submitted.

GitHub conventions

Branches

• Make pull requests to the master branch only if you wish to contribute to README, LICENSE or similar meta data files.
• To contribute with Stata code files, create a fork from the master branch and point your pull request back to the same branch.
• If your pull request is related to an open issue , reference the issue in your PR message. If the contribution solves the issue, add the message "Resolves issue #X".

Folder structure

• do-files should be saved in the Library/do folder
• User-written commands not published in SSC should be saved in the Library/ado folder
• Data files should be saved in Library/data
• Output figures should be saved in docs/figure