linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hin-Tak Leung <hintak.leung@gmail.com>
To: Till Kamppeter <till.kamppeter@gmail.com>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Greg KH <greg@kroah.com>,
	linux-kernel@vger.kernel.org,
	lsb-discuss@lists.linux-foundation.org
Subject: Re: Linux wireless GSoC 2010 project ideas
Date: Thu, 4 Feb 2010 04:52:36 +0000	[thread overview]
Message-ID: <3ace41891002032052h13be767buabb77523c0cc2d90@mail.gmail.com> (raw)
In-Reply-To: <4B620A72.7050202@gmail.com>

On 1/28/10, Till Kamppeter <till.kamppeter@gmail.com> 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.

Perhaps at this point, it might be a good idea to share some insights
for reasons of failures/non-competition. I think the first year (2008)
of LF's participation, it was 6/8 competion over all? How did 2009 do?
Luis mentioned that 2/3 failed out of the 3 wireless-related project,
but AFAIK there were about 10 accepted in 2009 under the LF umbrella -
what's the completion rate for the other 7? It is probably a good idea
to write some of that up (non-competition and the possibility of
re-do) in one of Linux Foundation's wiki pages.

AFAIK the overall non-competition rate across all organization is
about 10% so the 2/8 in 2008 wasn't too bad.

> P. S.: Do you know someone with knowledge in data compression? I will
> run a project at OpenPrinting which is about data compression.

What are you thinking of? :-)

Hin-Tak

  parent reply	other threads:[~2010-02-04  4:52 UTC|newest]

Thread overview: 27+ 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 [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-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=3ace41891002032052h13be767buabb77523c0cc2d90@mail.gmail.com \
    --to=hintak.leung@gmail.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --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).