Gentoo Archives: gentoo-project

From: "Chí-Thanh Christopher Nguyễn" <chithanh@g.o>
To: gentoo-project@l.g.o
Subject: Re: [gentoo-project] Council: Policy for Systemd units
Date: Sat, 15 Jun 2013 09:32:48
Message-Id: 51BC3483.4010304@gentoo.org
In Reply to: Re: [gentoo-project] Council: Policy for Systemd units by Tom Wijsman
1 Tom Wijsman schrieb:
2 > On Sat, 15 Jun 2013 02:44:50 +0430
3 > Chí-Thanh Christopher Nguyễn <chithanh@g.o> wrote:
4 >
5 >> Tom Wijsman schrieb:
6 >>
7 >>> Oh, and not to forget about X-openrc, X-cron, X-..., ... and so on.
8 >>
9 >> X-selinux if you want an example of what is currently in tree.
10 >
11 > That's not the point, the point is that different approaches are used;
12 > this leads to inconsistency that makes things harder for our users.
13
14 So what? If one approach is better, then over time it will win over the
15 others. If there is not one single best approach, then users will have
16 to live with the diversity (or inconsistency as you call it).
17
18 >
19 >
20 >>> Putting the maintenance burden on users is the worst thing we can
21 >>> do.
22 >>
23 >> Users have no extra maintenance burden in this case.
24 >
25 > They do, because of the inconsistency they can't take a single action.
26 >
27 >> Users have to make informed decisions, which is something they have
28 >> to do all the time anyway when using Gentoo.
29 >
30 > Irrelevant to the maintenance burden, it is not about not making
31 > informed decisions but rather about not making them harder to apply.
32
33 "Follow this HOWTO/guide" is not hard.
34
35
36 >> IIRC, QA needs no formal justification for masking a package.
37 >
38 > They do, otherwise they can't pursue their goal; if they don't define
39 > quality and can't justify themselves, then what exactly do they assure?
40
41 Usually QA does justify their actions, but I found nowhere a rule that
42 this is a requirement.
43
44 >> You are free to pursue what you think is best for any particular group
45 >> of users that you care about. Just don't expect anybody else to share
46 >> that ambition.
47 >
48 > They don't have to, because there is no reason for them to be bothered;
49 > at least not in the sense of caring for any group of users.
50
51 Indeed.
52
53 >> x11 team decided some time ago that we would not let proprietary
54 >> drivers hinder the progress of X.org packages.
55 >
56 > This is irrelevant, since optional files do not hinder progress.
57
58 This is very relevant. Imagine if one day a user comes and wants us to
59 include a very small, almost zero-maintenance, upstream-rejected patch
60 for xorg-server that makes it easier to run proprietary drivers on
61 Gentoo. Oh wait, someone already did[1].
62
63 And if any other developer disagrees, he is welcome to make his own
64 xorg-server package that includes this patch.
65
66 >> Would it be better for our users if we instead bent over to
67 >> accommodate for the binary blobs from AMD, Intel (yes, Intel) and
68 >> NVidia?
69 >
70 > Yes, I don't see how this is a problem for the X11 team.
71
72 This is not a problem for the X11 team, but one for the users that we
73 care about, namely the ones who use the free/open source drivers. They
74 would not see latest package versions in stable with latest features and
75 bugfixes, until the proprietary drivers are compatible with them.
76 >> However for all *I* care, blob users can go use Windows.
77 >
78 > They don't have to, and using Gentoo as a means to bother users one
79 > hates isn't really the right approach to go about it; that's careless.
80
81 I don't hate that group of users, I just don't care about them. I do not
82 do anything to deliberately sabotage their choice to use blobs, but I to
83 put it in the words of a well-known kernel developer[2]: I refuse to tie
84 my hands behind my back for them. If they use blobs, it is their problem.
85
86 >> Other developers care more, and put a lot of effort into making the
87 >> blobs palatable on Gentoo.
88 >
89 > Glad they do.
90
91 Yes, that is very cool.
92
93 >> You mean that page? http://www.gentoo.org/main/en/about.xml
94 >> I don't see the words "direction" or "stream", nor anything similar
95 >> mentioned there.
96 >
97 > Why do the exact words have to be there. It being an about and
98 > therefore it is sufficient to give a description of Gentoo.
99 >
100 > "automatically ... for just about any ... need", I don't see how
101 > "maintenance burden" is "automatically" and how "all *I* care" is
102 > "any ... need"; that would be disrespectful to what Gentoo is.
103 >
104 > In fact, if you want more exact words; a better read is
105 >
106 > http://www.gentoo.org/main/en/philosophy.xml
107 >
108 > which has "goal" & "philosophy", uses the word "should" several times,
109 > "strive", "mission" and more. Are you going to ignore this as well?
110
111 I don't ignore this. It describes Gentoo as tools which work for the
112 goals of the user. So create the tools that are fine for your users. I
113 will create those that are fine for mine, and they all can be part of
114 Gentoo. The about or philosophy pages do not put an upper limit on the
115 number of tools that can be in Gentoo.
116
117 >>>> Gentoo is a collection of individuals which each work on a small
118 >>>> part of it, and the interference in that is kept to the necessary
119 >>>> minimum, mostly by Council enacted rules. I would be very unhappy
120 >>>> if that were to change.
121 >>>
122 >>> You can't avoid interference, it is bound to happen sooner or later;
123 >>> when it does, Council shouldn't be implied, but rather be the
124 >>> exception.
125 >>>
126 >>> I would be very unhappy if Gentoo only ran on rules and silence;
127 >>> these not only affect our developers, but even more also our users.
128 >>
129 >> Interference does happen, I did not claim otherwise.
130 >
131 > You claimed it to be kept minimum; that's either silence or ignorance.
132
133 I said it needs to be kept to the *necessary* minimum. That is for
134 example QA rules like observing visibility requirements, no substantial
135 changes to stable packages, technical implementation of legal rules like
136 RESTRICT for packages with problematic license, and so on.
137
138 >> If you disagree with another developer, you of course are entitled
139 >> to complain loudly and try to convince him of your way.
140 >
141 > This in not about developers agreeing, it is about our users agreeing.
142 >
143 > Oh, and that philosophy link above, it has "user" all over the place...
144
145 Users are diverse and they don't agree on many things either. yngwin is
146 not alone in rejecting non-upstreamed systemd units in his packages,
147 there are many users who don't want them either (whether that is a
148 rational decision or not) and for whom this change is unwelcome. So
149 these are the users that he cares about.
150
151
152 Best regards,
153 Chí-Thanh Christopher Nguyễn
154
155
156 [1] https://bugs.gentoo.org/show_bug.cgi?id=462656
157 [2] https://lkml.org/lkml/1999/2/8/13

Replies

Subject Author
Re: [gentoo-project] Council: Policy for Systemd units Tom Wijsman <TomWij@g.o>