4 ms·

wow good catch, thanks, just fixed it! Is your concern more ideologically or are you worried about actually getting in trouble for using it? happy to assuage

by sawka 5y ago

wow good catch, thanks, just fixed it! Is your concern more ideologically or are you worried about actually getting in trouble for using it? happy to assuage your fears if it is the latter.

notRobot 5y ago
It's both, honestly. (1) I can't incorporate Hibiki into anything (A)GPL licensed, which many of my projects are. (2) Ideologically I can't get behind something non-free, even though I completely understand why you wrote the license the way that you did. Realistically all it's going to do is hinder adoption (see parent comment of mine). (3) You can say I'm not going to get into trouble, but your license says otherwise, and I really can't use something unless I'm 100% sure I'll be in the okay, ya'know?
- sawka 5y ago
  Fair enough. I realize the AGPL integration is a deal breaker. For point 3, true, which is why I could offer a proprietary license that does say you'd be 100% okay (although it still wouldn't work for point 1).
  - notRobot 5y ago
    The problem is -- everything that I write is FOSS! So I can neither use your current license, nor a proprietary license I purchase from you! I am happy to pay for a FOSS license, but obviously that will then allow other people to use the code without paying for it, because of the nature of FOSS.
  - learc83 5y ago
    Don’t try to please everyone. If someone is a FOSS purist, they aren’t going to accept a license with any of the restrictions that prevent companies from offering a hosted service.
dec0dedab0de 5y ago
I think you should just avoid associating your project with open source or free software. It comes off bad when you see it's not really. Just make the license free to use except for a saas. And you'll accomplish what you want without being misleading.
- sawka 5y ago
  Okay, I'll definitely consider that -- didn't mean to be misleading. I really intended that the license should not be encumbering for 99% of use cases. I'm actually happy if SaaS companies use the product for dashboards, configuration screens, or admin tools, etc. I just don't want them offering a service that allows 3rd parties to write and host Hibiki code. The intent was that if you're at a company and write Hibiki code, you're all good, no problem. If you're at a company and you're offering a service which lets your customers write Hibiki code that you then host, then that's no good.
  - andybak 5y ago
    Use an existing, well understood licence or else most people with even a half decent understanding of software licenses will run a mile.
    - gjs278 5y ago
rglullis 5y ago
What is the problem with the AGPL?

by sawka 5y ago

wow good catch, thanks, just fixed it! Is your concern more ideologically or are you worried about actually getting in trouble for using it? happy to assuage your fears if it is the latter.

notRobot 5y ago

It's both, honestly. (1) I can't incorporate Hibiki into anything (A)GPL licensed, which many of my projects are. (2) Ideologically I can't get behind something non-free, even though I completely understand why you wrote the license the way that you did. Realistically all it's going to do is hinder adoption (see parent comment of mine). (3) You can say I'm not going to get into trouble, but your license says otherwise, and I really can't use something unless I'm 100% sure I'll be in the okay, ya'know?

sawka 5y ago
Fair enough. I realize the AGPL integration is a deal breaker. For point 3, true, which is why I could offer a proprietary license that does say you'd be 100% okay (although it still wouldn't work for point 1).
- notRobot 5y ago
  The problem is -- everything that I write is FOSS! So I can neither use your current license, nor a proprietary license I purchase from you! I am happy to pay for a FOSS license, but obviously that will then allow other people to use the code without paying for it, because of the nature of FOSS.
- learc83 5y ago
  Don’t try to please everyone. If someone is a FOSS purist, they aren’t going to accept a license with any of the restrictions that prevent companies from offering a hosted service.

dec0dedab0de 5y ago

I think you should just avoid associating your project with open source or free software. It comes off bad when you see it's not really. Just make the license free to use except for a saas. And you'll accomplish what you want without being misleading.

sawka 5y ago
Okay, I'll definitely consider that -- didn't mean to be misleading. I really intended that the license should not be encumbering for 99% of use cases. I'm actually happy if SaaS companies use the product for dashboards, configuration screens, or admin tools, etc. I just don't want them offering a service that allows 3rd parties to write and host Hibiki code. The intent was that if you're at a company and write Hibiki code, you're all good, no problem. If you're at a company and you're offering a service which lets your customers write Hibiki code that you then host, then that's no good.
- andybak 5y ago
  Use an existing, well understood licence or else most people with even a half decent understanding of software licenses will run a mile.
  - gjs278 5y ago

rglullis 5y ago

What is the problem with the AGPL?