upstream license change

[0-8-15]

Maybe you want to follow the license change upstream zerotier underwent? Just for simplicity?

[gdamore]

Yikes. The BSL is pretty much completely incompatible with the license here -- such that their licensing has made this project incompatible.

libzt doesn't seem to have that problem, but the situation is far from obvious. I need to investigate.

I've been thinking to rewrite this code to make use of KCP anyway, and if I do that I will probably apply my own BSL, with identical terms. (As ZeroTier isn't sponsoring any of our work, commercial licenses for this library will need to be purchased from Staysail Systems, Inc. Don't work, we will charge less than you'd be paying ZeroTier, so it will become a small additional bump.)

[gdamore]

Actually, there is no code really here, and nothing that goes to customers. So for now there is no license conflict.

Having said that, I'll probably pull the ZeroTier transport out of NNG properly into a separate repo, like I have done for the wolfSSL plugin, and request commercial licensees pay Staysail. Again, it will be a small additional ask on top of what you'd be paying for ZeroTier in the first place.

[0-8-15]

On Sun, 01 Mar 2020 21:05:42 +0000 (UTC) gdamore ***@***.***> wrote: Actually, there is no code really here, and nothing that goes to customers. So for now there is no license conflict.

What's actually the bad thing about the BSL from your point of view?

Having said that, I'll probably pull the ZeroTier transport out of NNG properly into a separate repo, like I have done for the wolfSSL plugin, and request commercial licensees pay Staysail. Again, it will be a small additional ask on top of what you'd be paying for ZeroTier in the first place.

My $0.02: Looks like zerotier is now stable. In a way. They seem to be busy rewriting everything in Go. Support from zerotier seems unrealistic. Too many failed attempts here. As a potential customer they lost me already.