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 07:37:53 -0400 [thread overview]
Message-ID: <CAGfcS_mG5v2Y8a8w9ix4jdst6WR+v9BunwTj4=CTOm0eytBV0g@mail.gmail.com> (raw)
In-Reply-To: <21008.27285.932342.231536@a1i15.kph.uni-mainz.de>
On Sun, Aug 18, 2013 at 2:32 AM, Ulrich Mueller <ulm@gentoo.org> wrote:
>>>>>> On Sat, 17 Aug 2013, William Hubbs wrote:
>
>> The Council agrees that all preparations for dropping support
>> for separate /usr without an initramfs or similar boot mechanism are
>> complete.
>
> Why such a hurry? We have voted that we would "eventually" drop
> support, and in the log you can find that we were talking about a
> timeframe of six months.
>
> I suggest that we revisit the topic no earlier than in six months from
> now.
Personally I was thinking WITHIN the next six months, not taking no
action for six months and then restarting the debate.
I think williamh is perfectly within his rights to suggest that we're
ready to go. Anybody who has a problem with his suggestion is also
within their rights to state a specific objection (something
actionable).
I just don't see any reason for waiting, at least not right now. If
the argument is that we should give users some period of time to
prepare, then we should be sending out some kind of specific news item
telling them what preparations to make and THEN waiting.
That said, it wouldn't hurt to maybe discuss on-list some of the
potential actions the council might take.
1. Obviously if we don't think documentation/etc is ready then no
action gets taken at all (we leave the current decision in-place).
If we think docs/etc are in place there are a few different positions
we could take:
2. We could ask that news be sent out before the first significant
change to / and there be some time period before taking action on it.
(ie, we trust maintainer discretion)
3. We could ask that maintainers of packages in / get council
approval for each move to /usr with at least brief justification and a
proposed communication plan. (ie, we don't trust maintainer
discretion)
4. We could tell maintainers not to make deliberate changes without
individual approval, but they could WONTFIX bugs that point out small
regressions/etc without approval. (ie let's not open the floodgates
yet, but we can relieve some pressure on maintainers and let entropy
take its course)
5. With #3-4 at some point the council would decide that they've
approved enough changes that further approvals are moot, and the
requirement for pre-approval would be rescinded.
Here is my personal take: The stated reason for dropping separate
/usr support without an initramfs/etc is that this is a config that
upstreams are steadily moving away from. I get that, and I don't want
maintainers to have to bend over backwards to keep it working. That
said, I also don't see a need to make huge overnight changes (if a
maintainer thinks this is the only way to reduce their workload,
please speak up). I think that this should probably be handled like
the kde4 transition, or the gnome-systemd transition. That is, we
provide a reasonable amount of support for the status quo until that
state of affairs just isn't tenable.
If anybody feels we're already at the point where supporting the
status quo is untenable by all means speak up. I don't want to make
maintainers work harder, but I also don't want to force changes
earlier than necessary without some reason for it.
That said, those who feel that we're not ready need to state a
specific actionable objection. "The docs aren't ready" isn't specific
or actionable. "The handbook should say xyz in this section" or "the
dracut guide should specify that the usrmount module should be enabled
if you have a separate /usr and how" are.
Finally, I could see the /usr merge as a POSSIBLE reason to move
things sooner. If somebody wants to propose some plan to make that
happen they should do so, and we can debate it on this list and so on.
However, I don't see any value in moving a bunch of stuff around
purely for the sake of a /usr merge when there isn't any plan to
finish the work. If anybody is thinking about that being the driver
they need to have a plan that actually gets us to the end goal, and of
course we need to agree that this is even a goal we want to have.
Rich
next prev parent reply other threads:[~2013-08-18 11:37 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 [this message]
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
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_mG5v2Y8a8w9ix4jdst6WR+v9BunwTj4=CTOm0eytBV0g@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