git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Elijah Newren <newren@gmail.com>
Cc: Joel Holdsworth <jholdsworth@nvidia.com>,
	Git Mailing List <git@vger.kernel.org>,
	Tzadik Vanderhoof <tzadik.vanderhoof@gmail.com>,
	Dorgon Chang <dorgonman@hotmail.com>,
	Joachim Kuebart <joachim.kuebart@gmail.com>,
	Daniel Levin <dendy.ua@gmail.com>,
	Johannes Schindelin <johannes.schindelin@gmx.de>,
	Luke Diamand <luke@diamand.org>, Ben Keene <seraphire@gmail.com>,
	Andrew Oakley <andrew@adoakley.name>
Subject: Re: [PATCH v2 3/3] git-p4: add "Nvidia Corporation" to copyright header
Date: Mon, 13 Dec 2021 00:11:55 +0000	[thread overview]
Message-ID: <YbaPy8UhzIwRuNYm@camp.crustytoothpaste.net> (raw)
In-Reply-To: <CABPp-BEyBLzWY2andDXZV6AgkQpnt1sp_rSThy84=qXMt2D8nA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2350 bytes --]

On 2021-12-11 at 21:19:18, Elijah Newren wrote:
> On Fri, Dec 10, 2021 at 12:30 PM Joel Holdsworth <jholdsworth@nvidia.com> wrote:
> >
> > The inclusion of the coorporate copyright is a stipulation of the
> > company code release process.
> > ---
> >  git-p4.py | 1 +
> >  1 file changed, 1 insertion(+)
> >
> > diff --git a/git-p4.py b/git-p4.py
> > index 5568d44c72..17e18265dc 100755
> > --- a/git-p4.py
> > +++ b/git-p4.py
> > @@ -5,6 +5,7 @@
> >  # Author: Simon Hausmann <simon@lst.de>
> >  # Copyright: 2007 Simon Hausmann <simon@lst.de>
> >  #            2007 Trolltech ASA
> > +#            2021 Nvidia Corporation
> >  # License: MIT <http://www.opensource.org/licenses/mit-license.php>
> >  #
> >  # pylint: disable=invalid-name,missing-docstring,too-many-arguments,broad-except
> > --
> > 2.33.0
> 
> Can we just git rid of these lines entirely?

In the case of the MIT License, it is a condition of the license that
the copyright notices be preserved, so no, we cannot remove them.
Specifically, the first paragraph, which grants permissions states that
they are "subject to the following conditions", one of which is as
follows:

  The above copyright notice and this permission notice shall be
  included in all copies or substantial portions of the Software.

The other is the total exclusion of warranty or liability.

As for the rest of the codebase, the GPL v2 states that the exercise of
copying and distribution is permitted, "provided that you conspicuously
and appropriately publish on each copy an appropriate copyright notice
and disclaimer of warranty."  I am not an attorney, but I'm pretty sure
that it would not be permissible to remove a copyright notice unless the
code to which it referred were no longer present and that would not
count as publishing an appropriate copyright notice.

However, that doesn't mean we need to add to them, but I will state that
as a contributor who primarily contributes on his own time, I don't
think it's unreasonable for a contributor to request that a copyright
notice be applied where applicable as attribution, since that's the only
compensation one receives for one's contributions.  Such copyright
notices could live in a central file for convenience, however.
-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

      reply	other threads:[~2021-12-13  0:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-10 15:30 [PATCH v2 0/3] Transition git-p4.py to support Python 3 only Joel Holdsworth
2021-12-10 15:30 ` [PATCH v2 1/3] git-p4: remove support for Python 2 Joel Holdsworth
2021-12-12 17:50   ` Andrew Oakley
2021-12-12 22:01     ` Ævar Arnfjörð Bjarmason
2021-12-10 15:31 ` [PATCH v2 2/3] git-p4: eliminate decode_stream and encode_stream Joel Holdsworth
2021-12-10 15:31 ` [PATCH v2 3/3] git-p4: add "Nvidia Corporation" to copyright header Joel Holdsworth
2021-12-10 18:57   ` Luke Diamand
2021-12-11 21:19   ` Elijah Newren
2021-12-13  0:11     ` brian m. carlson [this message]

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YbaPy8UhzIwRuNYm@camp.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=andrew@adoakley.name \
    --cc=dendy.ua@gmail.com \
    --cc=dorgonman@hotmail.com \
    --cc=git@vger.kernel.org \
    --cc=jholdsworth@nvidia.com \
    --cc=joachim.kuebart@gmail.com \
    --cc=johannes.schindelin@gmx.de \
    --cc=luke@diamand.org \
    --cc=newren@gmail.com \
    --cc=seraphire@gmail.com \
    --cc=tzadik.vanderhoof@gmail.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 public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).