User:Sharihareswara (WMF)/TODO

Sumana Harihareswara's TODO list General, braindump, somewhat prioritized, necessarily incomplete.

Continuing

 * Continue following up with potential volunteers
 * Every Monday, help Mark prep for bug triages, set work priorities
 * 1:1, bug triage meeting, TL;DR meeting, platform engineering meeting, commit access queue meeting
 * GSoC wrapup
 * Push on merges
 * Submit blog post to Google
 * Get update from parser team and publicize their efforts

New/one-time

 * NOLA hackathon followup
 * a ton of follow-up to do: email volunteers/external people (Microsoft, GSoC)
 * India hackathon
 * outreach & recruiting
 * SocialCoding4Good followup, including email to wikitech-l
 * Email wikitech-l about using  &   keywords
 * Help Leslie find partman help
 * Help Aaron find volunteers to help with https://bugzilla.wikimedia.org/show_bug.cgi?id=31864 and https://bugzilla.wikimedia.org/show_bug.cgi?id=31863
 * Start keeping more systematic track of incoming contributors
 * Work with Mark Hershberger (and the rest of the Development Community group) to improve bug triage and reduce the unreviewed commit backlog
 * Ask Roan whether it is possible to filter the mediawiki.org code review stuff by reviewer.
 * Talk with Brion re code review mentoring/IRC office hours
 * Discuss testing community stuff with Mark & Ashar (testing mailing list? meetings?)
 * Mentor summit followup

Soon

 * ping Rob next week about TLDR/other-team coordination
 * Look into Bugzilla management ops stuff, consult with RobLa.
 * Create specs for community metrics needs... to gather baseline metrics about volunteer base & corporate MediaWiki usage/contributions
 * http://fastwonderblog.com/2011/06/22/open-source-community-metrics/
 * Sumana to identify available devs
 * Sumana: developing CRM-ish solution for devs
 * Investigate contributor agreement/ToS
 * find out if http://wiki.ubc.ca/Help:Widgets/SlideShare http://www.mediawikiwidgets.org/Widget:SlideShare is good with the new HTML5 magic
 * Send out hackathon metrics thoughts?
 * gather & publicize Platform Eng meeting notes
 * gather & publicize notes from MW core team meeting
 * find developers who have been reverted most (proportionally) recently, talk with them about improving
 * re pywikipediabot commit access: write a guide - explain how to get it; document on meta, link to from mediawiki.org
 * ask http://wiki.ubc.ca/Special:Version about their extensions
 * Talk with Dario re followup from Data Summit
 * help fundraising team liaise with Wikimedia, Drupal, CiviCRM, etc. communities
 * Consider .deb issues, getting volunteer packagers to fix
 * write MarkH a note for him to post to Debian pkgers list re hiphop
 * remind him to file an intent to package bug -- or rather request for a package
 * also Mark knows Red Hat packager dude now at Mozilla

Recruit

 * Sumana to document best practices for aiding enthusiastic general & specifically driven volunteers
 * find PhotoCommons testers and users, & suggest people port it to other CMSes
 * find WikiLove localizers
 * find Narayam testers
 * find HipHop packagers
 * find someone to shepherd Josh's page-by-page-auth extension
 * reach out to http://wikiindex.org/User:Gwsuperfan
 * HipHop: Sumana will target Fedora and Ubuntu for recruiting packagers, maybe CentOS (RPMs anyway)
 * (Sumana to help get contributors to package HipHop for different *n*x distros, to make it easier to work with)
 * testers for MediaWiki OpenID extension
 * reach out to http://phpsp.org.br/
 * More on Chad's global config RfC
 * redlink off WMF GenEng page
 * recruit volunteers to work on this
 * Get into gadgets/user scripts community
 * Get into extensions community
 * Get into toolservers community
 * Get into templates community

