Notices by Stefano Maffulli (ed@social.opensource.org)

Attend OSI’s town hall on May 21st at 11:30am Eastern Time and other events from Maintainer Month. https://opensource.org/blog/may-is-maintainer-month-celebrating-those-who-secure-open-source #OpenSource

Reprehensible behavior.

@webmink https://meshed.cloud/@webmink/114403402649782407

@kevin Two people decided not to agree to the board agreement, they excluded themselves, a third missed the deadline by hours. You be the judge of their behavior.

And yes, there were bumps. That's why `The board has directed the Board Development committee to run a retrospective by April 19, 2025 and bring to the board any recommendations for the future.`

@jwildeboer

@edodusi The AGPL and the GNU Manifesto are different things, I don't see how one could be the evolution of the other. I'm not afraid of challenging the GNU Manifesto (I have a track record of doing that :)) I did that recently to see if it is still valid in the era of ChatGPT, read https://opensource.org/blog/open-source-ai-establishing-a-common-ground (TLDR: The principles still hold true today)

In an increasingly complex digital world, having access to reliable Open Source expertise is crucial. https://opensource.org/blog/your-support-our-focus-the-osis-2025-roadmap-to-a-stronger-open-source-ecosystem #OpenSource

@evan Concern trolling is still trolling, right? :)

@jwildeboer I like what you did here :) On the positive thread I offer OSI roadmap, which includes hard projects asked by many people https://opensource.org/blog/your-support-our-focus-the-osis-2025-roadmap-to-a-stronger-open-source-ecosystem
@mccoysmith @suehle @carlopiana

@jwildeboer what do you mean it didn't go well? @mccoysmith @suehle @carlopiana are a impressive talents I'm sure they'll be great directors who will help the organization continue to grow

@kevin Two people decided not to agree to the board code of conduct, they excluded themselves, a third missed the deadline by hours. You be the judge of their behavior.

And yes, there were bumps. That's why `The board has directed the Board Development committee to run a retrospective by April 19, 2025 and bring to the board any recommendations for the future.`

@jwildeboer

Announcing the new directors of OSI board https://opensource.org/blog/announcing-the-new-directors-of-osi-board #OpenSource

@bkuhn @jwildeboer @osi @larsmb @downey The agreement you and @richardfontana signed was not the one the board sent you and, most importantly, is not the one everyone else (candidates and sitting directors) signed.
This is my last message on the topic.

@mattl point taken, we have to be better and take better care of the website.
For the elections, Matt: are you a paying supporter? If so, you should have received a ballot and 4 reminders to vote.
@ehashman

Go ask questions to the candidates of @osi elections on the forum https://discuss.opensource.org/t/a-vision-for-osis-future/846

https://mastodon.uno/@carlopiana/114098096710309440

@dalias that's the spirit! Burn everything down! Let's all go use ... pen, paper and flying pigeons, like in the old days https://en.wikipedia.org/wiki/IP_over_Avian_Carriers

I'm curious: How many of the people who complain about #Mozilla ToS pay for Firefox? What's the ratio between overall users and small donors?

@lxo I still can't see why that'd be considered a violation of the OSD and not a license violation... I wasn't at the OSI at the time, I was on the FSFE board (or about to join it, I don't remember the exact dates). Worth discussing it over beers :)

@lxo I'm confused. Are you talking about GPL violations according to the interpretation of the FSF?

@lxo "a couple of years before OSI was founded", you wrote?

The licenses of Llama and Deepseek contain clear violations of the Open Source Definition, these things are *not* Open Source at a more fundamental level.

The new Open Source AI Definition doesn't even kick in.

So much noise and disinformation.

@dalias it's a shame that a company is called Open something and has nothing to do with that name.