[Talk-us] Any interest in Google Code-In?

Ian Dees ian.dees at gmail.com
Fri Oct 29 14:00:39 BST 2010

On Fri, Oct 29, 2010 at 7:47 AM, Richard Weait <richard at weait.com> wrote:

> On Thu, Oct 28, 2010 at 10:07 PM, Ian Dees <ian.dees at gmail.com> wrote:
> > Hi everyone,
> > At the Google Summer of Code mentors summit this past weekend Google
> asked
> > us (the organizations that participated in Summer of Code) to also
> > participate in the Google Code-In project. The Code-In project is similar
> to
> > the Summer of Code but for 13-18 year olds. The tasks are meant to be
> much
> > smaller: the students are supposed to sign up for one task at a time,
> they
> > get $100 for every 3 tasks they complete (up to $500).
> > I talked a bit with Carol (the Google woman running the project) who
> liked
> > me suggestion for putting up a bunch of mapping-related projects. For
> > example, a project could be "map 100 restaurants in your area" or "map
> all
> > stores in mall X".
> I'm not in favour of this idea.  Mapping for pay will encourage gaming
> the system for money and ripping data from other sources.  It will

I'm also worried about ripping data from other sources, but I don't know
what you mean by "gaming the system". Anyone can make inflammatory edits but
it currently happens very infrequently. Why do you think adding money to the
mix would change that situation?

> also create a group of mappers who will stop when the money runs out
> and potentially resentment among the mappers who have mapped thousands
> of restaurants for the love of mapping or the love of their town.

The goal behind Code-In is to expose younger students to open source. Even
if exposing kids to OpenStreetMap involves rewarding them somehow, they have
at least participated and (hopefully) assisted the community. Perhaps they
will join the league of people who do this for fun after getting rewarded
for the initial investment of learning what OSM is and how to edit properly.

> If there are bite-sized code contributions, let's have a look at that.
>  GSoC already has retention issues in the larger projects.  Not every
> GSoC student continues with their project after the summer period.  I
> see this as a larger problem in a project with a lower initial barrier
> to entry.
I think you'll already have a hard time getting GSoC participants to stay
with any of their projects: they're students with busy lives. GSoC is their
summer job and when its over they have to start classes and do homework.
They leave with cash and some coding experience and the mentoring
organization steps away with some fresh code and some cash as well. I think
expecting students of any caliber to stick with their projects after getting
rewarded is a pretty high bar to reach for.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-us/attachments/20101029/b24e7303/attachment.html>

More information about the Talk-us mailing list