From: flameeyes@gmail.com (Diego 'Flameeyes' Pettenò)
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: One request for the next SoC: non already-devs students
Date: Sun, 02 Mar 2008 20:25:09 +0100 [thread overview]
Message-ID: <m2ir05j5d6.fsf@gmail.com> (raw)
In-Reply-To: 47CAF9D1.6020303@gentoo.org
[-- Attachment #1: Type: text/plain, Size: 2442 bytes --]
Richard Freeman <rich0@gentoo.org> writes:
> Do we inspire them by telling them that anybody who has made this choice
> in the past is not to be rewarded financially for doing so?
This brings up a different point of view too. Why should just somebody
be rewarded financially and not someone else? Why only people who are
still in school, and not people who left school? I don't even want to
think what might happen if there was something like Debian's DunkTank
flame in here.
> A bigger concern is this. Which is better for gentoo? Taking somebody
> who has never worked on gentoo and paying them money to possibly
> accomplish something on the project, or taking somebody who is already
> doing quite a bit and pay them so that they can accomplish even more
> without the distraction of a day job?
Do you think that $4500 (which is, by now, less than €3000) during the
summer will stop anybody already contributing from finding a day job? I
sincerely don't think so.
It does, though, help new people to _try_ working on Free
Software. Students paid for SoC don't need to find a temporary job for
that summer to build up experience (which is what I suppose most
students would like to do, you can't expect a huge pay for three months
of work _in the summer_), it's a good pay, for three months of work, but
it's far from being a pay good enough for anybody to actively stop
looking for a job. They will have to understand, though, that Gentoo is
not a job and you won't end up always being paid to help that.
Sincerely, I find the "without the distraction of a day job" argument to
be pretty silly. How can an eventual, possible, not sure at all, and for
sure not stable, check of €3000 once an year stop anybody from finding a
dayjob? It's like counting on winning the lottery twice an year to
sustain yourself. I live with my parents still, in the past years I had
unstable jobs (paying more than €3000) during the start of the year and
then had almost nothing between spring and winter, I have no monthly
expenses, and I still struggle to find money to buy a new box.
It might be an added incentive to get experience in Free Software rather
than as a third-grade programmer helper in a small software company with
most of the stable programmers taking weeks off for the summer, but for
sure can't replace a stable job.
--
Diego "Flameeyes" Pettenò
http://blog.flameeyes.eu/
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2008-03-02 19:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-02 15:47 [gentoo-dev] One request for the next SoC: non already-devs students Diego 'Flameeyes' Pettenò
2008-03-02 18:48 ` Thilo Bangert
2008-03-02 19:02 ` Richard Freeman
2008-03-02 19:25 ` Diego 'Flameeyes' Pettenò [this message]
2008-03-02 19:57 ` [gentoo-dev] " Wulf C. Krueger
2008-03-02 20:52 ` Brian Harring
2008-03-02 18:57 ` [gentoo-dev] " Robin H. Johnson
2008-03-02 20:37 ` Alec Warner
2008-03-02 20:42 ` Alec Warner
2008-03-02 20:45 ` [gentoo-dev] " Diego 'Flameeyes' Pettenò
2008-03-02 22:56 ` Diego 'Flameeyes' Pettenò
2008-03-03 0:30 ` Christian Faulhammer
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=m2ir05j5d6.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