public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: flameeyes@gmail.com (Diego 'Flameeyes' Pettenò)
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Proposal for (next year's probably) SoC
Date: Wed, 05 Mar 2008 22:07:37 +0100	[thread overview]
Message-ID: <m2skz4517q.fsf@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1940 bytes --]


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 [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=FFmpeg_Summer_Of_Code_2008

-- 
Diego "Flameeyes" Pettenò
http://blog.flameeyes.eu/


[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]

             reply	other threads:[~2008-03-05 21:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-05 21:07 Diego 'Flameeyes' Pettenò [this message]
2008-03-06  0:59 ` [gentoo-dev] Proposal for (next year's probably) SoC Marius Mauch

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=m2skz4517q.fsf@gmail.com \
    --to=flameeyes@gmail.com \
    --cc=gentoo-dev@lists.gentoo.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