OpenSUSE board non-confidence effort fails

The openSUSE board troubles that LWN reported on in March have continued to simmer, and the promised election for an empty seat has not yet been held. During this time, instead, the project has voted on a petition to declare a lack of confidence in the board as a whole, a result that would have forced the election of an entirely new board. In the end, the number of votes fell far short of the number required, and the existing board will move forward with the election plan.

From:		Ariez Vachha - openSUSE <AJV-AT-opensuse.org>
To:		opensuse-project-AT-opensuse.org, board-AT-opensuse.org
Subject:		[opensuse-project] openSUSE Board - Non-Confidence Petition results
Date:		Wed, 15 Jul 2020 11:40:44 +0800
Message-ID:		<bb6bcbef-f71d-0382-2879-8dc75e33c326@opensuse.org>
Archive-link:		Article


The results of the  openSUSE Board - Non-Confidence Petition are as follows:

* Total number of eligible voters: 509
* Total number of votes recorded: 104
* Number of "Yes" votes recorded: 59
* Number of "Blank" votes recorded: 45
* Percentage of "Yes" votes: 11.6%

* Result insufficient support. - The petition requires over 20% of the
membership for to trigger an election of the whole board.

Details of the upcoming election for the unfilled board seats will be
published here in the next few days.

-- 
openSUSE Election Committee
election-officials@opensuse.org

-- 
To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org
To contact the owner, email: opensuse-project+owner@opensuse.org

OpenSUSE board non-confidence effort fails

Posted Jul 16, 2020 19:48 UTC (Thu) by salimma (subscriber, #34460) [Link] (6 responses)

small correction: the previous LWN report was in March, not May

OpenSUSE board non-confidence effort fails

Posted Jul 16, 2020 20:46 UTC (Thu) by ris (subscriber, #5) [Link] (5 responses)

You are correct. I have fixed it. Please, in the future, send an email to lwn@lwn.net so the comment stream doesn't get clogged with typos.
Thanks

OpenSUSE board non-confidence effort fails

Posted Jul 22, 2020 8:03 UTC (Wed) by job (guest, #670) [Link] (4 responses)

This is such a common occurrence that it might suggest a checkbox for "private comment to the editor" in the comment box could be helpful.

OpenSUSE board non-confidence effort fails

Posted Jul 28, 2020 10:49 UTC (Tue) by flussence (guest, #85566) [Link] (3 responses)

It'd probably work about as well as the prominent bold notice directly above the textbox.

Maybe it's the placement that causes people to totally ignore it?

OpenSUSE board non-confidence effort fails

Posted Jul 28, 2020 15:28 UTC (Tue) by mathstuf (subscriber, #69389) [Link]

This is the problem I've been fighting lately. In response to issues people raise that could be fixed with docs, I now ask "where did you look?". It's interesting to see how many say "nowhere" which only sometimes seems to cause some self-reflection on the core issue at hand.

OpenSUSE board non-confidence effort fails

Posted Jul 29, 2020 23:17 UTC (Wed) by neilbrown (subscriber, #359) [Link] (1 responses)

> Maybe it's the placement that causes people to totally ignore it?

That's my thought too.

I'd suggest replace the "Preview comment" button with two buttons.
"Report Typo" and "Preview comment".

Then when viewing the preview, have a "Report Typo" button that comes before the "Publish comment" button.

Maybe check the comment for a few keywords like "typo", and if present - move the "Publish comment" way over to the right.

Of course, then we'll get complaints about a "Nanny state" which treats us all like children.

OpenSUSE board non-confidence effort fails

Posted Aug 7, 2020 7:47 UTC (Fri) by flussence (guest, #85566) [Link]

Maybe moving the current message next to the "Preview" button would help? That's where the eyes are going to naturally follow using a mouse.

Take that with a grain of salt - I'm not a professional UX designer or psychologist (just aware that this stuff is subtle and hard in the same way as crypto).