oshug

oshug@oshug.org

424 discussions

Fwd: Non-assertion pledges... for (patented) open source hardware?
by Bryan Bishop 05 Apr '10

05 Apr '10

---------- Forwarded message ---------- From: Bryan Bishop <kanzure(a)gmail.com> Date: Wed, Mar 24, 2010 at 1:17 PM Subject: Fwd: Non-assertion pledges... for (patented) open source hardware? To: GOSH! - Grounding Open Source Hardware <gosh(a)piksel.no>, Open Manufacturing <openmanufacturing(a)googlegroups.com>, diybio <diybio(a)googlegroups.com>, kanzure(a)gmail.com Hey all, I sent this email to the cc-patents mailing list. Supposedly that's where the CC groupies were to be gathering, but I haven't seen a response yet, and it seems like it might be a black hole (I hope not!) http://lists.ibiblio.org/mailman/listinfo/cc-patents Anyway, I am forwarding this email so that others (on the GOSH!, diybio and open manufacturing lists) can comment and provide whatever inputs they can. Thanks! ---------- Forwarded message ---------- From: Bryan Bishop <kanzure(a)gmail.com> Date: Mon, Mar 22, 2010 at 5:31 PM Subject: Non-assertion pledges... for (patented) open source hardware? To: cc-patents(a)lists.ibiblio.org, Bryan Bishop <kanzure(a)gmail.com> Hey all, I have found my way here from this page: http://wiki.creativecommons.org/Patent_Tools_Public_Discussion I was wondering about the non-profit-research-only non-assertion pledge tool mentioned on the page. I became aware of the patent tools discussion in light of the open source hardware community. Ayah Bdeir dropped a nice link for us to follow and lead us here. In particular, one idea that I have been kicking around (fed to me in part by Joe Rayhawk) for the hardware community is a non-assertion pledge for patent owners who wish to promote open source hardware. In this scenario, OSI, FSF, EFF, TAPR, CC, and DFSG principles would be written into a set of principles that would guide whether or not something is considered to be "open source" (in the hardware community sense). I am not sure how specific this would have to be or how impractical it presently sounds. The GNU General Public License v3 is very specific about redistribution, modification, etc., and the rights granted to the end-user. Would something equally verbose be needed at the center of this patent pledge scenario? >From the mile-high view, it seems that the non-profit-research-only specification is more stringent than the open source hardware community would prefer as a legal vehicle. Already we see businesses like Makerbot Industries licensing their content under CC-BY 3.0 and in some cases GPL, BSD, etc., deeper in the internal RepRap community. In this instance, there are no patents involved. But it would be easy to imagine a scenario where patents were involved from the onset. The proliferation of open source hardware in the commercial markets is really interesting, and IMHO worth investigating whether or not it would be possible. Yes, I understand that this is *not* the intent of the research non-assertion pledge currently on the CC wiki. In light of these ideas, and the recent "Opening Hardware" workshop in NYC, I was wondering if anyone has comments, thoughts and advice to share? Thank you! I also have many links to dump if anyone is interested in the topology of these communities at the moment, and what various projects are using for licenses, etc. - Bryan http://heybryan.org/ 1 512 203 0507 -- - Bryan http://heybryan.org/ 1 512 203 0507

1 0

Fwd: Apt-get for Hardware
by Bryan Bishop 05 Apr '10

05 Apr '10

