gnuplot surprisingly also has a strange license, containing “Permission to modify the software is granted, but not the right to distribute the complete modified source code.”

How do you decide what to archive, and what is the long term plan? If Annas goes down it can be pieced together again? Or is it served to users now too?

The archive team sounds interesting!

What can an ordinary user do at this point that would help?

Norway is a rich country so the government can help people buy electric instead of gasoline cars. Of course, they got rich by selling oil, but yes.

“The discussion continued for quite a while without making much headway.”

I think Debian is interesting, being such a large project of collaboration. I want this democratic, volunteer, non-corporate backed, free project to show that 10000 eyes make bugs shallow. I wish this model produced new ways of doing things, bringing people together in the spirit of creativity and playful productivity.
I’ve used Debian in different ways for around 15 years now, and I really want it to succeed.
Having said that, there is a “but…” looming in the back of my mind. But… it’s difficult to ignore that other distributions are the ones pushing Linux forward. The innovation from Fedora and the distributions still called OpenSuse explore new areas which become the standards.
This is not criticism of Debian, I just wonder if we humans are capable of collaborating freely at that level without some top-down force directing work forward, or if we are bound to being one step behind, always trying to catch up to what others have already done?

https://wiki.debian.org/DontBreakDebian#Don.27t_make_a_FrankenDebian

What about the proposal to just drop the name openSUSE with no replacement? And let each distro just be called Tumbleweed, Leap, Aeon, etc.

Unicode in filenames can be a bad idea, since there are more than one way to achieve what looks like the same character. So matching patterns could fail if you think it’s one way, but it’s actually another representation in unicode.

In recent turn of events, openSUSE Aeon will probably just be Aeon, and the name openSUSE will disappear everywhere.

What started as openSUSE Micro Desktop is now openSUSE Aeon. It’s still RC2, and RC3 will probably be easier to do a clean install since it will add full disk encryption, but if you want to check it out now it’s reliable and works well.

I understand, and it’s a great thing that we all can decide our experience. About the maker community, I guess the other option is to just create it and see what happens. If beehaw is defederated with many other instances, it would limit potential spread (again, this might be a desired outcome), but maybe it would fit in here: https://discuss.tchncs.de/communities or a similar instance?
I would be interested in a maker community, right now I’m subscribed to various niche ones like lasercutting, microcontroller, etc.

Oh, bummer.

There’s !makerstuff@lemmy.world with 400 subscribers, and not much action. But if you start adding more posts, maybe others will too.

People seem to think that those who choose permissive licences don’t know what they’re doing. Software can be a gift to the world with no strings attached. A company “taking” your code is never taking it away from you, you still have all the code you wrote. Some people want this. MIT is not an incomplete GPL, it has its own reasons.

For example, OpenBSD has as a project goal: “We want to make available source code that anyone can use for ANY PURPOSE, with no restrictions. We strive to make our software robust and secure, and encourage companies to use whichever pieces they want to.”

If you don’t want to touch anything, you could boot from a live USB image and try it?

I wonder how much work would be needed to make a “FreeDesktop Linux” complete OS, with the runtime + whatever it needs beyond that. Then when you install a flatpak, it’s just like installing, uh, I didn’t think this through tbh.

PC-DOS on an IBM 5150 (iirc).

There’s a difference between stability and reliability. Stable means that functionality is the same over a period of time, no major changes to how it works. Reliable means that it doesn’t crash all the time. If something crashes the same way for the same reason, it’s stable but not reliable. If something changes a lot but doesn’t crash, it’s reliable but not stable.
In practice what it comes down to is a choice if you want outdated but known bugs or new surprise bugs.

You are more than welcome to remove the need for any passwords at all on the linux systems you admin. Good thing about free software is that you decide how you want it, hack up or put up.