Shared Platform for OSI Reform
Item 1. Repeal the Open Source AI Definition (OSAID)
Item 2. Adopt a process for formal review of previously approved licenses
Item 3. Remove “code of silence” from Board Member Agreement
Item 4. Directors should be allowed to use FOSS for Board activities
Which of these points are the OSI's current leadership so committed to blocking that they would make Luke's candidacy their hill to die on?
1. https://mas.to/@bkuhn@floss.social 2. https://codeberg.org/OSI-Reform-Platform/platform 3. https://ebb.org/bkuhn/blog/2025/02/28/osi-board-election.htm...
Details: https://openpath.quest/2025/luke-missed-the-memo/
---
Update from OSI: https://bsky.app/profile/opensource.org/post/3liz24zxtfk2i
OSI’s Continually Changing Election Story https://fossforce.com/2025/02/osis-changing-election-story/
It wouldn't matter anyway as they announced the deadline as 17 February, which would mean midnight local time by default (and should mean midnight AoE, especially for an organisations purporting to be concerned with openness).
But I also feel like if there’s no timezone for a deadline then you should assume the worst case (which here would be UTC) and make sure you submit before?
The author left it so late that in 95% of the world it was no longer the 17th Feb.
I agree with the author: the timezone of the organisation is what I'd expect.
The worst _reasonable_ case is UTC. Nobody is thinking UTC+14.
> I agree with the author: the timezone of the organisation is what I'd expect.
If the job was a local office job, I’d expect a local time zone. But the board of directors isn’t restricted to California or even the USA.
They should accept they made a mistake and accept the nomination.
You cannot assume a timezone. Especially as a computer programmer, we should know that. It was Feb 17 somewhere in the world until 12:00 Feb 18 UTC