Curt Wuollet: > This is a good question for all. What do we do with non-code IP that > belongs to the project? With code we can retain copyright and license as > GPL. What the heck do I do with this? > Can you GPL artwork??!!?? I can't see why not, particularly since it's functional artwork, but then again I'm not a lawyer. I would expect that the letter of the GPL would require one to include an artwork floppy disk with each board; we can either consider this a feature, or make a special exception (for the case of unmodified artwork only). Jiri -- Jiri Baum <[email protected]> Connect the power cable, interface cable and ground wire only in the methods indicated in the this manual. It may lead to fire. -- OKIPAGE 8z user's manual _______________________________________________ LinuxPLC mailing list [email protected] http://linuxplc.org/mailman/listinfo/linuxplc

 

Could you not put in a line of text at one edge of the board refering to GPL license and a web adress explaining further /Johan Bengtsson ---------------------------------------- P&L, Innovation in training Box 252, S-281 23 H{ssleholm SWEDEN Tel: +46 451 49 460, Fax: +46 451 89 833 E-mail: [email protected] Internet: http://www.pol.se/ ---------------------------------------- _______________________________________________ LinuxPLC mailing list [email protected] http://linuxplc.org/mailman/listinfo/linuxplc

 

Check here. This is a repository of open source hardware designs. http://www.opencores.org/ _______________________________________________ LinuxPLC mailing list [email protected] http://linuxplc.org/mailman/listinfo/linuxplc

 

Hi Johan The artwork already refers to the project :^) I consider it our "business card". Perhaps I could refer to the GPL although that is worded specifically for software. I'm considering simply assigning the copyright to the Linux PLC project and leaving it at that. Legal manipulation and remedies are unbecoming to an OSS project, being much more the tool of our less altruistic competitors. Regards cww _______________________________________________ LinuxPLC mailing list [email protected] http://linuxplc.org/mailman/listinfo/linuxplc

 

We might look at the GPL Document license for the public dio48 stuff. You might also consider it for any documentation for the Puffin project. GNU Free Documentation License Version 1.1, March 2000 http://www.gnu.ai.mit.edu/copyleft/fdl.html In essence it is a way to ensure that public documents remain public. In part it says -----quote----- 0. PREAMBLE The purpose of this License is to make a manual, textbook, or other written document "free" in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others. This License is a kind of "copyleft", which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software. We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference. -----end quote----- > Perhaps I could refer to the GPL although that is worded specifically for > software. In fact Stallman refers to the GPL and believes that you can apply it to other than code. See http://www.gnu.ai.mit.edu/philosophy/license-list.html#DocumentationLicenses Where he says under the heading "The Design Science License" -----quote----- Note, though, that the GNU GPL can be used for general data which is not software, as long as one can determine what the definition of "source code" refers to in the particular case. As it turns out, the DSL also requires that you determine what the "source code" is, using approximately the same definition that the GPL uses. -----end quote----- You might also look at The Design Science License itself at http://dsl.org/copyleft/dsl.txt Hope this helps Ray _______________________________________________ LinuxPLC mailing list [email protected] http://linuxplc.org/mailman/listinfo/linuxplc

 

Hi Ray and all Yes, Those could be useful but I get the feeling no one has really figured out the hardware end. I'm not entirely sure what abuse would be for that matter, or how I would ever know. There's really nothing unique there, the only reason someone hasn't done it this way is that it's a lot more profitable to sell racks and modules. I am doing it because I need it and the project needs it and it promotes the use of Linux in automation. In a way, it's already viral. Someone making these cheap by the boatload would further the cause. Even someone making these for a reasonable profit would simply be making it easier for those who don't want to build their own. And there's no way to extort money from hapless victims if we offer the option of making your own batch at cost. The only downside is that they will also work with Windows :^). I'd just like to make sure that each and every one says "The LinuxPLC Project". By the way, the boards arrived today and by working late to breathe soldering fumes, I was able to complete a board for testing Monday. I almost grabbed the drivers and boards and cables etc., etc. and brought them here but, I think I'm going to do something else for the weekend, I'm a little crisp around the edges. I'll probably go shooting, do some car and home repairs, and write some documentation. I might as well get paid for testing it as long as it's an option, we need it right now at my day job too. We have more "real world" loads and such there as well, including a machining cell that is waiting for it and LinuxVision. Regards cww _______________________________________________ LinuxPLC mailing list [email protected] http://linuxplc.org/mailman/listinfo/linuxplc