Migrated account from @CosmicTurtle@lemmy.world

  • 1 Post
  • 35 Comments
Joined 8 months ago
cake
Cake day: April 9th, 2024

help-circle





  • 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.







  • The Winamp Collaborative License is a free, copyleft license for software and other kinds of works. It is designed to ensure that you have the freedom to use, Modify, and study the software, but with certain restrictions on the distribution of modifications to maintain the integrity and collaboration of the project.

    Oh god…

    No Distribution of Modified Versions: You may not distribute modified versions of the software, whether in source or binary form. No Forking: You may not create, maintain, or distribute a forked version of the software. Official Distribution: Only the maintainers of the official repository are allowed to distribute the software and its modifications.

    Copy left is not a protected term but yeah this is a shit license.

    And how the fuck do you contribute code back without forking the project?!

    EDIT: It looks like an issue has already been created and I absolutely love this thread where the license they are using is in violation of Github TOS.

    They should have just kept the source closed! The speculation is that whomever purchased it wants to crowdsource contributions without adding any value themselves.


  • I agree with this. Self-hosting requires the user to understand their network, their software, how it all interacts.

    If you provide a hardware product and call it a solution, people are going to expect a turn-key solution like a plug-and-play router.

    You’re going to end up supporting a bunch of newbies who, by no fault of their own, can’t tell you an error code in the console let alone whatever UI you give them.

    I think a better solution would be a course that walks newbies through self hosting.






  • I absolutely cannot stand this kind of logic.

    “We make a shit ton of money on this very critical piece of software!”

    “Then let me fix it!”

    “NO! It’s making us money NOW! It only stops making us money when it’s broken. At which point then we fix it.”

    “But that might be hours. We can minimize downtime if we plan properly.”

    "But it’s making us money NOW!1!1!”

    I shit you not I have had various versions of this conversation throughout my career, across industries, across disciplines.