Changes

Jump to: navigation, search

BMO/UserRoles

586 bytes added, 22:09, 4 April 2013
Possible Next Actions
** https://bugzilla.gnome.org/page.cgi?id=describeuser.html&login=danielle%40madeley.id.au
* Revive dkl's past canned comment work and revise for rolling out to production. Needs a couple things done to be production quality.
* Add more detail to the Dashboard such as providing a review link to Splinter directly if an attachment review flag has been requested. Show a list of bugs that have not been acted on after a specified period of time or possibly need to beclosed. Show a list of recently visited bugs for the user to get back to quickly.* Improve the current Splinter by fixing some of the smaller issues with regard to patch parsing. Then work toward separating out the patch parsing logic from javascript anduse the built in PatchReader code instead. And then lastly, look into replacing Splinter with codereview.js making sure we keep feature parity with the current tool. https://wiki.mozilla.org/BMO/Splinter* Talk to Releng about helping us with support of the AutoLand system and make sure that it becomes maintained properly by IT. Figure out what needs to be done on BMO to supsupport the additional features needed by AutoLand and then get some testing and feedback from engineers.
** Should start this discussion ASAP.
* Work with Byron to decide on how to best implement user roles in BMO and figure out how to migrate people to the proper roles (mozillians.org?).
* Work with Triage to decide on how we can improve the current bug view and what documentation could be improved to make the bug report better informed. Also see what statusstatuses/keywords/etc. can be added/changed to make it more apparent that a bug is ready for a developer to look at (think: READY state).
** Latter is hopefully being solved right now in the "Making CanConfirm default to UNCO state" discussion.
** Great first role since lizzard is sorting out triage processes right now.
Confirm
241
edits

Navigation menu