From: "Giacomo A. Catenazzi" <cate@cateee.net>
To: Rik van Riel <riel@redhat.com>
Cc: Alexey Zaytsev <alexey.zaytsev@gmail.com>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
Vegard Nossum <vegard.nossum@gmail.com>
Subject: Re: Google's Summer of Code?
Date: Wed, 05 Mar 2008 14:57:05 +0100 [thread overview]
Message-ID: <47CEA6B1.3080803@cateee.net> (raw)
In-Reply-To: <20080304152303.2a041814@cuia.boston.redhat.com>
Rik van Riel wrote:
> On Tue, 4 Mar 2008 23:05:34 +0300
> "Alexey Zaytsev" <alexey.zaytsev@gmail.com> wrote:
>> Maybe the Kernelnewbies should stand up as the mentoring organisation?
>
> Kernelnewbies is just a community of people, without much organization.
>
> However, I would be happy to coordinate a group of mentors for Linux
> kernel Summer of Code as well as be a mentor for the kernel subsystems
> that I know something about.
>
> If we can find mentors to cover most of the kernel (volunteers? anyone?),
> we can do a good enough job of mentoring the students that we could sign
> up for Summer of Code.
>
> Summer of Code could also be a good way to get some kernel related work
> done, for example LTP tests for kernel subsystems that do not have a
> test suite yet. Maybe not the most interesting work, but it can be very
> educational as well as useful - that and $5000 may be enough to motivate
> students to get some of this "boring work" done :)
I propose and I could mentor two projects about automagical kernel
configuration:
- add support to menuconfig, to show what you should enable (not
really an automagical configuration, but more an helper which
know better(?) your hardware).
- new ideas about hardware/protocol detection and detection heuristics.
I've already done some parts: generating an hardware->kernel driver
database ( http://cateee.net/lkddb/ ), and a working prototype of
autoconfiguration ( http://testing.cateee.net/autokernconf/ ).
I really want to have new ideas and other developers. I think the
idea are appealing to students, and it doesn't requires a lot of
knowledge of kernel internal.
ciao
cate
next prev parent reply other threads:[~2008-03-05 13:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 18:45 Google's Summer of Code? Pekka Enberg
2008-03-04 19:35 ` Linus Torvalds
2008-03-04 19:55 ` Pekka Enberg
2008-03-04 20:05 ` Alexey Zaytsev
2008-03-04 20:23 ` Rik van Riel
2008-03-05 13:57 ` Giacomo A. Catenazzi [this message]
2008-03-05 15:38 ` Romano Giannetti
2008-03-06 8:36 ` Pekka Enberg
2008-03-04 20:13 ` Andrew Morton
2008-03-04 20:38 ` Andi Kleen
2008-03-05 2:01 ` text processing (Re: Google's Summer of Code?) Oleg Verych
2008-03-04 21:44 ` kernelprojects::menuconfig [was:Re: Google's Summer of Code?] Jan Engelhardt
2008-03-05 6:09 ` Willy Tarreau
2008-03-04 20:51 ` Google's Summer of Code? Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2008-03-04 21:11 Casey Schaufler
2008-03-05 7:41 ` Avi Kivity
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=47CEA6B1.3080803@cateee.net \
--to=cate@cateee.net \
--cc=akpm@linux-foundation.org \
--cc=alexey.zaytsev@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=riel@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=vegard.nossum@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