public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: alicef <alicef@gentoo.org>
To: gentoo-dev-announce@lists.gentoo.org,
	Gentoo Development <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] GSoC 2020: Call for mentors and project ideas
Date: Fri, 17 Jan 2020 01:00:02 +0900	[thread overview]
Message-ID: <6ec6df8d-9006-dcca-1f41-b0f98b7f7f7c@gentoo.org> (raw)


[-- Attachment #1.1.1: Type: text/plain, Size: 2710 bytes --]

Hello,


As always, Gentoo plans to participate in the Google Summer of Code
2020. We are looking for new project ideas and are always open for
new mentors.
Google Summer of Code is a big opportunity for making Gentoo project more
visible and get more people interested to join Gentoo and helping out.

1. Project ideas

GSoC projects should be suitable for 3 months worth of work for
a student, taking into account time required for students to get in
touch with the project, to learn some details, to fix mistakes and
make improvements. Most students are not yet seasoned developers,
so their coding rate will be likely slower than yours.

Usually projects are something more complicated than just writing
some ebuilds, however if non-trivial ebuild related work is
required, e.g. to write new eclasses and adapt existing packages to
use them (or add new ones), this should do too.

Ideas from previous years may be reused, but this should not be
abused, since Gentoo moves forward and we have new stuff to do.

If you have an idea, but can't be a mentor, please still tell us
about it, we'll try to find a mentor later.

Ideas should be put to our wiki: [1].
The page contains ideas adding howto.

2. Mentors

If you want to be a mentor, welcome! It is not necessary to be a
Gentoo developer in order to be a mentor, but project must be
Gentoo related.

Mentoring requires some time. It depends much on a student, but is
usually within 4-10 hours per week. If you don't have that much
time, but still want to help, you may become a backup mentor.
Students often have 2 mentors to eliminate bus factor and to
improve expertise in a project.

Please keep in mind that GSoC is not just about new code, but about
bringing new people to community and we have developers which where
GSoC students in the past. So time invested in students will result
not only in some problems solved, but into bringing new people to
our community and strengthening ties with existing participants.

Mentors should enlist themselves on the wiki: [2].

If you have any questions or proposals, feel free to reply to this
e-mail, or contact us via #gentoo-soc IRC channel on FreeNode[3],
or by writing to project's alias[4].



[1] https://wiki.gentoo.org/wiki/Google_Summer_of_Code/2020/Ideas
[2] https://wiki.gentoo.org/wiki/Google_Summer_of_Code/2020/Mentors
[3] http://webchat.freenode.net/?channels=gentoo-soc
[4] mailto:soc-mentors@gentoo.org


Thanks,
Alice


-- 
======================================
Thanks,
Alice Ferrazzi

Gentoo Kernel Project Leader
PGP: 2E4E 0856 461C 0585 1336 F496 5621 A6B2 8638 781A
====================================== 

[-- Attachment #1.1.2: 0x5621A6B28638781A.asc --]
[-- Type: application/pgp-keys, Size: 19695 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2020-01-16 16:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-16 16:00 alicef [this message]
2020-01-25 12:53 ` [gentoo-dev] GSoC 2020: Call for mentors and project ideas Benda Xu
2020-02-02 11:47   ` Benda Xu
2020-02-02 16:54     ` Gerion Entrup
2020-02-03  4:20       ` [gentoo-dev] Ebuild Generators (Was: GSoC 2020: Call for mentors and project ideas) Benda Xu
2020-02-03  9:42         ` Gerion Entrup
2020-02-03 12:19           ` [gentoo-dev] Ebuild Generators Benda Xu
2020-02-03 12:30             ` Michael 'veremitz' Everitt
2020-02-03 13:20             ` Gerion Entrup
2020-02-03 13:26               ` Michał Górny
2020-02-11 15:18                 ` Tom Gillespie
2020-02-11 23:36                   ` Benda Xu
2020-02-12  7:56                   ` Gerion Entrup

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=6ec6df8d-9006-dcca-1f41-b0f98b7f7f7c@gentoo.org \
    --to=alicef@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