@kevin Also, now that I've outed myself that I have an EV, I have to test the offer for source that I got. I suspect sadly that it will fail with offer-fail or incomplete-CCS.

Admittedly, I tend to wait until the two-year mark to test offers both because I'm busy, but also because offers *must* be valid for 3 years under the v2 group of GPL Agreements, and as long as parts are available under v3.

Nevertheless, I urge everyone else to test your offers, or upload them to https://sfconservancy.org/usethesource

@kevin I get the joke, but I'm actually baffled by this feature altogether. The vehicle I drive has this feature as well, and it seems a safety concern to me. There are safety moments where quick acceleration beyond speed limit rather than braking are necessary to avoid collision.

I always drive the speed limit myself except in emergency, & think the audible & visual warning when you exceed the speed limit make much more sense for safety.

I signed for petition asking OSI to publish the "complete, unaltered" results of the board of directors election. Please sign after reading the story. OSI excluded all votes for three candidates before publishing election results.

Story on LWN: https://lwn.net/Articles/1019215/

Some OSI Affiliate Members such as GNOME Foundation, Open Source Hong Kong, and few former OSI Presidents, board members, and some developers also signed.

Thanks for eventually correcting the misstatements. The public apology I asked for, though – 42 days ago – was an apology that @osi had *made* the statements, which you agree were incorrect.

After weeks of private negotiations where you made it clear an actual apology for the statements themselves was off the table, & today's new mistake, it seems you still aren't offering that apology?

No matter – all can be forgiven if you just do what so many people asked you to do:
https://codeberg.org/OSI-Concerns/election-results-2025

Thanks for eventually correcting the misstatements. The public apology I asked for, though – 42 days ago – was an apology that @osi had *made* the statements, which you agree were incorrect.

After weeks of private negotiations where you made it clear an actual apology for the statements themselves was off the table, & today's new mistake, it seems you still aren't offering that apology?

No matter – all can be forgiven if you just do what so many people asked you to do:
https://codeberg.org/OSI-Concerns/election-results-2025

All in #OpenSource & #FreeSoftware pls read @Diziet's blog re: politics:
https://diziet.dreamwidth.org/19879.html
Circa 2001-03, someone first called me a “Free Software politician”; I was then offended but by 2012 had decided my memoirs, when I write them, will be titled “The Accidental Politician”.
Stable, predictable governance bureaucracy & political norms/decorum are essential. It's being lost in both global politics & FOSS politics rn.
#OSI election debacle is an example of latter: https://codeberg.org/OSI-Concerns/election-results-2025

@jxself

There are so many spoofs in that movie that are lost on folks who didn't fly before 2001-09-11, including the zone thing.

Now it's just signs that say no stopping $500 fine in all places and lax enforcement.

And cell phone lots.

I had to spend 5 minutes once explaining to a Zoomer that people used to have free speech in airports like any public place which is premise of joke in scene that follows.

In other news, we are getting old, my friend.

Which of these organizations do you have a positive opinion of?

#poll #FLOSS #FreeSoftware #OpenSource #PublicGoods #Mozilla #Firefox

@brouhaha
😢 … I'll take it as a note that over at my day job at @conservancy we've *gotta* improve our outreach!

BTW, SFC is hoping to run even more AMA-style video chat sessions for SFC Sustainers this year (we typically do at least 3 a year, but hoping to do more):
https://sfconservancy.org/sustainer/

I can say as an SFC staffer that we definitely want to help folks form an opinion about us and our work — and everyone there is open-minded to dissent & disagreement from community.

Cc: @ygor

In bilateral negotiations, both sides made compromises for text we all agreed clarified the misstatements while honoring @osi's political goals (e.g., to never say my or @richardfontana's name on their blog).

Such negotiation & abiding by its outcomes in good faith are central to unity among disagreeing #FOSS factions.

I've done ≥ 100 of these kinds of negotiated public statements w/ other #OpenSource leaders in my 25 year career.

This marks first time someone reneged without even a warning!

