703655 - Create list of 50 mentored web development bugs covering all major sites

Status: NEW

(Websites :: Other, enhancement)

Description

[David Boswell]

We should create a list of mentored bugs for people interested in getting involved with web development that cover all of our major sites.  For more information on how to mark bugs as mentored, see:

https://wiki.mozilla.org/Mentors

In the short-term this list will help Luke, who is responding to webdev inquiries coming from the Get Involved pages, find good bugs to give to people.  

Longer term these mentored bugs can be used in a tool to help people more easily find good bugs themselves.  For an example of what that could look like, see this demo page:

http://www.joshmatthews.net/bugsahoy/

Comment 1

[Luke Crouch [:groovecoder]]

Like http://mzl.la/webdev_mentored_bugs ? Or should we make a wiki page with that bug list?

Comment 2

[David Boswell]

(In reply to Luke Crouch [:groovecoder] from comment #1)
> Like http://mzl.la/webdev_mentored_bugs ? 

That's great.  Since we have a list we could close this bug -- unless we wanted to try to create a list with a certain number of mentored bugs (50 maybe?).

> Or should we make a wiki page with that bug list?

Having a wiki to display these mentored bugs sounds like bug 735026.  That page will include a dynamic list of mentored bugs for a range of different sites.

Comment 3

[Luke Crouch [:groovecoder]]

I think that's a reasonable objective - have 50 [mentor= webdev bugs available to potential contributors. I'm cc'ing a bunch of webdev's who should be able to tag such bugs in their projects.

Comment 4

[Devika Sugathan]

Hello,
I'm an absolute beginner and would like to work on this.

Comment 5

[tofumatt [:tofumatt]]

Devika: This project would require knowledge of Mozilla structure and process so isn't a great place to start as a beginner. Sorry about that!

I think this issue could probably be closed as there have been good first bug initiatives since and the web development teams are now spread out across products rather than one big team. It's probably best to find a project you'd like to work on and go from there.