Skip to content

Comment on Chef dependency removed after agreement with ICEparent

Comments

I think it's reasonable whatever one's view. He made it. He can pull it. This is literally what this freedom is all about. I don't understand when the personal expression of developers of free software became constrained by some kind of nebulous corporate responsibility.

Sorry, I'm just a jaded old man pining for the old days of just throwing some code over the fence and letting folks use it.

Well he's hasn't climbed over the fence and taken it back. He just stopped throwing it over the fence on a continuous basis , right?

I suppose that would make it an empty gesture devoid of practical consequence then?

Looking through the commit history[0], he doesn't even look to be all that prolific as compared to other contributors. One would imagine those folks would keep on keeping on in some fashion.

[0] - https://gitlab.openminds.be/mirror/chef-sugar/commits/master

That "day" never really existed; you always own the consequences of your actions, even if you choose to pretend you don't.

Seth, to his credit, is doing what he can about his. Legally, there isn't much. But if a minor inconvenience--and it is minor because Chef is already busily scrubbing his name from "chef-sugar-ng", including removing him from the cookbook's authors, they can get their replacement just fine--alerts members of the Chef community to their ratshit behavior, that's a positive. Because some, who do not hold amorality as a virtue as is en vogue in these parts, will probably take exception to it, too, and they should know.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.