1 |
On Wed, 04 Jun 2014 00:49:48 +0200 |
2 |
Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
3 |
|
4 |
> Indeed. It really comes down to a judgement call whether to compose a |
5 |
> news item or not. |
6 |
|
7 |
True, it is not always easy; although some of us want or try to figure |
8 |
this out in advance, even predictions won't help to determine how well |
9 |
the users will experience these kind of effects. The more these events |
10 |
happen, the more I think they're aftermath is inevitable, the more it |
11 |
would be nice to redesign to prevent the events from happening. |
12 |
|
13 |
Especially when you get to know the Portage output better, it is hard to |
14 |
judge how well the Portage output still is for existing users; I have |
15 |
no motivation to improve the Portage output for myself, given I can |
16 |
find my way in it in a reasonable amount of time (given the parameters |
17 |
--tree and --unordered-display which are not default). |
18 |
|
19 |
But that's where it stops; though I recognize that it is not as helpful |
20 |
for new users, as well as want to improve it for them, it is hard to |
21 |
know where to start and what kind of output to go for. We're locked |
22 |
down to a particular view; thinking of other views, it'll be hard to see |
23 |
one where there is a benefit that outweighs the costs implementing it. |
24 |
|
25 |
So, then you can come to the conclusion that we have good enough output |
26 |
considering the conditions in which the output can be changed; and as a |
27 |
result of it not changing, we rely more and more on its knowledge. |
28 |
|
29 |
> I myself in my sysadmin day job get this right about 50% of the time |
30 |
> if I'm lucky. I've learned (via hard knocks) that if a number of |
31 |
> people raise concerns, then it very well might not be bikeshedding, |
32 |
> it might be valid. |
33 |
|
34 |
What I'm trying to say was that it is still in some way valid when you |
35 |
bike shed; it isn't so much anymore about the central point being |
36 |
discussed about being valid, but the idea behind why you're discussing |
37 |
that central point. |
38 |
|
39 |
Among other things, this highlights things in the organization and/or |
40 |
respect of the matter at hand; it won't result a change wrt to the |
41 |
central point, but it'll result in a change of organization and/or |
42 |
respect. |
43 |
|
44 |
Just because you can't quickly find out a date to go out with someone |
45 |
doesn't mean you can't do it more organized and respectful next time. |
46 |
|
47 |
> Often as the BOFH I'm too close to the technical problem to notice |
48 |
> the human elements - that needs a view from 10 feet back. |
49 |
|
50 |
When faced with a technical problem; there are 3 or more ways to take a |
51 |
stance, some of which conflicting stances make the human part matter: |
52 |
|
53 |
1. Aggressive: You want your work to happen and lead to results. |
54 |
|
55 |
2. Defensive: You want to prevent your work from changing, you want to |
56 |
prevent the results of your work from changing. |
57 |
|
58 |
3. Neutral: You don't know much about the work, it's not clear what |
59 |
you want; given that, you'll play devil's advocate to learn more of it. |
60 |
|
61 |
Now, with any of these; it is easy to get into the human elements, |
62 |
which have to do with a problem in the organization (expectations, |
63 |
planning, reports, ...) or respect (finding out what works for both). |
64 |
|
65 |
Sometimes the view is too far back, because you're as explained above |
66 |
grown used to the situation; when that happens, you get stuck and |
67 |
either need to make a comprise not in your favor or need to move on. |
68 |
|
69 |
A lot of compromises, some recently, get made; which I'm happy about. |
70 |
|
71 |
A lot of us are here for improving Gentoo, we can't just always |
72 |
agree on the particular way in which to do that; but it'll be the net |
73 |
result of all those (dis)agreements, compromises and walks that count. |
74 |
|
75 |
> News items are probably one of Gentoo's best ideas ever. |
76 |
|
77 |
True that. |
78 |
|
79 |
-- |
80 |
With kind regards, |
81 |
|
82 |
Tom Wijsman (TomWij) |
83 |
Gentoo Developer |
84 |
|
85 |
E-mail address : TomWij@g.o |
86 |
GPG Public Key : 6D34E57D |
87 |
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D |