From: Chris Reffett <creffett@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Portage QOS
Date: Thu, 09 Jan 2014 16:08:39 -0500 [thread overview]
Message-ID: <52CF0FD7.8010608@gentoo.org> (raw)
In-Reply-To: <52cf09c2.463f700a.4b43.58d7@mx.google.com>
On 01/09/2014 03:42 PM, Igor wrote:
> Hello Duncan,
>
> Thursday, January 9, 2014, 9:59:50 PM, you wrote:
>
> Thank you for the reply. I started to comment first... but it was more
> philosophy a mature and grown up, experienced man and I don't think
> I have right to comment it.
>
> Statistically if you have more users the probability of the system
> survival of any architecture, philosophy or type is higher. People
> learn, they're not fixed and if they at the beginning do not share
> the philosophy of the system but they can use it - they may like it,
> understand it and follow it and support later. Many people I asked
> are not minding to help Gentoo getting better by turning on
> feedback. If you remember - feedback worked well for Perl once and
> many used it and Perl is very traditional.
>
> It's like a chess game. You have the system in it's prime. There is
> already one fork from Gentoo. There will be more. It's inevitable. You
> have to understand that not all the developers share the same
> philosophy - and it OK.
> And they may fork Gentoo with time and pull half of the team to their
> side.
>
> When there is a competition between systems with equal philosophy the
> only thing that stands between who is going to live and who is going
> to die is the number of users.
> The fight will focus not around philosophy or system but around gaining
> user support. The competitor can build a better, more friendly system
> sharing basically the same design and he will win it over.
>
> To keep in power it's in your deepest interest to close the open gates that
> invite competition while the power is in your hands. This is a failure
> many grown up companies made they belive they're forever and gods. I could
> share with you privately with several examples that prove that concept
> wrong.
>
> Your competitors will build basically the same system targeting the
> same philosophy but more user oriented, friendly. User oriented - means
> each user opinion matters.
>
> There might be millions of users but each is treated like he is the only one.
>
>
> PortageQOS is small step, it's not everything or main part of the
> system, it's a just small contribution. But it will close the door and
> you'll have another peaceful 8 years to rule.
>
Right here is the big problem: you're not looking at this from the
perspective of the average Gentoo developer. We don't care about market
share. We don't care whether we're on top for another few years. There
are several forks of Gentoo. I doubt most devs care about them. I
personally know that we're not going to compete with Debian, which has a
huge contributor, or Ubuntu or Red Hat, which have whole companies
behind them. You're selling this as if you're selling to a company which
wants to be on the top of the market and beating out competitors, and
that's not what we are. We are a source-based distro that requires some
effort from users, and people want that or they don't want it.
> What we need is a vote YES or NO. If you against it - vote NO. It's
> perfectly normal, if there would be no NO there would be no need voting.
>
>
>> Actually, in that regard it's very possible that gentoo's long planned
>> and worked toward cvs-to-git conversion will help finally bust that
>> barrier for gentoo as well. Time will tell I guess, but that's one more
>> reason to try to help make it happen.
>
>
>
>
Chris Reffett
next prev parent reply other threads:[~2014-01-09 21:09 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 7:24 [gentoo-dev] Portage QOS LTHR
2014-01-09 8:12 ` Alec Warner
2014-01-09 12:44 ` Igor
2014-01-09 14:12 ` Christopher Schwan
2014-01-09 15:26 ` Igor
2014-01-09 15:55 ` Jeroen Roovers
2014-01-09 16:37 ` Igor
2014-01-10 0:27 ` heroxbd
2014-01-10 12:41 ` Igor
2014-01-10 13:51 ` Rich Freeman
2014-01-10 0:16 ` heroxbd
2014-01-10 0:31 ` Patrick Lauer
2014-01-10 1:19 ` Tom Wijsman
2014-01-10 1:52 ` Patrick McLean
2014-01-10 2:40 ` Tom Wijsman
2014-01-10 6:17 ` Brian Dolbec
2014-01-10 18:14 ` Ciaran McCreesh
2014-01-10 7:54 ` heroxbd
2014-01-10 18:11 ` Ciaran McCreesh
2014-01-11 3:57 ` Patrick Lauer
2014-01-10 1:02 ` Tom Wijsman
2014-01-10 9:10 ` heroxbd
2014-01-10 14:54 ` Tom Wijsman
2014-01-10 12:23 ` Igor
2014-01-10 12:30 ` René Neumann
2014-01-10 12:30 ` Igor
2014-01-10 12:39 ` Patrick Lauer
2014-01-10 13:05 ` Igor
2014-01-10 13:18 ` René Neumann
2014-01-10 18:19 ` Ciaran McCreesh
2014-01-10 19:06 ` René Neumann
2014-01-10 14:05 ` heroxbd
2014-01-12 10:47 ` [gentoo-dev] " Steven J. Long
2014-01-10 13:10 ` [gentoo-dev] " Igor
2014-01-10 14:02 ` Rich Freeman
2014-01-10 15:16 ` Tom Wijsman
2014-01-10 18:12 ` Ciaran McCreesh
2014-01-09 15:49 ` Ben Kohler
2014-01-09 16:11 ` Igor
2014-01-09 17:59 ` [gentoo-dev] " Duncan
2014-01-09 20:42 ` Igor
2014-01-09 21:08 ` Chris Reffett [this message]
2014-01-10 12:10 ` Igor
2014-01-10 12:26 ` René Neumann
2014-01-10 12:52 ` Igor
2014-01-10 12:57 ` René Neumann
2014-01-10 15:39 ` Tom Wijsman
2014-01-10 16:36 ` Mike Frysinger
2014-01-10 18:17 ` Greg KH
2014-01-10 19:38 ` Duncan
2014-01-10 22:36 ` heroxbd
2014-01-11 1:28 ` Duncan
2014-01-09 19:35 ` [gentoo-dev] " yac
2014-01-11 15:00 ` Naohiro Aota
2014-01-12 10:28 ` Igor
2014-01-12 19:31 ` Igor
2014-01-12 19:31 ` Igor
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=52CF0FD7.8010608@gentoo.org \
--to=creffett@gentoo.org \
--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