Jon Stahl wrote: >> -----Original Message----- >> From: [EMAIL PROTECTED]
>> I know you aren't (all) lawyers, but I could use some general guidance >> in the following situation: >> >> Question: How do you distinguish ownership/copyright and licensing of >> paid work when some of the work is configurations, some is coding, > some >> is probably reusable or you think you 'may' be asked to do the same >> thing again at a future date by other customers (or perhaps even > his/her >> competitor). Who owns what? > > You'd probably want to specify ownership in your initial contract with > customer A. Not infrequently, open source consultants will say that > they retain ownership/copyright of what they create, while granting a > GPL (or equivalent) license to the contractee. > > Without such an explicit specification, I think you're likely in muddy > waters and would need to consult a lawyer. Or at least someone smarter > than me. ;-) > > I'd love to hear if others have experience with this, it's a great > question. Of course, IANAL :-) I agree with Jon, that you should make it clear that you retain ownership of code, or that it is licensed in such a way that you can reuse it (eg, GPL). I would be surprised if many of your clients had a problem with that, as they're used to buying software without ever owning the code, anyway. Additionally, you want to ensure that, since you're likely dealing with large amounts of GPL and ZPL licensed code written by others, they _can't_ actually own the major code-base, anyway. -- derek _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
