Good advice yes. Having a rough architecture document in a repository is more than welcome, it's needed to help on-boarding. This is unfortunately not the norm in FOSS projects.

Making sure maintainers are well paid is indeed an ongoing problem. There is currently no perfect solution within the world we live in. This is indeed no reason to blame the maintainers themselves for the approach they picked.

Good reminder that contributions are not only about code. Documentation, support, release management and so on are very important as well and too often underrated.

Looks like good progress has been made. A few more adjustments would be welcome before it gets ratified.

Very nice progress on this type of architecture. It's definitely needed in part because it lowers the inference cost quite a lot. It's also nice to see it released with under the Apache 2 license and the training set be documented.

Good exploration on how the total cost of ownership is spread depending on how is licensed the software you use and where you get your support from. I think there's one point a bit too glanced over in the analysis of the cost for the proprietary SaaS case: what's the cost of fixing a bug that affect your team? You might be a tiny fish in a large pond, good luck getting attention from support in this case.

Yes, there's something to do in this space. More funding is necessary, some form of platform might help... but it definitely won't be enough.

Very interesting ruling, this opens the door to more parties being able to sue to enforce the GPL not just the authors.

This is a stupid move on Unity's part... they're built on LGPL but ban others in their store to have LGPL dependencies. Shame on them. Good move from Videolabs though, wish them lots of success.

The current compromise might not be as bad as anticipated. Some things could be improved still. The community needs to be involved in the process.

Funny reverse engineering of the latest SteamOS to use it in a different context. Give some information on their system design.

Alright, it's 2024... Looking for a New Year Resolution? This is definitely the one you should contemplate! Maybe also prepare your switch to Plasma 6, but different story. 😉

A bit of an older article I'm bumping into again. It lays out fairly well the current limits and issues with Free Software as it is defined today. I'm unconvinced it can be solved via licenses but the debate needs to happen... I feel that somehow it's too much ignored.

Definitely the right move, more extensions are pouring in. People should benefit from them on Android as well.

Good news for the Godot Engine. Let's see where this goes in the coming years.

Very needed evangelization. Go forth and make apps for Linux!

Another important software release. Let's wish luck to the new maintainers!

Very interesting review, we can see some interesting strengths and weaknesses. Also gives a good idea of the different ways to evaluate such models.

Interesting food for thought. The later point about the tension between business and users lately is also a good one and should be kept in mind. That's an ethical concern you find most in companies publishing Free Software though. It's not the full packaged solution but a good starting point.

Interesting experiment. It makes for a very large file but there are a few clever tricks in there.