From: Eric Gallager <egall@gwmail.gwu.edu>
To: Martin Jambor <mjambor@suse.cz>
Cc: gcc@gcc.gnu.org, Jakub Jelinek <jakub@redhat.com>,
Martin Liska <mliska@suse.cz>,
"Joseph S. Myers" <joseph@codesourcery.com>,
David Edelsohn <dje.gcc@gmail.com>
Subject: Re: Google Summer of Code 2018: Call for mentors and ideas
Date: Thu, 18 Jan 2018 19:51:00 -0000 [thread overview]
Message-ID: <CAMfHzOv6PkzK1gBqSJcAiiYub=jz7dGh=ZhsdjDOeByEGVJw9w@mail.gmail.com> (raw)
In-Reply-To: <ri6efmoxtek.fsf@suse.cz>
On 1/17/18, Martin Jambor <mjambor@suse.cz> wrote:
> Hi,
>
> following a discussion at IRC about an upcoming deadline to register GCC
> as an independent organization for Google Summer of Code 2018 (GSoC), I
> have volunteered to serve as the org-admin for GCC if:
>
> - there is not another volunteer (so step up if you are!),
>
> - the community does not object (so let me and/or the steering
> committee know if you think I am not the right person!), and
>
> - we have at least 4 good project ideas together(!) with willing
> mentors by next Monday January 22 (the deadline is on Tuesday). I
> will be very happy if we have more.
>
> There are project ideas on our GSoC wiki page
> (https://gcc.gnu.org/wiki/SummerOfCode) but those are not associated
> with a willing mentor and it is basically an idea dump, it is often not
> clear how up to date the proposals are and often they are just a bit too
> terse.
>
> Therefore I would like to ask all seasoned GCC contributors who would
> like to mentor a GSoC student to send a reply to this thread with their
> idea for a project. If you have an idea but you do not want to be a
> mentor then I will consider it only if it is really interesting, really
> specific (e.g. improving -O2 -g *somehow* is not specific) and I would
> have to be reasonably confident I'd find a good mentor for it. So far I
> have the following ideas from the IRC discussion:
>
> 1) Jakub is willing to mentor (with someone from GDB but I reckon that
> we will find someone) a project implementing OMPD.
>
> 2) Martin Liška is willing to mentor either:
> 2a) -fsanitize=type (He provided URL https://reviews.llvm.org/D32197
> but it gives me a 404 error) or its prototype, or
> 2b) bash code completion like:
>
> http://blog.llvm.org/2017/09/clang-bash-better-auto-completion-is.html
> but frankly I am afraid it is too small to be a GSoC project, or
> 2c) textual representation of LTO stream a.k.a. lto-dump tool
>
> 3?) Joseph Myers brought up idea to do "built-in functions for TS 18661
> floating-point functions - which has the feature that there are a
> lot of similar built-in functions for C99/C11 functions to serve as
> a guide for how to implement things)" ...Joseph, would you be
> willing to mentor it?
>
> Please send me your idea for a project you'd like to mentor. Also feel
> free to comment on other proposals including those above. I intend to
> put successful project ideas from this thread into a prominent position
> on the wiki page. Remember, I want at least four plausible ones with
> willing mentors until Monday, January 22nd 23:59 CET.
>
> All sorts of information are available from the GSoC web page at
> https://summerofcode.withgoogle.com/, for example guides for mentors are
> at
> https://developers.google.com/open-source/gsoc/resources/guide#mentor_manual
>
> Thanks,
>
> Martin
>
Would it make sense to recycle old GSoC projects that never got
completed? I'm wondering about the "replace libiberty with gnulib" one
next prev parent reply other threads:[~2018-01-18 19:51 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 17:54 Martin Jambor
2018-01-17 21:06 ` Joseph Myers
2018-01-19 13:17 ` Martin Jambor
2018-01-19 16:34 ` Joseph Myers
2018-01-19 17:31 ` Richard Biener
2018-01-17 22:16 ` Joel Sherrill
2018-01-18 9:19 ` Martin Liška
2018-01-19 13:50 ` Martin Jambor
2018-01-18 9:41 ` Martin Liška
2018-01-19 14:09 ` Martin Jambor
2018-01-19 14:13 ` Martin Jambor
2018-01-22 15:10 ` Martin Liška
2018-01-22 15:40 ` Martin Liška
2018-01-18 19:51 ` Eric Gallager [this message]
2018-01-18 20:31 ` Joseph Myers
2018-01-19 14:17 ` Martin Jambor
2018-01-18 23:10 ` Andi Kleen
2018-01-19 14:24 ` Martin Jambor
2018-01-23 10:56 ` Martin Jambor
2018-01-23 11:08 ` Prathamesh Kulkarni
2018-01-23 15:49 ` Martin Liška
2018-01-23 23:11 ` Martin Jambor
2018-02-13 13:02 ` Martin Jambor
2018-02-14 22:10 ` Janus Weil
2018-02-15 9:20 ` Martin Jambor
2018-02-15 10:52 ` Christopher Dimech
2018-02-15 12:12 ` Janus Weil
2018-02-15 13:59 ` Martin Jambor
2018-03-29 15:37 ` Joseph Myers
2018-03-29 16:40 ` Joseph Myers
2018-03-29 17:07 ` Martin Jambor
2018-04-03 11:30 ` Peryt, Sebastian
2018-04-03 14:09 ` 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='CAMfHzOv6PkzK1gBqSJcAiiYub=jz7dGh=ZhsdjDOeByEGVJw9w@mail.gmail.com' \
--to=egall@gwmail.gwu.edu \
--cc=dje.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=mjambor@suse.cz \
--cc=mliska@suse.cz \
/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).