oshug

oshug@oshug.org

418 discussions

Fwd: [GOSH] open-source hardware definition.
by Bryan Bishop 16 Apr '10

16 Apr '10

Forwarding to the other relevant lists.. ---------- Forwarded message ---------- From: David A. Mellis <dam(a)mellis.org> Date: Fri, Apr 16, 2010 at 2:20 PM Subject: [GOSH] open-source hardware definition. To: gosh(a)piksel.no Cc: mako(a)atdot.cc, ayahbdeir(a)gmail.com Hey guys, At the opening hardware workshop at Eyebeam we went over many of the same issues that were discussed at GOSH, so I wanted to try to tie the two conversations together. In New York, we decided to start by defining open-source hardware in a way that those of us that practice it can agree to. We hope that this will help us to establish norms of behavior for those using the term, similar to the way in which the phrase "open-source" has a fairly clear meaning for software despite the fact that it is not trademarked or otherwise legally protected. I see this as complementary to the organization and trademark approach of OHANDA, and hope that both can help to define and promote open-source hardware. In particular, I wanted to get your opinions on the draft definition at <http://freedomdefined.org/OSHW>. This is a work-in-progress that attempts to explain what we mean when we say open-source hardware, in as straightforward a manner as possible. Comments? Suggestions? I know that OHANDA is using a modified version of the FSF's four freedoms, but I think there's room for multiple definitions, with varying perspectives or approaches, as in open-source software (e.g. four freedoms and the DFSG). Do you think this definition is something you'd be interested in supporting, as individuals, particular OSHW projects, or through OHANDA? David P.S. If you're interested in continued discussion and development of the definition, Ayah (in CC) should be able to add you to the opening hardware mailing list that we've been using. _______________________________________________ GOSH mailing list GOSH(a)piksel.no https://piksel.no/mailman/listinfo/gosh -- - Bryan http://heybryan.org/ 1 512 203 0507

1 0

Anatomy of contemporary GSM cellphone hardware.
by Andrew Back 14 Apr '10

14 Apr '10

A rather cool paper from GSM hacker (OpenBSC and OsmocomBB etc) Harald Welte: http://laforge.gnumonks.org/weblog/2010/04/14/#20100414-anatomy_of_gsm_cell… Will perhaps be good reading for anyone planning to attend the Open Source in Telecomms event on the 22nd that will have an OpenBTS presentation: http://ossg.bcs.org/2010/03/22/open-source-in-telecommunications-london-220… Cheers, Andrew -- Andrew Back mailto:andrew@osmosoft.com http://carrierdetect.com

1 0

Fwd: [open-science] Open Knowledge Conference (OKCon) in London on 24th April 2010
by Bryan Bishop 14 Apr '10

14 Apr '10

---------- Forwarded message ---------- From: Jonathan Gray <jonathan.gray(a)okfn.org> Date: Wed, Apr 14, 2010 at 1:25 PM Subject: [open-science] Open Knowledge Conference (OKCon) in London on 24th April 2010 To: open-science <open-science(a)lists.okfn.org> Hi, A quick reminder that this year's Open Knowledge Conference (OKCon) is taking place in London on 24th April 2010 - in 10 days time! There are still tickets left - and you can register at the following link: http://www.okfn.org/okcon/register/ Speakers and sessions include: * 'State of the Nation' Keynotes: - Matthias Schindler, Wikimedia (Germany) on 'Bibliographic Data and the Public Domain' - Glyn Moody, on the 'Post-Analogue World' - Peter Murray-Rust, on 'Recent Developments in Open Science' - Chris Taggart, on 'Open Local Government Data' - Sören Auer, on 'Linked Open Data' - Jordan Hatcher, on 'Open Licensing for Data' * Ideas and Culture with talks on analyzing 'Dickens Letters' and 'Making the Physical from the Digital' * Open Bibliographic Information with talks on 'The Itinerant Poetry Library' and the 'Journal Commons' * Community Driven Research with talks on 'Climate data' and 'Open Archaeology' * Civic Information with talks on 'Using Open Government Data to Profile Politicians' and the 'Straight Choice' * Open Government Data and PSI in the EU which looks at the current state of play in France, Norway, Germany, the UK and elsewhere * Tools with talks on 'Large-scale data handling and revisioning' with the Genome, Ontowiki, CKAN and more * Open Data and the Semantic Web with talks about South Korean DBPedia and Thesaurus Management Tool ‘Pool Party’ * Open Data in International Development including talks from PublishWhatYouFund and on OpenStreetMap in Haiti Further details are available at: http://blog.okfn.org/2010/04/14/okcon-2010-nearly-here-24th-april-2010-in-l… http://www.okfn.org/okcon/programme More information: * Main conference page: http://www.okfn.org/okcon/ * FAQ: http://www.okfn.org/okcon/faq If you have any questions please email Sara Wingate-Gray at sara.gray(a)okfn.org. We look forward to seeing people there! All the best, -- Jonathan Gray Community Coordinator The Open Knowledge Foundation http://blog.okfn.org http://twitter.com/jwyg http://identi.ca/jwyg _______________________________________________ open-science mailing list open-science(a)lists.okfn.org http://lists.okfn.org/mailman/listinfo/open-science -- - Bryan http://heybryan.org/ 1 512 203 0507

