public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Denis Dupeyron <calchan@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Cc: gentoo-dev-announce@lists.gentoo.org
Subject: [gentoo-dev] It is GSoC season again
Date: Tue, 9 Feb 2016 23:11:07 -0700	[thread overview]
Message-ID: <CA+CSuAKLsKHec6tJa9ApT4swS=a0NZ7C_khK5A2x71K4j4aJHQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1789 bytes --]

Google Summer of Code 2016 is starting.

If you are a student please be patient. Your time will come soon, at which
point we'll be able to answer all your questions. In this initial phase the
audience is project mentors. Note that you do not need to be a Gentoo
developer to be a mentor.

While we are finalizing the application, we need all of you to submit your
project ideas before the end of next week (February 19th). To do so you
should go to [1] and follow the instructions in the "Ideas" section. If you
proposed an idea last year and would like to propose it again for this
year, you can look it up at [2] and add it to [1]. Or you can just tell us
and we will do it for you. Don't hesitate to add an idea even it isn't
totally fleshed out; we will help you fill in the blanks. A project
represents 3 months of full-time work for a student. A good rule of thumb
is that it should take you between 2 and 4 weeks to complete depending on
how expert you are in the field. You can also have a look at [2] for
examples.

If you would like to be a mentor for this year please tell us sooner rather
than later. You can be a mentor following up with students while they're
working on their project, or you can be an expert-mentor in a specific
field who will be called in to advise on an as-needed basis (or maybe
never). We will also need people to help us review project proposals. In
case you can help in any capacity don't hesitate to contact us. GSoC is
seriously fun!

If you want to reach us or have any questions about any of the above, the
easiest way is to ping Calchan or rafaelmartins in the #gentoo-soc channel
on Freenode.

Thanks,
Calchan.

[1] https://wiki.gentoo.org/wiki/Google_Summer_of_Code/2016/Ideas
[2] https://wiki.gentoo.org/wiki/Google_Summer_of_Code/2015/Ideas

[-- Attachment #2: Type: text/html, Size: 2168 bytes --]

             reply	other threads:[~2016-02-10  6:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-10  6:11 Denis Dupeyron [this message]
2016-02-11  0:43 ` <DKIM> [gentoo-dev] It is GSoC season again Nicolas Sebrecht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CA+CSuAKLsKHec6tJa9ApT4swS=a0NZ7C_khK5A2x71K4j4aJHQ@mail.gmail.com' \
    --to=calchan@gentoo.org \
    --cc=gentoo-dev-announce@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox