git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Stefan Beller <stefanbeller@gmail.com>
Cc: Dennis Kaarsemaker <dennis@kaarsemaker.net>,
	dwheeler@dwheeler.com, git <git@vger.kernel.org>
Subject: Re: [PATCH] clone: Warn if clone lacks LICENSE or COPYING file
Date: Sat, 21 Mar 2015 21:59:30 -0700	[thread overview]
Message-ID: <xmqqoanld3v1.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <550E430F.9010308@gmail.com> (Stefan Beller's message of "Sat, 21 Mar 2015 21:20:31 -0700")

Stefan Beller <stefanbeller@gmail.com> writes:

> To spin this further it would be interesting to have
> a server advertisement during git clone which indicates
> if this setting is recommended to be set.
> Then hosting sites popular in the open source world such as
> github could enable this feature, and the client may enable
> this for the currently cloned repository (the user may have
> a global setting set to suppress this message though).
>
> At $work the default of not advertising checking for such a
> feature would be set.

Hmm.

An open source hosting site can help better by checking at the
project creation time, because the people who interact with that
interface are solely in the position to set and publish licensing
terms.  The general consumer who are cloning and fetching do not
have direct control over this, and the only thing the could do to
nudge the publishers is with an out-of-line communication, e.g.
sending e-mails telling the publisher "I am interested in using your
ware, but you do not have licensing terms described, which makes me
wary; please improve".

An approach that checks only the top-level directory for fixed
filename pattern would not be an effective way to protect the
cloners, either.

I am personally not interested in the patch under discussion, with
or without "please be quiet" configuration.

Thanks.

  reply	other threads:[~2015-03-22  4:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-21 18:06 [PATCH] clone: Warn if clone lacks LICENSE or COPYING file David A. Wheeler
2015-03-21 20:21 ` Dennis Kaarsemaker
2015-03-22  4:20   ` Stefan Beller
2015-03-22  4:59     ` Junio C Hamano [this message]
2015-03-23 16:46       ` David A. Wheeler
2015-03-23 21:00         ` Ævar Arnfjörð Bjarmason
2015-03-22 17:56 ` Ævar Arnfjörð Bjarmason
2015-04-03 21:18   ` David A. Wheeler
2015-04-03 21:26   ` Junio C Hamano
2015-03-26 16:56 ` Kevin D

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=xmqqoanld3v1.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=dennis@kaarsemaker.net \
    --cc=dwheeler@dwheeler.com \
    --cc=git@vger.kernel.org \
    --cc=stefanbeller@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.
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 NNTP newsgroup(s).