Hacker News Reader

Comment by deckar01 | Hacker News Reader

You might consider including the BSD licenses those projects were published under in your minified JavaScript file. Is this project's source code published anywhere?

View on HN

Thanks for the heads up. Our deploy process was stripping out all the attributions :(. This has been fixed and they are back in now. Regrettably the project's source is not currently available.

Awesome! Thanks for working on this project.

As someone who is not a developer and doesn't know that much about open source licenses, is this something you have to do? If I built something using React, I have to publish their license with my code? If I build something with Javascript, do I have to publish their license as well?

Do I have to tell everyone what technologies I've used to built my software, or...? That seems weird to me, but again I'm not a developer so I've never dealt with that. I've never released a license with my Bash scripts.

Attribution is the common requirement among most open source licenses [0]. Developers occasionally reference or link to the license, but the proper thing to do is to include the license in its entirety with the source code.

> I've never released a license with my Bash scripts.

You reserve all rights to your published works without stating otherwise. Developers would be wise to avoid redistributing unlicensed works without the written consent of the copyright holder(s).

[0] https://code.tutsplus.com/tutorials/open-source-101-licensin...

Reply on news.ycombinator.com