linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: Theodore Ts'o <tytso@mit.edu>,
	Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
	"Luis R. Rodriguez" <mcgrof@gmail.com>,
	linux-kernel@vger.kernel.org,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Witold Sowa <witold.sowa@gmail.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	Grant Likely <grant.likely@secretlab.ca>
Subject: Re: Google Summer of Code 2010 - Please resolve duplicates
Date: Mon, 19 Apr 2010 15:57:00 -0700	[thread overview]
Message-ID: <4BCCDFBC.4020907@gmail.com> (raw)
In-Reply-To: <20100419224634.GG1800@kroah.com>

On 04/19/2010 03:46 PM, Greg KH wrote:
> On Mon, Apr 19, 2010 at 12:39:34PM -0700, Till Kamppeter wrote:
>> Hi,
>>
>> two students who applied for your projects have applied also for
>> another organization's project and they got accepted by us and by
>> the other organization.
>>
>> Until Wednesday Google wants these situation to be resolved until
>> Wednesday April 21, 17:00 UTC. Please contact the students and/or
>> the organization to agree on one of the project for each student.
>>
>> In addition, the ranking of the students (to decide who actually
>> gets our slots) and the mentor assignments have to be finalized by
>> the same date and time.
>>
>> Duplicates not be resolved until then will be resolved on an IRC
>> meeting on Wednesday April 21 at 19:00 UTC. The meeting takes place
>> in the #gsoc channel on Freenode.
>>
>> Please mail me if a mentor needs to be (re)assigned.
>>
>>     Till
>>
>>
>>
>> ----------------------------------------------------------------------
>>
>> Hi all,
>>
>> I have opened the duplicate information for students to all of your
>> orgs. If you view your student proposals now the ones that are ranked
>> to be accepted that are duplicated with another org will be marked in
>> red. If you click on the proposal you will see the contact information
>> for the other organization(s)'s admins near the bottom of the
>> proposal.
>>
>> You must also have a mentor assigned to all the students in your top N
>> slots by now. If you do not have a mentor assigned to them the
>> duplicate detection script will not pick them up and we may have
>> duplicates we don't know about. That is bad, please fix that if its
>> the case.
>>
>> Please try to resolve as many of these duplicate situations via email
>> in the next two days as possible - contact your fellow organizations,
>> be clear with each other about who is taking the student, and then
>> rank the student up if you are accepting him/her or mark the student
>> ineligible with a public comment that you have marked it ineligible
>> because of a duplicate situation if you are not taking the student.
>>
>> The deadline for changing rankings is 17:00UTC on Wednesday, April 21.
>> All duplicates that have not been resolved by 17:00 UTC will be taken
>> to the IRC meeting at 19:00 UTC.
>
> Have a pointer to the web site to do this?
>
> thanks,
>
> greg k-h
>

Sorry, here we go:

http://socghop.appspot.com/gsoc/org/list_proposals/google/gsoc2010/lf

Requires login as mentor.

    Till

  reply	other threads:[~2010-04-19 22:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-19 19:39 Google Summer of Code 2010 - Please resolve duplicates Till Kamppeter
2010-04-19 22:46 ` Greg KH
2010-04-19 22:57   ` Till Kamppeter [this message]
2010-04-20  7:19     ` Till Kamppeter
2010-04-19 22:58   ` Hin-Tak Leung
2010-04-20  6:13 ` Johannes Berg
2010-04-20 12:43 ` Grant Likely
2010-04-20 17:31   ` Till Kamppeter

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=4BCCDFBC.4020907@gmail.com \
    --to=till.kamppeter@gmail.com \
    --cc=acme@ghostprotocols.net \
    --cc=grant.likely@secretlab.ca \
    --cc=greg@kroah.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.com \
    --cc=tytso@mit.edu \
    --cc=witold.sowa@gmail.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 NNTP newsgroup(s).