Moving to GPLv3 - the practical side of it

[Mats Lidell]

Hi,

I have been looking into the move to GPLv3 and how to go about that in 
practice.  So I have changed the GPLv2 identifying script info a script that 
replaces the GPLv2 text with a GPLv3 text. 

Now comes the practical side of it. If I apply that script the patch will be 
rather big and it will at best only take care of the files that clearly has a 
GPLv2 license and change that into GPLv3. Would that be an acceptable way to 
go? Changing all GPLv2 into GPLv3 and then fix the rest as we go along? 

Or should we fix the possibly tricky cases first before doing the big 
copyright text replacement operation?

Related to that is the questions I have asked before on the list (but as yet 
hasn't been answer what I'm aware of ayway). I repeat them below:

 - There seems to be quite a few files with no clear license. What
   does that mean or imply for a move to GPLv3?  Shall or must we keep
   them as is or can they be move to GPLv3?

 - And how about item #13 [see Jerry James analysis] which are copyrighted 
   by IBM. Even though they don't have a stated license that seems still to be
   a problem to me. Can they really be used with GPLv3?

 - Is the analysis, [that Jerry James did,] detailed enough or do we need 
   to go through each file and tag them as I proposed earlier?

Yours
-- 
%% Mats