From: Martin Jambor <mjambor@suse.cz>
To: Prathamesh Kulkarni <prathamesh.kulkarni@linaro.org>
Cc: gcc@gcc.gnu.org, David Edelsohn <dje.gcc@gmail.com>
Subject: Re: Google Summer of Code 2018: Call for mentors and ideas
Date: Tue, 23 Jan 2018 23:11:00 -0000 [thread overview]
Message-ID: <ri6inbs187q.fsf@suse.cz> (raw)
In-Reply-To: <CAAgBjMngsTt0E0_W3y5R3Pgw7FS=rSNW-hUvsASQjWKfPuk0XA@mail.gmail.com>
Hi,
On Tue, Jan 23 2018, Prathamesh Kulkarni wrote:
> On 23 January 2018 at 16:26, Martin Jambor <mjambor@suse.cz> wrote:
>> Hi,
>>
>> On Wed, Jan 17 2018, Martin Jambor 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.
>>>
>>
>> I consider the above conditions fulfilled and have started applying.
>>
>> Unfortunately, Google requires there are at least two org-admins for an
>> organization. We need to an additional admin by 6pm CET, which is in a
>> little over 6 hours. So, who would like to do this with me? (We can
>> have up to five :-).
> If it's OK, I can volunteer to be backup admin.
>
I was happy to accept both this offer from Prathamesh and another one
from Honza and put down both as a co-org-admins and submitted our
application. We'll be notified before February 12th whether we were
accepted.
I'll update the wiki with the new ideas tomorrow.
Thanks,
Martin
next prev parent reply other threads:[~2018-01-23 23: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 [this message]
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=ri6inbs187q.fsf@suse.cz \
--to=mjambor@suse.cz \
--cc=dje.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--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).