Longer-term
My goal is to facilitate volunteer contributions, and there are a few missing parts right now that slow me down, and slow down volunteers who want to help. The main problems I'm worried about:
 * Code review in general. For example, per https://www.mediawiki.org/wiki/MediaWiki_roadmap/1.18/Revision_report, we've been stuck at 46 to-review revisions tagged 1.18 for about a week.  And the http://toolserver.org/~bryan/stats/codereview-status-diff.png chart is worrying.
 * Ideas: I know RobLa is working on this. Some ideas: Get aggressive about hiring the security engineer (who will do code review)...
 * We are simply not good enough at reviewing and responding to new volunteers' contributions quickly. They usually come through Bugzilla, and we have 146 MediaWiki patches in BZ waiting for review:  https://bugzilla.wikimedia.org/buglist.cgi?keywords=patch%2C%20need-review%2C%20&keywords_type=allwords&order=Last%20Changed&type0-0-6=matches&field0-0-4=short_desc&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=MediaWiki&type0-0-2=substring .  I predict the Bugzilla patch queue will continue to exist even after we switch to git, because many newbies won't learn git until after they start contributing patches.
 * Ideas: Mark and I try to get through twenty patches each week (we failed at sprinting in early November; maybe we need a daily meeting?); I encourage a patch review squad, especially new developers who don't have as many commitments already; do it at hackathons as a way to teach code review?
 * Our best source of interested developers will be MediaWiki administrators. But we don't provide a good pipeline for them to get involved in development.  And it's hard for administrators to even learn of the existence of extensions and to intuit which extensions would be best to install, and thus to get on the path to becoming power users (and possibly developers).
 * Ideas: get a pointer onto the last page of the install screen that to links to an extensions portal on mediawiki.org, and mention the four that people really ought to install, like Cite; do a sweep of some "powered by MediaWiki" sites and their Special:Version pages and contact them to suggest extensions to install; publicize Gadgets more when ResourceLoader 2 comes out, and suggest to them that they use the main gadgets repo...


 * Build awareness of our Great Movement Projects & Strategic Opportunities in the existing volunteer development community and in new & returning volunteers -- important
 * Goal for the TL;DR team - not just about increasing contribution, also aligning community around our goals.
 * Sumana to author post(s) about priorities from whitepaper (help from Guillaume), to reach out to tech communities, encourage volunteers
 * get Debian/Ubuntu pkg of MediaWiki onto 1.17 - low priority.
 * Get toolserver account to make, host tools to gather & display stats re SVN & bugzilla
 * Get in-person MediaWiki ramp-up help from engineers, and synthesize that into training documents for future installfests
 * find PHP students/kids to encourage into MediaWiki at schools
 * help them with travel to hackathons & invite them
 * Build my knowledge of conferences, distribution channels, and other means by which we can find potential volunteers, and running pilot events as seems feasible.
 * http://www.catchafire.org/org_home
 * try to get pro bono security pentesting? maybe from Matasano or a similar firm
 * Consider PCF, Mozilla, GNOME, etc for QA infrastructure idea -- mailing list, etc.
 * think, and soon, about community/contributor guidelines, both behavioral & coding
 * Check how Mozilla & Canonical do Agile, + Launchpad, OpenStack & other open source Agile projects
 * investigate Mozilla (they started requiring tests a few years ago) on how they get volunteers to write tests
 * shell bugs: Communication plan. E.g. foundation-l, & think about longterm messaging for all admins, for notifications, & translations.
 * watch out for shell bug process & organize volunteer sprints
 * get Claudia the data about current situation. What kind of people develop the software today?
 * analysis of committers, what characteristics they have. She has a bunch of scripts in Java and we are encouraging her to share them with us.
 * specify the features. What's possible?  Ohloh.....
 * check out http://sonivis.org/
 * http://worldvista.org/conference_presentations/21st_VCM_GMU/CMU%20presentation.pdf/view
 * http://conway.isri.cmu.edu/%7Ejdh/web-pubs/pdfs/vista_report_2010_final-formatted.pdf
 * chase deployment privilege separation
 * travel plans -- submit proposals
 * Ramp up on my technical knowledge of MediaWiki

Recruit

 * look at getting volunteers to help Siebrand re WikiBhasha - removing cruft, adding support for Google MT
 * look at getting ideas, testing re hackpad as editor
 * look into code review mentorship program
 * ask ops to contribute upstream their custom hacks to OTRS
 * look up Dmitriy Sintsov,, the evil IP address, Banaticus & Billinghurst re: music sheets plugin
 * documentation: per RobLa's suggestion:
 * I would suggest is that we potentially recruit people who work on the more technical parts of enwiki, rather than just focusing on people who are already on mediawiki.org. Maybe start at "Village Pump (technical)" and then also see what editors are active on things like template help pages and other scarier parts of the system.


 * and Zak's plan: http://www.mediawiki.org/wiki/User:Zakgreant/Tech_Docs_Plan_(2011-01/P6M)
 * recruit user Pinky, MattJ, & Lhridley
 * reach out to JeLuF, Jojo, aran per ohloh