Here's the actual text we bilaterally negotiated w/ #OSI
> “In other venues, OSI inadvertently called the board agreement the board code of conduct. The board agreement governs our conduct as directors expected of leaders at OSI above and beyond, and the OSI code of conducts (License Review CoC, Event CoC, Discourse TOC) govern our whole community. To our knowledge, all involved with this election, even those who did not sign our board agreement, agreed to be held to the OSI code of conduct(s)”

I appreciate @ed deleted post falsely claiming @richardfontana & I “refused to sign OSI's Code of Conduct” & that #OpenSource Initiative posted our privately negotiated correction for similar misstatements…
https://opensource.org/blog/announcing-the-new-directors-of-osi-board#:~:text=agreed%20to%20be%20held%20to%20the%20OSI%20Code%20of%20Conduct
… 'tho my gratitude is abated b/c despite weeks of bilateral negotiations by email, OSI tried to unilaterally change the agreed statement (screenshot).
https://floss.social/@bkuhn/114438544297568433 has more.

NB: the Candidate Agreement didn't exist until last week (a month after election).

@neptune22222 I shouldan give the number in years in hex so I don't expose I'm *that* old.

So, I've been using Emacs 0x22 years and 0x33 years old myself.

Also, I admit I used 'bc'' to verify those amounts, by typing ibase=16 to check my numbers and then stupidly said ibase=10 instead of ibase=A to change back to decimal. 🤦

Like when I tried to run a poker game w/ chips denominated in powers of 2: in the end, humans are genetically decimal & binary, octal, & hex will eventually trick you.

@jbqueru @bekit

😊

@bkuhn @bekit This is a wonderful recommendation. It's highly practical, and at the same time it doesn't require to redefine everything that we currently know about FOSS.

I appreciate that you chimed in from a position of experience and expertise. Your work helps relative noobs like me make informed decisions. In my case, I think this'll continue to mean AGPLv3+.

@markgalassi

It's even a more complex story than that: Software in the Public Interest tried to trademark "open source", failed, Bruce Perens and ESR got into a big argument (semi-public), which they apparently resolved, and then by the time it was all sorted out, the SPI application had missed deadlines and everyone got worried it was a generic term already (which it probably was from the beginning, given the common journalist use of the term).

@zacchiro

@neptune22222 obviously but it still would be nice to allowed to make any string an abbrev. Mainly, the thing was that after 34 years of using the same program for 50-80% of my work (depending on the day), it's rare that its behavior can surprise me as it did today.

Forgive the anthropomorphization, but I have been in a very long relationship with Emacs and I thought I knew it better than this.

@smlckz Very kind of you. I truly wasn't pulling a “hey, would you UTSL for me” — I just had planned to do it later and thought the comment was a funny anecdote.

Still, this may or may not be the best way to implement abbrevs in the first place, but I see why it was done this way for convenience given that you can just overlay the relevant abbrev table on top of the syntax table for any any given mode.

I've used Emacs almost every day of my life since 1991-08, so how in the 🤬 did I never know that apparently abbrevs must match /[0-9A-Za-z]+/ ?

Use case: I type Unicode chars quickly with abbrevs that are “the thing w/ ‘y’ on the end” — e.g.: I write “🤬” by typing “cursey”.

I wanted “<=y” to yield “≤”. As Hall & Oates told me in song when I was a child:

🎶 No can do! 🎶

I haven't dug into manuals nor UTSL'd yet, but this has gotta be a legacy restriction that serves no purpose now, right? 🤔

I've spent the plurality of my career enforcing copylefts such as #GPL

I apologize; this sounds arrogant, but:

I know more about methods, efficacy, & options for enforcing #copyleft terms than anyone else.

I'm absolutely sure a copyleft-style clause (like that in the so-called
“Hippocratic License”) would never curtail immoral behavior in use of software if that behavior doesn't relate to software itself (i.e.,copying, modifying,redistributing,reinstalling, deploying).

Cc: @jbqueru @bekit