- cross-posted to:
- technews@radiation.party
- cross-posted to:
- technews@radiation.party
HashiCorp recently changed Terraform from an open source model to something that requires licensing, so folks got together, forked the code, and created OpenTF.
HashiCorp recently changed Terraform from an open source model to something that requires licensing, so folks got together, forked the code, and created OpenTF.
That misses the point, imo. Much of Hashi’s ecosystem was created by people who contributed to the product believing it was community owned, as that’s what the license said.
Oracle tried to do similar when they closed the source for Hudson. Hudson was forked, creating Jenkins, and I would be surprised if folks even remember Hudson today.
Oxide Computing gets into the details on their podcast: https://youtu.be/QaU94LY891M
The OpenTF site itself provides a view on that point: https://opentf.org/#regular-user
And they’re right; while you might consider yourself compliant with today’s version of the license, they can change those terms whenever, and however they like in the future.
I weirdly do remember Hudson from my previous roles as a software developer, but like so many products forked that way it’s barely a footnote in history at this point.
So if there are many contributors to the code they are continuing to use, did they get agreement from all that they could close source? Or does the license not require that?
Well. I feel ignorant. Use Jenkins all the time, never heard of Hudson. Looks like I need to do some readin’.
But yeah, I’m guessing you’re right :)
Here is an alternative Piped link(s): https://piped.video/QaU94LY891M
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I’m open-source, check me out at GitHub.
I was wondering why their classes have Hudson in the package name. I just never bothered to look it up.