From: github.com@gnu.support
To: "syl20bnr/spacemacs"
<reply+AF5M4K24CWRJD5PV4KMTBAV6JORUZEVBNHHDBSUAQA@reply.github.com>
Cc: emacs-tangents@gnu.org
Subject: Re: [syl20bnr/spacemacs] Proposal to improve GPL compliance (#14444)
Date: Wed, 3 Mar 2021 22:50:33 +0300 [thread overview]
Message-ID: <YD/oiS5QtAslYMTF@protected.rcdrun.com> (raw)
In-Reply-To: <syl20bnr/spacemacs/issues/14444/789893593@github.com>
* Lucius Hu <notifications@github.com> [2021-03-03 20:07]:
> @thanhvg
> Code snippets you found online are usually `unlicensed` and you can
> adapt those into your codebase, with the following exceptions:
> - If the (apparent) author claims that it's licensed, then you should check the license compatibility.
> - If the hosting website claims it owns the copyright or the
> - contents on its website is under a specific license, then you also
> - need to check the compatibility.
That is absolutely incorrect.
Any works are automatically protected unless author has some different
licensing terms.
When some work is there without license that means it is protected by
copyright laws and thus proprietary. It becomes free software only if
explicitly stated so.
Please see the question answered related to US copyrights:
https://www.copyright.gov/help/faq/faq-general.html
Where it says:
"Do I have to register with your office to be protected?
No. In general, registration is voluntary. Copyright exists from the
moment the work is created. You will have to register, however, if you
wish to bring a lawsuit for infringement of a U.S. work. See Circular
1, Copyright Basics, section “Copyright Registration.” "
Thus when work is created, be it piece of text, software, paintings,
image, the copyright exists from the moment work is created. Without
explicitly licensing it as free software it is not free and thus
cannot just be copied and pasted as somebody wish and want.
In the end that spoils the GNU GPL licensed free software with
proprietary software for which one have never got permission.
> In general, if it's unlicensed you just need to include the link to
> the original page/author.
That is incorrect. See above.
While in US it is recommended to register copyrights, it exists just
as in all other countries automatically from the moment of creation of
the work.
next prev parent reply other threads:[~2021-03-03 19:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <syl20bnr/spacemacs/issues/14444@github.com>
[not found] ` <syl20bnr/spacemacs/issues/14444/788139959@github.com>
2021-03-01 18:54 ` [syl20bnr/spacemacs] Proposal to improve GPL compliance (#14444) github.com
[not found] ` <syl20bnr/spacemacs/issues/14444/788212009@github.com>
2021-03-03 5:44 ` github.com
[not found] ` <syl20bnr/spacemacs/issues/14444/788214244@github.com>
2021-03-03 6:32 ` github.com
[not found] ` <syl20bnr/spacemacs/issues/14444/788279842@github.com>
2021-03-03 6:59 ` github.com
[not found] ` <syl20bnr/spacemacs/issues/14444/788544413@github.com>
2021-03-03 7:06 ` github.com
[not found] ` <syl20bnr/spacemacs/issues/14444/789479245@github.com>
2021-03-03 7:10 ` github.com
[not found] ` <syl20bnr/spacemacs/issues/14444/788977796@github.com>
2021-03-03 7:17 ` github.com
[not found] ` <syl20bnr/spacemacs/issues/14444/789126947@github.com>
2021-03-03 7:18 ` github.com
[not found] ` <syl20bnr/spacemacs/issues/14444/789468543@github.com>
2021-03-03 7:21 ` github.com
[not found] ` <syl20bnr/spacemacs/issues/14444/789512582@github.com>
2021-03-03 10:08 ` github.com
[not found] ` <syl20bnr/spacemacs/issues/14444/789893593@github.com>
2021-03-03 19:50 ` github.com [this message]
[not found] ` <syl20bnr/spacemacs/issues/14444/789995307@github.com>
2021-03-03 20:02 ` github.com
[not found] ` <syl20bnr/spacemacs/issues/14444/790262904@github.com>
2021-03-04 6:26 ` github.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YD/oiS5QtAslYMTF@protected.rcdrun.com \
--to=github.com@gnu.support \
--cc=emacs-tangents@gnu.org \
--cc=reply+AF5M4K24CWRJD5PV4KMTBAV6JORUZEVBNHHDBSUAQA@reply.github.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.