Google Code-In is a contest to introduce pre-university students (ages 13-17) to the many kinds of contributions that make open source software development possible. Students must complete tasks (see examples), one at a time. The Google Code-in 2013 contest runs from November 18, 2013 to January 6, 2014.
https://www.mediawiki.org/wiki/Google_Code-In
There has been a discussion in this list about listing little bugs ready for newcomers. I'm sure there is also potential for documentation tasks e.g. small tutorials or step-by-step guides. Also, do you have cleanup tasks that someone must do (or program a little script / bot to do)? All these are good potential tasks for Code-in.
What do you think?
We are currently preparing the proposal to apply by Oct 28, next Monday. If you can add at least 5 tasks to the wiki page linked above then you will be ready for the next level - if we are one of the organizations selected on November 1.
If you have questions just ask, here or at the related talk page.
PS: Lydia is an expert Code-in mentor / org admin but I'm explicitly NOT requesting her to get involved as she usually volunteers to so. This is in fact a very good opportunity for new mentors with some free time and a will to help new contributors that perhaps perhaps will stick around and become Wikidata fans thanks to you.