[Kde-pim] KMail License issues.

[Tom Albers]

Op woensdag 17 september 2008 00:57 schreef u:
> It's most effective to do an SVN log;
> 
> for i in $FILES ; do
> 	svn log --xml svn://anonsvn.kde.org/home/kde/trunk/KDE/kdepim/$i | \
> 	grep '^<author>' | sed 's/<[^>]*>//g' | sort | uniq -c | sort -rn
> done
> 
> something like that will tell you authors and counts of contributions, so you 
> know who to track down first. In general:

Hmm, A slightly different approach is to use:
http://websvn.kde.org/*checkout*/trunk/KDE/kdesdk/scripts/relicensecheck.pl?revision=852507

This will give you the contributors + there approval to relicense + the amount of code that's theirs in LOC, which gives you an *idea* about there importance. Still a 0 LOC contributor can be important if all his lines are only changes a small bit... whitespaces are excluded iirc.

> 1) For files with no license header, ask the first contributor (svn log | grep 
> author | tail -1) what the license would have been, something like:
> 
> 	"Because the file <foo> has no license we cannot -- in the strictest sense of 
> copyright law -- continue to distribute it, so I'm contacting all of the 
> contributors to determine what the license should have been. Implicitly your 
> file <foo> would have been following the license of other files in the 
> directory, which is <GPLv2 or LGPLv2>, but we need to make that explicit. 
> Please answer these two questions:
> 
> - which license would you have originally used <GPLv2, GPLv2 or later, LGPLv2, 
> LGPLv2 or later> for the file <foo>?
> 
> - do you agree to re-license the file now to the current KDE PIM license which 
> ought to apply to <foo>, which is <GPLv3 or later, LGPLv3 or later>?
> 
> I will need your answers -- as original author of the file -- to carry the 
> question to other contributors in the file, so that we can do a licensing and 
> re-licensing properly and continue to distribute the work under strict 
> copyright interpretations. Of course you want the software to be Free 
> Software, but that means doing some of the "paperwork" too, that's why I'm 
> asking this question now."
> 
> 2) Go to all contributors with a similar question.
> 
> 3) Add relevant header.
> 
> 4) Commit &| profit!

Yes, 

If you want to do a KDE a favor, contact them and ask them to answer the five questions from 
http://techbase.kde.org/Projects/KDE_Relicensing

That way you secure their permission for all files in KDE. If you receive answer to those questions, simply adjust the relicense script and you will see the change. 

You can also sent me the email where they answer the five questions so I can archive them in the permissions git repository that we have used in the past. That way the permission is archived and not only in your personal mailbox.

My advise would be not to approach it file by file, but make a list of all people that you need permission from and approach them. Personal approach works best, but you need a strict regime in reminders, etc. Best is to not do it alone, you will get demotivated rather soonish.

Toma
-------------- next part --------------
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/