User:Sharihareswara (WMF)/TODO

Sumana's TODO general, incomplete, braindump, not prioritized

Week of 1 June

 * vacation Monday & Tuesday
 * look for metadata working group lead post-GLAMCamp
 * Continue following up with potential volunteers, with especial attention to parser.

Soon

 * Continue to manage GSoC -- urgent
 * Gather baseline metrics about volunteer base & corporate MediaWiki usage/contributions -- important
 * Sumana to identify available devs
 * Sumana: developing CRM-ish solution for devs
 * Ask Roan whether it is possible to filter the mediawiki.org code review stuff by reviewer.
 * Work with Mark Hershberger (and the rest of the Development Community group) to improve bug triage and reduce the unreviewed commit backlog -- important
 * Build awareness of our Great Movement Projects & Strategic Opportunities in the existing volunteer development community and in new & returning volunteers -- important
 * Sumana to author post(s) about priorities from whitepaper (help from Guillaume), to reach out to tech communities, encourage volunteers
 * Document Berlin hackfest and build relationships with volunteers I met there
 * Sumana & Guillaume to clean up documentation from Berlin 2011 hackathon. Copypasting some notes into wiki pages.
 * Ramp up on my technical knowledge of MediaWiki
 * Build my knowledge of conferences, distribution channels, and other means by which we can find potential volunteers, and running pilot events as seems feasible.
 * Consider PCF, Mozilla, GNOME, etc for QA infrastructure idea -- mailing list, etc.
 * Check how Mozilla & Canonical do Agile, + Launchpad, OpenStack & other open source Agile projects
 * think about what to do with the big meeting (GenEng)
 * 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
 * Send RobLa, etc. notes re Canonical & code review
 * chase Table of Contents extension for Etherpad
 * file bug re Etherpad scrollbar problem
 * chase deployment privilege separation
 * create braindump of how testing currently works, and what decisions we need to make, and how volunteers will be involved in writing & maintaining test cases
 * travel plans -- submit proposals
 * get business cards
 * get work computer
 * get MediaWiki-related flyers designed

Recruiting

 * recruit wiki gnomes for Project pages
 * Sumana to document best practices for aiding enthusiastic general & specifically driven volunteers
 * watch parser conversation, point people to http://www.mediawiki.org/wiki/Future/AST and http://www.mediawiki.org/wiki/Future/Parser_test_cases to contribute
 * find PhotoCommons testers and users, & suggest people port it to other CMSes
 * find WikiLove localizers
 * find Narayam testers
 * find HipHop packagers
 * 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)
 * look at getting volunteers to help Siebrand re WikiBhasha - removing cruft, adding support for Google MT
 * look at getting volunteers to test MediaWiki OpenID extension
 * look at getting ideas, testing re hackpad as editor
 * contact OverlordQ and Greg Sabino Mullane re Postgres support, http://www.chesnok.com/daily/2011/05/19/announcing-postgres-open/
 * https://bugzilla.wikimedia.org/16794
 * look into code review mentorship program
 * Joachim, & Markus Glaser talked about Selenium, PHPUnit, QUnit, Cruise Control, & testing infrastructure & process
 * ask ops to contribute upstream their custom hacks to OTRS