From: Brian Harring <ferringb@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: One request for the next SoC: non already-devs students
Date: Sun, 2 Mar 2008 12:52:18 -0800 [thread overview]
Message-ID: <20080302205218.GA23459@seldon.hsd1.ca.comcast.net> (raw)
In-Reply-To: <200803022057.07269.philantrop@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1931 bytes --]
On Sun, Mar 02, 2008 at 08:57:03PM +0100, Wulf C. Krueger wrote:
> On Sunday, 02. March 2008 20:25:09 Diego 'Flameeyes' Pettenò wrote:
> > > 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.
>
> From my point of view it's pretty simple: I don't see us generating enough
> interest among people not yet associated with Gentoo to successfully
> participate.
>
> Your idea would be fine with me if we had enough people wanting to do it
> but I don't really see that happen.
It could be argued that devs have an inherint advantage- they have far
greater access to devs to hash out their ideas, aware of what issues
the distro is facing, etc. All of that adds up giving devs a better
range of prospects for proposals and ironing out their proposals.
To be clear also, I'm not implying any backhand dealings here- just
that I view it as a bit of a closed system that makes it easier for
those already in the circle to succeed.
Personally, I'm not a fan of a flat out "no devs allowed"- a
percentile limit however, seems like a good step towards trying to
enable a focus on new blood (or even those new to FOSS).
Basically, devs have it easy in hammering out a proposal from where
I'm sitting- I'd like to see gains in trying to enable new blood,
whether doing some limiting of devs or a greater outreach. I'm not
suggesting crap proposals should be accepted purely because they're
from non-dev also, although I'd be tempted to give prioritization to
nondevs if it's neck in neck.
> > Why should just somebody be rewarded financially and not someone else?
>
> Because as a student people usually need the money more.
SoC is limited to students anyways, thus kind of moot continuing that
particular line of discussion...
~brian
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-03-02 20:52 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 ` [gentoo-dev] " Diego 'Flameeyes' Pettenò
2008-03-02 19:57 ` Wulf C. Krueger
2008-03-02 20:52 ` Brian Harring [this message]
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=20080302205218.GA23459@seldon.hsd1.ca.comcast.net \
--to=ferringb@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