Outreachy: Difference between revisions

Outreachy (view source)

Revision as of 22:18, 20 March 2017

284 bytes added , 20 March 2017

→‎bugzilla.mozilla.org improvements: edit and add fourth option

Emceeaich

Administrators

550

edits

@@ Line 271: / Line 271: @@
 '''Project Description:'''
-) [BMO RESKIN] Mozilla recently rebranded, and BMO doesn't match this re-branding at all. It would be nice to reskin it to look like the central Mozilla property it is.
+Participant would select from one of these projects:
+) [BMO RESKIN] Mozilla recently re-branded, and BMO doesn't match the new look. It would be nice to reskin it to look like the central Mozilla property it is.
 Skills: CSS, HTML Templates, Perl
-) [BZ KANBAN] There is a kanban board that works using bugzilla APIs: https://github.com/leif81/bzkanban it would be very nice for (some teams, anyway) if this was integrated into BMO.
+) [TRIAGE VIEW] Build a supplemental bug editing view optimized for triaging bugs. This would afford the participant the chance to do rapid prototyping, test ideas with senior engineers, and help with an important workflow
+Skills: JavaScript, CSS, HTML, Perl
+) [BZ KANBAN] There is a kanban board that works using bugzilla APIs: https://github.com/leif81/bzkanban it would be very nice for (some teams, anyway) if this was integrated into BMO.
 Skills: JavaScript, CSS, HTML, Perl
-) [METRICS GRAPHICS @ BMO] We have a very old reporting infrastructure that generates reports server-side and looks ugly. Meanwhile, another part of Mozilla has created the metrics graphics library. At minimum, replacing our existing reporting system with this would look spiffy.
+) [METRICS GRAPHICS @ BMO] We have an old reporting infrastructure that generates reports server-side and looks ugly. Meanwhile, another part of Mozilla has created the metrics graphics library. We would like to replace the old infrastructure with the new.
 ====Implement UI Automated Tests for Treeherder using Selenium and Jasmine====