Xentrk
Part of the Furniture
I have been revising my scripts that I use for Selective Routing on Asuswrt-Merlin and plan to post them on GitHub. I have been reading up on Open Source licenses. It seems the best choices come down to MIT vs GPL 2 vs GPL 3. I have posted snips of my code over time as the scripts have evolved. @Martineau was instrumental in helping me understand how Selective Routing works. @john9527, @RMerlin, @thelonelycoder and @Adamm have all offered input and suggestions or answered questions I had about the inner workings of the AsusWRT-Merlin and John's Fork. @Martineau provided his useful entware check function which I incorporated into the code. I greatly appreciated the collaboration. It has made the scripts much better and I have also learned in the process.
I want to continue the collaboration and provide the ability for others to offer suggestions for improvement or make changes. So with that information, what license do you recommend? There are many pages on the net discussing the pros and cons. Following is one summary from https://exygy.com/which-license-should-i-use-mit-vs-apache-vs-gpl/ for a comparison of the differences.
Thanks you for your input.
I want to continue the collaboration and provide the ability for others to offer suggestions for improvement or make changes. So with that information, what license do you recommend? There are many pages on the net discussing the pros and cons. Following is one summary from https://exygy.com/which-license-should-i-use-mit-vs-apache-vs-gpl/ for a comparison of the differences.
Another way of looking at it is that you’re picking a license based on what you are afraid of. All of these licenses assume you’re afraid of being sued. The MIT license is if you’re afraid no one will use your code; you’re making the licensing as short and non-intimidating as possible. The Apache License you are somewhat afraid of no one using your code, but you are also afraid of legal ambiguity and patent trolls. With the GPL licenses, you are afraid of someone else profiting from your work (and ambiguity, and patent trolls). This is a radical simplification, but if nothing else it can be a helpful framework in discussing with your attorney what license makes sense for your software.
Thanks you for your input.