public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] rfc: separate /usr preparation vote
Date: Sun, 18 Aug 2013 09:46:33 -0400	[thread overview]
Message-ID: <CAGfcS_mRK9khLRkxwUcEHo5_8BSqA23_GNF1c6NT7QE546rB7Q@mail.gmail.com> (raw)
In-Reply-To: <5210C73B.8050602@opensource.dyc.edu>

On Sun, Aug 18, 2013 at 9:08 AM, Anthony G. Basile
<basile@opensource.dyc.edu> wrote:
>
> ditto.  I want this debated in the community, ie, I want to hear the
> community say "all the preperation for dropping support ... are complete".

The community will never say that, just like no community ever said
"hey, we need a source-based linux distro!"

Progress and change gets initiated by individuals or small teams, and
the community always has to play catch up.  That's just how change and
innovation works.

The role of the community is to say why preparations AREN'T complete.
The default needs to be action, not inaction.  If we only change
things when a majority are clamoring for change, then I suggest that
anybody cares about running an interesting distro fork Gentoo now.
This isn't CentOS, and we're not going to backport patches to linux
2.4 until 95% of our customers agree that whatever proprietary blob
they're using is ready for 2.6.

Don't get me wrong - I'd love to see debate.  However, williamh made a
proposal, and if somebody wants to argue that we aren't ready yet then
they need to step up and do it.  That is how every court in the world
works, as far as I know (if you don't show up, you don't get a say).
I'm not really chomping at the bit to see stuff move to /usr, but if
people have a reason to ask for inaction, they need to voice it, and
not just ask everybody else to pass time.  If there is a reason to
hold things up I'll be the first to agree to hold things up, but there
has to be a reason, otherwise I'll probably support WONTFIXing any
separate-/usr regressions on existing packages, not putting any
restrictions on packages that weren't stable more than a year ago, and
allowing large changes to packages older than that if they can be
justified.

Rich


  reply	other threads:[~2013-08-18 13:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-17 22:20 [gentoo-project] rfc: separate /usr preparation vote William Hubbs
2013-08-18  6:32 ` Ulrich Mueller
2013-08-18 11:37   ` Rich Freeman
2013-08-19  2:48     ` William Hubbs
2013-08-19  3:10       ` Rich Freeman
2013-08-19  3:48         ` Rick "Zero_Chaos" Farina
2013-08-19 11:31           ` Rich Freeman
2013-08-19  6:19       ` Sven Vermeulen
2013-08-19  6:30       ` Ulrich Mueller
2013-08-19 13:35         ` Ian Stakenvicius
2013-08-18 13:08   ` Anthony G. Basile
2013-08-18 13:46     ` Rich Freeman [this message]
2013-08-19  0:18       ` Denis Dupeyron
2013-08-19  0:29         ` Rick "Zero_Chaos" Farina
2013-08-19  1:40       ` Anthony G. Basile
2013-08-19  1:57         ` Rich Freeman
2013-08-27 19:11 ` Roy Bamford
2013-08-27 19:30   ` Ian Stakenvicius
2013-08-28  0:46     ` Rich Freeman
2013-08-27 19:30   ` Rick "Zero_Chaos" Farina
2013-08-28  1:25     ` William Hubbs
2013-08-28 15:04       ` Sven Vermeulen

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=CAGfcS_mRK9khLRkxwUcEHo5_8BSqA23_GNF1c6NT7QE546rB7Q@mail.gmail.com \
    --to=rich0@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