From: Simon Marchi <simon.marchi@polymtl.ca>
To: jose.marchesi@oracle.com
Cc: gdb@sourceware.org
Subject: Re: GSoC
Date: Tue, 07 Feb 2017 22:13:00 -0000 [thread overview]
Message-ID: <08b7dfffb6f5c908e3c8b5d25a8171e7@polymtl.ca> (raw)
In-Reply-To: <87wpd17k6r.fsf@oracle.com>
On 2017-02-07 16:41, jose.marchesi@oracle.com wrote:
> A friend of mine suggested that the GDB project should participate in
> the Google Summer of Code. However, the deadline to register as a
> mentoring organization is this Thursday, in two days! So we need
> to
> act fast if we want to participate. From what I can see, the
> application process is relatively straightforward, but somebody
> needs
> to take care of it (I don't think it has to be the person who will
> be
> the mentor, since this may depend on the actual chosen project). I
> can be that somebody if nobody else wants to.
>
> Note that if for whatever reason you don't make it, or if you want to
> avoid the overhead of organizing, GDB can still participate under the
> GNU umbrella.
>
> We already applied as a mentoring application, and are currently
> collecting project ideas in summer-of-code@gnu.org.
Ok, good to know, thanks. I think it's still a good idea for projects
to apply on their own to increase visibility.
Simon
next prev parent reply other threads:[~2017-02-07 22:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 21:00 GSoC Simon Marchi
2017-02-07 21:40 ` GSoC Phil Muldoon
2017-02-07 22:11 ` GSoC Simon Marchi
2017-02-07 21:41 ` GSoC Jose E. Marchesi
2017-02-07 22:13 ` Simon Marchi [this message]
2017-02-08 17:12 ` GSoC Tom Tromey
2017-02-09 15:48 ` GSoC Simon Marchi
2017-02-09 18:59 ` GSoC Tom Tromey
2017-02-09 21:35 ` GSoC Simon Marchi
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=08b7dfffb6f5c908e3c8b5d25a8171e7@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb@sourceware.org \
--cc=jose.marchesi@oracle.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