3 ms·
MIT might be a bit too strong of a switch for the author, but I think there is a better compromise than the AGPL. The AGPL has some worrying clauses in it that
by WorldMaker 10y ago
MIT might be a bit too strong of a switch for the author, but I think there is a better compromise than the AGPL. The AGPL has some worrying clauses in it that make it the actual legal nightmare that people used to paint the GPL with. I realize that may be the intention of the project author, but it does severely limit even other open source developers' willingness to touch the project with a ten foot pole.
I think a standard GPL license would be an improvement that would keep the intention and avoid some of the larger headaches of the Affero version.
Looks like Dokany is already LGPL/MIT-dual licensed though, so probably would just use that if I were building in this space: https://github.com/dokan-dev/dokany https://github.com/dokan-dev/dokany
- billziss 10y agoSome good points here. I admit that I do not fully understand all consequences of licensing this under the AGPL vs the GPL (and I mean social rather than legal). On the question of why AGPL/GPL and not a more free license like BSD: when I started out the project my intention was to place it under a BSD license. But after working on it for 4-5 months and writing about 25-30 KLOC, with much of it being kernel-mode code I had to reexamine the licensing decision. I did not want to go back on my decision to open source the project, but I also felt that I should see something out of all this hard work (believe me when I say that Windows kernel mode is not fun). Bill Zissimopoulos