From: Till Kamppeter <till.kamppeter@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>, Greg KH <greg@kroah.com>,
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>
Subject: Google Summer of Code 2010 - Please ASSIGN (not propose) mentors to the students
Date: Sat, 10 Apr 2010 20:39:45 +0200 [thread overview]
Message-ID: <4BC0C5F1.20309@gmail.com> (raw)
Hi,
on Tuesday morning the distribution of the student slots to the
mentoring organizations will take place. The number of slots which each
organization gets depends mainly on how many student applications with
assigned mentor (not only proposed mentors) they have.
So please ASSIGN a mentor to each good application of your work area.
On the page with the list of student proposals
http://socghop.appspot.com/gsoc/org/list_proposals/google/gsoc2010/lf
all good applications must appear in the second list ("Student Proposals
already under review sent to The Linux Foundation") and in the column
"Mentor" must be a name of a mentor, NOT simply "N Proposed". To assign
a mentor to a student click on the proposal in the list to get the
proposal's page, there, under "Admin options" select the desired mentor
from the list. If you want to mentor and you are not listed, see my
previous posting on how to get mentor.
If you do not mentor by yourself but the one who should mentor the
student is not available in the moment so that he cannot do the steps to
get mentor and to assign himself to the student until end of Monday,
please assign yourself as mentor to get the student considered when the
slots get distributed. The mentor assignment can be changed at any time.
Till
reply other threads:[~2010-04-10 18:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4BC0C5F1.20309@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=acme@ghostprotocols.net \
--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).