From: Till Kamppeter <till.kamppeter@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: Evgeny Novikov <novikov@ispras.ru>,
Alexey Khoroshilov <khoroshilov@ispras.ru>,
"Luis R. Rodriguez" <mcgrof@gmail.com>,
"lsb-discuss@lists.linux-foundation.org"
<lsb-discuss@lists.linux-foundation.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
Open Printing <printing-architecture@lists.linux-foundation.org>,
chris holcombe <chris.holcombe@canonical.com>,
Chris MacNaughton <chris.macnaughton@canonical.com>
Subject: Re: [lsb-discuss] Google Summer of Code 2016 - Many new applications
Date: Wed, 30 Mar 2016 15:33:59 -0300 [thread overview]
Message-ID: <56FC1C17.70703@gmail.com> (raw)
In-Reply-To: <20160328144214.GA10444@kroah.com>
On 03/28/2016 11:42 AM, Greg KH wrote:
> On Sat, Mar 26, 2016 at 03:07:18PM -0300, Till Kamppeter wrote:
>>> If there's anything else I need to do here, becides try to find a
>>> co-mentor, please let me know.
>>>
>>
>> I am grateful if you could enter as co-mentor, especially if there is any
>> kernel project now which has only one mentor.
>
> I don't understand, we only have one kernel project with one proposed
> mentor (me) right now, are we requiring all projects to have 2 mentors
> now? I've never done it that way in the past...
Generally, a single person can mentor a student, but if something
unforeseen happens to a mentor, there is a backup. The backup mentor
actually does not need to mentor as long as there is all OK with the
primary mentor. He only needs to "WANT TO MENTOR" to later on be able to
do the evaluations if the primary mentor is not able to do so.
Till
next prev parent reply other threads:[~2016-03-30 18:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 17:39 Google Summer of Code 2016 - Many new applications Till Kamppeter
2016-03-24 18:08 ` Greg KH
[not found] ` <1943931458892174@web3o.yandex.ru>
2016-03-25 17:23 ` [lsb-discuss] " Greg KH
2016-03-25 22:58 ` Till Kamppeter
2016-03-25 23:46 ` Greg KH
2016-03-25 23:56 ` Till Kamppeter
2016-03-26 0:00 ` Till Kamppeter
2016-03-26 0:18 ` Greg KH
2016-03-26 0:39 ` Till Kamppeter
2016-03-26 14:15 ` Greg KH
2016-03-26 14:25 ` Till Kamppeter
2016-03-26 16:46 ` Greg KH
2016-03-26 17:04 ` Greg KH
2016-03-26 18:07 ` Till Kamppeter
2016-03-28 14:42 ` Greg KH
2016-03-30 18:33 ` Till Kamppeter [this message]
2016-03-26 19:28 ` Denis Silakov
2016-03-26 19:43 ` Alexey Khoroshilov
2016-03-26 19:49 ` Luis R. Rodriguez
2016-03-26 20:00 ` Till Kamppeter
2016-03-26 19:59 ` Till Kamppeter
2016-03-26 0:17 ` Greg KH
2016-03-26 0:36 ` 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=56FC1C17.70703@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=chris.holcombe@canonical.com \
--cc=chris.macnaughton@canonical.com \
--cc=greg@kroah.com \
--cc=khoroshilov@ispras.ru \
--cc=linux-wireless@vger.kernel.org \
--cc=lsb-discuss@lists.linux-foundation.org \
--cc=mcgrof@gmail.com \
--cc=novikov@ispras.ru \
--cc=printing-architecture@lists.linux-foundation.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 NNTP newsgroup(s).