From: Witold Sowa <witold.sowa@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: Re: Google Summer of Code 2009: Another wireless application
Date: Mon, 06 Apr 2009 00:02:42 +0200 [thread overview]
Message-ID: <49D92A82.8010108@gmail.com> (raw)
In-Reply-To: <3ace41890904042017y34a50374k193b5ea5761f3840@mail.gmail.com>
Hin-Tak Leung pisze:
> On Sat, Apr 4, 2009 at 11:07 AM, Witold Sowa <witold.sowa@gmail.com> wrote:
>
>> Hin-Tak Leung wrote:
>>
>>> (Hi Till!) - personally I like to see AP mode in network manager...
>>> there are two students on this (neither look too promising on first
>>> glance, but I could be wrong.)
>>>
>>> I haven't been checking lately - seems to have fewer students this year?
>>>
>>>
>> Actually, I disagree. I am ready to discuss my ideas and prove that I
>> have suitable skills to carry on the project.
>>
>
> You are free to discuss your ideas - but it was quite inappropriate of
> me to comment on merits and relative merits of students' applications
> in an open list, and I apologize for that.
>
There is nothing to apologize for. I think that proposals should be
discussed publicly. It would point mistakes which applicants do and help
them to avoid doing them later (eg. next year). Constructive criticism
is always welcomed.
> You are welcomed to try - and please do. But mind you a few things
> (and same applies to other students' applications):
> somebody who is knowledgeable in the topic of your choice needs to
> agree to be your mentor, and so far that has not happened - Dan has
> not agreed to consider any of the AP mode applications yet AFAIK;
> also, project ideas are compared and considered both within linux
> foundation, and in GSoC as a whole: Google only funds X numbers of
> projects each year, and only Y are allocated to Linux foundation.
>
I thought it works in a bit different way. I thought that mentor is
determined to lead some project before the applications are submitted.
Then, proposals are sorted in order of quality and importance and the
best Y applications is being accepted. Thanks for making it clear.
next prev parent reply other threads:[~2009-04-05 22:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 18:08 GSoC '09 applicant : Introduction k roy
2009-03-24 19:56 ` Luis R. Rodriguez
2009-03-27 17:41 ` Till Kamppeter
2009-03-27 18:26 ` Luis R. Rodriguez
2009-03-30 22:47 ` Google Summer of Code 2009: Another wireless application Till Kamppeter
2009-04-03 11:05 ` Till Kamppeter
2009-04-03 16:58 ` Till Kamppeter
2009-04-03 17:03 ` Till Kamppeter
2009-04-03 19:08 ` Till Kamppeter
2009-04-03 19:12 ` Till Kamppeter
2009-04-04 1:20 ` Hin-Tak Leung
2009-04-04 10:07 ` Witold Sowa
2009-04-05 3:17 ` Hin-Tak Leung
2009-04-05 22:02 ` Witold Sowa [this message]
2009-04-05 22:42 ` Hin-Tak Leung
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=49D92A82.8010108@gmail.com \
--to=witold.sowa@gmail.com \
--cc=linux-wireless@vger.kernel.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).