On Sat, 2008-07-05 at 11:37 +0100, Tejas Guruswamy wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Mark Ellis wrote: > | On Fri, 2008-07-04 at 13:43 +0200, Jonny Lamb wrote: > |> On Fri, Jul 04, 2008 at 11:12:24AM +0100, Tejas Guruswamy 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. > |> > |>> I assume trunk/kde4-kio_rapip is OK as far as the naming goes. > |> I prefer trunk/kde4-kio-rapip to be honest, but if you are stuck on that > |> name, then go ahead. > |> > | > | Can I suggest renaming kio-rapip to kio-rapip-kde3, and making kde4 the > | standard kio-rapip ? I don't really do kde, but I get the impression > | kde3 is now a bit old. > | > > So what's the decision on the naming and licensing issues? Should I wait > for a consensus or go ahead and do a checkin?
Hi! About the licensing: All modules I started in SynCE (libsynce, librapi2, rra, serial, dccm, dynamite, unshield, and some others) are MIT licensed because of my personal preference, but I have not required contributors of new modules to use this license. This means that some other modules use the GPL. The important thing is that there are not different licenses in the same module! :-) Best Regards, David -- ------------------------------------------------------------------------- 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
