Confirmed users
241
edits
| Line 3: | Line 3: | ||
=== User Roles === | === User Roles === | ||
* Generate different user roles based on what tasks a user is trying to complete when using the BMO system | * Generate different user roles based on what tasks a user is trying to complete when using the BMO system. | ||
* Possible roles could be: | * Possible roles could be: | ||
** Triager: Someone who spends most of their time trying to determine if bugs are valid, if any additional information is required, and placing the bugs into the correct | ** Triager: Someone who spends most of their time trying to determine if bugs are valid, if any additional information is required, and placing the bugs into the correct product/component to get the proper attention. | ||
** Community Member: Someone involved with using the various products/projects and submitting feedback/bug reports when encountered. They are people who maintain their bugs | ** Community Member: Someone involved with using the various products/projects and submitting feedback/bug reports when encountered. They are people who maintain their bugs and make sure that Mozilla has enough information to ensure a proper fix/change. | ||
** Administrator: Manages the day-to-day duties of making sure that BMO has the proper products/components/versions/milestones/etc. needed for users to find the right place | ** Administrator: Manages the day-to-day duties of making sure that BMO has the proper products/components/versions/milestones/etc. needed for users to find the right place to report their bug. Also is involved with updating permissions for those requesting more access. | ||
** Patch Reviewer: Normally an engineer or someone well versed in the project's code and inner workings that will review other's patches for anything that can be improved. | ** Patch Reviewer: Normally an engineer or someone well versed in the project's code and inner workings that will review other's patches for anything that can be improved. They would need a helpful UI for viewing the patch, making comments on specific lines/sections, and then setting the proper flags to let the author know the status of the patch. Once the patch is reviewed (r+) they can then pass it off the the proper person to commit. | ||
** Patch Committer: Once a patch for an issue/feature has been reviewed, the committer (who may be same as reviewer) is responsible for overseeing that the patch is | ** Patch Committer: Once a patch for an issue/feature has been reviewed, the committer (who may be same as reviewer) is responsible for overseeing that the patch is committed to the proper project branch and also that it doesn't cause any regressions. This could be through the Try service or other means of automated building. The patch committer could then possibly pass off to QA to let them test the fix/feature once a new build is available containing the change. | ||
** And possibly others. | ** And possibly others. | ||