1 |
On Tue, Apr 24, 2012 at 6:26 PM, William Hubbs <williamh@g.o> wrote: |
2 |
> Honestly, I agree with you. I am a udev maintainer myself, and the udev |
3 |
> maintainers did not bring this issue to council. More than that, no one, |
4 |
> that I recall, discussed any ramifications of this vote with any udev |
5 |
> maintainers before bringing it to council. |
6 |
> |
7 |
> The ramifications, as I said in my previous email, are not just udev |
8 |
> related (see the section in my previous email about the /usr merge). |
9 |
> |
10 |
> Once we start implementing the /usr merge, it will not matter whether |
11 |
> you use udev or not, you will have to have an initramfs if your /usr is |
12 |
> separate. |
13 |
|
14 |
I have mixed feelings on this. |
15 |
|
16 |
The fact that the ramifications are not just udev-related tends to |
17 |
point to the fact that this shouldn't simply be up to the udev team. |
18 |
These are big changes for Gentoo, and there is a great deal of |
19 |
controversy across the Linux world resulting from them (the |
20 |
Shuttleworth vs Pottering debate being the latest iteration of this). |
21 |
Everybody has to live with this stuff, which points to council |
22 |
involvement. |
23 |
|
24 |
On the other hand, somebody has to maintain all this code, so having a |
25 |
bunch of non-udev-maintainers telling them what to do is not a great |
26 |
thing either. Worst case you end up with a bunch of frustrated people |
27 |
giving up on it, which leaves us much worse off. If you are paying |
28 |
your staff you can tell them what to do, but with volunteers you need |
29 |
to be more "inspirational" in your leadership. If the udev team |
30 |
thinks this is the way the wind is blowing then either more people |
31 |
need to step up and help them maintain more configurability, or we |
32 |
need to just work with them to make the ride as smooth as we can. I |
33 |
don't think anybody wants to see needless end-user pain here in any |
34 |
case, and as far as I can tell the udev maintainers are quite willing |
35 |
to work with other projects (genkernel, dracut, docs, etc) as needed. |
36 |
|
37 |
Lots of people have pointed out alternative options, and I've always |
38 |
been a proponent of "Gentoo is about choice." However, if we want a |
39 |
choice to be available people do need to step up and make those |
40 |
choices available. Volunteer distros don't work well when people tell |
41 |
others how to maintain their code. We struggle enough with basic |
42 |
quality control sometimes, and I think most of us can admit it when we |
43 |
make a mistake in these areas (if for no reason than out of pride in |
44 |
our work). To ask developers to build to somebody else's design in a |
45 |
volunteer organization may be asking a bit much. |
46 |
|
47 |
I think the best we can do is look for opportunities to give people |
48 |
choices when they're practical, and when people are willing to pitch |
49 |
in and maintain their side of the interfaces. You don't even have to |
50 |
be a Gentoo developer to do that - just look at OpenRC/etc - get an |
51 |
account on github, do good work, and ask some developer to commit your |
52 |
ebuilds. |
53 |
|
54 |
Rich |