1 |
On Wed, Aug 24, 2011 at 7:45 AM, Thomas Kahle <tomka@g.o> wrote: |
2 |
> Sorry, but NO. If you want you can make a big noise message that asks |
3 |
> users to install the cron-job but opt-out is not an option here. |
4 |
|
5 |
Well, that's up to the Council/Trustees ultimately, but opinions (and |
6 |
better still reasoning) are welcome since both would no-doubt want to |
7 |
reflect the will of the community (and whatever is legal in the |
8 |
jurisdictions that matter). |
9 |
|
10 |
One option that many distros employ is a forced opt-in/out decision. |
11 |
During the install process they simply ask the user, and they have to |
12 |
hit either yes or no to continue. The reason most people don't opt-in |
13 |
is that they don't think about it, and this forces the issue. |
14 |
|
15 |
The Gentoo analogue would be to put something in make.conf or whatever |
16 |
that must be set one way or another. Maybe have an opt-in use flag |
17 |
and an opt-out use flag and if you don't set either emerge just dies |
18 |
with a notice or something. No doubt somebody could come up with a |
19 |
more elegant solution. |
20 |
|
21 |
Maybe another line of discussion that could inform the debate is what |
22 |
the value of this information is? For a company, knowing what |
23 |
packages are popular helps them to allocate resources. Gentoo is a |
24 |
volunteer effort and devs allocate their effort based on personal |
25 |
preference, though perhaps some would care about package popularity to |
26 |
an extent. So, we might not benefit to the same degree from this kind |
27 |
of information, since we can't crack the whip and force people to fix |
28 |
some broken package that is popular. |
29 |
|
30 |
Rich |