| 1 |
It is regrettable that the leak occurred, but I think the impact of the leak is overblown. If any council member feels that his ability to make sound technical judgments was compromised by the leak, then he should resign. If none believe that they have been compromised, then I see no reason to worry about "bad winners". We presumably voted on our perceptions of the technical decisions that others would make. Knowledge of how people voted is irrelevant in making technical decisions. |
| 2 |
|
| 3 |
That being said, I am concerned about retribution in the form of harassment from the losers. Such behavior has no place in an open source project, but I fear that not everyone subscribes to this ideal. Little can be done about those that do not, but c'est la vie. |
| 4 |
|
| 5 |
The most we can do now is to endeavor to prevent recurrences of this leak. I think it is important that the election officials not "beat themselves up" over this. Nothing is a better teacher than experience and any feelings of regret are best channelled into the positive outlet of being more careful in the future. e.g. making a checklist of what to do and another checklist of what not to do. |
| 6 |
|
| 7 |
> On Jul 17, 2014, at 8:15 AM, "Anthony G. Basile" <blueness@g.o> wrote: |
| 8 |
> |
| 9 |
>> On 07/17/14 07:49, hasufell wrote: |
| 10 |
>> Dirkjan Ochtman: |
| 11 |
>>>> On Thu, Jul 17, 2014 at 1:38 PM, hasufell <hasufell@g.o> wrote: |
| 12 |
>>>> Doesn't that make the vote invalid? |
| 13 |
>>> |
| 14 |
>>> I don't see why it would. Maybe if voters would have known in advance |
| 15 |
>>> that their votes might be compromised. |
| 16 |
>> |
| 17 |
>> IMO, it doesn't matter if the violation had an effect on the result. It |
| 18 |
>> matters that there was a violation of procedure. |
| 19 |
> |
| 20 |
> Unfortunately it does have an effect since council members now know who voted for them and who didn't and this can make for bad feelings, impartiality etc. I'm not sure how to deal with this since a re-vote will not make this knowledge go away. While not a perfect solution, maybe we should just try to ignore it as much as possible? |
| 21 |
> |
| 22 |
> -- |
| 23 |
> Anthony G. Basile, Ph.D. |
| 24 |
> Gentoo Linux Developer [Hardened] |
| 25 |
> E-Mail : blueness@g.o |
| 26 |
> GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA |
| 27 |
> GnuPG ID : F52D4BBA |
| 28 |
> |
Archives