Hi all & David, > Just to clarify: mmw does *not* necessarily speak for Google Code on this.
if there were confusion there: I don't speak for google at all, I only answer quickly from my iphone :) you can feel it 8-) > mmw: Sorry to be blunt, but this is a policy decision, and it seems > you have no idea what our policy actually is. no problemo, you are welcome to correct me, maybe I misunderstood the request shit happens :-), and was totally ignorant about this policy as I can say I understood this request in this way: "I have a project for instance under BSD* license adn I am using a third library under LGPL, here there is no problem regarding the licenses "no collision", for convenience, I am hosting this third part because I applied some patches and moves (that I did under the LGPL License)" but now as you point a policy that I ignored, it makes sense not to take risks to host dual licenses projects because people doesn't not respect or try to understand if there's any conflict between licenses especially some young punks around, but it's not the case for long term open-source/SAAVY developers, that open-source mainly for fun not to show off :-) and Thomas is one of them. so I do apologize if I "misleaded" someone here, it was certainly not my intention, only shared some ideas that appear not to be conform with google-hosting rules Best, - mmw On Fri, May 29, 2009 at 8:19 AM, David Anderson <[email protected]> wrote: > > Just to clarify: mmw does *not* necessarily speak for Google Code on this. > > mmw: Sorry to be blunt, but this is a policy decision, and it seems > you have no idea what our policy actually is. If that is the case, > please refrain from replying, as you may confuse people into doing > something that will get them banned. > > As to the original question: I admit ignorance as to the policy of > Google Code on this topic, but I'm sure someone from the team is going > to step in and fill you in. > > - Dave > > On Thu, May 28, 2009 at 14:30, mm w <[email protected]> wrote: >> >> Hi Thomas, this is the life of many open-source projects >> >> - you can add your license in the file header >> - you may create a ReadMe File and specify that you are using a dual License >> - you can create two(n-...)-projects: >> --> CoreOS >> --> Building-Tools >> >> - you can may a "general License" for your work e.g new BSD, >> and let the various licenses at sub-project entries level >> >> On Thu, May 28, 2009 at 2:12 PM, Thomas Heller <[email protected]> >> wrote: >>> >>> On May 26, 1:09 pm, Thomas Heller <[email protected]> wrote: >>>> Hello, >>>> >>>> I intend to create a google code project containing a linux version >>>> for an embedded system. This stuff will of course be GPL licensed. >>>> >>>> However, I want to also make build scripts and downloads available >>>> for projects that are licensed in a different way, Python for example. >>>> >>>> So, is it ok to include Python-licensed files in a GPL project? >>> >>> Any ideas from anyone? >>> >>> Can I make files available as downloads that have a non-GPL, but >>> another >>> open-source license? >>> > >>> >> >> > >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hosting at Google Code" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-code-hosting?hl=en -~----------~----~----~----~------~----~------~--~---
