1 |
On 13/11/16 08:17, Michał Górny wrote: |
2 |
> On Sun, 13 Nov 2016 01:53:15 +0000 |
3 |
> "M. J. Everitt" <m.j.everitt@×××.org> wrote: |
4 |
> |
5 |
>> Ok so for the sake of clarity, we have a purely technical issue, which |
6 |
>> is either right or wrong .. and then someone takes it as a personal |
7 |
>> affront, instead of being mature and professional, and accepting the |
8 |
>> correction, learning the lesson, to put into practise in future. So |
9 |
>> instead of the issue being purely technical .. said person MAKES it |
10 |
>> personal .. and therefore themselves causes a conflict .. which requires |
11 |
>> some form of Discipline .. which breeds hate .. and ... |
12 |
>> |
13 |
>> .. you see where I'm going .. ?! |
14 |
> I don't see what your problem is. |
15 |
> |
16 |
> QA handles the technical issue, and stays the correct body for |
17 |
> the technical part of the issue. If someone adds a behavior issue for |
18 |
> it, Comrel handles the latter. There are two separate issues, that have |
19 |
> some common evidence. |
20 |
> |
21 |
> Of course, it sometimes did happen that one of the bodies already |
22 |
> issued the ban, making any work on the other end unnecessary. I don't |
23 |
> see a problem with that either. |
24 |
> |
25 |
> Do we have any common members between Comrel and QA? That could be |
26 |
> a conflict but could be easily solved via excluding the common member |
27 |
> from the latter team for this particular issue. If you really think |
28 |
> it's a problem. |
29 |
> |
30 |
I think your argument holds water, but perhaps it's overkill to create |
31 |
two "issues"/bugs, if you will, and go from there. However, if both |
32 |
projects (QA and ComRel) were to amass evidence pertaining to their |
33 |
respective 'expertises', and present a single issue to Council, then |
34 |
perhaps this may be one pathway to take. I think some clarification |
35 |
policy/procedure in the form of guidelines would probably help here .. |
36 |
but the first step is inevitably divorcing the technical from the |
37 |
personal 'end' of the problem, which was the root of my original post :). |