public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Hubbs <williamh@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Council meeting: Tuesday 13 November 2012, 19:00 UTC
Date: Sun, 11 Nov 2012 12:43:30 -0600	[thread overview]
Message-ID: <20121111184330.GA7436@linux1> (raw)
In-Reply-To: <20121111085136.GB83592@gentoo.org>

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

On Sun, Nov 11, 2012 at 09:51:36AM +0100, Fabian Groffen wrote:
> On 10-11-2012 13:37:48 -0600, William Hubbs wrote:
> > > Last but not least, I see no reason (given we have to keep the code
> > > anyway) to make sysadmins, that feel unsure about this on their running
> > > production systems, go into this route.  You don't know what custom code
> > > they have installed/running.  They'll be on their own (no
> > > udev/GNOME/whatever support), but most likely they won't care about that
> > > at all.
> > 
> > No, we don't know what custom code people are running, but custom
> > someone is running is not an excuse to block change. We just
> > have to make change happen in an orderly fashion and make sure people
> > are aware of the change so they can find ways on their end to adapt.
> > Isn't that reasonable?
> 
> I look at it from the other side, why do we have to make upgrading
> impossible for people that can not, or will not perform that change?

If there are people running gentoo Linux who CAN NOT do this, they
definitely should speak up. That's exactly why a newsitem needs to be
sent out announcing this and giving a time window before we go forward
with anything.

There is a difference between CAN not and WILL not. If you disagree with
what I'm about to say say so, but it seems to me that if someone WILL
not perform a change, that is more something they should worry about,
not us.

William


[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2012-11-11 21:02 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-06 21:28 [gentoo-project] Council meeting: Tuesday 11 November 2012, 19:00 UTC Fabian Groffen
2012-11-08 16:30 ` [gentoo-project] Re: [gentoo-dev-announce] " Alexis Ballier
2012-11-08 17:46   ` Rich Freeman
2012-11-08 18:25     ` William Hubbs
2012-11-08 17:45 ` [gentoo-project] " William Hubbs
2012-11-08 18:15   ` Fabian Groffen
2012-11-08 18:53     ` William Hubbs
2012-11-08 21:16       ` Rich Freeman
2012-11-08 22:09         ` William Hubbs
2012-11-08 22:28           ` Rich Freeman
2012-11-08 23:46       ` Alexis Ballier
2012-11-09  5:13         ` William Hubbs
2012-11-09 11:19           ` Rich Freeman
2012-11-09 11:33           ` Alexis Ballier
2012-11-09 15:32             ` William Hubbs
2012-11-09 16:03               ` Rich Freeman
2012-11-09 17:01                 ` William Hubbs
2012-11-09 18:21               ` Fabian Groffen
2012-11-10  1:42                 ` William Hubbs
2012-11-10  9:00                   ` Fabian Groffen
2012-11-10 19:37                     ` William Hubbs
2012-11-10 19:39                       ` Ian Stakenvicius
2012-11-10 21:10                         ` [gentoo-project] Council meeting: Tuesday 13 " Petteri Räty
2012-11-11  8:51                       ` Fabian Groffen
2012-11-11 18:43                         ` William Hubbs [this message]
2012-11-09 18:21               ` [gentoo-project] Council meeting: Tuesday 11 " Alexis Ballier
2012-11-09  8:26         ` Fabian Groffen
2012-11-11  8:53 ` [gentoo-project] [corrected date] Council meeting: Tuesday 13 " Fabian Groffen
2012-11-11 10:57 ` [gentoo-project] Council meeting: Tuesday 11 " Ulrich Mueller
2012-11-17 19:02 ` [gentoo-project] Summary Council meeting Tuesday 13 November 2012 Fabian Groffen

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=20121111184330.GA7436@linux1 \
    --to=williamh@gentoo.org \
    --cc=gentoo-project@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