Hi, all Adding a copyright to source code or scripts (i.e., to any original work) does not _actually_ prevent people from selling or copying that work or using it for other purposes.
What a copyright does is establish ownership rights in that piece of work. These ownership rights can then be used (if the need arises) to litigate, sue and attempt to collect compensation. The problem in most cases is that, unless the resources of the owner are large enough, the detection of a violation of those ownership rights is difficult, and litigation incredibly expensive and long. And, unless the copying and distribution is obvious (easier to establish in some works - like code or books), the act of litigating usually does not succeed too well. Hence copyright violation lawsuits are rare. Thus, any control of work is best done by explicit licenses - that either provide the work for a fee/cost, or are declared free (such as the licenses from Apache, MIT and the GPL in the case of open source, for example). Even this does not guarantee violations, but, at least, it sets the rules under which the work has been made available and is an easier way to get lawyers to handle litigation. Particularly if there is a sufficiently large monetary reason to do so. Sidebar: GPL is particularly disconcerting. Since using GPL open source is like an infection - new code built using stuff that is licensed via GPL also acquires GPL characteristics and becomes open. So, most companies (including mine) have Open Source Policy documents that describe exactly what open source licensed code their software designers can use inside their own material. Z > -----Original Message----- > From: Framers [mailto:framers- > [email protected]] On Behalf Of Klaus > Daube > Sent: Tuesday, May 24, 2016 01:37 AM > To: [email protected] > Subject: Re: [Framers] OT: Copyright rules for scripts > > Friends, > > I have now asked the author of the purchased script. Here is his answer: > < > The reason I copyright my scripts is so that people don't resell them as is > or give copies to others. However, you are free to modify the code and use it > in your own scripts as you have done. Yours is different enough that I would > not consider it an infringement on the copyright. You are welcome to do what > you want with this particular script. I compile some of my commercial scripts > in order to protect the code. For custom scripts like yours, I expect > that some users will use parts of the code in their own scripts. Please let > me know if you have any questions or comments. > Thank you very much for being concerned enough about it to ask me about > it. > > > > This disencumbers me and reflects my thoughts about the issue: > - Sharing ideas is not the same as commercialising them. > - Referencing the source of building blocks (in the manner of citations) > or the base of a script not only 'honours' the author but also allows > the later user to get additional information. > - Significant changes and new ideas minimise the potential of infringement. > - Any intellectual work is based on other peoples work - There is no progress > if "intellectual property" is put in the vault and no one else can make use > of it. > However, this work must be remunerated according to it's use (license, ...) > - The "all rights reserved" clause at least lets one think about the issue. > > I particularly thank for the remarks from Scott Prentice and the link he > provided. > Klaus Daube _______________________________________________ This message is from the Framers mailing list Send messages to [email protected] Visit the list's homepage at http://www.frameusers.com Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/ Subscribe and unsubscribe at http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com Send administrative questions to [email protected]
