<div dir="ltr">Thank you Guido, I just replied you privately with the link to the subscription form. After that, you wait for further instructions. Thanks!!</div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 19, 2017 at 3:57 PM, Guido Stein <span dir="ltr"><<a href="mailto:gstein@appgeo.com" target="_blank">gstein@appgeo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I would be interested in participating, is there a list I should join or form I should fill out to help out?<div><br></div><div>-Guido<br><div><br></div><div><br></div></div></div><br><div class="gmail_quote"><div><div class="h5"><div dir="ltr">On Tue, Sep 19, 2017 at 7:48 AM Margherita Di Leo <<a href="mailto:diregola@gmail.com" target="_blank">diregola@gmail.com</a>> wrote:<br></div></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr">Dear Community,<div><br></div><div>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.</div><div><br></div><div>As always, we need your help! We need mentors. </div><div>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. </div><div><br></div><div>In fact, the tasks for google code in are supposed to take 3 to 5 hours for students to complete, and entail:</div><div>* coding</div><div>* documentation / training</div><div>* outreach / research</div><div>* quality assurance</div><div>* user interface</div><div><br></div><div>See examples here [2].</div><div><br></div><div>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. </div><div><br></div><div>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. </div><br>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 <a href="http://osgeo.org" target="_blank">osgeo.org</a>, 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. <div><br></div><div>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!</div><div><br></div><div>Cheers!!<br><div><br></div><div><br></div><div>[1] <a href="https://opensource.googleblog.com/2017/09/announcing-google-code-in-2017.html" target="_blank">https://opensource.<wbr>googleblog.com/2017/09/<wbr>announcing-google-code-in-<wbr>2017.html</a></div><div>[2] <a href="https://developers.google.com/open-source/gci/resources/example-tasks" target="_blank">https://developers.google.<wbr>com/open-source/gci/resources/<wbr>example-tasks</a></div><div>[3] <a href="https://wiki.osgeo.org/wiki/Google_Code_In_2017" target="_blank">https://wiki.osgeo.org/<wbr>wiki/Google_Code_In_2017</a><br clear="all"><div><br></div>-- <br><div class="m_1715864352322851971m_4483609122154969991gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><font color="#666666">Margherita Di Leo</font></div></div></div></div></div></div></div></div></div>
</div></div></div></div></div>
______________________________<wbr>_________________<br>
Discuss mailing list<br>
<a href="mailto:Discuss@lists.osgeo.org" target="_blank">Discuss@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/discuss" rel="noreferrer" target="_blank">https://lists.osgeo.org/<wbr>mailman/listinfo/discuss</a></blockquote></div>
<br>
<span style="color:rgb(128,128,128);font-family:'Courier New';font-size:10px;background-color:rgb(255,255,255)">This e-mail message and any attachments may contain confidential or legally privileged information. If you are not an intended recipient or otherwise authorized to receive this message, you should not use, copy, distribute, disclose or take any action based on the information contained in this e-mail or any attachments. If you have received this message and material in error, please advise the sender immediately by reply e-mail and delete this message. Thank you on behalf of Applied Geographics, Inc. (AppGeo).</span></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><font color="#666666">Margherita Di Leo</font></div></div></div></div></div></div></div></div></div>
</div>