1 0

Fwd: [kanzure@gmail.com: [Open Manufacturing] Fwd: Non-assertion pledges... for (patented) open source hardware?]
by Bryan Bishop 06 Apr '10

06 Apr '10

Another view on the issue follows. ---------- Forwarded message ---------- From: Jon Phillips <jon(a)rejon.org> Date: Thu, Mar 25, 2010 at 4:59 PM Subject: Re: [kanzure(a)gmail.com: [Open Manufacturing] Fwd: Non-assertion pledges... for (patented) open source hardware?] To: "Hard- and Software Development, Kernel, Distribution, Roadmap" <developer(a)lists.qi-hardware.com> That list may very well be a blackhole, but the people on the other end at CC are my friends. I'm working on this part of the puzzle pretty actively right now, esp. after getting a core dump from many working in the space at Opening Hardware at Eyebeam last week: http://scienceblogs.com/commonknowledge/2010/03/open_hardware.php Basically, for our vices, there are two parts I believe we need for whatever we want to call OPEN/PUBLIC patents. I'm preferring the PUBLIC PATENTS concept right now, basically to try and make easier/more clear patents so that anyone can use them and not get sued, or rather, to try to make sure that anyone can build upon hardware and software innovation without the fear of litigation. So, what I think we need is: 1.) a place where patents of all forms can be publicly disclosed loudly and with a disclaimer for those submitting patentable ideas which have, at least in the USA, a 1 year grace period on being registered, so that the public can be assured that in that 1 year grace period, the patentable idea will not be submitted as a patent, or if it is, it is released under the/a public patent license. After that 1 year, the patentable idea (that is not patented), is available for anyone to use if not patented...which leads to next point... 2.) A Public Patent License which basically allows for any patent to be used safely by the public. This would be useful for old patent portfolios and if one spends the money to patent something and then to release under a public patent license. Right now, what I can source is that best path for COPYLEFT hardware projects (and those feigning with the weak terms OPEN HARDWARE, FREE HARDWARE, OPEN SOURCE SOFTWARE and OPEN SOFTWARE), is to publish loudly on public channels when new innovation happens (details on this to be decided of course). Qi-Hardware wiki is a great community resource for this, as well as your blog, or other places. Publishing loudly publicly provides prior art for this type of 1 year grace period to occur. I'm working on a new public project with some of the actors in the space if anyone here is interested...My goal is to create such a site for all sorts of freeing of patents, and also to insure Science Commons/CC create a very functional and useful public patent license that people can use. Let's call that the PPL (Public Patent License)...or as I'm saying: patents for (the) PPL (people). I must admit, I'm not precise on my terms around patents and my above knowledge is forming mostly around patents in the USA. But, to get patents right internationally, thats even more fun. For now, my concern is really about getting a clear path on a solution for those worried about patents or working in our FLOSS and COPYLEFT HARDWARE communities. Please rip my statements to shreds and/or provide some counterpoints...and, when this is annoying, we can post up more to the cc-patents list. jon <topPost /> On Wed, Mar 24, 2010 at 7:41 PM, cristian paul peñaranda rojas <paul(a)kristianpaul.org> wrote: > ----- Forwarded message from Bryan Bishop <kanzure(a)gmail.com> ----- > > Date: Wed, 24 Mar 2010 14:17:12 -0500 > From: Bryan Bishop <kanzure(a)gmail.com> > 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 > Subject: [Open Manufacturing] Fwd: Non-assertion pledges... for (patented) > open source hardware? > > 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 > > -- > You received this message because you are subscribed to the Google Groups "Open Manufacturing" group. > To post to this group, send email to openmanufacturing(a)googlegroups.com. > To unsubscribe from this group, send email to openmanufacturing+unsubscribe(a)googlegroups.com. > For more options, visit this group at http://groups.google.com/group/openmanufacturing?hl=en. > > ----- End forwarded message ----- > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > > iEYEARECAAYFAkuqzWQACgkQOAZrK37R8yKSNACg4yJqmAGpAYYuEa13epsNlygD > 8jwAmwWL9BzSaKVxjqb1Gp/ZP/8sNbem > =M+XW > -----END PGP SIGNATURE----- > > _______________________________________________ > Qi Developer Mailing List > Mail to list (members only): developer(a)lists.qi-hardware.com > Subscribe or Unsubscribe: http://en.qi-hardware.com/mailman/listinfo/developer > -- Jon Phillips http://rejon.org/ http://fabricatorz.com/ internet: @rejon + skype: kidproto +1.415.830.3884 (sf/global) +86.134.3957.2035 (china) _______________________________________________ Qi Developer Mailing List Mail to list (members only): developer(a)lists.qi-hardware.com Subscribe or Unsubscribe: http://en.qi-hardware.com/mailman/listinfo/developer -- - Bryan http://heybryan.org/ 1 512 203 0507

3 2

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