I have added basic information to the profile, so technically we are
"green". All main fields are entered.
Application draft:
https://docs.google.com/document/d/1l-sElXZ2Wmd5DkCH_y4YXQbqGQ20KfhvqZMNY65iTgI/edit?usp=sharing
But there are some missing ones which are really important:

   - Common Task information for students. IMO it should be a page on
   jenkins.io. Left empty for now
   - Short instructions or tips to be displayed with every task. May
   include limited Markdown
   <https://developers.google.com/open-source/gci/help/markdown>. Example:
   See http://link for information on how to checkout, build, and run the
   code. Don't forget to join the IRC channel to ask mentors questions.
   - OR: A URL for a web page that will be linked to from every task in the
      "Working with Jenkins project" section

IMHO we need a jenkins.io landing page for Google Code-In similarly to what
has been created for GSoC.

Anyway, in the current state Google Code-In is a high-risk project. We need
more contributors to make it efficient (task editors, code reviewers) to
make it efficient. Any contributions to the issue list will be appreciated,
this is the most critical part right now

Best regards,
Oleg


On Fri, Sep 14, 2018 at 2:22 PM Supun Wanniarachchi <[email protected]>
wrote:

> Hi all,
>
> As we discussed during the last meeting[1] I have been started to create
> Draft Tasks[2]. We need to create at least 25 tasks before the Organization
> Application Deadline: September 17. Please add your tasks in "Google
> Code-In 2018 Draft Tasks"[2] document before the application deadline.
>
> [1]
> https://docs.google.com/document/d/11jPv9UU4vBWvNrN4NdZGAechABY8IiIgqQ06bLb-MlE/edit?usp=sharing
>
> [2]
> https://docs.google.com/document/d/19iVscMUNsh0Fv5plEMky4UTJsrGlLZDH764Fi8nKBrg/edit?usp=sharing
>
>
> Best regards,
> Supun.
>
> On Wed, Sep 5, 2018 at 9:51 PM Kristin Whetstone <[email protected]>
> wrote:
>
>> From my perspective, I'd love to get help with some of the documentation
>> tasks.  I'd like to participate, and would be willing to help out wherever
>> needed.
>>
>> Thanks!
>> Kristin
>>
>> On Sun, Sep 2, 2018 at 6:59 AM, Aldrin Leal <[email protected]> wrote:
>>
>>> I'd love to - I've got a couple of small tasks in my plugins, and I've
>>> happy to help mentor a Student into doing it. Not only for fun, but also to
>>> give back. What should be our next steps?
>>>
>>> --
>>> -- Aldrin Leal, <[email protected]> / https://ingenieux.io/about/
>>>
>>> On Sun, Sep 2, 2018 at 5:47 AM, Oleg Nenashev <[email protected]>
>>> wrote:
>>>
>>>> Hi Supun,
>>>>
>>>> // Added Jenkins Developers group to CC
>>>>
>>>> FYI, Google Code-in (GCI) is a contest to introduce pre-university
>>>>> students (ages 13-17) to open source software development. IMHO
>>>>> participating GCI is a great advantage to the community and hope its bit
>>>>> different experience for all of us. Last year GCI was very successful and
>>>>> 25 opensource mentoring organizations participated [1]. I think this year
>>>>> we also can apply as a mentoring organization. Your suggestions would be
>>>>> greatly appreciated.
>>>>>
>>>>> [1]
>>>>> https://opensource.googleblog.com/2018/01/google-code-in-2017-winners.html
>>>>>
>>>>
>>>> I think it may be interesting to the Jenkins community. Our main
>>>> challenge would be to create enough small tasks
>>>> <https://developers.google.com/open-source/gci/resources/example-tasks>
>>>> which should be doable by a newbie contributor. It should be possible for
>>>> "Design" and "Documentation" sections, QA and research are also possible.
>>>> Regarding Coding, it will require processing of newbie-friendly
>>>> <https://issues.jenkins-ci.org/issues/?jql=project%20%3D%20JENKINS%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20labels%20%3D%20newbie-friendly>
>>>> tasks and describing them properly. It is certainly doable, but we need a
>>>> number of contributors, especially in the following timeframes:
>>>>
>>>>    - Sep 06 - Sep 17 - Applications
>>>>    - Oct 23 - Dec 27 - Contest
>>>>
>>>> In my case, I am not available to drive the applications period, my
>>>> schedule is fully packed due to the DevOps World | Jenkins World prep work.
>>>> November-December will be also quite busy for me, I prefer to not commit on
>>>> being an active mentor during this period. If somebody is interested to be
>>>> an organization admin (e.g. Supun), I will be happy to provide as much
>>>> assistance as I can.
>>>>
>>>> Would anybody from Jenkins Developers be interested in participating?
>>>> Generally it requires creating/describing small tasks in the area of your
>>>> interest (plugins you maintain, etc.)
>>>>
>>>> Best regards,
>>>> Oleg
>>>>
>>>>
>>>>
>>>> On Thu, Aug 30, 2018 at 7:59 AM Supun Wanniarachchi <
>>>> [email protected]> wrote:
>>>>
>>>>> Hi All,
>>>>>
>>>>> FYI, Google Code-in (GCI) is a contest to introduce pre-university
>>>>> students (ages 13-17) to open source software development. IMHO
>>>>> participating GCI is a great advantage to the community and hope its bit
>>>>> different experience for all of us. Last year GCI was very successful and
>>>>> 25 opensource mentoring organizations participated [1]. I think this year
>>>>> we also can apply as a mentoring organization. Your suggestions would be
>>>>> greatly appreciated.
>>>>>
>>>>> [1]
>>>>> https://opensource.googleblog.com/2018/01/google-code-in-2017-winners.html
>>>>>
>>>>> Best Regards,
>>>>> Supun.
>>>>>
>>>>> ---------- Forwarded message ---------
>>>>> From: Google Code-in Mentors <[email protected]>
>>>>> Date: Thu, Aug 30, 2018 at 1:04 AM
>>>>> Subject: [GCI-mentors] GCI 2018 org applications open September 6-17 -
>>>>> contest begins October 23rd for students
>>>>> To: Google Code-in Mentors <[email protected]>
>>>>>
>>>>>
>>>>> Hello GCI mentors,
>>>>>
>>>>> We are pleased to announce Google Code-in (GCI) 2018 <http://g.co/gci>,
>>>>> the 9th consecutive year of our contest for pre-university students ages
>>>>> 13-17. Please be aware GCI will start about a month earlier this year
>>>>> than in previous years - the contest starts for students October 23rd!
>>>>>
>>>>> The GCI timeline, FAQs, Rules and flyers have been updated on the contest
>>>>> site <http://g.co/gci>.
>>>>>
>>>>> Organizations -- If you would like to apply for the 2018 program
>>>>> please start thinking about the tasks you would like students to work on
>>>>> and reach out to your community members to ask if they would like to be
>>>>> mentors for the program. *Organization applications open for GCI orgs
>>>>> *next week on Thursday, September 6th, and close less than 2 weeks
>>>>> later on Monday, September 17th. We will announce organizations on 
>>>>> Tuesday,
>>>>> September 18th giving orgs 5 weeks to create their tasks before the 
>>>>> contest
>>>>> begins on October 23rd.
>>>>>
>>>>> The major changes for GCI 2018 are:
>>>>>
>>>>>    -
>>>>>
>>>>>    Orgs will evaluate the 20 students completing the most tasks with
>>>>>    their org when deciding on finalists and winners
>>>>>    -
>>>>>
>>>>>    Orgs will choose 6 finalists (instead of 5)
>>>>>    -
>>>>>
>>>>>    We have renamed the User Interface category to Design
>>>>>    -
>>>>>
>>>>>    Students will have to wait until Google reviews their Parental
>>>>>    Consent form before they can claim their first task. This will slow 
>>>>> things
>>>>>    down but it is a requirement to be able to continue the program.
>>>>>    -
>>>>>
>>>>>    No tasks asking for personal information about students will be
>>>>>    allowed (this includes tasks asking for students to introduce 
>>>>> themselves
>>>>>    with info like what country they are from, or photos of the students, 
>>>>> etc.).
>>>>>
>>>>> We are looking to continue the growth of this program and reach a
>>>>> record number of teenagers this year! Read more on today’s blog post
>>>>> <https://opensource.googleblog.com/2018/08/announcing-google-code-in-2018.html>
>>>>> .
>>>>>
>>>>> If you have any questions about Google Code-in please contact us at
>>>>> [email protected]
>>>>>
>>>>> Best,
>>>>>
>>>>> Stephanie and Mary
>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "Google Code-in Mentors" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to [email protected].
>>>>> To post to this group, send email to [email protected].
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/gci-mentors/a0aa5a28-3853-4f4f-a547-7cb816932147%40googlegroups.com
>>>>> <https://groups.google.com/d/msgid/gci-mentors/a0aa5a28-3853-4f4f-a547-7cb816932147%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>>
>>>>> --
>>>>> Thank You & Best Regards,
>>>>>
>>>>> Supun Wanniarachchi | Software Engineer
>>>>>
>>>>> Sysco LABS | 55A Dharmapala Mw, Col. 03
>>>>> ( *Mobile*: +94716326119 | Blog: blog.supun.me)
>>>>>
>>>>>
>>>>> [image: Github] <https://github.com/Supun94> [image: LinkedIn]
>>>>> <https://www.linkedin.com/in/supun-wanniarachchi-21b37a97/> [image:
>>>>> Twitter] <https://twitter.com/SuuPuuN>
>>>>>
>>>>>
>>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Jenkins Developers" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to [email protected].
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLDyMFMq-8s2qvt1ZOydiB%2BnCiOuAJPRftGb2zgjuogehQ%40mail.gmail.com
>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLDyMFMq-8s2qvt1ZOydiB%2BnCiOuAJPRftGb2zgjuogehQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>>> .
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins GSoC Mentors" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>> To post to this group, send email to
>>> [email protected].
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-gsoc-mentors/CALpo8NuKRZ%3D-qjs91%3DU9vu%3Dii%2BByFwJ6KoVuKu8qROQPd0ADgg%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/jenkinsci-gsoc-mentors/CALpo8NuKRZ%3D-qjs91%3DU9vu%3Dii%2BByFwJ6KoVuKu8qROQPd0ADgg%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Kristin Whetstone
>> Software Engineer
>>
>> CloudBees, Inc.
>>
>> [image: CloudBees-Logo.png]
>>
>> E: [email protected]
>>
>
>
> --
> Thank You & Best Regards,
>
> Supun Wanniarachchi | Software Engineer
>
> Sysco LABS | 55A Dharmapala Mw, Col. 03
> ( *Mobile*: +94716326119 | Blog: blog.supun.me)
>
>
> [image: Github] <https://github.com/Supun94> [image: LinkedIn]
> <https://www.linkedin.com/in/supun-wanniarachchi-21b37a97/> [image:
> Twitter] <https://twitter.com/SuuPuuN>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCxVESihd%3Dq--GCKFyGDawORL_D5zZJbKcb5GJ_B9M4XQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to