From: Sam Jorna <wraeth@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Future of gentoo's stable and unstable trees: what are your thoughts?
Date: Mon, 31 Jul 2017 12:56:18 +1000 [thread overview]
Message-ID: <20170731025617.GB14487@dt001651.civica.com.au> (raw)
In-Reply-To: <assp.0385f55c39.20170730224458.2146bda9@o-sinc.com>
[-- Attachment #1: Type: text/plain, Size: 2319 bytes --]
On Sun, Jul 30, 2017 at 10:44:58PM -0400, William L. Thomson Jr. wrote:
> On Mon, 31 Jul 2017 10:28:31 +1000
> Sam Jorna <wraeth@gentoo.org> wrote:
> >
> > Wouldn't it make more sense to make Gentoo *more* attractive to run in
> > corporate environments, rather than simply saying "We're not RHEL so
> > why bother"?
>
> No disagreement. That has always been my interest. Though has not been
> others. It was in part why I became a trustee. For things like vendor
> certified hardware, looking into certifications, events, and a whole
> lot more. But people rather lambast, insult, and stand in the way rather
> than either get out of the way or work with me.
>
> It surely could happen without me but has not. I am definitely not
> against such happening. But it would require tremendous change and
> leadership. Which I do not see ever changing. I wish things were
> otherwise.
>
> > People do use Gentoo in production environments, both personally and
> > professionally, even if it is those that have more investment in doing
> > so than the average IT Joe. By removing stable, we would be reducing
> > the potential arguments for the few who do want to use Gentoo in that
> > sort of environment. We would be becoming more of a niche distro.
>
> Preaching to the choir. That is not why companies I know who ran Gentoo
> are leaving or left. One told me they did not want to be in the
> operating system business. Stable or not, there are fewer companies
> running Gentoo that were before. Due to other reasons that are not
> changing, culture, etc.
>
> Companies that run it today I doubt would change if stable went away.
> If they left Gentoo, they have many reasons far beyond lack of a stable
> branch/tree.
>
> > "Hey, lets try Gentoo - it's really configurable."
> > "What's their stable policy? How often does it break?"
> > "Stable? What's that?"
>
> How about no foundation. Not even a legal entity. No certifications
> from vendors, nor for employees. No one to hire for official support.
> There are so many things far beyond anything having to do with a stable
> tree or not.
Sorry, I thought this thread was about whether to keep or discontinue
the separation between stable and testing branches.
--
Sam Jorna (wraeth)
GnuPG Key: D6180C26
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 858 bytes --]
next prev parent reply other threads:[~2017-07-31 2:56 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 21:22 [gentoo-dev] [RFC] Future of gentoo's stable and unstable trees: what are your thoughts? Sergei Trofimovich
2017-07-24 21:52 ` [gentoo-dev] " Pacho Ramos
2017-07-24 23:22 ` [gentoo-dev] " Peter Stuge
2017-07-24 23:52 ` Rich Freeman
2017-07-25 4:34 ` [gentoo-dev] " Duncan
2017-07-25 6:26 ` Hans de Graaff
2017-07-25 6:18 ` [gentoo-dev] " Hans de Graaff
2017-07-25 9:18 ` Pacho Ramos
2017-07-25 11:54 ` Michał Górny
2017-07-25 12:15 ` Pacho Ramos
2017-07-25 13:19 ` Michał Górny
2017-07-25 13:23 ` Pacho Ramos
2017-07-25 11:26 ` Rich Freeman
2017-07-25 7:44 ` Sergei Trofimovich
2017-07-28 10:44 ` Andreas K. Huettel
2017-07-28 12:45 ` Marek Szuba
2017-07-28 13:10 ` Sam Jorna (wraeth)
2017-07-28 19:59 ` William L. Thomson Jr.
2017-07-28 21:21 ` David Seifert
2017-07-31 0:28 ` Sam Jorna
2017-07-31 0:40 ` Benda Xu
2017-07-31 2:44 ` William L. Thomson Jr.
2017-07-31 2:56 ` Sam Jorna [this message]
2017-07-31 15:00 ` William L. Thomson Jr.
2017-07-31 12:59 ` Andreas K. Huettel
2017-07-31 14:43 ` William L. Thomson Jr.
2017-07-31 14:47 ` David Seifert
2017-07-28 19:44 ` Alec Warner
2017-07-29 1:05 ` Rich Freeman
2017-07-31 14:52 ` Alec Warner
2017-07-31 15:11 ` Rich Freeman
2017-07-31 16:51 ` Peter Volkov
2017-08-01 0:24 ` [gentoo-dev] " Duncan
2017-08-01 0:55 ` Rich Freeman
2017-08-01 1:45 ` Duncan
2017-07-31 16:44 ` [gentoo-dev] " Michał Górny
2017-07-29 4:18 ` Daniel Campbell
2017-07-29 16:41 ` Mart Raudsepp
2017-07-29 19:10 ` David Seifert
2017-07-29 18:03 ` Andrew Savchenko
2017-07-25 7:22 ` Dirkjan Ochtman
2017-07-25 13:10 ` [gentoo-dev] " Michael Palimaka
2017-07-25 13:22 ` Rich Freeman
2017-07-25 20:16 ` Daniel Campbell
2017-07-25 13:36 ` Pacho Ramos
2017-07-25 14:15 ` Peter Stuge
2017-07-29 18:08 ` [gentoo-dev] " Christopher Head
2017-07-31 6:49 ` R0b0t1
2017-07-25 9:03 ` [gentoo-dev] " Agostino Sarubbo
2017-07-25 19:45 ` Markus Meier
2017-07-25 20:12 ` Rich Freeman
2017-07-26 5:49 ` Hans de Graaff
2017-07-25 12:59 ` Michael Palimaka
2017-07-25 13:30 ` Pacho Ramos
2017-07-25 13:51 ` Michał Górny
2017-07-25 14:13 ` [gentoo-dev] " Michał Górny
2017-07-25 14:28 ` Rich Freeman
2017-07-27 23:12 ` Denis Dupeyron
2017-07-27 23:41 ` Rich Freeman
2017-07-28 0:03 ` Denis Dupeyron
2017-07-28 21:24 ` William Hubbs
2017-07-29 10:24 ` Andrew Savchenko
2017-07-28 20:10 ` William L. Thomson Jr.
2017-07-28 21:12 ` A. Wilcox
2017-07-28 21:41 ` William L. Thomson Jr.
2017-07-29 13:41 ` Andreas K. Huettel
2017-07-28 21:45 ` [gentoo-dev] " Duncan
2017-07-28 21:56 ` William L. Thomson Jr.
2017-07-29 19:44 ` Walter Dnes
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=20170731025617.GB14487@dt001651.civica.com.au \
--to=wraeth@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