1 |
Hey Sebastian, |
2 |
|
3 |
On 30 June 2010 06:15, Sebastian Pipping <sping@g.o> wrote: |
4 |
> Arun, |
5 |
[...] |
6 |
>> And another one for "More direct democracy": |
7 |
>> |
8 |
>> a) How would you decide what questions go up for public vote and which |
9 |
>> ones stay with the council? |
10 |
> |
11 |
> Good question! I think a few voices from developers (say three) |
12 |
> requesting a vote should force a global vote. If the council were |
13 |
> deciding on that, the concept would be useless. At least that's my |
14 |
> current understanding. |
15 |
> |
16 |
> |
17 |
>> b) For questions like "- Should Python 3.x be stable?", isn't that for |
18 |
>> team leads to decide? And for the council to resolve in case of |
19 |
>> conflicts? |
20 |
> |
21 |
> It's too important to leave it to the Python team alone in my eyes. |
22 |
> Previous threads have shown that consensus is hard to find on Python 3.x |
23 |
> related topics. A direct vote from all developers would reveal what the |
24 |
> majority really wants for that topic. |
25 |
|
26 |
It is my opinion that dismissing the opinions of the people who are |
27 |
actually doing the work is not a good way to motivate the same people |
28 |
(I don't even disagree with you about the Python team's approach to |
29 |
3.x in the tree, but I disagree with how you think it should be |
30 |
handled). |
31 |
|
32 |
>> c) For questions like "- Should developer X be banned?", would you be |
33 |
>> willing to do this if it meant a lot of washing of dirty linen in |
34 |
>> public, or protracted flamewars (and other reasons why we have a bunch |
35 |
>> of level-headed people in place to deal with this calmly and quietly)? |
36 |
>> If no, where would you draw the line? If yes, how would you deal with |
37 |
>> the fallout? |
38 |
> |
39 |
> I'm not understanding all of that, honestly. |
40 |
> On a part I understood: Solving isues on that front may be worth extra |
41 |
> "noise" as the goal is to noticably improve atmosphere after. |
42 |
> Please help me to understand the rest of your question. |
43 |
|
44 |
The problem is not noise. The problem is that an issue that needs to |
45 |
be escalated to Devrel could not be resolved by the involved |
46 |
developers or the people who were present at the time. Moreover, there |
47 |
are strong emotions from the devs (and often their friends too), and |
48 |
people will end up saying things that they may eventually regret. |
49 |
|
50 |
Dragging this out in public /will/ polarise the community, result in |
51 |
more public conflict, very likely without a complete picture of the |
52 |
story on both sides being available. Devrel's purpose is to avoid |
53 |
this, and I believe this does work (we can debate their efficacy or |
54 |
how things can improve, but saying it doesn't work is unfair, IMO). I |
55 |
don't see how your proposal would deal with this fallout. |
56 |
|
57 |
Cheers, |
58 |
-- |
59 |
Arun Raghavan |
60 |
http://arunraghavan.net/ |
61 |
(Ford_Prefect | Gentoo) & (arunsr | GNOME) |