Git development
 help / color / mirror / Atom feed
From: Johannes Sixt <j6t@kdbg.org>
To: dwheeler@dwheeler.com, git <git@vger.kernel.org>
Subject: Re: [PATCH] clone: Warn if LICENSE or COPYING file lacking and !clone.skiplicensecheck
Date: Sun, 22 Mar 2015 09:23:33 +0100	[thread overview]
Message-ID: <550E7C05.4060603@kdbg.org> (raw)
In-Reply-To: <E1YZTZI-0002QE-3r@rmm6prod02.runbox.com>

Am 22.03.2015 um 01:16 schrieb David A. Wheeler:
> Warn cloners if there is no LICENSE* or COPYING* file that makes
> the license clear.  This is a useful warning, because if there is
> no license somewhere, then local copyright laws (which forbid many uses)
> and terms of service apply - and the cloner may not be expecting that.
> Many projects accidentally omit a license, so this is common enough to note.
>
> You can disable this warning by setting "clone.skiplicensecheck" to "true".
>
> For more info on the issue, feel free to see:
> http://choosealicense.com/no-license/
> http://www.wired.com/2013/07/github-licenses/
> https://twitter.com/stephenrwalli/status/247597785069789184
>
> Signed-off-by: David A. Wheeler <dwheeler@dwheeler.com>

The opt-out works only when placed in the system-wide or user 
configuration. That places a maintenance burden on *ALL* existing 
installations that do not want the warning.

If you really want to hard-code such a policy decision into Git, then 
make it an opt-in so that members of the license squad can enable it.

I don't need it.

-- Hannes

  reply	other threads:[~2015-03-22  8:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-22  0:16 [PATCH] clone: Warn if LICENSE or COPYING file lacking and !clone.skiplicensecheck David A. Wheeler
2015-03-22  8:23 ` Johannes Sixt [this message]
2015-03-22  9:45 ` Duy Nguyen

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=550E7C05.4060603@kdbg.org \
    --to=j6t@kdbg.org \
    --cc=dwheeler@dwheeler.com \
    --cc=git@vger.kernel.org \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox