On 07/09/2018 05:47, Patrick Shanahan wrote:
* Richard Brown <RBrownCCB@opensuse.org> [09-06-18 15:47]:
On Thu, 6 Sep 2018 at 20:43, Per Jessen <per@computer.org> wrote: [...]
That is fair enough, I absolutely accept your position. Now shall we bring the proposal to a vote? I mean, let's finish the thread by tabling a motion for the board to vote on. I am not sure if my wording is good enough, I would prefer if someone could help out.
Yes, I would certainly like to know who voted what afterwards. :-)
Answering your question with a question - why should this be something the Board decide on? should we instead consider this as a Membership vote?
instead of volumous almost answers, do it and stop talking about it. bring the matter to a vote. and probably the vote should be by the Membership as it will define actions expected from those who that same Membership ultimately elects.
asking for a close of debate and:
I hereby move for a vote by the Membership to mandate a public record of the comitteemenbers vote for, against or abstention of, for $SUBJECT, to be included in the minutes. a reason for the particular vote would be welcome but not mandatory. note that private matters as those of a particularly personal matter or of non-disclosure type would be considered outside this direction.
call for seconds
I would argue that to start doing this outside of exceptional circumstances is changing the role of the board and if most members of the community actually want this they should write a clear proposal for changing the function [1] of the board as to when they should be responsible for voting and when they should put the vote to the members, if you can't clearly articulate this then how do you expect the board to? once you have written such a proposal you can then call for a vote of all members on the change to the role of the board practically it might make sense to hold such a vote at the same time as the next election. Personally i'd strongly advocate for not making this change due to reasons already outlined in this thread. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B