Outreach programs/Possible mentors

What possible and actual mentors need to know.

Before

 * 1) Read our Selection process and Lessons learned.
 * 2) Become a mentor officially (at GSoC 2015 melange):
 * 3) *login,
 * 4) *click "Create profile" on the home if you see such an orange button,
 * 5) *then "Start connection" (with Wikimedia),
 * 6) *once you are accepted as a mentor: "Wish to mentor" the proposals you want to mentor.
 * 7) Seek long term contributors, not just new features. It probably takes more time to mentor a project than to complete it yourself.
 * 8) Choose the best candidate, not the one that arrived first. Early birds have more chances indeed, but we must respect the timeline.
 * 9) Don't choose a candidate based only on a convincing proposal and past experiences. They must complete microtasks related with their project.
 * 10) Communicate transparently in public channels, allowing fairness among candidates and involvement of other community contributors.
 * 11) Require from all candidates public documentation and regular participation in the community channels of your choice.
 * 12) Score you own candidates. OPW has self-explanatory options. In GSoC, we have:
 * 13) * [[File:Inkscape_icons_draw_star.svg]] decline
 * 14) * [[File:Inkscape_icons_draw_star.svg]] [[File:Inkscape_icons_draw_star.svg]] still unsure
 * 15) * [[File:Inkscape_icons_draw_star.svg]] [[File:Inkscape_icons_draw_star.svg]] [[File:Inkscape_icons_draw_star.svg]] accept
 * 16) Don't share any information about acceptance with your candidates before the official announcements.

During

 * 1) Aim to get a viable minimum product out the door. Fine tune plans as needed. Don't leave the merge to the end.
 * 2) Require your contributors to release soon, release often, and report in the project wiki page on a weekly basis.
 * 3) Be in touch regularly, between daily ping and weekly calls.
 * 4) Encourage them to participate in community spaces and to ask there for help, with or without you.
 * 5) Before the end of the program make sure all the open tasks are documented, all the known bugs are filed.

After

 * 1) Share your own conclusions of the project, help improving our lessons learned.
 * 2) Recommend new tasks to the not-so-new contributor, in your project or wherever you think they will fit in our community.

Guides for mentors

 * GSoC Mentoring manual.
 * The DOs and DON’Ts of Google Summer of Code: Mentor Edition.
 * Federico's HOWTO
 * "What makes a good mentor"

The bench
Past mentors, just for reference. If former mentors are missing, just add them.


 * Raylton P. Sousa: Interested in stuff relating to sister [non-wikipedia] projects (or maybe generic things like this and this).
 * Brian Wolff.: Particularly interested in any project where the student is a member of the relevant community the project is targeting, and the student came up with the project him/her-self to fix a problem that they are actually encountering.
 * Jeroen De Dauw: I'm involved with both Semantic MediaWiki and Wikidata and willing to mentor interesting projects related to either. I prefer to mentor students who already have a decent background with doing development work.
 * Yury Katkov: I'm involved in developing extensions for MediaWiki and Semantic MediaWiki plus I'm active community member focused on bringing MediaWiki closer to a 3rd party companies and developers.
 * Siebrand Mazeland: Available for helping with the student selection process, available as a mentor if really needed. I'm not really a developer, but I have a little experience in working with them.
 * Yuri Astrakhan: Will mentor most of the external API related work.
 * Tyler Romeo: I'm available to mentor the E:CSS, E:UploadWizard, the XML sitemaps extension, automatic category redirects, and/or E:OEmbed*. Which one I do I'll leave up to somebody who has a better idea of which projects WMF would prefer. Depending on the time commitment involved, I may be able to mentor more than one project.
 * Thomas PT: I'm available as co-mentor for Wikisource-related proposals. I won't be able to help in June and the begin of July but I'll be very pleased to help in August.
 * Yaron Koren: Semantic MediaWiki, Semantic Forms, and related extensions.
 * James Forrester: VisualEditor related projects.
 * Niklas Laxström: internationalization projects.
 * Santhosh Thottingal: internationalization projects.
 * Federico Leva: willing to co-mentor Tools for mass migration of legacy translated wiki content as Meta-Wiki community liasion.
 * Runa Bhattarcharjee: internationalization projects.
 * Alolita Sharma: internationalization projects.
 * Ariel Glenn: Wikimedia offline projects.
 * Kelson: Wikimedia offline projects (openZIM/Kiwix).
 * Matt Flaschen: Prototyping inline comments and SASS/LESS support for ResourceLoader
 * Rusty Burchfield: CSS extension projects.
 * Michael Dale: Multimedia / HTML5 related projects.
 * Sam Reed: Bugzilla-MediaWiki extension.
 * Katie Filbert: Wikidata-related projects.
 * Pau Giner: internationalization projects.
 * Amir E. Aharoni: internationalization projects, right-to-left languages, translation, outreach.
 * Jan Luca Naumann: MW-Moodle-extension
 * Stephan Gambke: I contribute to extensions connected to Semantic MediaWiki and would mentor in that area.
 * Željko Filipin: Browser Test Automation
 * Chris McMahon: Browser Test Automation
 * Zaran: willing to co-mentor the proofread page extension refactoring.
 * Nischay Nahata: I would be available to co-mentor projects related to Extension:UploadWizard.
 * Micru: Available to co-mentor the Book upload customization project.
 * Daniel Kinzler: Available to mentor Wikibase-related projects, as long as they are not too heavy on JavaScript.
 * Sébastien Santoro: I'm offering to mentor Wikimedia Commons related projects. I'm also available for a more generic project for a student who comes from another language and would like to learn PHP / improve PHP skills.
 * Kartik Mistry: Internationalization projects, translation.
 * Sumana Harihareswara: Product management, community management, documentation.
 * S Page: Mentor projects related to Flow (discussion and collaboration software)
 * John Vandenberg: especially Pywikibot, but also development practises and tools.