I don’t think that’s quite right. The Linux kernel, Firefox and Chromium all sit around 30 millions lines of code, last I checked, so if you add the rest of the operating system, it should still have more lines of code than the browser.
But yes, similar order of magnitude.
Their point is that the maintainer did not sign a contract that requires them to perform maintainer duties. They can choose to stop doing it at any point. They can choose to axe a feature that you deem essential. They can choose to rewrite the project in COBOL for the fun of it.
You may not like it, but that is how it is.
The only legal document involved is the license and any open-source license I’ve seen so far, has stated that the program is provided as is.
This is the license under which rsync is provided: https://www.gnu.org/licenses/gpl-3.0.en.html
See sections 15 and 16.
The only way you get to have a say in the matter, is by forking and becoming a maintainer yourself.
Hmm, seems to work like you want for me. Using Plasma 6.6 with the icons-only task manager…
Coming at it from the Rust ecosystem, I’d primarily opt for uploading release binaries somewhere. You don’t particularly need a setup script, since Rust programs are generally self-contained.
Publishing a package in addition to that really isn’t hard, but would be my secondary choice, since users are not likely to have cargo on their system.
Well, and cargo compiles on the target machine, which is great for supporting unusual architectures, but you may have C libraries included where it’s just a gamble whether you can compile them on a given target system.
Should perhaps add that you can generally run Linux distributions off of a USB stick for that first impression.
Just follow a tutorial for how to install Linux and when you see the actual installer on screen, you can just close the installer without installing and then click around in the UI.
It will be slow, because it’s running off that slow USB connection, but otherwise this is pretty much the operating system as it is when fully installed.
Lots of folks also like the unmarketable names, because you know that it’s not a corporate project. You’re hearing about it, because it’s actually good, and not just because some startup got VC money to do marketing.
Heck, the reverse is true as well. This project is better specifically because it has that name. You just know some transfemmes are tirelessly hacking away at it, because they enjoy the silly name.
Alt+F3 can also work (possibly in addition to Alt+Space)…
Same. For whatever reason, I kind of hate all cursor themes. I disliked Breeze the least, then thought about how I’d want to change Breeze to improve it, realized that would look much worse, and since then I’ve been content with Breeze.
Always amused me that sudo !! is actually more keypresses (at least on keyboards where typing ! requires holding Shift).
@Dionysus@leminal.space found out that it’s a feature in fish shell, which I can confirm.
Same reason there’s a ScrollLock key on keyboards. Didn’t always have scrollbars and if the application prints more than you can read, you want to pause that…
Yeah, it comes from customizing cars and has a somewhat racist background, but many folks learn the word in the Linux communities and have no idea of any of that…
Falsche Community? 😅
Nah, you can have a license that says you get a cupcake and another license that says you need to give up your first-born.
And then you can mush those licenses to say that you need to give up your first-born, but you get a cupcake in return.
Unless the specific license terms contradict, this is totally possible.
AGPL is specifically for web services. For example, if Nextcloud were provided under the GPL, Amazon or the like could serve a modified version of Nextcloud without having to hand out their modifications. As far as the GPL is concerned, Amazon is the user and the software just happens to accept requests from the network.
With AGPL, those who use the software over the network are also deemed users and therefore have the right to access the source code.
I imagine, the scenario would be that the cloud service links against a library under the supposed new license.
And then, even if you’re just using the cloud service over the network, you can demand changes to the source code of that library to be open-sourced.
I imagine, it’s just too much of a niche and practically not enforceable anyways.
You would need to somehow know that a web service is a using a modified version of your library, then you’d be able to demand those library changes to be open-sourced.
And well, just in general, covering all kinds of niche use-cases isn’t terribly healthy for open-source licenses, because each modification is something that can be challenged in court and which might be incompatible with other licenses.
Ultimately, a library under such a specialty license would probably not see much use either. You could only really depend on it in AGPL applications. And at some point, you do have to ask yourself, if it’s even useful to develop your library then.
Had a refinement yesterday, where we decided that we should add all tickets of an epic individually into the milestone (except for two).
And for whatever reason, our project manager had decided to use the in-browser split view and was struggling against that, but also just was about to do it in some cumbersome way. I think, he wanted to manually compare the list of issues in the epic vs. the milestone.
Either way, I could tell that he’d need 10+ seconds to even get started. And telling him how to do it would probably take equally long. So, I just open each issue of the epic in a new tab and check on each tab that the issue is in the milestone or add it, then close the tab. And yep, I was long done when he was still trying to find the issue list for the milestone.
That was certainly one of those moments. 🫠
He isn’t entirely familiar with that issue tracking UI, so it’s fine, and of course, it is my job to be good with computers and all that, but still felt wild that he could’ve easily needed ten times as long to do the same thing.
Last week, some LLM bot commented under one of our issues and it became apparent pretty quickly, that it is a bot. So, I went to report it (incredibly the report menu did say they want reports for bots).
I filled out the reporting form probably five times in total, trying at different times of the day. Every time, I got an error 500 (Internal Server Error) as response.
Later, I checked my mails, and saw that actually two of my reports did go through, meaning I created two tickets on their side.
What those mails also said: They’re very sorry, if it takes longer, since they’re currently experiencing a higher number of reports.
Gee, I wonder why.
It was one of the stated goals for Servo itself to be designed like that. But I don’t think anyone at Mozilla expected Servo to take over from Gecko. They were already quite happy that they were able to incorporate Servo’s style engine and URL bar implementation and such into Gecko.