1 |
On Sat, Sep 24, 2011 at 3:10 AM, Mike Frysinger <vapier@g.o> wrote: |
2 |
> On Sat, Sep 24, 2011 at 02:49, Duncan wrote: |
3 |
>> Unfortunately, locking a bug to kill the whining is likely to have rather |
4 |
>> more negative effects than one might have anticipated. One would think |
5 |
>> comment locking would be a logical enough extension to have been |
6 |
>> implemented by now; perhaps this is why it hasn't been. (Full visibility |
7 |
>> locking is of course different, security bugs and all.) |
8 |
> |
9 |
> i don't see any negative effects so far. |
10 |
|
11 |
Well, you can probably count the 22 emails preceding this one, and the |
12 |
22 that are sure to follow... |
13 |
|
14 |
User-rel is definitely the appropriate way to handle things like this. |
15 |
There are legitimate technical disagreements over the best way to |
16 |
handle this situation, and I can't approve of Nikos's tendency to |
17 |
personalize things in the bug. On the other hand, simply telling him |
18 |
to get lost is likely to just lead to more flames/etc. |
19 |
|
20 |
This seems like a bit of a tempest in a teapot - we're not talking |
21 |
about a glibc ABI change hitting the tree without planning. A few |
22 |
obscure packages with questionable practices have broken, and are |
23 |
being fixed. We can move on. |
24 |
|
25 |
The fact is that Mike's attitude does not truly reflect the attitudes |
26 |
of all developers, and Nikos's attitude does not reflect the attitudes |
27 |
of all users. So, going into generalities that amount to devs vs |
28 |
users is just going to rile a lot of people up. Gentoo is a |
29 |
community, and devs benefit from a user pool from which new devs |
30 |
emerge (and other random contributions), and users obviously benefit |
31 |
from devs typically at no cost to themselves. Being on the trustee |
32 |
list I get to see the countless donations (often small, sometimes not) |
33 |
coming from the community (no doubt from both devs and users) that let |
34 |
us have things like rsync servers and the mailing list we're posting |
35 |
on. It is really in all of our interests to work together. Devs on |
36 |
the infra team spend no small number of hours making it all work, but |
37 |
it is nice when they need new hardware to just be able to ask and get |
38 |
a check cut, often due to no small number of users. |
39 |
|
40 |
Communities also have to have rules, and when users are dissatisfied |
41 |
with how a developer is handling something there are better and worse |
42 |
ways to handle it. Obviously working it out is the best way. If you |
43 |
need help with that there is always devrel. Simply posting flames on |
44 |
a bug is not the right way to handle it. |
45 |
|
46 |
But, again, this is a bit of a tempest in a teapot, and hopefully |
47 |
something we can all think about. |
48 |
|
49 |
Rich |