Create a pretty page that combines https://blog.mozilla.com/webdev/get-involved/ info with list of bugs for each site. (http://www.mediawiki.org/wiki/Extension:Bugzilla_Reports)
Actually it should use https://github.com/mozilla/mediawiki-bugzilla, which is installed already.
Ricky, Mike and I just tried this out and got a basic page working at https://wiki.mozilla.org/Webdev/GetInvolved This pulls in mentored bugs for AMO, SUMO and MDN. There's still a lot of polish that could be done here, including adding contact information, screenshots, refining query to show just open bugs, etc. We'd also want to expand this to include at least a few more sites. Ricky said he'd take a pass at the page and would open a bug to have the old static Webdev get involved page redirected to this. We can also talk to Luke about how to include the link to this in the information we're sending to people interested in Webdev coming through the Get Involved page.
I can't seem to find the new Canned Response content. The copy on https://wiki.mozilla.org/Mozilla.org/Contribute/Canned_responses#Coding_.28Webdev.29 is the old stuff. https://bitly.com/bundles/mozillafoundation/9 shows the IRC link is the most-clicked, so I think we should keep that in the response. The next most-clicked is the mentored bugs list. Distant 3rd and 4th are the "Bugzilla for Humans" video and the documentation links. So, I'd say we keep the IRC link and also link to this page for the mentored bugs along with a link to Bugzilla for Humans and Docs.
(In reply to Luke Crouch [:groovecoder] from comment #3) > I can't seem to find the new Canned Response content. The copy on > https://wiki.mozilla.org/Mozilla.org/Contribute/Canned_responses#Coding_. > 28Webdev.29 is the old stuff. The latest canned response is in the Webdev action plan at https://wiki.mozilla.org/Contribute/Webdev#Canned_Response The email text that the form is using is also in Github at https://github.com/mozilla/bedrock/blob/master/apps/mozorg/templates/emails/webdev.txt > https://bitly.com/bundles/mozillafoundation/9 shows the IRC link is the > most-clicked, so I think we should keep that in the response. The next > most-clicked is the mentored bugs list. Distant 3rd and 4th are the > "Bugzilla for Humans" video and the documentation links. > > So, I'd say we keep the IRC link and also link to this page for the mentored > bugs along with a link to Bugzilla for Humans and Docs. Changing the mentored bugs link to the new wiki page sounds like a good idea. If the other links are being clicked on much less frequently it may make the next steps clearer for people to remove them from the auto-response. Maybe a better place for the "Bugzilla for Humans" and documentation links are from the new Get Involved with Webdev wiki page?
FYI, I just added a little polish to the page -- added screenshots and linked the IRC channels. Other people should consider what's there as a template and feel free to use it to add information about other sites that have mentored bugs you want to get in front of webdev contributors.
I finished adding the rest of the projects that were on the blog page along with the mentored bugs. It looks like we have almost 40 mentored bugs total (I think the goal was 40?).
I don't think we ever settled on a set of volunteer goals, but having a goal for the number of open mentored bugs makes sense. We probably also want to connect this to a goal for having an average time to resolution for mentored bugs to make sure we're actually getting things done and not just creating a list of bugs that never get fixed. I'll add this as a discussion topic for the next Webdev Contribute Group.
Closing as fixed since the new page is now live. We can track linking to this and measuring the effectiveness in separate bugs. Also see the Webdev contribute plan for more information: https://wiki.mozilla.org/Contribute/Webdev
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in before you can comment on or make changes to this bug.