linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Khoroshilov <khoroshilov@ispras.ru>
To: Till Kamppeter <till.kamppeter@gmail.com>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>, Greg KH <greg@kroah.com>,
	lsb-discuss@lists.linux-foundation.org,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [lsb-discuss] Linux wireless GSoC 2010 project ideas
Date: Wed, 17 Feb 2010 20:07:02 +0300	[thread overview]
Message-ID: <4B7C2236.7020807@ispras.ru> (raw)
In-Reply-To: <4B620A72.7050202@gmail.com>

Till,

Are you going to setup a wiki page to collect proposed GSoC projects for
the LF application this year?
Something similar to [1].

[1] http://www.linuxfoundation.org/en/Google_Summer_of_Code_2009

--
Regards,
Alexey


Till Kamppeter wrote:
> Great to hear from you.
>
> I will apply again for the LF entering as a mentoring organization and I 
> will add your projects to the list of proposed projects for the LF 
> application.
>
>     Till
>
> P. S.: Do you know someone with knowledge in data compression? I will 
> run a project at OpenPrinting which is about data compression.
>
>
> Luis R. Rodriguez wrote:
>   
>> Google has confirmed it will have a Google Summer of Code for 2010
>> [1]. Last year we had a few projects suggested (4) and accepted (3)
>> under the Linux Foundation sponsoring organization umbrella [2].
>> Unfortunately out of the three projects that were approved only one
>> completed successfully, that of the adding AP support to Network
>> Manger. I haven't seen specific updates to the progress of that but I
>> do know some patches were indeed submitted to help with this effort.
>> Perhaps the student can elaborate more.
>>
>> The other projects that did not pass are up as suggestion for this
>> year again, but am hoping there are more. If you do have a project
>> idea please just go ahead and add your idea to the list of possible
>> projects [3]; you don't have to fill out a full page for it for now
>> but the more details you can add the better. If the Linux Foundation
>> does give us a few slots I recommend we be a little more strict about
>> acceptance criteria since our failure rate was pretty high (2/3) and
>> it would be better to see other projects get accepted if we do not
>> have the confidence our projects will be completed. One possibility to
>> help with the success rate of our projects might be to narrow the
>> scope down a little more. I think the testing and GeoClue project
>> might have been a little too ambitious and although we did have pretty
>> excited students we saw no progress at all.
>>
>> If you have ideas for projects just feel free to add to the wiki. We
>> should strive to get all project ideas finalized by the middle of
>> February, latest the end of February. Hopefully towards the end of
>> February we can see who would be willing to mentor each project.
>> Google plans on starting to accept would-be-mentor organization
>> applications on  March 8th so we'll need our ideas finalized well
>> before that so we can send them as suggestions to the Linux Foundation
>> to see if we can get a few good project candidates accepted.
>>
>> [1] http://groups.google.com/group/google-summer-of-code-discuss/browse_thread/thread/d839c0b02ac15b3f
>> [2] http://wireless.kernel.org/en/developers/GSoC/2009
>> [3] http://wireless.kernel.org/en/developers/GSoC/2010
>>
>>   Luis
>>
>>     
>
>   


  parent reply	other threads:[~2010-02-17 17:07 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-28 21:38 Linux wireless GSoC 2010 project ideas Luis R. Rodriguez
2010-01-28 22:06 ` Till Kamppeter
2010-01-28 22:14   ` Luis R. Rodriguez
2010-02-04  4:52   ` Hin-Tak Leung
2010-02-17 17:07   ` Alexey Khoroshilov [this message]
2010-01-28 23:15 ` Frederic Weisbecker
2010-01-28 23:23   ` Luis R. Rodriguez
2010-01-28 23:31     ` Greg KH
2010-01-28 23:41       ` Frederic Weisbecker
2010-01-28 23:51     ` Till Kamppeter
2010-03-09 22:43       ` Frederic Weisbecker
2010-03-12  8:12         ` Till Kamppeter
2010-03-18  3:40           ` Frederic Weisbecker
2010-03-12  8:59         ` Till Kamppeter
2010-03-12  9:38           ` [lsb-discuss] " Denis Silakov
2010-03-12  9:57             ` Till Kamppeter
2010-03-21 19:49             ` Frederic Weisbecker
2010-01-31 21:03 ` Witold Sowa
2010-01-31 21:20   ` Johannes Berg
2010-02-01 18:01     ` Luis R. Rodriguez
2010-02-01 20:14       ` Maxim Levitsky
2010-02-01 20:17         ` david
2010-02-01 21:31           ` Maxim Levitsky
2010-02-03  9:23             ` Holger Schurig
2010-02-01 22:12         ` Nick Bowler
2010-02-02  4:25           ` Pat Erley
2010-02-03  9:25             ` Holger Schurig
2010-02-03 14:24               ` pat-lkml
2010-02-03 18:48                 ` Luis R. Rodriguez
2010-02-05  5:16                   ` Pat Erley
2010-02-05 15:49                     ` Luis R. Rodriguez
2010-02-04  8:32                 ` Kalle Valo
2010-02-04 22:36                   ` Pat Erley
2010-02-22 21:25 ` Luis R. Rodriguez

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=4B7C2236.7020807@ispras.ru \
    --to=khoroshilov@ispras.ru \
    --cc=greg@kroah.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lsb-discuss@lists.linux-foundation.org \
    --cc=mcgrof@gmail.com \
    --cc=till.kamppeter@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).