←back to thread

My open source project was relicensed by a YC company [license updated]

(twitter.com)
932 points sohzm | 1 comments | 04 Jul 25 02:04 UTC | HN request time: 0.318s | source
Show context
JonChesterfield ◴[04 Jul 25 10:38 UTC] No.44463274[source]▶
"Fair enough. Since this was our first OSS project, we didn’t realize at first. We’ve now revised it. Thanks for your contribution."

We didn't notice that we copied your codebase, changed the name then pretended to have built it in four days?

Good grief.

replies(4): >>44463726 #>>44464302 #>>44464429 #>>44465698 #
gpderetta ◴[04 Jul 25 11:52 UTC] No.44463726[source]▶
"we are sorry we got caught"
replies(2): >>44463787 #>>44464227 #
reactordev ◴[04 Jul 25 12:03 UTC] No.44463787[source]▶
I would be running for the hills if I were YC. This is the kind of attitude that ends up in lawsuits.
replies(4): >>44463989 #>>44464390 #>>44464431 #>>44472783 #
gryfft ◴[04 Jul 25 12:38 UTC] No.44463989[source]▶
I thought tech companies were supposed to move fast and break stuff.
replies(2): >>44464096 #>>44470104 #
whilenot-dev ◴[04 Jul 25 12:54 UTC] No.44464096[source]▶
I think that phrase was coined in an era when the tech sector moved so fast that the prevailing law couldn't keep up. It caught up somewhat, but obviously there's still much leeway for improvement. Break all the wrong habits, rigid conventions and old traditions you want, just play along with the governing laws.
replies(3): >>44464196 #>>44464247 #>>44464896 #
1. avisser ◴[04 Jul 25 14:30 UTC] No.44464896[source]▶
IMO that phrase came about when old tech companies (the IBMs of the world) had

  * waterfall
  * design up-front
  * source control systems that
    * defaulted all files to read-only
    * required you to "check-out" files, potentially locking other devs out from editing them [1]
  * probably didn't have unit tests so "deploying to prod" meant "doing a full QA pass, done by human beings"
  * there was no CI/CD (We had "Build Engineers")
In this context, pushing a change to SVN/git/hg, having tests run automatically, then having CI/CD push new code to production, all as a side-effect of one engineer push a button? That was moving fast, and occasionally, breaking the whole website. But we got better tests, better CI/CD, metrics, green/blue, ... We learned it was unequivocally better than the old way.

[1] Reserved Checkouts: https://www.ibm.com/docs/en/clearcase/11.0.0?topic=ucm-check...