public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Martin Jambor <mjambor@suse.cz>
To: GCC Mailing List <gcc@gcc.gnu.org>,
	Gfortran mailing list <fortran@gcc.gnu.org>,
	libstdc++@gcc.gnu.org
Subject: GCC GSoC 2022: Call for project ideas and mentors
Date: Thu, 06 Jan 2022 17:20:18 +0100	[thread overview]
Message-ID: <ri6czl4x2d9.fsf@suse.cz> (raw)

Hello,

another year is upon us and Google has announced there will be again
Google Summer of Code 2022 (though AFAIK there is no specific timeline
yet).  I'd like to volunteer to be the main Org Admin for GCC again so
let me know if you think I shouldn't or that someone else should, but
otherwise I'll assume that I will.

There will be a few important changes to the GSoC this year.  The most
important for us is that there will be two project sizes: medium-sized
projects which are expected to take about 175 hours to complete and
large projects expected to take approximately 350 hours (the size from
2020 and earlier).  I expect that most of our projects will be large but
I think we can offer one or two medium-sized ideas too.

Google will also increase timing flexibility, so the projects can run
for longer (up to 22 weeks) allowing mentors to go on vacation and
students to pause and focus on exams.  Talking about students, Google is
going to open the program to all adults, so from now on, the
participants working on the projects will be called GSoC contributors.

Slightly more information about these changes can be found at
https://opensource.googleblog.com/2021/11/expanding-google-summer-of-code-in-2022.html
I am sure we will learn more when the actual timeline is announced too.

======================== The most important bit: ========================

Even before that happens, I would like to ask all (moderately) seasoned
GCC contributors to consider mentoring a student this year and ideally
also come up with a project that they would like to lead.  I'm
collecting proposal on our wiki page
https://gcc.gnu.org/wiki/SummerOfCode - feel free to add yours to the
top list there.  Or, if you are unsure, post your offer and project idea
as a reply here to the mailing list.

=========================================================================

Eventually, each listed project idea should have a) a project
title/description, b) more detailed description of the project (2-5
sentences), c) expected outcomes, d) skills required/preferred, e)
project size and difficulty and f) expected mentors.

Project ideas that come without an offer to also mentor them are always
fun to discuss, by all means feel free to reply to this email with yours
and I will attempt to find a mentor, but please be aware that we can
only use the suggestion it if we actually find one.

Everybody in the GCC community is invited to go over
https://gcc.gnu.org/wiki/SummerOfCode and remove any outdated or
otherwise bad project suggestions and help improve viable ones.

Finally, please continue helping (prospective) students figure stuff out
about GCC like you always do.  So far I think all of them enjoyed
working with us, even if many sometimes struggled with GCC's complexity.

I will update you as more details about GSoC 2022 become available.

Thank you, let's hope we attract some new talent again this year.

Martin


             reply	other threads:[~2022-01-06 16:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-06 16:20 Martin Jambor [this message]
2022-01-07 17:41 ` David Malcolm
2022-01-12  9:53 ` Martin Jambor
2022-01-12 10:01   ` Martin Jambor
2022-03-09 14:39 ` Martin Jambor
2022-03-10  2:09   ` Jerry D
2022-03-10 16:13     ` Damian Rouson
2022-03-10 16:22       ` Martin Jambor

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=ri6czl4x2d9.fsf@suse.cz \
    --to=mjambor@suse.cz \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=libstdc++@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).