There's no "apolitical" projects. Claiming the contrary is just trying to hide your agenda. While our engineer culture keeps falling for it, really bad actors are benefiting from it...
Finally a sensible approach to communicate license compliance for client side content delivered via a browser. It's not too much of a bother so let's hope it gets picked up.
Clearly the situation of copyright around LLM uses is complex. It's easy to fall into code which can't be copyrighted if there's not enough human input to produce the work (and keep in mind that "prompting" is likely not enough input). This also raises questions about potential copyright violations. Looks like following the guidelines of the SFC for contributing to Free Software projects is getting especially important.
Interesting policy. I think it strikes a good balance.
Excellent piece. I'm feeling unease at this widespread confusion between european ownership and digital freedom. What we collectively need is the latter. There's no sovereignty to be had in a proprietary ecosystem, be it owned by an European company or not.
An illustration of the political and ethical acumen being low in our profession in general and in some (most?) Open Source projects in particular...
Really this kind of AI push is a bad move for employers, especially when interacting with FOSS communities so much. This forces people to pass the ethical issues onto volunteers...
Some news from the Apertus project, they released smaller models. Interesting work.
This is an interesting proposal, let's hope it gets picked up and appear in more licenses.
A very balanced set of recommendations from the SFC around LLM uses. It's just the beginning and still lacks a bit in details. It's very welcome though and I look forward to their updates.
Or why modern economics mostly loose the plot when you try to factor Open Source in there simplistic theories.
The latest move by the US government treating LLMs like dangerous weapons tells something about the geopolitical moment. Can we collectively raise to the challenge and build on cooperation instead? It'd be a much better position than assuming governments or big companies will make the right choices for everyone else in isolation.
In part useful, in part satire I think. Still it gives a good idea of various governance models in FOSS communities.
More an experiment than something I'd recommend for real. Still it shows there's a gap we need to close in the licenses available. Let's hope the OSI and the FSF will do strong moves toward closing this gap.
Not sure it warranted the "dumb" mention in the title. Still it's likely a good idea to have a list of the ways projects can die.
Weird decisions, this is really backwards...
Indeed, a reminder that the two concepts are not necessarily aligned. It kind of misses the point about corporate Open Source with no open contributions which can be easily captured as well. But indeed for the individual side project you might not need the whole burden of issues and contributions, you get to choose.
This piece is strongly worded but the logic is sound. We see many examples of power plays in guise of "innovation" which lead to killing openly sharing (and so killing real innovation). It's urgent to fight back and ensure things stay open.
It totally makes sense. If you're a FOSS project you have to invest in getting more long term contributors, which requires mentoring. The contributions themselves are not something to maximise. I wish more communities would follow that path.
Looks like some governments noticed that they can move away from GitHub and are testing the waters. Good idea!