This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [IMPORTANT] slots assigned

Hi Richard,

Richard Biener <> writes:

> On Thu, 14 Apr 2016, Giuseppe Scrivano wrote:
>> Hi everyone,
>> We got 18 slots from Google.
>> It is less than we expected so not everyone is going to be satisfied by
>> the split below.
>> We have time until next week (deadline April 20, 2016 at 20:59 CEST)
>> to assign mentors to each project, but to give us time to review things,
>> please do this as soon as possible.  Please directly notify me off-list
>> when you have assigned the mentors so I can check that in the web
>> interface (I have not found a way in the new interface to look up this
>> information without going through all the proposals).
>> For each proposal, please be sure there is only one mentor assigned to
>> it and that each project has total proposals with a mentor == Assigned
>> slots.
>> I have assigned these slots based on the number of mentors available for
>> each project, but if you feel like giving away any slot to another
>> project, please do it.
> ...
>> Name: GCC
>> Assigned: 2
> So it looks like we need to scrap one of the three GCC proposals
> (currently all have Mentors "assigned" - well, not sure if
> "want to mentor" counts as assigned).
> There's the GIMPLE FE, Addressing mode selection and replacing
> libiberty with gnulib.
> To me the last one is least interesting (no observable effect to
> users or developers).

please let's discuss these things privately.  I doubt someone is going
to give a slot back as we got 4 less than what we requested, but if it
happens, GCC can take it.  Please notify me once two proposals get a
mentor assigned and I'll mark them accepted.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]