# 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 (opens new window) repository and in some cases linked to an issue logged on the repository for that specific component.
There is a bug template (opens new window) 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
- Typically, the bug is initially triaged in the #ml-oss-bug-triage (opens new window) public channel on Mojaloop Slack
- 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. Details for security issues are covered here: https://docs.mojaloop.io/community/contributing/cvd.html
- During bug triage, priority and severity are assigned to the bug after majority consensus and consultation with reporter(s)
- Based on the priority and severity the bug is taken up by the Core team or other contributors based on a collaborative effort.
- Once it is taken up, conversation and updates happen on GitHub issue and slack channel.
# Triage
- The discussion regarding the issue is open to a public for normal bugs / issues
- Based on the discussions, a final call on the priority and severity of the issue is made by the Core team in consultation with the reporter(s).
- The list and the process will be updated as it evolves.
- Mojaloop bug triage slack channel #ml-oss-bug-triage (opens new window)