Hi, Google Code-in is about to start:
http://www.google-melange.com/gci/homepage/google/gci2013 https://www.mediawiki.org/wiki/Google_Code-In
We have currently 72 tasks published and 13 mentors. We are still looking for more mentors and tasks. If you are interested, contact me.
This is the first time Wikimedia participates in this program and the only certain prediction at this point is that we all will learn a lot.
We have been warned that especially the first two weeks will be quite messy, with many impatient newcomers landing in our community channels and asking for help / feedback / review. Please be kind with them. Things will eventually settle down, partially because our documentation will be better, partially because the students interested in Wikimedia will be familiar with the basics and will know where/how to ask.
Ideally https://www.mediawiki.org/wiki/Google_Code-In should contain answers and links to answers for the frequently asked questions. Try to answer GCI students with links to the appropriate pages, and try to assure that such links are available at our GCI wiki page.
Thank you for your patience. I have no doubt that your direct or indirect help will pay off with better documentation for all kinds of newcomers interested in many areas of contribution.
/me goes to prepare a hot beverage. It is going to be fun.
On 11/18/2013 08:52 AM, Quim Gil wrote:
Hi, Google Code-in is about to start:
http://www.google-melange.com/gci/homepage/google/gci2013 https://www.mediawiki.org/wiki/Google_Code-In
You can see all our open tasks at
http://www.google-melange.com/gci/org/google/gci2013/wikimedia
GCI is moving fast. We need more mentors and tasks, especially for software development! See below.
On 11/18/2013 09:04 AM, Quim Gil wrote:
http://www.google-melange.com/gci/homepage/google/gci2013 https://www.mediawiki.org/wiki/Google_Code-In
You can see all our open tasks at
http://www.google-melange.com/gci/org/google/gci2013/wikimedia
Here goes a first report. I will send more of these but not as verbose. After one day we have
77 tasks in total, from which
* 2 have been closed as FIXED:
PROVIDE CSS CLASS (HLIST) TO DEFINE HORIZONTAL LISTS IN MEDIAWIKI CORE http://www.google-melange.com/gci/task/view/google/gci2013/5772232571748352
TRIAGE (RETEST) ANY 10 OF MEDIAWIKI VECTOR SKIN (DEFAULT) BUG REPORTS http://www.google-melange.com/gci/task/view/google/gci2013/5884303300886528
* 3 have been marked NeedsReview by the students:
MAKE SIMPLESEARCH PARAMETERS TO APIOPENSEARCH CONFIGURABLE http://www.google-melange.com/gci/task/view/google/gci2013/5903692930744320 See https://gerrit.wikimedia.org/r/#/c/96162/
FIX LOW RESOLUTION RSS/ATOM FEED ICON FOR SIDEBAR http://www.google-melange.com/gci/task/view/google/gci2013/5795046364282880 See https://gerrit.wikimedia.org/r/#/c/96197/
ADD A "GO BACK TO TOP" BOTTON TO KIWIX http://www.google-melange.com/gci/task/view/google/gci2013/5839120244932608
* 2 marked for review have been pushed back by the mentors:
FILE PAGES SHOULD USE HIDPI 'SRCSET' ATTRIBUTE FOR THE MAIN IMAGE http://www.google-melange.com/gci/task/view/google/gci2013/6705304553127936
SUPPRESS NATIVE "INVALID E-MAIL" WARNING ON SPECIAL:CHANGEEMAIL http://www.google-melange.com/gci/task/view/google/gci2013/5315763447529472
We are missing more mentors and tasks, especially in the category of DEVELOPMENT. The program is called "Code-in", right? It's not too late. Come on, step in!
https://www.mediawiki.org/wiki/Google_Code-In#Become_a_Wikimedia_GCI_mentor
These students will help you getting actual work done. If you are busy enough to create tasks in Google Melange just point Andre Klapper and me to the related bug reports and we will do that piece of work for you.
Google Code-in weekly update. Summary:
WE NEED MORE TASKS, URGENTLY!
http://www.google-melange.com/gci/dashboard/google/gci2013#all_org_tasks
We are expecting new tasks coming from Mobile, Wikidata, Language and Lua templates. Still, GCI students are crunching tasks faster than we are able to create new ones. Please join the party with your tasks!
https://www.mediawiki.org/wiki/Google_Code-In
On 11/19/2013 10:23 AM, Quim Gil wrote:
GCI is moving fast. We need more mentors and tasks, especially for software development!
This is still very true a week after starting Google Code-in. These are the numbers so far:
* 32 tasks have been completed (28% from the current total of 90)
MediaWiki core, PyWikiBot, Kiwix, and mediawiki.org have been the main beneficiaires so far. We have seen students following the process in Gerrit and Bugzilla as described, some picking things up quickly, some needing an initial push.
* 24 are currently claimed, meaning that 24 students are currently working on them.
* 3 need review, 6 need more work, 2 are possibly abandoned, 9 were left by students that had claimed them.
* Only 13 tasks haven't been touched at all in this first week.
As you can see, this is working.
First lesson: the best GCI tasks are those expecting an exact result e.g. a SVG with PNG fallback to substitute a low-resolution icon. Tasks giving more margin to creativity (write an article or a wiki page about certain topic) have a higher risk of requiring a lot more mentorship and obtaining mixed results.
Second lesson: org admins can cover mentors when the tasks are well defined and must be resolved via Gerrit & Bugzilla. The help received from non-mentor community members commenting in Gerrit changes and gug reports is priceless! Thank You Very Much for your help.
Interesting data of the first week of GCI, shared by the organizers:
1929 students registered (this is already higher than what we had at
the halfway point last year)
84 countries represented 342 tasks completed by 162 students
Since completed 32 and there are 10 organizations, we are just lightly below average. I would say this is pretty good considering that it is our first time.
And no, it's not late for you to join as mentor and bring your tasks. :)
On 11/25/2013 10:51 AM, Quim Gil wrote:
Google Code-in weekly update. Summary:
WE NEED MORE TASKS, URGENTLY!
http://www.google-melange.com/gci/dashboard/google/gci2013#all_org_tasks
We are expecting new tasks coming from Mobile, Wikidata, Language and Lua templates. Still, GCI students are crunching tasks faster than we are able to create new ones. Please join the party with your tasks!
https://www.mediawiki.org/wiki/Google_Code-In
On 11/19/2013 10:23 AM, Quim Gil wrote:
GCI is moving fast. We need more mentors and tasks, especially for software development!
This is still very true a week after starting Google Code-in. These are the numbers so far:
- 32 tasks have been completed (28% from the current total of 90)
MediaWiki core, PyWikiBot, Kiwix, and mediawiki.org have been the main beneficiaires so far. We have seen students following the process in Gerrit and Bugzilla as described, some picking things up quickly, some needing an initial push.
- 24 are currently claimed, meaning that 24 students are currently
working on them.
- 3 need review, 6 need more work, 2 are possibly abandoned, 9 were left
by students that had claimed them.
- Only 13 tasks haven't been touched at all in this first week.
As you can see, this is working.
First lesson: the best GCI tasks are those expecting an exact result e.g. a SVG with PNG fallback to substitute a low-resolution icon. Tasks giving more margin to creativity (write an article or a wiki page about certain topic) have a higher risk of requiring a lot more mentorship and obtaining mixed results.
Second lesson: org admins can cover mentors when the tasks are well defined and must be resolved via Gerrit & Bugzilla. The help received from non-mentor community members commenting in Gerrit changes and gug reports is priceless! Thank You Very Much for your help.
Hi, we are still leaving the caps here:
On 11/25/2013 10:51 AM, Quim Gil wrote:
Google Code-in weekly update. Summary:
WE NEED MORE TASKS, URGENTLY!
http://www.google-melange.com/gci/dashboard/google/gci2013#all_org_tasks
We have 72 tasks completed, 24 currently in progress, and 28 open!
The good news is that current mentors kept adding tasks, we got new mentors, and we even got some "external" volunteers (not mentors) committing to propose and review tasks within their areas.
The result: we recovered from last week's free fall, but we are still needing more tasks in order to keep up with GCI students.
New mentors are still welcome!
Look what I mean, in colors:
https://commons.wikimedia.org/wiki/File:Wikimedia_at_Google_Code-in_2013.png
MatmaRex has more stats showing activity per students and mentors:
https://www.mediawiki.org/wiki/Google_Code-in/Statistics
We are expecting new tasks coming from Mobile, Wikidata, Language and Lua templates.
This was mostly true, except for Lua templates. I was hoping to get mentorship help at https://en.wikipedia.org/wiki/Wikipedia:Lua_requests#Looking_for_Lua_mentors... . I will create the tasks myself, hoping to get help reviewing the tasks. If you want to mentor Lua templates tasks, please step in.
We got also new tasks for MultimediaViewer and UploadWizard. Thank you!
An area that has grown fast is QA, through browser automation tasks.
Still, GCI students are crunching tasks faster than we are able to create new ones. Please join the party with your tasks!
Google Code-in: 3 weeks past, 4 weeks to go.
https://www.mediawiki.org/wiki/Google_Code-In
We have 113 tasks completed, 22 currently in progress, and 30 open. The graph looks very good so far: https://www.mediawiki.org/wiki/File:Wikimedia_at_Google_Code-in_2013.png
What the graph doesn't reflect is the fact that these numbers currently rely on just a few mentors and external contributors, which is not very sustainable.
This is how you can help:
* Anybody can identify new GCI tasks. CC Andre and me in bug reports, or contact us directly for any other type of task.
* If you are a mentor without open tasks, please create new tasks.
The math is simple: we won't have any problem if every mentor creates one new task when one of your tasks is completed. You can decide the amount of work you want to handle by having more or less open tasks at the same time. Having one task open at a time doesn't require much dedication, please do it.
Thank you everybody for your help!
Google Code-in: 4 weeks past, 3 weeks to go.
https://www.mediawiki.org/wiki/Google_Code-In
We have 133 tasks completed, 20 in progress, and 37 open. These numbers are more relaxed than in previous weeks:
https://www.mediawiki.org/wiki/File:Wikimedia_at_Google_Code-in_2013.png
This is due to two factors:
* students are busier than usual at school, finishing evaluations and assignments before holidays * some mentors are being very effective relying on types of tasks that are easy to clone, like porting functionality from PyWikiBot compat to core, fixing internationalization problems in MediaWiki, internationalizing MediaWiki documentation, providing SVG versions of Wikimedia logos, or adding template data for VisualEditor.
The activity is expected to increase again this weekend, and keep being high until the end of the program on January 6. Also most mentors will have some days of vacation, which might affect our capacity to mentor students and review tasks.
This week I will ping directly all the mentors that haven't got involved at this stage, asking them to take care of at least one task at a time. This isn't much work for one person, and is the ultimate trick to keep the program going in the last 3 weeks.
Thank you again for your attention and your help.
Google Code-in: 5 weeks past, only 2 weeks to go.
https://www.mediawiki.org/wiki/Google_Code-In
We have 170 tasks completed, 17 in progress, and 26 open.
We are struggling again creating new tasks! We are relying in some categories of tasks that can be cloned, but we are missing easy coding tasks again.
https://www.mediawiki.org/wiki/File:Wikimedia_at_Google_Code-in_2013.png
Proposing GCI tasks is very simple at this point: just CC Andre Klapper and me in a related bug report, or contact us via email. We will take care fo the rest.
Only 2 weeks to go! Please help us in the final sprint.
I tagged you in a few bugs Quim!
On Mon, Dec 23, 2013 at 10:25 AM, Quim Gil qgil@wikimedia.org wrote:
Google Code-in: 5 weeks past, only 2 weeks to go.
https://www.mediawiki.org/wiki/Google_Code-In
We have 170 tasks completed, 17 in progress, and 26 open.
We are struggling again creating new tasks! We are relying in some categories of tasks that can be cloned, but we are missing easy coding tasks again.
https://www.mediawiki.org/wiki/File:Wikimedia_at_Google_Code-in_2013.png
Proposing GCI tasks is very simple at this point: just CC Andre Klapper and me in a related bug report, or contact us via email. We will take care fo the rest.
Only 2 weeks to go! Please help us in the final sprint.
-- Quim Gil Technical Contributor Coordinator @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Yesterday I couldn't send the weekly report. Here it goes, although the data is from Monday to keep weekly consistency.
Summary: look at this! https://www.mediawiki.org/wiki/File:Wikimedia_at_Google_Code-in_2013.png
Google Code-in: 6 weeks past, LESS THAN A WEEK TO GO!
https://www.mediawiki.org/wiki/Google_Code-In
We have 219 tasks completed, 17 in progress, and 42 open.
Org admins Andre and me can't express how thankful are we for the great team collaboration and mentorship performance achieved thanks to the contributions of many official and unofficial mentors, in the GCI site, Gerrit, and Bugzilla. In a couple of months we have learned meny good lessons that we will be able to apply not only in the next GCI edition, but also (and mainly) in our processes to welcome new contributors with appropriate tasks.
We are also getting good feedback from the GCI students that have "survived" with us until this stage. As an indication, currently we have about half of the students that we had after the first week of GCI, yet they are completing just as many tasks. In fact we had some problems related with excess of productivity (e.g. two students going after the same task) but things seems to be relaxing a bit now. We can't blame these students, GCI rules implicitly promote this hypercompetitiveness, students are young and full of energy. :)
For the first time I can say that we don't need new mentors, and we don't actually need new tasks (although additions of coding tasks are still welcome, and they are still being taken by some brilliant young developers). Thank you to everybody helping. Let's finish the last sprint!
On 2013-11-18 12:52 PM, "Quim Gil" qgil@wikimedia.org wrote:
Hi, Google Code-in is about to start:
http://www.google-melange.com/gci/homepage/google/gci2013 https://www.mediawiki.org/wiki/Google_Code-In
We have currently 72 tasks published and 13 mentors. We are still looking for more mentors and tasks. If you are interested, contact me.
This is the first time Wikimedia participates in this program and the only certain prediction at this point is that we all will learn a lot.
We have been warned that especially the first two weeks will be quite messy, with many impatient newcomers landing in our community channels and asking for help / feedback / review. Please be kind with them. Things will eventually settle down, partially because our documentation will be better, partially because the students interested in Wikimedia will be familiar with the basics and will know where/how to ask.
Ideally https://www.mediawiki.org/wiki/Google_Code-In should contain answers and links to answers for the frequently asked questions. Try to answer GCI students with links to the appropriate pages, and try to assure that such links are available at our GCI wiki page.
Thank you for your patience. I have no doubt that your direct or indirect help will pay off with better documentation for all kinds of newcomers interested in many areas of contribution.
/me goes to prepare a hot beverage. It is going to be fun.
-- Quim Gil Technical Contributor Coordinator @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
So just to clarify, for those of us who are non-mentors, we can treat the gci students just like normal people (by which I mean, if they ask for help, help them. If they submit code review it, etc. I wouldn't have to record or do anything special if I am reviewing code and I just happen to review a patch submitted by a gci student?)
-bawolff
On 11/18/2013 09:36 AM, Brian Wolff wrote:
So just to clarify, for those of us who are non-mentors, we can treat the gci students just like normal people (by which I mean, if they ask for help, help them. If they submit code review it, etc. I wouldn't have to record or do anything special if I am reviewing code and I just happen to review a patch submitted by a gci student?)
Exactly. The point of this program is to show GCI how open source projects work. Just treat them like regular new contributors. The mentors of their task and the GCI org admins will do the rest.
Thank you!
wikitech-l@lists.wikimedia.org