The voting for the Movement Charter Drafting Committee is now closed. We are truly grateful to all the voters who participated (despite the complexity of the voting procedure). We will look through the data this week and plan to announce the election results next Monday, November 1 2021.
Thank you for your kind attention! Kaarel
On Mon, Oct 25, 2021 at 12:01 PM Kaarel Vaidla kvaidla@wikimedia.org wrote:
This is a short note that *the elections of the Movement Charter Drafting Committee will close October 24, 23:59 Anywhere on Earth. This is in 3 hours*. If you have not voted yet, but would like to do so, here is the link to the landing page https://meta.wikimedia.org/wiki/Movement_Charter/Drafting_Committee/Elections .
Thank you for your kind attention and have a great week! Kaarel
On Wed, Oct 20, 2021 at 12:20 PM Dan Garry (Deskana) djgwiki@gmail.com wrote:
On Wed, 20 Oct 2021 at 10:10, Dan Garry (Deskana) djgwiki@gmail.com wrote:
You're definitely right about that. SecurePoll is a mess. I was the product lead for a project to improve it in 2014, and whilst we did manage to make quite a few improvements to the functionality and management, we only got a fraction done of what we wanted to, the tool is still sorely deficient. There's documentation about the project https://www.mediawiki.org/wiki/SecurePoll_2014_Redesign, if you're interested. I'm not surprised that WMF leadership is very reluctant to improve it, and if I were in their shoes, I'd be avoiding it, especially since none of the people involved in the 2014 project work at the WMF anymore.
I think we need to get over the "not invested here" https://en.wikipedia.org/wiki/Not_invented_here tendency when it comes to running elections, and research to see if there's a good third-party solution. I suspect we'd actually save money using a third-party solution compared to trying to improve SecurePoll. I've not done a competitive analysis, so I don't know what sorts of things are available, and maybe there aren't any. But, at least, we should look.
Or, scope out designing a lightweight tool hosted on Toolforge or similar infrastructure, that integrates with the wikis and other data sources via the API, rather than actually being a MediaWiki extension. So many of the things that SecurePoll does (voter eligibility list generation, authentication, vote collection and collation, etc.) can be done using API integrations or data dumps; there's nothing instrinsic to it that requires it to be a MediaWiki extension, it was only done that way because that's the way we did everything back when. Developing a tool like that on Toolforge is so much easier and less complex than developing a MediaWiki extension. There's so many successful examples of this way of doing things; pageviews.toolforge.org is a good example.
(Sorry for the follow-up email spam, the thought occurred to me as soon as I hit send.)
Dan _______________________________________________ Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/wiki/Wikimedia-l Public archives at https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/... To unsubscribe send an email to wikimedia-l-leave@lists.wikimedia.org
--
Kaarel Vaidla (he/him)
Movement Strategy https://meta.wikimedia.org/wiki/Strategy/2030
Wikimedia Foundation https://wikimediafoundation.org/