[Discuss] Open Hardware defintion and eagle files

phillip torrone pt at oreilly.com
Fri Sep 14 14:26:47 UTC 2012

hey mike,

if you really want to help:
-write tutorials on using open tools for design (kicad, geda). post them on instructables, make projects or elsewhere. email links to sites like make, hack-a-day, etc.
-make videos show how to use on using open source tools for design (kicad, geda) - post these on yotube, contact the many video-learning efforts out there like kahn, code academy, etc.
-show how to convert/import the eagle xml for open tools.
-run workshops that teach using these open tools, if you need any badges to award students to show and share their new skills, i can send you some out for free for kicad and geda.


On Sep 14, 2012, at 10:12 AM, Mike Dupont <jamesmikedupont at googlemail.com> wrote:
> Well, for OSHW to be credible it needs to be clear.
> How about a OSHW disclosure process, I felt misled and I am sure more
> will be in the future.
> lets make a range of licenses like CC has and make it clear what they mean.
> you can call OSHW v1 the core license and then add in more "freedoms"
> if you want to make it look like a feature and not a bug.

> On Fri, Sep 14, 2012 at 4:10 PM, Bryan Bishop <kanzure at gmail.com> wrote:
>> On Fri, Sep 14, 2012 at 1:49 AM, Mike Dupont wrote:
>>> I am willing to help with this process if there is interest , maybe
>>> for the next version of the license.

More information about the discuss mailing list