Google Code-in 2017 just started:
https://www.mediawiki.org/wiki/Google_Code-in/2017
You might remember the announcement email from a few weeks ago.[1]
In the next seven weeks, many young people are going to make their
first contributions to Wikimedia. Expect many questions on IRC and
on mailing lists by newcomers who have never used IRC or lists
before. Your help and patience is welcome to provide a helping hand!
Thanks to all mentors who have already registered & provided tasks!
You have not become a mentor yet? Please consider it!
You get some smaller tasks fixed and it is fun!
* Think of easy tasks in your area that you could mentor.
Areas are: Code, docs/training, outreach/research, quality
assurance, and user interface. "Easy" means 2-3h to complete for
you, or less technical ~30min "beginner tasks" for onboarding).
* OR: provide an easy 'clonable' task (a task that is generic and
could be repeated many times by different students).
* Note that you commit to answer to students' questions and to
evaluate their work within 36 hours (but the better your task
description the less questions. No worries, we're here to help!)
For the full info, please check out
https://www.mediawiki.org/wiki/Google_Code-in/Mentors
and ask if something is unclear.
Thank you again for giving young contributors the opportunity to learn
about and work on all aspects of Free & Open Source Software projects.
Now bring your tasks!
Cheers,
andre
[1] https://lists.wikimedia.org/pipermail/wikitech-l/2017-
October/088956.html
Hey everyone,
The voting phase of the 2017 Community Wishlist Survey has now started.
Read the proposals and support the ones you want to support to make the
wikis better:
https://meta.wikimedia.org/wiki/2017_Community_Wishlist_Survey
Click on the categories to find the proposals. The voting will close on
December 10.
That's the important part of this email. Feel free to follow the link above
and starting voting right now.
The longer version:
The Community Wishlist Survey decides what the Wikimedia Foundation
Community Tech team will work on over the next year. The team is responsible
for addressing the top 10 wishes on the list, as well as some wishes from
smaller groups and projects that are doing important work, but don't have
the numbers to get their proposal into the top 10. The Wishlist is also
used by volunteer developers and other teams, who want to find projects to
work on that the community really wants.
Come help set the agenda.
If you want to see what the team has done in 2017, see the status report
from last month:
https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Status_repor…
What you can do now:
*) Vote. This is the most important thing.
*) Spread the word. We really want people to find this, of course, and
we'll work on finding the best balance between spreading the news to
everyone and not being annoying, but please do help to spread the
information in your local community – Village Pump equivalents, IRC
channels, social media groups and so on.
*) Help translating the pages. We want the process to be as available as
possible for everyone. It's not every available if it's only in English.
*) If you want to get short updates through the notification system, you
can sign up for the Community Tech Newsletter:
https://www.mediawiki.org/wiki/Newsletter:The_Community_Tech_Newsletter
FYI:
Wikimedia has been accepted as one of 25 organizations in Google Code-
in (GCI) 2017!
GCI is a contest for 13-17 year old students to work on smaller tasks
on your To-Do list. It starts on Nov 28th. We need at least 75 tasks by
then. Code, docs, research, design, QA, anything (except translations)!
What you should do:
BECOME A MENTOR:
1. Go to https://www.mediawiki.org/wiki/Google_Code-in/2017
2. Add yourself to the mentor's table.
3. Get an invitation email to register on the contest site.
IDENTIFY AND PROVIDE SMALL TASKS:
1. Create a Phabricator task (which would take you 2-3h to complete)
or pick an existing Phabricator task you'd mentor.
2. Add the "Google-Code-In-2017" project tag.
3. Add a comment "I will mentor this in #GCI2017".
Feel free to directly create tasks on the GCI website yourself once
you've registered. (We can also import them for you.) If your project
does not use Phabricator: Just create tasks directly on the GCI site.
Looking for task ideas? Check the "easy" tasks in Phabricator:
https://www.mediawiki.org/wiki/Annoying_little_bugsoffers links.
Make sure to cover expectations and deliverables in your task.
And once the contest starts on Nov 28, be ready to answer and review
contributions quickly (within 36 hours).
Any questions? Just ask, we're happy to help.
Thank you for your help to get young people into FOSS projects!
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
Reminder: Technical Advice IRC meeting again **tomorrow, Wednesday 4-5 pm
UTC** on #wikimedia-tech.
The Technical Advice IRC meeting is open for all volunteer developers,
topics and questions. This can be anything from "how to get started" over
"who would be the best contact for X" to specific questions on your project.
If you know already what you would like to discuss or ask, please add your
topic to the next meeting: https://www.mediawiki.org/wiki/Technical_
Advice_IRC_Meeting
This meeting is an offer by WMDE’s tech team. Hosts of tomorrows meeting
are: @addshore & @CFisch_WMDE.
Hope to see you there!
Michi (for WMDE’s tech team)
*Kind regards*
*Alangi Derick N*
*V. Developer @ Wikimedia*
*https://meta.wikimedia.org/wiki/User:Alangi_Derick
<https://meta.wikimedia.org/wiki/User:Alangi_Derick> *
*[image: https://twitter.com/AlangiDerick]
<https://twitter.com/AlangiDerick>
<https://www.facebook.com/derick.alangi> *