From: Martin Jambor <mjambor@suse.cz>
To: Arthur Cohen <arthur.cohen@embecosm.com>
Cc: David Edelsohn <dje.gcc@gmail.com>,
Thomas Schwinge <thomas@codesourcery.com>,
gcc-rust@gcc.gnu.org
Subject: Re: GCC GSoC 2024: Call for project ideas and mentors (rust)
Date: Tue, 23 Jan 2024 21:59:00 +0100 [thread overview]
Message-ID: <ri634un3gx7.fsf@> (raw)
In-Reply-To: <598a9cc0-6fea-45fd-b24a-db9b47f3169c@embecosm.com>
Hi Arthur,
On Fri, Jan 19 2024, Arthur Cohen wrote:
> Hi Martin,
>
> On 1/15/24 18:48, 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.
>
> I think that'd be good :) we've really appreciated all the work you've
> done for the past editions.
>
> We'll be discussing project ideas with the rest of the gccrs team and
> will update the page shortly. We'd love to mentor again this year.
Thanks a lot. The organization registration ends February 6th, I guess
that is when the GSoC folks are going to start looking at applications
and idea lists. So please consider that your deadline though of course
the earlier the better :-)
Thanks again,
Martin
prev parent reply other threads:[~2024-01-23 20:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <65a56fff.050a0220.665f7.e82fSMTPIN_ADDED_BROKEN@mx.google.com>
2024-01-19 12:38 ` GCC GSoC 2024: Call for project ideas and mentors Arthur Cohen
2024-01-23 20:59 ` Martin Jambor [this message]
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=ri634un3gx7.fsf@ \
--to=mjambor@suse.cz \
--cc=arthur.cohen@embecosm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-rust@gcc.gnu.org \
--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).