Thank you Andre for mentioning Newsletter extension here. For the numbers, we have 15 tasks completed as of 14 days, and we have 1 more left with a student working on it. Andre asked me to share how GCI works for our project, in an attempt to *push* more maintainers in this list to add in and mentor more GCI tasks. Its a fact that Wikimedia is running out of tasks, and lets hope this mail goes through well.

Some general pointers, which I think works out:

1. Come out with simple *independent* tasks for your project - which has a proper description for a complete newcomer of what needs to be done. This can start usually with a line like 'This tasks requiures $extension to be installed'. 2. Never underestimate the students - from what I see from their patchsets, the students who I had to deal with are really good, and understand the software pretty easily. Good luck to get those there. 3. If you *cannot* find tasks for the project, think about dropping an email to *any* Google Summer of Code/Outreachy intern who has worked *previously* with your project. This works great, and we had huge help coming around from them. Even though a lot of mails were sent, personal email from the maintainer can mean much more, I would say. 4. If you know any non developers who can test your application brining in more design and software bugs - they are your best chance. If your extension/project is in a design review phase - each and every *sensible* comment can be made a GCI task! We had our extension hosted in labs - http://newsletter-test.wmflabs.org/ - and we had people like Quim Gil ready to test things out, bringing in more bugs = yay! 5. If you have some *partial* bug fix already in Gerrit, and you are too *lazy *to finish it - a task with the name 'To complete Gerrit change: <change>' also makes sense, and is allowed by GCI rules. 6. In any case, you can always follow https://www.mediawiki.org/wiki/Google_Code-in_2016/Mentors, and forward this to people who you think might be able to help out on things!

Hope this helps.

Thanks, Tony Thomas https://www.mediawiki.org/wiki/User:01tonythomas Home http://www.thomastony.me | Blog https://tttwrites.wordpress.com/ | ThinkFOSS http://www.thinkfoss.com

On Tue, Dec 13, 2016 at 6:49 PM, Andre Klapper aklapper@wikimedia.org wrote:

We are soon going to run out of Google Code-in tasks. Please mentor small and easy tasks! https://www.mediawiki.org/wiki/Google_Code-in_2016 Contact us if you need help or have questions!

Some GCI achievements of the last week (week 2 out of 7):

• Newsletter extension again received numerous patches
• Proposals for a redesign of the Romanian Wikipedia's main page
• MobileFrontend hooks documentation got updated
• One Wikispeech logo proposal (student still needs to upload to Commons)
• A long CREDIT showcase video got split into 'one video per topic' parts on Commons
• Deprecated "Article::getContent()" calls got replaced in several MediaWiki extensions
• Wikidata user docs were analyzed and improvements proposed
• In WikiEduDashboard, .erb html templates were converted to .haml
• The RelatedArticles extension received a design fix for the footer
• Updated screencast videos in the Phabricator help on mw.org
• More screenshots on extension pages (Echo, Poem, TemplateSandbox, …)
• Soon in the pageview API: Monthly request stats per article title!
• …and many many more.

Congratulations to all our students and thanks to all our mentors!

Thanks, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/

---

Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l