• 0 Posts
  • 15 Comments
Joined 2 years ago
cake
Cake day: June 2nd, 2023

help-circle





  • I don’t think either of these models can work. Fund-to-release is basically the same as crowdfunding, except painted as more focused. Now users, rather than “donate 5$ every month to fooProject” need to deal with a constant stream of “donate X$ to fooProject for Y feature / bug”, so it sharply increases subscription fatigue. I guess it wouldn’t be subscription fatigue then. Shopping fatigue?

    And what if bugfix X reaches 90% of the funding, and feature Y reaches 90% of the funding, but neither reaches 100%? With a simpler subscription the project would have a set amount of money to distribute across its internal needs.

    And this isn’t even touching on the subject of cost overruns. What happens when your feature estimated at 2 months of dev time is 60% done after 7 weeks? Do you ask for a second donation round?

    Rather, for this kind of focused work a project should keep one single treasury to distribute as needed, and have polls for contributors (monetary or otherwise) to vote on which parts to focus on first.

    The fund-to-release model shifts all the risk on the authors, who don’t see any monetary reward while the work is ongoing and are not guaranteed any even when the work is finished. Dev work needs a constant stream of funding (to eat, pay rent etc) unless the author starts with a sizeable initial treasury, in which case they can deal with big lump sumps to distribute as they need. But this requires at the very least the guarantee of payment once the work is done which, again, this model does not guarantee.

    Sorry I don’t have solutions to propose, but I think the flaws of these alternatives far outweigh their pros.



  • Why are you using networkd instead of networkmanager on a desktop?

    What a weird question. Networkd works anywhere systemd works, why whould desktops be any different.

    It’s the same as asking someone “why are you using systemd-boot instead of grub?” Because I like systemd boot better and it’s easier to configure. Same with networkd, configuration is stupid simple, I have installed it on my work machine even.

    As for op: since you can manually ping ip addresses and the issue seems to be time-based, could it be that your machine is somehow not renegotiating a dhcp lease?




  • That’s not how I read it at all

    By supporting work on a freelance basis for these topics, Valve enables us to work on them without being limited solely by the free time of our volunteers.

    Seems pretty explicit to me. Valve is allowing some arch linux contributors to work freelance for valve and get paid money to work on the things they would otherwise be working on for free. This allows these contributors to spend much more time working on these things because they can treat this work as the-thing-I-do-to-put-food-in-my-mouth rather than something extra they would do on the scraps of time they have on the side.


  • ugo@feddit.ittoLinux@lemmy.mlGoldilocks distro?
    link
    fedilink
    arrow-up
    6
    arrow-down
    1
    ·
    5 months ago

    +1. Arch is super easy to install, just open the install guide on the wiki and do what it says.

    It’s also really stable nowadays, I can’t actually remember the last time something broke.

    As a counterpoint, on ubuntu I constantly had weird issues where the system would change something apparently on its own. Like the key repeat resetting every so often (I mean multiple times an hour), weirdness with graphic drivers, and so on.

    That said, I also appreciate debian for server usage. Getting security updates only can be desirable for something that should be little more than an appliance. Doing a dist upgrade scares the shit out of me though, while on arch that’s not even close to a concern.



  • I think it’s possible that the filesystem ran out of inodes, so even though there is space on disk, there is no space in the filesystem metadata to store new files.

    Now, I don’t know off the top of my head how to check this, but I assume the answer is on the internet somewhere (am on phone and can’t help much more than this, sorry)



  • Reread the OP. They say:

    not on GNOME, because you have a panel at the top

    And

    when usign GTK apps on those [non-GNOME] desktops

    So you would not “access the controls above the app”, because having controls above the app is not covered by this scenario.

    The scenario is:

    1. You don’t have a top panel
    2. You have a maximized GTK app

    Which makes the close button be in the corner of the screen, but without actually extending to it.

    On topic: never knew this was a problem, guess I got spoiled by the Qt environment