4 ms·
> So the maintainers should be legally required to maintain the software, for free, forever, just because you depend on it? That is an insane level of entitleme
by ChrisMarshallNY 4y ago
> So the maintainers should be legally required to maintain the software, for free, forever, just because you depend on it? That is an insane level of entitlement.
I didn’t get that, at all, from the GP. They just said that it’s not (in their opinion) fair to build up a user base that becomes dependent, then use that dependency as leverage.
That’s basically the Sackler Family method.
I release a bunch of code, as MIT. If someone wants to use it, fork it, sell it, whatever. Just don’t expect me to be on the hook for maintaining it, or guaranteeing it.
If I want to drastically change it, or even do something evil, like have it phone home, I could do that (I won’t). I could also change the license, going forward, as these folks did.
I’m under no obligation to maintain my stuff for any reason, other than I use it, myself, so I want it to be good.
That said, I consider myself to be an excellent steward, of really good software, that no one (except Yours Truly) uses. That’s fine with me, but I take great care of my stuff, anyway.
If I sign a contract, then that’s a different matter.
- croes 4y agoWhat percentage of the user base is really affected by the license change?
- knocte 4y ago> They just said that it’s not (in their opinion) fair to build up a user base that becomes dependent, then use that dependency as leverage. And saying this doesn't make any sense. Because being opensource means lack of vendor lock-in. There's no "dependency". As soon as a new license is adopted, the users of the previous version can still use that previous version because it is still opensource, and create a fork out of it.
- naasking 4y ago> As soon as a new license is adopted, the users of the previous version can still use that previous version Can they technically? If nobody stored a copy of the code, and the copyright owner decides to change the license, any subsequent copies are under the terms of the new license no?
- croes 4y agoThey can still use the library and even decompile it if necessary.
- ChrisMarshallNY 4y agoIf I use a service like GitHub, then it’s child’s play to get previous versions. But that’s beside the point. If someone releases software without storing the whole build in configuration management, then I don’t feel particularly sorry for them.
- naasking 4y ago> If I use a service like GitHub, then it’s child’s play to get previous versions. And they could delete the repository. Even if they had a repository, as the copyright holders they could change the license retroactively. This is not a problem with a technical solution that I can see.
- ChrisMarshallNY 4y ago> as the copyright holders they could change the license retroactively I hope they have very good lawyers, then. I'm not sure how they could enforce that. > And they could delete the repository. That's why I said what I said about configuration management. I guess CM is no longer en vogue, these days. A main goal of CM, is to completely reproduce the build, from stored components, at any point in the product lifecyle. With a lot of SaaS services, I guess that it's not really possible to do that, anymore, but I'd be pretty leery of basing a business on ephemeral resources. I'd at least get a maintenance or local duplication contract with the author.
- naasking 4y ago> I hope they have very good lawyers, then. I'm not sure how they could enforce that. Why? Like I said, unless someone has a copy obtained with the original license, then any subsequent copies are accepted with the new license. There's nothing in the law that says the copyright holder can't change the license.
- californical 4y agoHow is that any different from a major open source maintainer deciding to quit the project and leave it out of date? It’s an identical outcome for the end user of the OSS. You wouldn’t demand that someone continues development of the project for free right? So they can either leave the project to rot, which seems morally fine to everyone, or they just also decided to start charging money for future updates.
- deleted 4y ago[deleted]
- fsckboy 4y agoyou're leaving out that your GP said there should be criminal liability on the author of the software if they change their license
- ChrisMarshallNY 4y agoNo. It just wasn’t really relevant to the argument that I should be forced to maintain something I wrote. I disagree with the “criminal liability” thing. I understand why someone might feel that way, as many folks write software as “dependency aggregates,” but that’s a whole other argument, and I already know my opinions on that matter aren’t particularly welcome.