Adam Williamson wrote: > On Fri, 2008-07-04 at 12:43 +0100, Jonny Lamb wrote: > >> One thing: your trunk/COPYING says GPLv2, but your Google Code front page >> says MIT. The former will take precedence, but after reading the front >> page, I'm wondering whether you deliberately put the GPL in your >> COPYING? Please make the license very clear upon importing into our SVN. > > As resident Mandriva licensing geek, I should chip in that the preferred > way to do this is to include an explicit declaration of the applicable > license at the top of each source file, along with a full copy of the > relevant license(s) in the top-level directory. For GNU licenses > remember to specify the version(s) of the license that you want to > apply.
The confusion actually stems from the original kio-rapip code I started with (from synce svn). There are two files present, COPYING (GPLv2) and LICENSE (MIT). The MIT license is then in the header of the source files. But then to confuse things further there is a rapip.lsm which has the license listed as GPL. I really wasn't sure which one was intended, but most of the SynCE project is under MIT so I just chose that in Google. The author was Volker Christian; is he still around? I don't feel I have changed the code enough for it to be a completely separate project, so if he did want it to be under GPL I'm happy to stick with that. Anyone know either way? And trunk/kde4-kio-rapip is fine with me if that's preferred. Regards, Tejas Guruswamy <[EMAIL PROTECTED]> ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ SynCE-Devel mailing list SynCE-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synce-devel
