2 ms·

Anyone know this hlky person and could get their take on this? The post seems to imply this person is a total d*k, but there’s always more than one side to the

• TAForObvReasons 3y ago
  When projects vendor or copy from other projects, license bodies typically include all relevant copyright statements and licenses even if the license body is the same as the parent project. NodeJS uses the MIT license [1] and reproduces the license for the MIT-licensed Acorn. OP stripped the copyright statement and license attribution without mentioning hlky or the originating project in the license file. OP proceeded to confuse matters by assuming that "AGPL" suffices. It seems like the copyright statement was the offense here. A simple email or github issue might have resolved the matter. Given the tenor of the relationship between the OP and hlky it should be no surprise that hlky opted for the "nuclear option" [1] https://github.com/nodejs/node/blob/main/LICENSE https://github.com/nodejs/node/blob/main/LICENSE
• thorum 3y ago
  hlky wrote most of the original code for the project, and might understandably think it’s “his” project. Setting aside whether his actions (which pissed everyone off and led to the code being rewritten from scratch without him under this new ‘hordelib’ package) were right or wrong, I can see how he would object to the other devs trying to remove his name from the license and basically pretend he doesn’t exist.