3 ms·
You just told the developer of a non-open source project to take your GPL code. That is a recipe for a copyright dispute.
by themerone 2y ago
You just told the developer of a non-open source project to take your GPL code. That is a recipe for a copyright dispute.
- dcminter 2y ago> the developer of a non-open source project The first line of the article says "We're building a new open-source CAD program"
- alright2565 2y agoIt's elastic license unfortunately: https://github.com/MattFerraro/CADmium/blob/main/LICENSE.md https://github.com/MattFerraro/CADmium/blob/main/LICENSE.md Which is a shame because the AGPL has nearly the same effect & the bonus of unjustifiably terrifying big-corp legal teams.
- marshray 2y agoOh, I guess I'm not touching it then.
- boarnoah 2y agoI'm confused, IIUC the AGPL can be simplified as "you can offer this software over the network, but like GPL the source must be available". Whereas Elastic license is about, "you must not deliver this software over the network as a cloud service". The things the Elastic license is trying to prevent seem very different to me?
- alright2565 2y agoIn effect, these are the same thing. If you try and deliver the software as a cloud service, you'll need to make the part that ties into your auth & observability stack, at the very least, open source. Cloud companies are unlikely to be comfortable doing that.
- phkahler 2y agoA comment on HN doesn't Trump the GPL on code mostly written by someone else. Also, they claimed to be open source even though they made a stupid license choice.