>>but it must maintain this code as open source with the same rights that you >>have to access and change it
Only if you are distributing the modified software. If you modify and only use it for your own purpose, you need not make it open source. Shibu Narayanan From: Sean Colyer [mailto:[email protected]] Sent: Tuesday, March 12, 2013 4:06 AM To: mrinal sharma; OpenPGP.js Mailing List Subject: Re: [openpgpjs] New modified openpgpjs repository Not entirely sure what the advantage of a creating another repository would be? Ideally you would make a "fork" on github and then bug fixes or enhancements could be pulled into the original fork for all to enjoy. We use GPL so you can create your own fork, but it must maintain this code as open source with the same rights that you have to access and change it. Does this help? Sean On Mon, Mar 11, 2013 at 4:55 PM, mrinal sharma <HYPERLINK "mailto:[email protected]"; \[email protected]> wrote: Hi All, I am planning to create a new opensource repository where I will add modified openpgpjs with some other tags and bug fixes which are currently not supported. I will be using the modified openpgpjs for encryption,decryption and signatures. I want to check with people in the mailing list, if by doing that will I break any license condition? This is my side project at this time. Your response is highly appreciated. Thanks, Mrinal _______________________________________________ http://openpgpjs.org
_______________________________________________ http://openpgpjs.org
