←back to thread

431 points dangle1 | 2 comments | | HN request time: 0.202s | source
Show context
sureIy ◴[] No.41861348[source]
I don't really understand why people complained.

The source is open, if don't want to contribute, don't. Just because something doesn't fit a specific definition it doesn't mean it's not worth of existence.

replies(3): >>41861433 #>>41861517 #>>41861792 #
belthesar ◴[] No.41861433[source]
The source wasn't open though, it was available, and it was provided in a sense that fully showcased that they did not understand what they were doing. Everything from licenses that were fully unenforceable and non-compliant with Github's license agreement to illegally distributing proprietary code to fundamentally misunderstanding how to use git.

It's one thing to provide a source available codebase. That's a choice, and it's fine for various definitions of fine. What they did was legally put themselves in hot water with the inclusion of proprietary dependencies, misrepresent what their intentions were, and likely irrevocably damage their reputation to a small, but vocal minority, who likely have a sizeable overlap with folks that know what Winamp is/was.

It's okay if none of that matters to you, or if it doesn't resonate with you, but the things that were done were comically awful in terms of sharing a codebase.

replies(4): >>41861568 #>>41861843 #>>41861869 #>>41862039 #
1. lukeschlather ◴[] No.41861568[source]
Describing this as "comically awful" seems strange. In terms of building a good open source project, they did a bad job. However they did a good job making the source available. Also given all the dependencies they may have (whether intentionally or not) followed the best path to make sure that the source would be useful. They ended up looking bad and exposing themselves to legal trouble, but I'm not sure this was awful, and they might even have known exactly what they were doing.
replies(2): >>41861750 #>>41862385 #
2. johnnyanmac ◴[] No.41862385[source]
Do people really not understand how bad this could be from a legal perspective. Licenses are a contract and they broke several contracts.

>They ended up looking bad and exposing themselves to legal trouble, but I'm not sure this was awful

For a company, I can't think of anything less awful than purposefully choosing to expose oneself to legal trouble. I'd say that qualifies as "comically awful".

>they might even have known exactly what they were doing.

In what way? Are they going bankrupt (so nothing to sue for) and just want to send out readable source on the way out, without enough care to strip out copyright and list dependencies? That's certainly a hail Mary, but I think that move does more damage to the community than goodwill.