From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org)
by finch.gentoo.org with esmtp (Exim 4.60)
(envelope-from <gentoo-dev+bounces-29724-garchives=archives.gentoo.org@lists.gentoo.org>)
id 1JX10D-0005HI-Jx
for garchives@archives.gentoo.org; Wed, 05 Mar 2008 21:18:17 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 3B8A2E0598;
Wed, 5 Mar 2008 21:08:06 +0000 (UTC)
Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183])
by pigeon.gentoo.org (Postfix) with ESMTP id E706DE0598
for <gentoo-dev@lists.gentoo.org>; Wed, 5 Mar 2008 21:08:05 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp.gentoo.org (Postfix) with ESMTP id 86D6066E5D
for <gentoo-dev@lists.gentoo.org>; Wed, 5 Mar 2008 21:08:05 +0000 (UTC)
X-Virus-Scanned: amavisd-new at gentoo.org
X-Spam-Score: -2.421
X-Spam-Level:
X-Spam-Status: No, score=-2.421 required=5.5 tests=[AWL=0.178,
BAYES_00=-2.599]
Received: from smtp.gentoo.org ([127.0.0.1])
by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id JiwzUso+j5jk for <gentoo-dev@lists.gentoo.org>;
Wed, 5 Mar 2008 21:07:59 +0000 (UTC)
Received: from ciao.gmane.org (main.gmane.org [80.91.229.2])
(using TLSv1 with cipher AES256-SHA (256/256 bits))
(No client certificate requested)
by smtp.gentoo.org (Postfix) with ESMTP id 7C20F66CAC
for <gentoo-dev@gentoo.org>; Wed, 5 Mar 2008 21:07:56 +0000 (UTC)
Received: from list by ciao.gmane.org with local (Exim 4.43)
id 1JX0q6-0006rz-E0
for gentoo-dev@gentoo.org; Wed, 05 Mar 2008 21:07:50 +0000
Received: from adsl-ull-35-42.48-151.net24.it ([151.48.42.35])
by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
id 1AlnuQ-0007hv-00
for <gentoo-dev@gentoo.org>; Wed, 05 Mar 2008 21:07:50 +0000
Received: from flameeyes by adsl-ull-35-42.48-151.net24.it with local (Gmexim 0.1 (Debian))
id 1AlnuQ-0007hv-00
for <gentoo-dev@gentoo.org>; Wed, 05 Mar 2008 21:07:50 +0000
X-Injected-Via-Gmane: http://gmane.org/
To: gentoo-dev@lists.gentoo.org
From: flameeyes@gmail.com (Diego 'Flameeyes' =?utf-8?Q?Petten=C3=B2?=)
Subject: [gentoo-dev] Proposal for (next year's probably) SoC
Date: Wed, 05 Mar 2008 22:07:37 +0100
Message-ID: <m2skz4517q.fsf@gmail.com>
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
micalg=pgp-sha1; protocol="application/pgp-signature"
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: adsl-ull-35-42.48-151.net24.it
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux)
Cancel-Lock: sha1:BESKDvp8nycC+/tYcpDVWtHkzsU=
Sender: news <news@ger.gmane.org>
X-Archives-Salt: 322f63c3-155f-4f30-9c54-5e147b5d15dd
X-Archives-Hash: 9b300e6dcbf08cbe1fd72cbdbb3e394e
--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
I think it could be useful to learn from other projects' handling of
SoC. The FFmpeg project has a list of "qualification tasks" for the
students to complete before they can accepted into SoC, as you can see
From=20[1].
The tasks are minor tasks that don't require a lot of time at hand, but
gives a good way to judge if the person is in for the experience or the
money, and might be able to cut the deal even for Gentoo devs if that is
really wanted.
How to implement it for Gentoo? Well I think we have the tool already:
Bugzilla. We just need to add a keyword SOC_QUALIFICATION_TASK; when a
developer think of a working qualification task, he can add the keyword
and CC the soc team or something like that.
Then the users can deal with the problems whenever they want, for the
next SoC, even during the year. When they submit their application, we
ask users to put the link to the bug that represented the qualification
task they completed.
To make the checking more easy, we could make sure that the person who
completed the task is listed in the Whiteboard, and that only Gentoo
devs can change that for the bugs for qualification task (letting only
devs opening them, or cloning the feature requests from user that become
a SoC qualification task, for instance).
Then get a tracker that is blocked by all the SoC qualification task
bugs, monitored by the SoC team, that can make sure how stuff is going
with the qualification tasks, and finally add a default query for the
tasks to the documentation about SoC.
I'm sure we can easily get some qualification tasks on; with a bit more
work we might also get qualification points (so that for instance minor
tasks alone can't cut the deal).
Maybe a bit complex, but I think it might be worth discussing.
[1] http://wiki.multimedia.cx/index.php?title=3DFFmpeg_Summer_Of_Code_2008
=2D-=20
Diego "Flameeyes" Petten=C3=B2
http://blog.flameeyes.eu/
--=-=-=
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
iD8DBQFHzwuZe2h1+2mHVWMRAi4hAJsEysNFY9pGqKMfNmP8Be005KZ34wCfaFQ4
9ClH9oeMEzjkeRG2zs0p0mI=
=wP1B
-----END PGP SIGNATURE-----
--=-=-=--
--
gentoo-dev@lists.gentoo.org mailing list