Evening Andrew: I have been going over the "Tasks" section of our change proposal trying to get an idea of how much work is involved.
One thing that came up was changing the license to EPL (I am assuming this is a requirement, when I checked the Eclipse Labs LGPL was not one of the accepted licenses). With that in mind I had two questions: 1) License transition Is there anything more needed then? I assume a vote by the PMC to change license, followed by doing all the work (updating headers, license.html files, splash screens and so on). About updating the file headers: a) it would be less work to file headers once (ie. after taking the foundation takes a cut of the codebase as one of the steps prior to an interm release?) b) Would be easier to follow the license traceability if we change the license now in github prior to repackaging 2) Git vs GitHub I noticed that GitHub joined the eclipse foundation (probably to support EGit). Is it possible to stay on github; or is it a case like with the apache foundation that the ability to shut off a problem repository promptly is advantageous. -- Jody Garnett
_______________________________________________ User-friendly Desktop Internet GIS (uDig) http://udig.refractions.net http://lists.refractions.net/mailman/listinfo/udig-devel
