From: Martin Jambor <mjambor@suse.cz>
To: "Peryt\, Sebastian" <sebastian.peryt@intel.com>
Cc: "gcc\@gcc.gnu.org" <gcc@gcc.gnu.org>, "Peryt\,
Sebastian" <sebastian.peryt@intel.com>
Subject: RE: Google Summer of Code 2018: Call for mentors and ideas
Date: Tue, 03 Apr 2018 14:09:00 -0000 [thread overview]
Message-ID: <ri6sh8cmo4d.fsf@suse.cz> (raw)
In-Reply-To: <17623B198193D741876BD81A6E3AE5AD3C61B4CA@irsmsx111.ger.corp.intel.com>
Hi Sebastian,
On Tue, Apr 03 2018, Sebastian Peryt wrote:
> Hi Martin,
>
> Frankly speaking I believe that students who discussed topics on mailing list might
> eventually just decide that they were too challenging for them and also competition
> appeared too difficult. As far as I remember student can only pick few organizations and
> maybe they just decided to pick some other projects where they expected higher chance
> of success. After all, as you wrote, it is students work to come up with good projects.
>
> Nevertheless, I'd suggest keeping discussions regarding GSoC projects, that took place in
> mailing list in wiki (as a summary or direct links) for future reference if someone would
> like to better understand how some elements work in GCC or would like to continue those works.
> Without any external link I'm afraid it might get lost in the mailing list soon.
I have pointers to the most important threads in my notes. I will
put them onto the wiki when I'll reorganize it after this GSoC year or
before the next one starts. Hopefully by that time we will have two
successful projects.
>
> From my personal point of view I think you did a great work with handling all communication
> regarding GSoC participation and I believe you are a perfect candidate for admin role next year.
Thanks a lot,
Martin
prev parent reply other threads:[~2018-04-03 13:11 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
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 [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=ri6sh8cmo4d.fsf@suse.cz \
--to=mjambor@suse.cz \
--cc=gcc@gcc.gnu.org \
--cc=sebastian.peryt@intel.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).