License

Question

License

thomas-holmes opened this issue 7 years ago · comments

Can you please add a license to your repository? I need to fork it to make the RNGs serializable and I cannot do so legally unless it has been licensed under something that allows this modification.

Appreciate it!

Michael T Jones · Answer 1 · Mon Jan 22 2018 13:15:49 GMT+0800 (China Standard Time)

oh! sorry. good point. recommended choice?

…

On Sun, Jan 21, 2018 at 6:44 PM, Thomas Holmes ***@***.***> wrote: Can you please add a license to your repository? I need to fork it to make the RNGs serializable and I cannot do so legally unless it has been licensed under something that allows this modification. Appreciate it! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#3>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHgypZjqMB9BbdZtt2F9Cq_x2VMo2xJwks5tM_X6gaJpZM4RmGSy> .

-- Michael T. Jones michael.jones@gmail.com

Thomas Holmes · Answer 2 · Mon Jan 22 2018 13:21:54 GMT+0800 (China Standard Time)

A permissive license would be ideal, but I'm not entirely certain how exactly licensing works when you've essentially re-implemented (probably while referring to the code) other another copyrighted work.

The original PCG implementation http://www.pcg-random.org/ is Apache licensed so I imagine that is probably a safe choice.

Michael T Jones · Answer 3 · Mon Jan 22 2018 13:27:32 GMT+0800 (China Standard Time)

will do

…

On Sun, Jan 21, 2018 at 9:21 PM, Thomas Holmes ***@***.***> wrote: A permissive license would be ideal, but I'm not entirely certain how exactly licensing works when you've essentially re-implemented (probably while referring to the code) other another copyrighted work. The original PCG implementation http://www.pcg-random.org/ is Apache licensed so I imagine that is probably a safe choice. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHgypdv3aWYbHzsTgaqfEbV4qT_XDUinks5tNBrygaJpZM4RmGSy> .

-- Michael T. Jones michael.jones@gmail.com

Michael T Jones · Answer 4 · Mon Jan 22 2018 13:39:45 GMT+0800 (China Standard Time)

done. On Sun, Jan 21, 2018 at 9:27 PM, Michael Jones <michael.jones@gmail.com> wrote:

…

will do On Sun, Jan 21, 2018 at 9:21 PM, Thomas Holmes ***@***.***> wrote: > A permissive license would be ideal, but I'm not entirely certain how > exactly licensing works when you've essentially re-implemented (probably > while referring to the code) other another copyrighted work. > > The original PCG implementation http://www.pcg-random.org/ is Apache > licensed so I imagine that is probably a safe choice. > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <#3 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AHgypdv3aWYbHzsTgaqfEbV4qT_XDUinks5tNBrygaJpZM4RmGSy> > . > -- Michael T. Jones ***@***.***

-- Michael T. Jones michael.jones@gmail.com

Thomas Holmes · Answer 5 · Mon Jan 22 2018 13:50:07 GMT+0800 (China Standard Time)

Thanks! The convention is to add a file named LICENSE, which I think the github interface can help with that, but it's a bit awkward on a pre-existing repo.

https://github.com/thomas-holmes/gterm/community/license/new?branch=master&template=apache-2.0

Michael T Jones · Answer 6 · Mon Jan 22 2018 13:58:07 GMT+0800 (China Standard Time)

thank you for holding my hand here on the license issue. doing this from bed...nighttime...happy to help...advice most beneficial

…

On Sun, Jan 21, 2018 at 9:50 PM, Thomas Holmes ***@***.***> wrote: Thanks! The convention is to add a file named LICENSE, which I think the github interface can help with that, but it's a bit awkward on a pre-existing repo. https://github.com/thomas-holmes/gterm/community/ license/new?branch=master&template=apache-2.0 — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHgypSKgsihZbeKtplWUONmaDTG4QzCFks5tNCGPgaJpZM4RmGSy> .

-- Michael T. Jones michael.jones@gmail.com

Thomas Holmes · Answer 7 · Mon Jan 22 2018 14:00:57 GMT+0800 (China Standard Time)

Haha. Thanks for addressing it so promptly and thank you for the clean pure go implementation. It's been quite useful to me :)

Have a good one!

Michael T Jones · Answer 8 · Mon Jan 22 2018 20:33:25 GMT+0800 (China Standard Time)

Great! delighted!

…

On Sun, Jan 21, 2018 at 10:00 PM, Thomas Holmes ***@***.***> wrote: Haha. Thanks for addressing it so promptly and thank you for the clean pure go implementation. It's been quite useful to me :) Have a good one! — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHgypYclHbJmdurDrpSK3KCYr_OJlz4Iks5tNCQZgaJpZM4RmGSy> .

-- Michael T. Jones michael.jones@gmail.com

Richard Artoul · Answer 9 · Sun Sep 30 2018 00:43:09 GMT+0800 (China Standard Time)

About to incorporate this into one of our libraries, thanks for making this available! This issue can probably be closed now :)

Michael T Jones · Answer 10 · Sun Sep 30 2018 03:34:24 GMT+0800 (China Standard Time)

Great!

On Sat, Sep 29, 2018 at 9:43 AM Richard Artoul ***@***.***> wrote: About to incorporate this into one of our libraries, thanks for making this available! This issue can probably be closed now :) — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHgypXPS0ZtRhKPkuzAVDweOIBg6Tgguks5uf6MegaJpZM4RmGSy> .

-- *Michael T. Jonesmichael.jones@gmail.com <michael.jones@gmail.com>*