Hello all,
There is a new internship opportunity in the Community Engagement
department for a Technical Design Intern. We are looking for a candidate
who works and/or studies in the field of computer science and information
systems, has experience in advanced wiki markup and design skills for web,
and the ability to excel in a fast-paced, multitasking environment, among
other qualifications. Knowledge and or experience with Wikimedia Projects
a plus!
The Technical Design Intern will work closely with the Communications and
Outreach Coordinator (that would be me!) on the Wikimedia Resource Center,
the redesign of the Evaluation Portal on Meta Wikimedia, and migration and
archiving of L&E portal pages from existing namespaces to new namespace,
among other tasks. You can find the complete job description here:
https://boards.greenhouse.io/wikimedia/jobs/488570#.WBE6X-
<https://boards.greenhouse.io/wikimedia/jobs/488570#.WBE6X-ErKRs>ErKRs
<https://boards.greenhouse.io/wikimedia/jobs/488570#.WBE6X-ErKRs>
If you are interested, please apply. If you know someone who might fit this
position, please forward the email to them!
Cheers,
*María Cruz * \\ Communications and Outreach Coordinator, L&E Team \\
Wikimedia
Foundation, Inc.
mcruz <mcruz(a)wikimedia.org>@wikimedia.org <mcruz(a)wikimedia.org> |
Twitter: @marianarra_
<https://twitter.com/marianarra_>
Google Code-in 2016 has been announced: A contest for 13-17 year old
students. While we wait for Wikimedia to get accepted:
Take those 10 minutes to find (or update) some Phabricator tasks in
your project(s) that would take an experienced contributor 2-3 hours.
* Do you have small, self-contained bugs you'd love to get fixed?
* Does your documentation need improvements?
* Does your user interface have small design issues?
* Does your Outreachy/Summer of Code project welcome small tweaks?
* Would you enjoy helping someone port your template to Lua?
* Does your gadget use some deprecated API calls?
* Do you have tasks in mind that welcome some research?
We have nearly 600 open "easy" tasks listed:
https://phabricator.wikimedia.org/maniphest/query/609oZQR8EpOH/#R
Are the tasks in your area clear enough and still valid?
And can you imagine helping a young person fix some of these tasks?
* Add the project "Google-Code-in-2016" and a comment in Phabricator
tasks that you would mentor those tasks.
* Tasks are welcome in five areas: Code; Outreach/Research;
Documentation/Training; Quality Assurance; User Interface.
* Add yourself to the table of mentors on the wikipage.
* Make sure the task description provides pointers to help the student.
* "Beginner tasks" (e.g. "Set up Vagrant"?) also very very welcome!
* "Generic" tasks also welcome (e.g. "Choose and fix 2 UI messages
from the task list in https://phabricator.wikimedia.org/T40638 ").
For complete info about Google Code-in, check
https://www.mediawiki.org/wiki/Google_Code-in_2016#Mentors.27_corner
Unsure about quality of contributions in GCI and effort? Please read
https://lists.wikimedia.org/pipermail/multimedia/2015-January/001009.html
Please ask if you have questions. Happy to help!
See you in Google Code-in!
*Inverencial PeaceAlangi Derick Ndimnain*
Here is a message from Quim Gil of Wikimedia
How to grow our technical community? This is a main topic at the upcoming
Wikimedia Developer Summit (San Francisco, January 11-13, 2017).
There is a call for participation open until the end of this month (October
31). Your proposals for discussions related to this main topic are welcome!
There are some ideas about possible topics at
https://www.mediawiki.org/wiki/Wikimedia_Developer_
Summit/2017/How_to_grow_our_technical_community
If you are interested in contributing to the discussions about How to grow
our technical community, please join us at the Summit (the deadline to
request travel sponsorship is next Monday, October 24).
PLEASE ENCOURAGE OTHER PEOPLE to submit a proposal and/or join the Summit.
This email will likely arrive to the core of the Wikimedia technical
community, but the chances to arrive to the periphery and beyond are a lot
smaller. We need your help! We want to discuss how to grow our technical
community including the perspectives of those who haven't joined us yet.
*Inverencial PeaceAlangi Derick Ndimnain*