| 1 |
> From what I see you are on both council and comrel. I think that is a |
| 2 |
> conflict of interest. |
| 3 |
> |
| 4 |
> Council and ComRel should check on each other. If someone is member of |
| 5 |
> both, then it is likely that he will avoid acting against either party |
| 6 |
> even if it necessary. |
| 7 |
> |
| 8 |
> Some worst case scenarios: |
| 9 |
> * you have a problem with a council member => you go to ComRel in need |
| 10 |
> of help |
| 11 |
> * you have a problem with a ComRel member => you go to council, because |
| 12 |
> going to ComRel isn't necessarily an option (e.g. the person is the |
| 13 |
> ComRel lead or you think that ComRel isn't in a functional state) |
| 14 |
> * If someone is on both parties and you got a problem with him, then the |
| 15 |
> situation is delicate and checks and balances are likely to fail |
| 16 |
|
| 17 |
Hey Julian, |
| 18 |
|
| 19 |
a few points can be made here (and have already been made in this thread). |
| 20 |
Let's first talk about the general situation... |
| 21 |
|
| 22 |
First of all, both comrel decisions and council decisions are always team |
| 23 |
actions. You may have seen the situation of "one comrel guy talks to someone |
| 24 |
and tells him 'please behave'". While this certainly has an effect, and would |
| 25 |
have been communicated within the comrel team, it does not have much formal |
| 26 |
meaning. In the (luckily rather rare) cases where a formal comrel decision |
| 27 |
that has consequences is needed, the steps are documented in detail, including |
| 28 |
who was involved in the decision making. |
| 29 |
|
| 30 |
[If you look at old public bugs tracking such events, you get across texts |
| 31 |
like "This suspension was agreed upon by x, y, z, a, b, and c. d also agreed |
| 32 |
with the decision."] |
| 33 |
|
| 34 |
The council has 7 members, comrel currently 15. So, even if an individual |
| 35 |
developer were in both groups and would really cast votes on both levels, that |
| 36 |
would not give this individual power to "box through" decisions on both |
| 37 |
levels. That said, I see it as good practice not to take part in any decision |
| 38 |
on both levels (and intend to stick to that should the case ever arise). |
| 39 |
|
| 40 |
Now about me personally... |
| 41 |
|
| 42 |
I was invited to join (then) devrel a short time before I was first elected to |
| 43 |
the council. For a large part I'm still trying to learn from the "comrel |
| 44 |
ancients" how things are done there, which is not so easy as long as (luckily) |
| 45 |
not much is happening. I consider the council work more important, and have |
| 46 |
only limited time. For these reasons, I tend to take things slow in comrel so |
| 47 |
far and prefer if other people pick up the phone. |
| 48 |
|
| 49 |
Cheers, |
| 50 |
Andreas |
| 51 |
|
| 52 |
|
| 53 |
-- |
| 54 |
Andreas K. Huettel |
| 55 |
Gentoo Linux developer |
| 56 |
kde, council |
Archives