> Oh absolutely, dual licensing would be the best way to go. (L)GPL is certainly not the way to go to if OpenPGP.js should > be implemented in commercial applications, due to its way too restrictive nature. > So either drop (L)GPL all together or provide dual licensing.
As far as I understand a large part of the work was done by the guys at recurity with gpg4browsers. What do you think Carsten... would dual licensing be an acceptable option? I would totally understand if that solution didn't fit to the culture of the project. The reason I ask is I don't know which direction safewith.memight go and that could be a relevant factor for future development. Tankred
_______________________________________________ http://openpgpjs.org
