Hacker News Reader

Comment by abtinf | Hacker News Reader

Just out of curiosity: if the original project was open source, why did you decide to restart from scratch?

I actually tried really hard not to

sent 15 emails over 9 months to the new owner, offering to help or even take over the repo but i had no replies.

Issues and PRs were ignored(you juste have to see the issues section of the report). Rebuilding from scratch was the only way to fix the licensing & continue the project i guess

So why didn't you fork it?

And what specifically were the licensing issues? workout.lol is MIT from what I can see.

the code was indeed MIT.

The licensing issue I referred to was about the videos: many of them came from paid/licensed sources

I think the missing context here is what is meant by “fix the licensing”. Both the original project and this new one are MIT, so naively there doesn’t seem to be an issue.

just fork it?

the original project was built in javascript with a NoSQL backend (mongo).

I wanted to move to a more "new", (robust?) and maintainable stack with TypeScript and a SQL-based backend (PostgreSQL)

This makes a lot more sense and sounds like a good move for the overall health of the project.

Open source just means the source code is available. It doesn't mean you can legally use it. That is, in fact, the whole point behind the most famous open source license, GPLv3: code is open source, but there are still restrictions on how you can use the code. I don't know about now (most projects I work on are MIT-licensed, these days), but there was rancor around the move from v2 to v3 because v3 was more restrictive.

'source available' means the source code is available. Open source comes with a whole set of guarantees [1] about free redistribution and derived works.

Copyleft licenses like the GPL come with extra guarantees that do not violate the core guarantees of open source software. Instead, they make them stronger. The 'restrictions' GPL imposes essentially boil down to this: "if you use (parts of) GPL software, you must give your users the same freedoms the GPL guarantees." GPLv3 and AGPL closed up loopholes that allowed people to bypass those clauses.

[1] https://opensource.org/osd

Your link is to a politicized advocacy group, the OSI. Are you above, say, forty years old? You should remember, then, the arguments over introducing "libre" as a term because "open source" didn't describe those free redistribution rights.

Even if it was licensed under GPL, which it isn't, forking the project to create another open source project is allowed, as long as the fork is also GPL licensed.

But in this case the original project used the MIT license, so the only requirement is that it the form includes attribution to the original project.

Reply on news.ycombinator.com