public inbox for
 help / color / mirror / Atom feed
From: David Malcolm <>
To: Martin Jambor <>,
	GCC Mailing List <>,
	 Gfortran mailing list <>,
Subject: Re: GCC GSoC 2022: Call for project ideas and mentors
Date: Fri, 07 Jan 2022 12:41:17 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Thu, 2022-01-06 at 17:20 +0100, Martin Jambor wrote:
> 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
> 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
> - 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.

How did it get to be 2022 already?

Thanks for organizing this.

I'd like to (again) mentor a project relating to the GCC static

I've updated the analyzer task ideas on:
but the ideas there are suggestions; if any prospective candidate has
other good ideas for things worth working on within the analyzer, let
me know.

Alternatively, I'm also up for mentoring relating to diagnostics or
libgccjit, if someone can think of an idea of suitable size and scope
for a GSoC project.


> =======================================================================
> ==
> 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
> 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-07 17:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-06 16:20 Martin Jambor
2022-01-07 17:41 ` David Malcolm [this message]
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:

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

  git send-email \ \ \ \ \ \ \

* 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).