Triaging Mojaloop OSS bugs

Raising a bug / issue

If there is a bug or issue in general an issue is logged as a bug or feature request on the project repository and in some cases linked to an issue logged on the repository for that specific component.

There is a bug template that can be used and encourages use of details such as versions, expected results and other details, which help with triage and reproducing the issue.

Once a bug is logged

  1. Typically, the bug is initially triaged in the #ml-oss-bug-triage public channel on Mojaloop Slack
  2. For Security and other sensitive issues, the bug is triaged on a private channel with current contributors, before information is made public at an appropriate time.
  3. During bug triage, priority and severity are assigned to the bug after majority consensus usually
  4. Based on the priority and severity the bug is taken up by the Core team or other contributors based on a collaborative effort.
  5. Once it is taken up, conversation and updates happen on the slack channl, but mostly on the issue itself.

Triage

  1. The discussion regarding the issue is open to a public for normal bugs / issues
  2. However, to start with, the voting rights are given to current contributors and stakeholders.
  3. Based on the discussions, a final call on the priority and severity of the issue is made by the Program Manager.
  4. If you think you need a vote, please reach out to Kim or Sam.
  5. Here are the voting members [14] for triaging bugs to start with.
    1. Adrian Hope-Bailie
    2. James Bush
    3. Kim Walters
    4. Lewis Daly
    5. Miguel deBarros
    6. Matt Bohan
    7. Miller Abel
    8. Neal Donnan
    9. Nico Duvenage
    10. Rajiv Mothilal
    11. Rob Reeve
    12. Sam Kummary
    13. Sri Miryala
    14. Warren Carew
  6. The list and the process will be updated as it evolves, this is a proposal to start with do a Pilot on.

results matching ""

    No results matching ""