---------- Forwarded message ---------- From: Bryan Bishop <kanzure(a)gmail.com> Date: Mon, Apr 5, 2010 at 1:22 PM Subject: Apt-get for Hardware To: austin-hacker-space(a)googlegroups.com, kanzure(a)gmail.com, Open Manufacturing <openmanufacturing(a)googlegroups.com>, Hackerspaces General Discussion List <discuss(a)lists.hackerspaces.org> Hey all, [this was originally sent to the Austin Hackerspace mailing list] I am presenting at Texas Linux Fest 2010 this Saturday (April 10th) on one of the projects I contribute to, dubbed SKDB. Essentially, it's apt-get for hardware. Registration for the conference is $40 and it's up at the Marchesa Event Center in Austin, Texas. Here's the scoop on the project (but some links first!): http://designfiles.org/dokuwiki/skdb git: http://designfiles.org/skdb.git irc: #hplusroadmap on irc.freenode.net irc logs: http://gnusha.org/logs/ and http://gnusha.org/irclogs.txt And in particular, the talk abstract: http://texaslinuxfest.org/talks/2010/apt-get-for-hardware/ """ SKDB is a method for sharing hardware over the internet. By "hardware" we mean not just designs for circuit boards, but also biological constructs, scientific instruments, machine tools, nuts and bolts, raw materials, and how to make them. You don't need to reinvent the wheel every time you begin a new project. Someone out there has probably already done most or all of the work for whatever you are trying to do, and then released the plans on the internet. There are many common tools and parts involved in making things. If only we could just "get" everything automatically from the web, DIY manufacturing would be much easier. Essentially we want to do something like "apt-get" for Debian or "emerge" for Gentoo, the Linux software package managers. SKDB simplifies the process of searching for free designs, comparing part compatibility, and building lists of materials and components and where to get them. You could even say SKDB is "apt-get but for real stuff". In SKDB, hardware is organized into packages. Packages are a standard and consistent way for programs to find data. Packages may contain CAD files, CAM parameters, computer-readable descriptions of product specifications, product-specific code, and bill of materials. For each part in a package there are a number of interface definitions, which describe how the part can connect with other parts, even parts from other packages. Each package also lists dependencies which have to be bought or built in order to successfully carry out a project. For example a drill press is required to make holes with a certain level of accuracy. SKDB downloads all of the dependencies automatically and compares them to your existing inventory, and generates instructions for your CNC machinery if you have any. """ There are some non-technical videos from a presentation I gave last December located here: http://gnusha.org/ .. Gnusha is an open source hardware co-op that I have working with. The text on the page is from an update email on 2010-01-12, and more recently there was a huge update in late March that I haven't sent out (still editing?). I also wanted to bring up an idea that I will be focusing on at the shop w/ Les. I think the linux kernel is a good starting point for running a fablab, machine shop, hackerspace, techshop, or even a lab. Essentially what I would love to have is, not only apt-get for hardware, but also machines hooked up to /dev on a server. So, maybe the laser cutter is mounted on /dev or otherwise through cupsd with a printer driver, or some hardware-over-network protocol if a machine is hooked up to EMC on a dedicated box. I'd also like to build something like /dev/parts for a vending machine of small parts- imagine calling up `cat` on a file and pipping it to a vending machine, and out pop your parts for a quickie project. For now, part bins are more efficient, but I suspect the (vague) idea is coming across. Anyway, it would be an interesting way of organizing a shop. A while back I had some silly shell scripts that I wanted to eventually, one day, work: http://github.com/kanzure/shelltrance/blob/master/shelltrance.txt .. but it's easy to spot how that shell script could be improved significantly (like, wtf is up with the call to `mail`). - Bryan http://heybryan.org/ 1 512 203 0507 -- - Bryan http://heybryan.org/ 1 512 203 0507

1 0

London: Open source hardware user group (OSHUG) (April 29th 2010)
by Bryan Bishop 05 Apr '10

05 Apr '10

Oh look, http://oshugxmos.eventbrite.com/ http://oshug.org/ "The primary goal is to provide an environment in which those with an interest in open source hardware can meet, share experiences and learn from each other. It is hoped that events will be shaped by the wider user group membership, and whilst meetings are initially being held in London, they could be held anywhere." """ Open Source Hardware User Group Event #1 An Introduction to XCore XS1 & Amino Open source hardware is an approach to building physical objects with the principle of allowing collaborative development, use and tinkering through the liberal licensing of artefacts such as manuals, software, schematic diagrams and CAD documents. Typical open source hardware projects range from simple electronic circuits to digital and radio systems, through reprogrammable computing platforms, to hardware that combines elements of electronic, mechanical and software engineering, such as 3D printers and laser engravers. This is the first of what is hoped will become a regular event for people with an interest in open source hardware. For the inaugural meeting we are fortunate to have presentations from Prof. David May FRS, CTO of XMOS Semiconductor, and Alan Wood of Folknology Labs. XCore XS1 (XMOS) David May will be known to many as architect of the transputer and author of the concurrent programming language, occam. As co-founder and chief technical officer of XMOS Semiconductor, he will be providing an introduction to the XCore XS1 microprocessor architecture and the associated development environment. [actual abstract TBC] XMOS is a fabless semiconductor company that develops multi-core multi-threaded processors designed to execute several real-time tasks, DSP, and control flow all at once. XMOS coined the term software-defined silicon, and this can be seen as midway between FPGA and MCU. However, unlike an FPGA there is no requirement for a complex HDL toolchain, and C and C++ can be employed in development, with XMOS extensions to C for concurrency (XC). Amino (Folknology Labs) Amino: a networked creator tool for hardware and software production. XMOS software-defined silicon technology serves to blur the line between software and hardware, and Amino uses this technology to further blur the line between prototyping and production. Amino is also Internet native, event driven and optimised for concurrency, and may be seen as a building block for networked open source hardware creation. Alan Wood - a.k.a. Folknology - originally trained in systems engineering, got lost in software engineering and open source for a decade, before returning back to his hardware roots via the open source hardware and makers movement that has gathered momentum over the last few years. Al's interest lay in pushing the envelope for open source hardware/software production and agility: "We are approaching a tipping point where open source and open creation physically changes the real world not just the virtual world. With Amino we are selling a creative tool, not a finished product. We are selling possibilities. The participant decides what runs on it, not us. We just give them as much as we can to help them through that process.". At the conclusion of the formal part we plan to head across the road to a pub, for open discussion and to plan future events. Note: * Due to security arrangements it is vital that people arrive on time, or if possible slightly early - any time from 17:45 is fine. If there is nobody on reception please call 020 7960 1771 for access. * If capacity is reached and you would like to attend please contact us, we'll put you on a waiting list and may arrange a larger venue if there is sufficient demand. """ http://oshug.org/cgi-bin/mailman/listinfo/oshug Hopefully they will be interested in collaborating with the broader open source hardware community: http://groups.google.com/group/openmanufacturing http://groups.google.com/group/diybio https://piksel.no/mailman/listinfo/gosh etc. - Bryan http://heybryan.org/ 1 512 203 0507

1 0

Test.
by Andrew Back 29 Mar '10

29 Mar '10

A test to the new oshug(a)oshug.org discussion list -- ignore. Cheers, Andrew -- Andrew Back mailto:andrew@osmosoft.com http://carrierdetect.com

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

oshug