LOGIN   :::   RECOVER PASS   :::   GET ACCOUNT    
Browse
  • Projects
  • Code (CVS)
  • Forums
  • News
  • Articles
  • Polls
  •  
    OpenCores
  • FAQ
  • CVS HowTo
  • Mission
  • Media
  • Tools
  • Advertise
  • Mirrors
  • Logos
  • Contact us
  • Job Opportunity
  •  
    Tools
  • Search
      
  • Download Cores (CVSGet)
  •  
    More
  • Wishbone
  • Perlilog
  • EDA tools
  • OpenTech CD
  •  
    Navigation: All forums > Cores > Message List > Message Post

    Message

    Reply | Reply all
    Date Prev | Date Next | Thread Prev | Thread Next Date Index | Thread Index

    From: Christoph Zimmermann<nussgipfel@b...>
    Date: Fri Aug 3 21:25:57 CEST 2007
    Subject: [oc] GPLv3 usable for open HW
    Top
    thanks for all these answers and comments.

    i see that the question about licensing hardware designs is still a hot
    topic. and the discussions are far away from the software comunities
    where it is now more a ideologic discussion where it is here still the
    question: can i use this license? what is "software" in my hardware
    project? or do we need a own license? and do i prohibit the normal use
    of hardware (production/selling/...)?

    attila:
    "> > have i understood the new GPLv3 right? is it realy so
    > > general applicable as i think?

    > If you think you've understood GPLv3, read again ;-)"

    yes i read it more then one time and decided to ask some other people
    to be shure :-)

    i have more or less still the same confusion as on the beginning,
    because my intial problem was, that i don't have, in my opinion,
    software to license. i have a design of a fpga integrator board which i
    would like to license in an open/free matter.

    so i change at this point of the discussion my question a bit:
    which licenses are usable for works like schematics, pcb files, gerber
    files?

    > TAPR open hardware license is one that asks for something back
    > without being a big burden. They ask for communication attempts about
    > modifications that are distributed, and if the attempt by email
    > fails, that ends that obligation. The form of design details
    > communicated is left unspecified and does not have to be complete in
    > some rigorous way.

    thanks for john to bring the TAPR ohl license to this discussion, i
    never heard from it before.


    for me personaly it is an important thing that when you made somthing
    complex and you made it free/open that something comes back when
    someone make something new whith it or make an improvement. like in
    science.
    but this of course a personal descision.


    christoph zimmermann


     
    Copyright (c) 1999 OPENCORES.ORG. All rights reserved.