License
kardianos opened this issue · comments
This looks like a nice start for integration to Zoho.
Please be aware, it is doubtful many people will be able to use a GPL3 licensed package. It is likely almost everyone who is interested in using both Go and Zoho will be unable to use this package.
Thanks for your comment, and duly noted. What are your suggestions for license? Are there any considerations I should make when changing the lisense; like versioning the current license to a different branch?
You could put in a different branch, but just changing the license and
tagging a new release would be enough.
BSD and MIT are both popular choices. The problem with GPL is it is viral
and Go is statically linked.
…On Fri, Jan 31, 2020, 06:19 Sam Morrison ***@***.***> wrote:
Thanks for your comment, and duly noted. What are your suggestions for
license? Are there any considerations I should make when changing the
lisense; like versioning the current license to a different branch?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#20?email_source=notifications&email_token=AAFYLMMWYJXG2DJZDMX3GF3RAQXPDA5CNFSM4KN6IMVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKOZDCY#issuecomment-580751755>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFYLMKQM2DFTUDSRV2PDE3RAQXPDANCNFSM4KN6IMVA>
.
Very good. Thanks for you suggestion. I am by no means attached to the
current license and will push the updated lisence in a bit.
PRs or feature requests are appreciated.
I am working on a new branch which is attempting to generate the structs
for each modules data type. Maybe I'll push the progress at the same time.
On Fri., Jan. 31, 2020, 8:30 a.m. Daniel Theophanes, <
notifications@github.com> wrote:
… You could put in a different branch, but just changing the license and
tagging a new release would be enough.
BSD and MIT are both popular choices. The problem with GPL is it is viral
and Go is statically linked.
On Fri, Jan 31, 2020, 06:19 Sam Morrison ***@***.***> wrote:
> Thanks for your comment, and duly noted. What are your suggestions for
> license? Are there any considerations I should make when changing the
> lisense; like versioning the current license to a different branch?
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <
#20?email_source=notifications&email_token=AAFYLMMWYJXG2DJZDMX3GF3RAQXPDA5CNFSM4KN6IMVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKOZDCY#issuecomment-580751755
>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AAFYLMKQM2DFTUDSRV2PDE3RAQXPDANCNFSM4KN6IMVA
>
> .
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#20?email_source=notifications&email_token=AEEUOIYG5WOT5NENDSNBSHTRAQYYTA5CNFSM4KN6IMVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKO2F3I#issuecomment-580756205>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEEUOI54HQPP5OQRZI4M52DRAQYYTANCNFSM4KN6IMVA>
.
Thanks!
…On Fri, Jan 31, 2020 at 3:30 PM Sam Morrison ***@***.***> wrote:
Closed #20 <#20>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#20?email_source=notifications&email_token=AAFYLML2MT6ANMPNUZEUCQ3RASX7TA5CNFSM4KN6IMVKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOWK7JKXY#event-2998834527>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFYLML6FA45CLZYB4CTMMDRASX7TANCNFSM4KN6IMVA>
.