public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] production vs enterprise and the direction of Gentoo
Date: Thu, 16 Jun 2005 16:04:49 -0400	[thread overview]
Message-ID: <1118952289.13606.7.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <42B1BD0E.3080402@badapple.net>

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

On Thu, 2005-06-16 at 12:55 -0500, kashani wrote:
> 	I'm an admin and have only worked in ISP, NSP, hosting, and startup 
> gigs. These systems tend to be fast moving, customer and feature driven, 
> and a bit on the bleeding edge. I don't believe any of those 
> environments fall into what is normally considered "enterprise", but 
> they are production systems with a premium on flexibility over stability 
> much like a Linux distribution we all know and love. :)

Production != Enterprise

I know what you mean, though.  However, you are definitely not the
target for any of Gentoo's "Enterprise" efforts, as they are, by design,
much slower moving and much less flexible.

> posting on the forums over a QA department of just me. So rather than 
> see Gentoo think about doing or not doing enterprise type stuff like 
> long releases, support contracts, etc I think most of us LAMP, MRTG, 
> Nagios, BIND, Postfix, Qmail, Postgres, thttpd, Courier, etc geeks would 
> like "just a bit more stability" rather than the overhead that comes 
> with enterprise features.

Honestly, the more bleeding edge it is, the less quality that is going
to be associated with it, simply due to new features and other such
things that will not have gotten as much testing/bug-fixing as the more
stable features.  Unless we have our own audit team specifically looking
for bugs and fixing them *before they are reported* then there isn't
much we can do to resolve this situation.

> 	To be honest /etc/portage/* tends be enough control for me, but I've 
> been doing admin work for 9 years. And I've got a test environment that 
> I use religiously. I do however answer a lot of questions in the Network 
> and Security forum where up and coming admins aren't so lucky. I don't 
> think any of us expect a foolproof system, but there is room for a bit 
> more stability that'll benefit all users... especially admins. :)

That is one of the problems we have here at Gentoo.  We provide ways of
doing things that you want to do.  Sometimes the methods are very
simple, other times, we expect you to know what you're doing.  The real
problem we have is how to balance between the "do everything for the
user" approach of some distributions and the "don't do a damn thing and
then let the user RTFM" approach that is a bit more common with Gentoo.
Personally, I think we simply need to make sure things get documented
well and leave it up to the community to provide the "support", as it
were.  This has worked quite well for Gentoo, and tends to tighten the
bond between users and developers.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2005-06-16 20:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-16 17:55 [gentoo-dev] production vs enterprise and the direction of Gentoo kashani
2005-06-16 20:04 ` Chris Gianelloni [this message]

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=1118952289.13606.7.camel@cgianelloni.nuvox.net \
    --to=wolf31o2@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