User:Sharihareswara (WMF)/TODO

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

Continuing

 * GSoC wrapup
 * Get final emails from Kevin Brown, Yuvi Panda
 * Get update from parser team and publicize their efforts
 * 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
 * gather & publicize Platform Eng meeting notes
 * 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
 * NOLA hackathon planning
 * Get into gadgets/user scripts community, invite people
 * Get into extensions community, invite people
 * Get into toolservers community
 * Get into templates community
 * systematize NOLA hackathon planning & recruiting
 * For hackathons: Star_Mississippi, X!
 * https://secure.wikimedia.org/wikipedia/wikimania2010/wiki/Schedule
 * https://secure.wikimedia.org/wikipedia/wikimania2010/wiki/Submissions/Creating_offline_version_of_Wiki_content_-_Solutions_and_Challenges
 * https://secure.wikimedia.org/wikipedia/wikimania2010/wiki/Submissions/Spatio-Temporal_Analysis_of_Revision_Metadata_and_the_STiki_Anti-Vandalism_Tool
 * http://wikitech.wikimedia.org/index.php?title=File:Ryan_Lane_-_How_to_be_a_part_of_the_MediaWiki_developer_community.pdf&page=26

New/one-time

 * Talk with Dario re followup from Data Summit
 * File expenses
 * gather & publicize notes from MW core team meeting
 * Set up dedicated identi.ca/twitter feed of upcoming MediaWiki bug triages & events (IRC office hours, etc.)
 * Finish up New Orleans hackathon recruiting & invitations
 * Follow up with tech community regarding AOSA book writing
 * Investigate contributor agreement/ToS
 * Arrange October travel, family care
 * computer setup
 * Weekend of Code planning
 * QA recruiting/interviewing
 * read, advise on Claudia's research thing

Soon

 * Chase IRC cloak
 * Send out hackathon metrics thoughts?
 * Turn HOWTO workshop notes into a real curriculum by 28 September for Madras hackfest
 * 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.
 * Work with Mark Hershberger (and the rest of the Development Community group) to improve bug triage and reduce the unreviewed commit backlog -- important
 * 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
 * find developers who have been reverted most (proportionally) recently, talk with them about improving

Longer-term

 * Build awareness of our Great Movement Projects & Strategic Opportunities in the existing volunteer development community and in new & returning volunteers -- important
 * Goal for the TLDR 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.
 * 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 Table of Contents extension for Etherpad
 * file bug re Etherpad scrollbar problem
 * 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)