[GRASS-dev] Fwd: [SoC] Google Code In (GCI) 2017 just announced! And we want to participate

[Veronica Andreo]

Ciao Lu,

I signed in and will attend the meeting tonight through IRC chat. I had
some ideas in mind:

- Design the t-shirt for the next code-sprint
- Add examples to xx manual pages
- Make a promo video for GRASS GIS
- Make new tutorial videos for GRASS GIS
- Enhance the visual index
- Make screenshots for release pages (eg.
https://trac.osgeo.org/grass/wiki/Grass7/NewFeatures74)
- Create screenshot for the next 74 release announcement

what do you think? too simple? too complicated?

cheers,
Vero


2017-09-25 18:12 GMT+02:00 Luca Delucchi <lucadeluge at gmail.com>:

> Someone interested?
>
> could be useful for testing (and maybe test case),  docs and translation...
>
>
> ---------- Forwarded message ----------
> From: Margherita Di Leo <diregola at gmail.com>
> Date: 19 September 2017 at 13:48
> Subject: [SoC] Google Code In (GCI) 2017 just announced! And we want
> to participate
> To: OSGeo Discussions <discuss at lists.osgeo.org>,
> geoforall at lists.osgeo.org, OSGeo-SoC <soc at lists.osgeo.org>
> Cc: "gsoc-adminosgeo.org" <gsoc-admin at osgeo.org>, atd.schubert at gmail.com
>
>
> Dear Community,
>
> great news! Google Code-in has just been officially announced [1] and
> we are excited to apply for the first time as mentoring organization!
> Google Code In is a program addressed to students aged 13 to 17.
>
> As always, we need your help! We need mentors.
> Mentors for Google code in are not necessarily top developers (they
> are also needed, but not only). Also educators, advocates, researchers
> are much needed, people that normally take care of documentation and
> preparation of educational material, that give presentations, take
> care of web site or wiki etc.
>
> In fact, the tasks for google code in are supposed to take 3 to 5
> hours for students to complete, and entail:
> * coding
> * documentation / training
> * outreach / research
> * quality assurance
> * user interface
>
> See examples here [2].
>
> The idea is to individuate suitable tasks and submit them in the bug
> tracker with a special keyword like "beginner" or something TBD. In
> this way, students can easily find and claim the task they're
> interested in.
>
> Note that the whole "how to" is to be discussed yet, for the moment,
> let's try to create a critical mass of interested volunteers.
>
> Here [3] I created a wiki page with relevant info, instructions,
> timeline etc. Kindly take a look and if you are willing to
> participate, please write an email to gsoc-admin AT osgeo.org, we will
> send you a form to fill with your data. Next step: in less than one
> week from now we'll have the first kickoff meeting on IRC in the
> channel #osgeo-gsoc at Freenode. Everyone that will have filled the
> form will be informed about exact date and time.
>
> Please, do participate, and bring your questions, your ideas and your
> energy with you. We don't have all the answers, but will try to figure
> things out together.. We believe that engaging the young generation
> will bring in OSGeo a breeze of innovation and fresh energy. Don't
> miss the opportunity to be part of the change!
>
> Cheers!!
>
>
> [1] https://opensource.googleblog.com/2017/09/announcing-google-
> code-in-2017.html
> [2] https://developers.google.com/open-source/gci/resources/example-tasks
> [3] https://wiki.osgeo.org/wiki/Google_Code_In_2017
>
> --
> Margherita Di Leo
>
> _______________________________________________
> SoC mailing list
> SoC at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/soc
>
>
> --
> ciao
> Luca
>
> www.lucadelu.org
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20170925/6a956fa6/attachment.html>