From: Martin Jambor <mjambor@suse.cz>
To: GCC Mailing List <gcc@gcc.gnu.org>
Cc: fortran@gcc.gnu.org,
Prathamesh Kulkarni <prathamesh.kulkarni@linaro.org>,
Jan Hubicka <hubicka@ucw.cz>
Subject: GCC and GSoC 2019
Date: Mon, 28 Jan 2019 22:32:00 -0000 [thread overview]
Message-ID: <ri6sgxcs9ap.fsf@suse.cz> (raw)
Hi,
today I have filed an application on behalf of the GCC project to be a
mentoring organization in the year 2019 of Google Summer of Code. I'd
like to have the following requests and announcements:
1. First and foremost, 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, of course.
2. I would like to thank a lot to those who have already confirmed that
they are willing to mentor a GSoC project.
3. 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, but please be aware that we can only make use the
suggestion it if we find a mentor. I might mention them on the wiki,
but only less prominently.
4. All knowledgeable GCC folk are invited to go over
https://gcc.gnu.org/wiki/SummerOfCode and simply remove any outdated
or otherwise really bad project suggestions. I would especially want
to ask GFortran and to a lesser extent C++ people to do so.
5. Please continue helping (prospective) students figure stuff out about
GCC like you always do.
6. I intend to be the main "org admin" for GCC organization, I have
asked Prathamesh Kulkarni and Honza Hubička to be my co-admins,
because we must have at least two. If anybody else would like to join
us, let me know.
More information together with GSoC 2019 time line is available at
https://summerofcode.withgoogle.com
Thank you, let's hope we attract some good young talent this year.
Martin
reply other threads:[~2019-01-28 22:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ri6sgxcs9ap.fsf@suse.cz \
--to=mjambor@suse.cz \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=prathamesh.kulkarni@linaro.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).