1 |
On Sun, Nov 13, 2011 at 10:49 AM, Thomas Sachau <tommy@g.o> wrote: |
2 |
> 1. Who defines, what the default should be and when it is acceptable to force an unknown amount of |
3 |
> users to change their settings? |
4 |
|
5 |
Well, this did go on a mailing list, and so far we have all of 13 |
6 |
unique participants, so this seems like a bit of a tempest in a teapot |
7 |
considering that the change is trivial to undo. |
8 |
|
9 |
I'll admit that it is pretty subjective either way, and that is just |
10 |
more of a reason not to turn it into a huge controversy. Users who |
11 |
would be most sensitive to changes won't even see this until it hits |
12 |
stable (if you don't like change, you shouldn't be running ~arch). |
13 |
|
14 |
This is actually the sort of thing that might make for a good news |
15 |
item (hey, we have a new setting and if you don't like it just do |
16 |
this...). |
17 |
|
18 |
Ultimately I think that it is up to the team maintaining a particular |
19 |
component of the distro to make initial determinations of how that |
20 |
component should behave, of course consulting with the list about |
21 |
things likely to be of wide interest is always good but this was done |
22 |
in this case. |
23 |
|
24 |
If people want to appeal there is always making an appeal to the team |
25 |
lead, and then to the Council. There should be no reprimands or |
26 |
stigma associated with having a decision reversed by the Council - |
27 |
people shouldn't have to second-guess minor decisions like this. |
28 |
|
29 |
I don't think it serves Gentoo to call for a vote (council, devs, or |
30 |
otherwise) every time somebody wants to change the portage defaults, |
31 |
especially regarding matters that are cosmetic. |
32 |
|
33 |
Rich |