OSS license for Wire
Danthar opened this issue · comments
Hi @rogeralsing ,
It seems you removed the Apache license from the project. Im inquiring because i would like to know what License you plan to change it to.
The legal department of the company i work for does not allow me to use an OSS project with no license (and some are prohibited outright). So please let me / the community know what your plans are regarding this topic, so I / we can plan accordingly.
Also I can imagine some users who are using Wire with Akka.Net and are using it for persistence would be very interested as well. If they find themselves in the position that they are no longer allowed to use Wire due to License issues, they would possibly have a rather nasty migration path ahead of them..
Also, why did you removed it in the first place ?
After investigating actual .Net serializer availabilities, I found that Wire gets absolutely the best score for its performance/serialized size/product integration aspects. Many thanks to @rogeralsing for the great product. I really enjoyed walking though its code and reading a story blog.
... but GPLv3 makes it nearly impossible to use in non-OSS applications. It is a pity indeed, because Wire has a great potential to become a de-facto leader among .Net binary serializers as Newtonsoft.Json is now among JSON ones. But not with this type of license of course...
Just wondering if there is any chance to support dual licensing (e.g. MIT/GPL) as some other OSS libraries do?
Apache 2 license re-added.
We are likely adding Wire support in Proto.Actor soon and development will be resumed.