[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: files in contrib/ without licence

From: Mark Phippard <markphip_at_gmail.com>
Date: Tue, 2 Dec 2008 17:45:36 -0500

On Tue, Dec 2, 2008 at 3:55 PM, Stefan Sperling <stsp_at_elego.de> wrote:

> the following files in contrib/ do not have a licence:
>
> cgi/mirror_dir_through_svn.cgi
> client-side/emacs/vc-svn.el
> client-side/svn_all_diffs.pl
> client-side/svn_load_dirs/svn_load_dirs.pl.in
> client-side/vim/diff-to-logmsg.vim
> client-side/vim/svn.vim
> hook-scripts/detect-merge-conflicts.sh
> server-side/backup-recipe.sh
> server-side/load_repo_with_mergesensitive_copy.sh
> server-side/svnmirror-test.sh
>
> This prevents downstream distributors from packaging these files.
> Besides my other Subversion duties, I am maintaining the OpenBSD
> port of Subversion and cannot include these files if they do not
> have a licence.
>
> The authors, and committers who committed these files (there's
> some overlap) are in Cc. Please add a licence to your file[s].
>
> It's enough if you add them on trunk.
> I will take care of backporting the licences to the 1.5.x branch
> (unless anyone has a problem with that, but I doubt that's the case.)

We have gone through this before, Peter Samuelson regularly brings
this up because Debian has the same issue. So I suspect the files
that are left without a license have mostly done so because we cannot
assign one. It looks like a couple in your list might be new files
where a license was overlooked and could be updated.

Why don't we boot these files from trunk and our tarballs? We could
create a new top-level folder for them or just get rid of them
altogether.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=978575
Received on 2008-12-02 23:46:01 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.