User:Sharihareswara (WMF)/TODO

Sumana's TODO general, braindump, somewhat prioritized, necessarily incomplete

Week of 27 June

 * Continue to manage GSoC -- urgent
 * Email all mentors & all students re upcoming midterm evaluations
 * Meet Aryeh
 * Get update from parser team and publicize their efforts
 * Follow up on contacts from Open Source Bridge
 * ping Danese & Erik re Developer Days
 * Documenting how our various test frameworks currently work -- 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
 * Update, focusing on architectural decisions to be made and opportunities for crowdsourcing
 * Finish rough edit of braindump, send to Mark & hashar
 * look into How To Write Unit Tests doc
 * Write up OSBridge conference report
 * check whether I am invited to mediawiki core meeting
 * Continue following up with potential volunteers, with especial attention to Wikimania, Postgres, WikiLove
 * Get Claudia's notes
 * Ask her about other open conferencing solutions for next week's TLDR meeting
 * ask for another order of business cards
 * look into getting Wikia people commit access. Who already has it?
 * send Carrie my dates for OSCON
 * start prepping Wikimania talk

Soon

 * Gather baseline metrics about volunteer base & corporate MediaWiki usage/contributions -- important
 * http://fastwonderblog.com/2011/06/22/open-source-community-metrics/
 * 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.
 * Find possible RTL devs
 * Ping the Israel Wikimedia
 * Ping people interested in the Egypt Wikimedia
 * Ping people interested in the Tunisia Wikimedia
 * Ping people interested in the Morocco Wikimedia
 * continue to look for metadata working group lead post-GLAMCamp
 * tell metadata & cultural partners people that Kaldari has to step back somewhat for 2 months
 * get comments on http://www.mediawiki.org/wiki/Requests_for_comment/Configuration_database
 * 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
 * Research high-volume MediaWiki contributors whom I don't know
 * Consider .deb issues, getting volunteer packagers to fix
 * Work with Mark Hershberger (and the rest of the Development Community group) to improve bug triage and reduce the unreviewed commit backlog -- important
 * every Monday, help Mark prep for bug triages, set work priorities
 * get global config object braindump from Chad & put it on project page
 * redlink off WMF GenEng page
 * recruit volunteers to work on this.
 * go through geneng meeting, ensure all project pages at least have stubs

Recruit

 * 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)

Longer-term

 * 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
 * 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.
 * 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
 * Re APS Wikipedia Initiative: Follow up on Rosta's toolserver account
 * chase Table of Contents extension for Etherpad
 * file bug re Etherpad scrollbar problem
 * chase deployment privilege separation
 * travel plans -- submit proposals
 * get work computer
 * get MediaWiki-related flyers designed
 * 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 volunteers to test MediaWiki OpenID extension
 * look at getting ideas, testing re hackpad as editor
 * 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