Migrated account from @CosmicTurtle@lemmy.world

  • 0 Posts
  • 36 Comments
Joined 1 year ago
cake
Cake day: April 9th, 2024

help-circle

  • This is essentially what Mozilla is doing but providing a legal framework for all open source projects.

    As an open source developer, my initial reaction is that this isn’t good. You’re just shifting the problem. Your code remains open source so if you have a python or JavaScript library that doesn’t require compiling, you can’t use this.

    Not only that, but FOSS requires you to provide build instructions for your binaries. Someone can clone your repository and run it through CI/CD and have a binary.

    I’m willing to be proven wrong here.

    I’ve seen only one method work well: strong copyleft FOSS licenses like AGPL that essentially make it impossible for a company like Amazon from profiting off your code without a separate agreement.

    You could add a non-commercial clause to your open source license. I can’t find the one that I used to use back in the day but essentially the goal is to augment whatever license you use by attaching a preamble that dictates how the software can be used.

    Attaching that clause does push the software out of FOSS and into source available since you are restricting who can use the software, which is why I stopped using it.

    Edit: found the clause I used to use back in the day. I don’t personally recommend it over more copy left licenses.











  • Also, make sure you have backups. I don’t care how stable NTFS drivers are I don’t fucking trust them for daily use, especially writes.

    I recommend copying files off of NTFS and onto ext4 if you’re able. If you can’t, try to keep operations to read only.

    I’ve lost too many drives due to stupid issues (sometimes me making an error, sometimes the driver not working properly).

    Backup:

    • 3 different locations
    • 2 different media formats
    • 1 offsite





  • Switching licenses to future versions doesn’t invalidate previous versions released under GPL.

    I’m not a lawyer but I deal with OSS licenses for work and I don’t know if there’s ever been a case like this, that I can think of anyway.

    Their previous versions, still being under the GPL, would require them to release a change to make it usable on desktops. Again, I’m not a lawyer here but there is a lot of case law behind the GPL and I think the user who made the issue could take them to court to force them to make the change if they don’t respond in 30 days.