From: David Malcolm <dmalcolm@redhat.com>
To: Martin Jambor <mjambor@suse.cz>,
GCC Mailing List <gcc@gcc.gnu.org>,
Gfortran mailing list <fortran@gcc.gnu.org>,
libstdc++@gcc.gnu.org, gcc-rust@gcc.gnu.org
Cc: David Edelsohn <dje.gcc@gmail.com>,
Thomas Schwinge <thomas@codesourcery.com>
Subject: Re: GCC GSoC 2024: Call for project ideas and mentors
Date: Wed, 17 Jan 2024 18:02:11 -0500 [thread overview]
Message-ID: <0c759899d4f098930ea310741f0f594f1b9f36da.camel@redhat.com> (raw)
In-Reply-To: <23282.124011512501100237@us-mta-390.us.mimecast.lan>
On Mon, 2024-01-15 at 18:48 +0100, Martin Jambor wrote:
> Hello,
>
> another year has passed, Google has announced there will be again
> Google
> Summer of Code (GsoC) in 2024 and the deadline for organizations to
> apply is already approaching (February 6th). I'd like to volunteer
> to
> be the main org-admin for GCC again but let me know if you think I
> shouldn't or that someone else should or if you want to do it
> instead.
> Otherwise I'll assume that I will and I hope that I can continue to
> rely
> on David Edelsohn and Thomas Schwinge to back me up and help me with
> some decision making along the way as my co-org-admins.
Hi Martin, thanks for stepping up, and thanks to you, David and Thomas
for your work on this in past years.
>
> ======================== The most important bit:
> ========================
>
> I would like to ask all (moderately) seasoned GCC contributors to
> consider mentoring a contributor 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.
I hope to mentor again this year; I've refreshed the analyzer ideas on
that page.
[...snip...]
Dave
next parent reply other threads:[~2024-01-17 23:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <23282.124011512501100237@us-mta-390.us.mimecast.lan>
2024-01-17 23:02 ` David Malcolm [this message]
[not found] <65a56fff.050a0220.665f7.e82fSMTPIN_ADDED_BROKEN@mx.google.com>
2024-01-19 12:38 ` Arthur Cohen
2024-01-15 17:48 Martin Jambor
2024-02-02 17:33 ` 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=0c759899d4f098930ea310741f0f594f1b9f36da.camel@redhat.com \
--to=dmalcolm@redhat.com \
--cc=dje.gcc@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-rust@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=mjambor@suse.cz \
--cc=thomas@codesourcery.com \
/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).