On Fri, Sep 13, 2013, at 11:28 AM, Michael Haberler wrote: > > Am 13.09.2013 um 16:54 schrieb Jeff Epler <jep...@unpythonic.net>: > > > I strongly wish to see at least a notice of copyright and terms in each > > new file, not least because it is the advice of the FSF given in the GPL > > itself. It avoids doubt about the status of each specific file, and the > > only costs identified so far are the author's time to insert the notice > > and a few tens of kB uncompressed text added to the 49 files I > > identified that are in UBC3 and not in master. > > I certainly do not have a problem to insert notices into the rtapi and the > few other source files, those will be fixed of course. > > I was referring specifically to configs/* and tests/* . > > What you are proposing is to add license statememts in some 5 or so new files > in configs - fine; that leaves the other 1700 or so existing files under > those directories without one, which doesnt make sense to me. This is why I > proposed the directory license statement solution for those directories.
I don't really have much of a stake in this one way or another. But to me it seems like the sample configs don't need copyright. Their sole reason for existance is to give users something to start hacking and chopping on. They are useless outside of the LCNC context. It's not like we need to protect those files with copyright to keep them from being used by some other CNC control. The config files are also fairly short, and frequently accessed by the user during machine configuration. Scrolling down past a long license notice is a nuisance. I propose something like the following as a header for the sample config files: # This file is a sample configuration for LinuxCNC. It is supplied # with no guarantees, as a convenience to the user, and with the # expectation that the user will modify it to suit his/her needs. # The author(s) hereby dedicate all copyrights and other related # rights in this file to the public domain. Short and simple. John Kasunich jmkasun...@fastmail.fm ------------------------------------------------------------------------------ How ServiceNow helps IT people transform IT departments: 1. Consolidate legacy IT systems to a single system of record for IT 2. Standardize and globalize service processes across IT 3. Implement zero-touch automation to replace manual, redundant tasks http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
