1 |
On Sun, 30 Mar 2014 07:00:42 -0400 |
2 |
"Anthony G. Basile" <blueness@g.o> wrote: |
3 |
|
4 |
> While implementing a new policy may not be the right approach (or so |
5 |
> I'm hearing from the community), I can bring forward at least 3 |
6 |
> examples of significant changes that were not discussed. I don't |
7 |
> think I would have difficulty convincing people of this fact. If we |
8 |
> do not enact policy then how is this problem addressed? |
9 |
> |
10 |
> As far as "driving people away" I will shift my efforts to |
11 |
> recruiting. I am a professor and can get more students into Gentoo |
12 |
> development. We cannot adopt a de facto situation where devs can |
13 |
> misbehave because they are indispensable. |
14 |
|
15 |
Had a whole conversation with WilliamH about this; my viewpoint after |
16 |
that conversation has changed, it isn't anymore to just go for the |
17 |
policy, but it boils down that there are multiple options to pick from: |
18 |
|
19 |
1) you fix it on the technical level, by introducing policy; |
20 |
|
21 |
2) you fix it on the personal level, by improving relations; |
22 |
|
23 |
3) you do nothing, letting people burn out in personal quibblings. |
24 |
|
25 |
Maybe more options exist, I dunno. |
26 |
|
27 |
Each option then has its advantages and disadvantages, a pick: |
28 |
|
29 |
1) Advantage: You prevent the concerns altogether. You get useful |
30 |
feedback on what you're planning to commit. |
31 |
|
32 |
Disadvantage: The loudest people can stall progress. People who |
33 |
disagree speak more than people than acknowledge it, even if |
34 |
there is a fifty-fifty situation it's hard to tell how to |
35 |
proceed; that leads to less progress than without discussion. |
36 |
|
37 |
2) Advantage: Improved communication. |
38 |
|
39 |
Disadvantage: You'll need to be though to get people to improve; |
40 |
as Anthony highlights, people currently are indispensable. The |
41 |
way to fix that is get more people, if you can get more people. |
42 |
|
43 |
3) Advantage: People learn through burning out to work together; |
44 |
because well, reverting and/or whatsoever yields no progress. |
45 |
|
46 |
Disadvantage: A personal quibbling every week or so. Mood drops. |
47 |
|
48 |
There are other (dis)advantage to these things; but I'm just saying, |
49 |
whatever solution we pick, we must be well aware of the goal as well a |
50 |
the consequence of that solution. And there's no way to pick no |
51 |
solution; because doing so, you'll pick the current (3) by default. |
52 |
|
53 |
That being said, these things come up due to a series of minor events |
54 |
over the last week; they all turn out to not be huge breakage, |
55 |
however ... what if one day someone commits something much worse? |
56 |
|
57 |
We do our best to mitigate the situation in that case; however, I hope |
58 |
that these cases don't become the habit, but rather the exception. |
59 |
|
60 |
So far, we've been doing fine though; but seeing that some things get |
61 |
committed where unintended side effects happen, it is still a worry. |
62 |
|
63 |
-- |
64 |
With kind regards, |
65 |
|
66 |
Tom Wijsman (TomWij) |
67 |
Gentoo Developer |
68 |
|
69 |
E-mail address : TomWij@g.o |
70 |
GPG Public Key : 6D34E57D |
71 |
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D |