Re: [PATCH] clone: Warn if clone lacks LICENSE or COPYING file

2015-04-03 Thread David A. Wheeler
On Sun, 22 Mar 2015 18:56:52 +0100, Ævar Arnfjörð Bjarmason ava...@gmail.com wrote: However perhaps an interesting generalization of this would be something like a post-clone hook, obviously you couldn't store that in .git/hooks/ like other githooks(5) since there's no repo yet, but having it

Re: [PATCH] clone: Warn if clone lacks LICENSE or COPYING file

2015-04-03 Thread Junio C Hamano
Ævar Arnfjörð Bjarmason ava...@gmail.com writes: As others have indicated here this feature is really specific to a single lint-like use-case and doesn't belong in clone as a built-in feature. However perhaps an interesting generalization of this would be something like a post-clone hook,

Re: [PATCH] clone: Warn if clone lacks LICENSE or COPYING file

2015-03-26 Thread Kevin D
On Sat, Mar 21, 2015 at 02:06:33PM -0400, David A. Wheeler wrote: 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

Re: [PATCH] clone: Warn if clone lacks LICENSE or COPYING file

2015-03-23 Thread David A. Wheeler
Junio C Hamano: 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. That doesn't help with the many projects that have *already* been

Re: [PATCH] clone: Warn if clone lacks LICENSE or COPYING file

2015-03-23 Thread Ævar Arnfjörð Bjarmason
On Mon, Mar 23, 2015 at 5:46 PM, David A. Wheeler dwhee...@dwheeler.com wrote: Junio C Hamano: 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 disagree, I think it's remarkably effective.

Re: [PATCH] clone: Warn if clone lacks LICENSE or COPYING file

2015-03-22 Thread Ævar Arnfjörð Bjarmason
On Sat, Mar 21, 2015 at 7:06 PM, David A. Wheeler dwhee...@dwheeler.com wrote: 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

Re: [PATCH] clone: Warn if clone lacks LICENSE or COPYING file

2015-03-21 Thread Dennis Kaarsemaker
On za, 2015-03-21 at 14:06 -0400, David A. Wheeler wrote: 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

[PATCH] clone: Warn if clone lacks LICENSE or COPYING file

2015-03-21 Thread 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

Re: [PATCH] clone: Warn if clone lacks LICENSE or COPYING file

2015-03-21 Thread Stefan Beller
On 21.03.2015 13:21, Dennis Kaarsemaker wrote: On za, 2015-03-21 at 14:06 -0400, David A. Wheeler wrote: 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

Re: [PATCH] clone: Warn if clone lacks LICENSE or COPYING file

2015-03-21 Thread Junio C Hamano
Stefan Beller stefanbel...@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,