Thanks for explaining. I think I will go with"fork". As long as all the changes
I make to the forked code and merge it to main, will I be able to use openpgps
in a pro-priority software?
Thanks,
Mrinal
________________________________
From: Sean Colyer <[email protected]>
To: mrinal sharma <[email protected]>; OpenPGP.js Mailing List
<[email protected]>
Sent: Monday, March 11, 2013 6:35 PM
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 <[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
