2016-2018 Board Nominees

Become an OSHWA member today to vote on nominees!

This year, we have 5  open seats on the OSHWA board. Board members will hold a 2-year position. Once board members have been chosen by the community, the board will appoint a President, VP, and Secretary. As every nominee answered “Yes” to having 5 hours a month to give to the board, we did not include that question in each nominee’s data. Board responsibilities include fundraising, advising on goals and direction, and carrying out compliance of the organization’s purposes and bylaws. The vote will be open on Oct. 16th through Oct 18th. Since the post is so long, here is also a .pdf spreadsheet of the nominees. Members will be emailed a link to vote. Here are the nominees in alphabetical order:

Harris Kenny                                                                                                                  

Why do you want to be on the board?

I believe in technology and culture that respect user freedom. I believe in what OSHWA is doing to advance these values, and that I could contribute a board member. As a board member, I would work to both execute current projects (e.g. OH Summit, certification) and also bring new ideas to help improve and grow OSHWA.

First, I believe there is room to expand OSHWA’s use of Free and Open Source tools in its operations as an organization. I feel I could most effectively advocate and implement this on the board, by both contributing and helping channel organizational and community resources to get it done. I personally use GNU/Linux and Free Software and would enjoy expanding the use of these tools by OSHWA.

I believe there is an opportunity to expand the resources OSHWA makes available to corporate members to help them grow their companies. For example, I recently started participating in the Open Source Design community and see great opportunities to share knowledge from groups like this and offer their expertise to OSHWA corporate members.

Finally, there a growing number of hardware companies being started thanks to 3D printing, however they are unfamiliar with Open Source Hardware. My work in the 3D printing industry and position on the board would help me advocate Open Hardware to those companies and (hopefully) increase their participation in the new OSHWA certification program.

It would be a privilege to join the OSHWA board. Thank you for your consideration!

What qualifies you to be a board member?

I am firmly committed to Open Source Hardware, Free Software, and Libre Innovation. I would bring this perspective to the board, continuing the progress OSHWA has made since its founding. I also believe my professional and educational experience are qualifications that make me a good fit for the board.

Professionally, I have demonstrated my commitment to Open Source Hardware during my nearly three years at Aleph Objects, Inc., a Free Software, Libre Innovation, and Open Source Hardware company and maker of the LulzBot line of desktop 3D printers. As Vice President of Marketing, I have had the privilege to help build the company as the 17th hire and first full time marketing hire, up to 140 employees (and growing!) today.

I am about to complete a MBA from the University of Denver. This education and my past professional experience in management and ERP consulting enable me to bring business insights to both help run OSHWA as an organization and help understand the needs of its corporate members.

Through my MBA, I have experience consulting with an organization that has a working board like OSHWA. I know how important it is for the board get things done to serve its members and grow the community. I recognize that joining the OSHWA board will mean work, and I welcome that.

Overall, I encourage members to consider commitment to Open Source Hardware as the most important qualification for the board. While I do have this, there are many others in the community who share these values and I would be proud to support them on the board if I am not selected.

Luka Mustafa                                                                                                                 

WHY DO YOU WANT TO BE ON THE BOARD?

To contribute towards making open hardware the de-facto way in the field of technology and thus cultivate the global development bringing together the best of many awesome technical developments that exist today. I believe we should collectively move towards transferring the success of open hardware for the maker movement into industry and everyday products we use. Open hardware is now in the position to significantly change they way we think about technology though four key topics: Open is Future-proof, enabling modification and upgrades of products, extending the lifespan of devices and making them more suitable for a larger number of users and empower them to be a part of the product more then from the passive user perspective. Open enables Collaborative-design, thus fundamentally shifting the manufacturer/user dynamics from one way communication to a joint effort to create the best solution. Open drives Fair-production on a significantly more fundamental level then simple transparency that is already becoming a norm, gaining trust of users though sharing the information and thus bear the collective responsibility of all technology users. Open means Total-ownership, contrasting a number of recent bad practices in industry where users are merely leasing the devices from the manufacturer cloaked under the normal sale and directly prohibiting the right to fix and modify for personal use. I wish to be on the board to drive the discussion on moving forward with open hardware outside the scope of maker movement and applying it to a larger number of products in our life.

WHAT QUALIFIES YOU TO BE A BOARD MEMBER?

The past 5 years I have dedicated to exploring open hardware from a number of different perspectives and projects and am currently a Shuttleworth Foundation Fellow and the founder of Institute IRNAS Race based in Slovenia, Europe dedicated to applying scientific advances to practice though open hardware. I have initiated the development of open source wireless optical communication system http://koruza.net that enables 1Gbps/10Gbps connectivity with light between buildings, set the development direction for http://goodenoughcnc.eu project to create affordable and self-replicating CNC machines on a global scale as well as a number of more scientifically oriented projects ranging for Symbiolab open hardware biolaboratory, a more recent development Vitaprint 3D printer for bio applications. I have been speaking at a number of scientific and open hardware events and evaluate the use of open hardware though my projects not only from the technical but also economical and legal perspectives. As well I am active in the Community wireless networking field though project http://wlan-si.net and have organized one edition of the largest annual event in this field, the Battlemesh V8 conference. My CV can be found on the following link: http://irnas.eu/team

Abhishek Narula                                                                                                               

WHY DO YOU WANT TO BE ON THE BOARD?

An artist engineer and an engineer artist, I am interested in exploring the space created between the intersection of art and technology. I use open source technology as a way of setting a critical lens on technological innovation. Through this I try to show how we interact with technology and also how we interact with each other. Being on the board will allow me to further explore these issues with the community at large. I also want to create an active community that uses technology as a medium for creative expressions and the arts. Being on the OSHWA will help me with this objective.

WHAT QUALIFIES YOU TO BE A BOARD MEMBER?

In our current situation, we are faced with many problems that pertain to the environment, education, societal justice etc. and the only way to address these is through collaborative communities. These communities can only be effective if they have access to free and unabridged information. Any systems and processes that hinder such conditions are not only anti-humanity, but in my humble opinion should be confronted, criticized and defeated with all our fervor. My background in electrical engineering, art and business give me the skills to contribute to the sustainability of the open source hardware community. A big part of my practice is based around community engagement, especially around the tools that I build and use. If elected on the board, I will be able to leverage this to further advance the objectives of OHSWA.

Nadya Peek                                                                                                              

WHY DO YOU WANT TO BE ON THE BOARD?

I believe technology to be a democratic tool. To enable this, I believe in creating reusable, modular, extensible, interoperable, and accessible technologies. Specifically, I believe in creating infrastructural technologies that can serve any (unintended) application. The Internet is a previous example of a successful infrastructure (providing a platform for applications such as the world wide web, email, or VOIP). Crucially, internet standards were open, free, and iteratively created by a community of practitioners. I believe Open Source Hardware can (and sometimes already does) fulfill similar infrastructural needs. Especially with excitement and progress around internet of things, self-driving cars, data-driven insights, robotics, or digital fabrication, I believe it is crucial to create, maintain, and improve free and open standards and to prevent walled gardens or silos of technology. Maker culture champions broader-base participation in technology, and I want to work on making sure that participation makes real lasting changes. I would like to serve on the board of the Open Hardware Association as I believe it to be an organisation uniquely focussed on developing, discussing, and disseminating open standards for technology.

WHAT QUALIFIES YOU TO BE A BOARD MEMBER?

I have been actively developing open source hardware for the past decade. I develop open-source fabrication technology under the Machines that Make project, and develop open-source machine controls and software at MIT’s Center for Bits and Atoms. I have worked on many engineering teams including for aerospace, manufacturing, medical devices, and architectural applications. I have helped set up more than 50 Fablabs and makerspaces throughout the world, giving me ample experience with how many different kinds of people interact with many different kinds of technology. I am one of the organisers of the annual global Fablab conference and am familiar with event planning and fund raising. I am an advisor to the Fab Foundation (a non-profit that globally facilitates fab labs), a judge for Hackaday’s prize, and on the editorial board of HardwareX, Elsevier’s open access journal focussed on open hardware. I have spoken about hardware and manufacturing on many occasions including at the White House, Solidcon, HOPE, and Chaos Computer Club Congress. I have a PhD from MIT and am in a band called Construction.

Luis Rodriguez                                                                                                              

WHY DO YOU WANT TO BE ON THE BOARD?

I see the open source hardware movement as a complete necessity for the future of the overall Free and Open Source movement. There are two key principles I’d like to ensure our community understands, 1) Open Hardware development is a key requirement to the success of the open source community 2) Open Hardware development is very likely where the best evolutionary methodology for the combination of best hardware and software will come about.

I’d like to help connect the open hardware community with FOSS projects and ensure nothing stands in between the two.

I have written about this here:

http://www.do-not-panic.com/2016/01/why-open-hardware-must-succeed.html

WHAT QUALIFIES YOU TO BE A BOARD MEMBER?

I’ve been working on the Linux kernel community for over 10 years now and have been in the trenches on dealing with companies addressing all regulatory concerns to support 802.11 drivers openly without firmware, and when firmware was required convinced companies to release firmware as open source. 802.11 was one of the last frontiers for getting proper support from vendors upstream on Linux, the experience gained in successfully addressing both legal challenges and Fear Uncertainty and Doubt in the industry over FOSS with wireless technologies should prove useful for helping the open hardware movement when faced with similar problems in the future with newer technologies.

I have also previously worked for a large non-fab silicon company, and have seen the issues we face in the community with both a largely patent encumbered world, and the limitations this imposes in our ecosystem.

I’d like to proactively help the open hardware movement by doing R&D in forecasting and addressing possible issues before they come up and connecting communities in the collaborative world as best as possible.

J. Simmons                                                                                                                 

WHY DO YOU WANT TO BE ON THE BOARD?

TL;DR – I think it is the right thing to do…

In 2009 I founded Mach 30 with a group of like minded individuals in order to develop open source spaceflight hardware. From the outset, I was on the lookout for others developing open source hardware of any kind so we could support each other under the belief that a rising tide helps all ships.

The moment I heard about the first Open Hardware Summit I made sure Mach 30 sent representatives so we could begin to connect with the larger OSHW community (we have been at every OHS since, except Rome). Later, when the OSHW movement’s leaders started work to form OSHWA, I shared Mach 30’s public documentation on our experience incorporating as a 501c3 public charity in the hopes that OSHWA could benefit from the lessons we learned when we incorporated.

And, now, I feel it is time to make the next step in showing my support for the OSHW community by stepping up to becoming a member of the board of directors.

WHAT QUALIFIES YOU TO BE A BOARD MEMBER?

I have been involved in non-profits for the majority of my life. I spent much of my school age years volunteering in community theaters, taking on roles on and off stage. I then went and got my undergraduate degree in technical theatre, which included courses in theatre (read non-profit) management. I applied all of these experiences to volunteer work in theatre until 2006.

Since 2009, I have been the president of Mach 30 (mach30.org), a non-profit dedicated to developing open source spaceflight hardware. As the president of Mach 30, I have run well over 100 business meetings (documenting these meetings with the same care we document our OSHW projects), worked on projects ranging from distributed Yuri’s Night celebrations (https://www.youtube.com/watch?v=y4TLxWVTIgM) to the development of OSHW projects like a rocket test stand (https://opendesignengine.net/projects/shepard-ts), and presented about OSHW at multiple Open Hardware Summits. You will also find some of my writing about OSHW documentation practices in Alicia Gibb’s book “Building Open Source Hardware”.

Matthias Tarasiewicz (parasew)                                                                                      

WHY DO YOU WANT TO BE ON THE BOARD?

I want to work on communicating Open Hardware to non-engineers and work on cultural aspects of Open Hardware communities, such as we did in our recent Book “Openism – Conversations in Open Hardware”. I want to contribute with our institute (RIAT) which is located in Vienna, Austria. I can help to organise and communicate European issues and be a contact point for European initiatives.

WHAT QUALIFIES YOU TO BE A BOARD MEMBER?

I am active in communicating Open Source Hardware and Open Source in general since more than 10 years. I am publishing books and articles about open culture and i am located in Europe, which would make me an ideal board member for European issues. I was the coordinator for the European Union project “AXIOM”, the first Open Hardware professional cinema camera and i am still very active in this project, so i know about the issues and challenges of Open Hardware design/development/distribution/fundraising, etc.

Michael Weinberg                                                                                                             

WHY DO YOU WANT TO BE ON THE BOARD?

To continue working on the OSHWA open source hardware certification.

WHAT QUALIFIES YOU TO BE A BOARD MEMBER?

“Qualifies” may be a strong word, but I have been on the board for the last two years and OSHWA hasn’t caught on fire. I’ve also done some of the work on the new open source hardware certification. In the interest of full disclosure, I’ll probably keep doing that even if I’m not on the board.

 

Become an OSHWA member today to vote on nominees!

OSHWA 2016-2018 Board Nominations Open!

OSHWA is looking for 5 new faces to join the board of directors for the Open Source Hardware Association. The nominee form is for self-nominations only. Please fill out the nominee form to become a nominee or forward the link to someone you want to nominate. Do not fill out the form for someone else. The purpose of this form is to tell voting members why you want to server on the OSHWA board. We will be publish the nominees and their answers on Oct. 14th. Board members hold a 2-year position. Once board members have been chosen by the community, the board will appoint a President, VP, and Secretary. Board responsibilities include fundraising, advising on goals and direction, and carry out compliance with the organizations purposes and bylaws. See the board member agreement to get a sense of the responsibilities. Board members are expected to adhere to the board attendance policy and come prepared having read the board packet. Board members are expected to spend 5-10 hours of time per month on OSHWA. Nominees can meet current board members who are present at the Summit on Oct. 7th to ask questions or submit questions to info@oshwa.org. Nominations will be open until Oct. 14th.

Nominee form.

Member voting will take place Oct. 16-18. Want to vote in the election? Become a member! Please note that only individuals can vote, corporate members cannot.

October IS Open Hardware Month

October is Open Source Hardware Month. You are invited to participate in events that will add clarity to the open source hardware definition, grow contributions to the movement, and provide education around how to publish a project or product as open source hardware.

Open Hardware Summit

The Open Hardware Summit is just a week away! OSHWA will be hosting our annual Open Hardware Summit in Portland, OR on October 7th. OSHWA is launching the Open Source Hardware Certification at the Summit. Tickets to the Summit are still available but going fast. See you in Portland!

OSHW Certification

OSHWA will launch the first version of the open source hardware certification. This is an open source hardware certifications administered by OSHWA. This certification is designed to benefit at least two parts of the open source hardware community.

First, it benefits purchasers of open source hardware by making it easy to identify truly open source hardware in the marketplace.  Projects and products obtaining certification and displaying the certification logo clearly communicate a commonly agreed upon definition of openness with customers and users.  While certification is not a condition for openness, obtaining certification is a way to make it clear to others that a given project is open source hardware.

Second, the certification benefits creators of open source hardware.  By giving creators specific guidelines, certification allows open source hardware creators to confidently declare their projects and products as open source hardware.  Certification also allows creators to defend that declaration by pointing to compliance with specific criteria defined in the certification process.

Users will self-certify compliance in order to use the certification logos.  Self-certification will give creators the right to use the OSHWA open source hardware certification logo.  As part of the self-certification process, creators will agree to subject themselves to penalties for non-compliance.  OSHWA will be responsible for enforcing those penalties.

Documentation Days

Throughout the month of October, OSHWA will be hosting several documentation days for anyone, individual or company to participate. Documentation Days will be free, community organized events to document your most recent open source hardware project following the OSHW definition and guidelines. This is the perfect time to document that project you just haven’t gotten around to open sourcing. Look on the events page for documentation days in your community throughout October. Or host your own Documentation Day! Follow us onTwitter or Facebook to stay tuned to the action.

Join OSHWA Today!

The Open Source Hardware Association is a 501(c)3 non-profit organization dedicated to being the voice of the open hardware community, ensuring that technological knowledge is accessible to everyone, and encouraging the collaborative development of technology that serves education, environmental sustainability, and human welfare. Become a member of OSHWA today! Board nominations and voting will happen soon, members get voting rights!

Documentation Days – Host your own!

oshwa-documentation-day-wbg-01

What is Documentation Day?

Throughout the month of October, OSHWA will be hosting several documentation days for anyone, individual or company, to participate. Documentation Days will be free, community organized events to document your most recent open source hardware project following the OSHW definition and guidelines. Look for documentation days from OSHWA’s board members and branches in their communities throughout October. Follow us on Twitter or Facebook to stay tuned and for dates and locations of our events and look for updates on our blog.

Why Documentation Days?

October is Open Source Hardware Month. This is the perfect time to document that project you  haven’t gotten around to documenting but want to make it open source. Documenting your hardware is the most important step in open sourcing your hardware because it gives other people a way to use, build upon, and possibly improve it. Your well-documented designs will live on and take various shapes as other people use them, create derivatives and share them. It is much easier to ask the community for help or find collaborators with well-documented hardware.  Publishing your design files publicly can also establish your hardware as prior art.  If someone attempts to patent something similar, that prior art can prove that the hardware existed before the patent application, thus preventing it from being granted.  Finally, more open source hardware documentation will set an example for others to open source and document their hardware!  This year’s Documentation Days will help standardize key elements of good open source hardware documentation.

To bolster the community-written Open Source Hardware definition, OSHWA is launching the open source hardware certification in October as well. Take this opportunity to read about the certification and join the movement.

Who can host a Documentation Day?

Anyone can host a documentation day! OSHWA’s board members will be hosting documentation days in various locations, but we can’t be everywhere. It is unlikely that OSHWA will be able to help with costs of a documentation day, but below are some tips to keep it cheap.  

How do you set up a documentation day?

Find a venue that has tables and chairs. Your local hackerspace may be a wonderfully aligned space to host a documentation day (and hopefully will not charge you a venue rate!). Public libraries may have free meeting rooms as well. Make sure the venue has lots of outlets for laptops – you may need to supply power strips.

Work with the venue to solidify a date. Send the date, time, location, and other details of your event to info@oshwa.org and your event will appear on the OSHWA Events page. If you’d like some physical handouts, include your mailing address.

Set up a way to RSVP (Email, Meetup, Eventbrite) if necessary. This is optional. You know your local area better than we do.

Use this logo when promoting your event: 

oshwa-documentation-day-wbg-01

Promote the event. The event must be a free, public event. Tweet @oshwassociation and we will retweet your event. Use hashtag #DocumentationDay.

Day of event:

  • Thank people for coming, introduce your documentation day as part of OSHWA’s Documentation Day series. Show slides and materials given to you by OSHWA. Point people towards oshwa.org and certificate.oshwa.org with questions.
  • After documenting hardware projects, ask people to use hashtag #iopensourced and #oshw and link to what they’ve documented.
  • Document the documentation day!  What worked?  What didn’t?  Did you and your participants develop any systems, processes, or templates that made creating documentation easier?  Be sure to share them with the larger community.
  • Don’t forget to clean up the venue at the end of your event.

White House’s Maker to Manufacturer Event

Open Source Hardware Breakout Session
Open Source Hardware Breakout Session

I was honored to lead a breakout session for the Maker to Manufacturer event hosted by the White House’s Office of Science and Technology. As the Executive Director of OSHWA, my break out session was on Open Source Hardware innovation. This is my take away from the individual viewpoints expressed by the group, highlighting what we can do as a community, as an industry, and from government and university perspectives. Below are the unedited notes from this breakout session. These ideas came from the collective participants in the breakout session and the views and ideas do not reflect those of the White House.

Our group discussed innovation through open source hardware through cross pollination in the open hardware community, industries, granting organizations, universities, and other institutions. In this way we can change what innovation looks like.

As a community, open source hardware needs to better explain the value proposition to the above listed institutions. We need to clarify the licensing around open source hardware, which OSHWA hopes to take a step toward with our certification process launching in Oct. With help, there could also be a database that grows out of the certification process with a space for contributing back and tracking changes. We need to offer educational experiences for policy makers and illustrate the social change and rapid innovation happening around open source hardware.

Within the government, the open source hardware community would like to be part of any process that might create limits though broad regulation around IP and hardware. We would like to see rethinking the standards and create scalable standards and taxonomies for open source hardware. We think it’s best for conversations in this space to strategically chose particular hardware fields to introduce, educate and change with open source hardware. Tax incentives for people to share their source publicly for the good of rapid innovation, foregoing a monopoly, would be well received in the community. Finally, we need the attention of the USPTO to alter the landscape of IP and be aware of open source prior art.

From a university perspective, a change must happen in the tech transfer offices for innovation to move forward at a university. Too often universities have IP constraints stemming from the Bayh-Dole Act which prohibits other inventions coming out of tax payer funded research and can even prohibit the inventor from continuing to innovate.

From an industry perspective, having a standard business case, such as royalties for creating a copy or derivative, would create a mutual respect. An understanding that risk adverse IP practices such as patents has a trickle down effect on innovation. In particular, open chipsets would be more useable. Industries could benefit from an open toolbox of the first 1,000 common pieces needed for any project, or a ‘simple things’ database containing source for the building blocks would be useful. In some industries also sharing test results with the source would be helpful.

At OSHWA we are reaching out to these four areas, community, government, university, and industry to assist in the changes reflected at this meeting.

Notes from the day, taken by Stephanie Santoso:

How do you innovate with open source hardware?

Moderated By Alicia Gibb, OSHWA

 October is open source hardware month

 We’re primed to create value with the public- we have lots of things that we can do.

Open source hardware is more of an IP concept. What policies currently stand in the

way of open innovation?

 University ownership of IP is a big one.

 Open source software- you know what the license is, you understand what it takes; but

with Creative Commons- you don’t even know what that means. It’s not clear what it is.

Hardware is weird because you can’t license it unless you have a patent. In October,

OSHWA will announce a certification (a trademark) to help Makers and entrepreneurs

understand the steps that they need to take to make sure their products are open

source based on OSHWA’s specific definitions.

 Matt: What does this do for the feedback loop for users? Ex. Bizzy box (sp?)- users

weren’t contributing content back to the community. What is the feedback loop which

incentivizes people to contribute the modifications back to the community?

 It would be great to have a clearly defined record system where you can track changes-

like a Github for hardware. When we look at open source hardware- we should look at

components- and what components you can open source too. Would be great to have

representatives from the semiconductor industry present at future conversations around

Maker to manufacturer. If they were repurposed to be reusable, this would be great.

Schematics for semiconductors are already available. Autodesk is creating a platform

where you can take modular components of your hardware design using an Autodesk

software platform and make them more openly accessible.

 Venkat: Would be great to have a database of open source hardware that makers in

makerspaces can use, so people know what’s already out there and available.

 Think about Texas Instruments- what’s the business case for a company to do open

source hardware? Why would TI or Intel care? You’d need to shift their mindset of how

they measure value- often its patents, but what about getting institutions to value

people who either develop open source hardware or contribute to open source hardware

projects in a similar manner?

 Frank Gayle: Should talk to NIST about how we think about standards. Michelle: we

should talk about taxonomy and how open source hardware fits.

 Fernando: I come from the pharma sector, which is different because it’s harder to

make a product mature. What’s the conceptual framework that moves us in this

direction? We don’t even have material property databases.

 What about procedural processes? It’s hard to divide these processes into specific

pieces. There may be interest in small scale manufacturing, but for large scale

manufacturing, we need to rethink this.

 Open source community- benefits will come for makers who are producing smaller scale

products. We are seeing that individuals are contributing to the open source hardware

community as a way to create a personal brand in some sense- open source represents

a certain set of values. Ex. We are seeing this on Hackaday’s open source project

platform

How might we screw this up?

1) Not explaining the value proposition well

2) Speed to market trumps the IP value proposition- we should remember this. Sometimes

patenting isn’t the best use of your time because things are happening so fast and you

want to make it to market.

3) Regulations- be careful of this- regulations aren’t necessarily a bad thing, but we should

have an active role in providing input and engage with regulators very early on.

4) Not being about to create an effective cost model. If there’s an acknowledgement that

there is a publicly available use of technology for the process, then you can better justify

this to the organization.

5) Failing to recognize that huge social change may be required in order for organizations

to embrace open source hardware. Ex. Navy can be generally hesistant and risk averse.

If you want create something new, it can be an incredibly long approval process. In

some cases, it makes sense to acquire something from outside of the organization than

try to create something in-house.

Announcing October as Open Source Hardware Month!

OSHWA would like to announce Open Source Hardware Month for the month of October 2016. OSHWA is inviting you to participate in events that will add clarity to the open source hardware definition, invite more people to contribute to the movement, and provide education around how to publish a project or product as open source hardware.

Some of OSHWA’s events are highlighted in the White House’s FACT SHEET on page 18: New Commitments in Support of the President’s Nation of Makers Initiative to Kick Off 2016 National Week of Making

Documentation Days

Throughout the month of October, OSHWA will be hosting several documentation days for anyone, individual or company to participate. Documentation Days will be free, community organized events to document your most recent open source hardware project following the OSHW definition and guidelines. This is the perfect time to document that project you just haven’t gotten around to open sourcing. Look for documentation days from OSHWA’s board members and branches in their communities throughout October. Follow us on Twitter or Facebook to stay tuned and for dates and locations of our events and look for updates on our blog.

OSHW Certification

OSHWA will launch the first version of the open source hardware certification. This is an open source hardware certifications administered by OSHWA. This certification is designed to benefit at least two parts of the open source hardware community.

First, it benefits purchasers of open source hardware by making it easy to identify truly open source hardware in the marketplace.  Projects and products obtaining certification and displaying the certification logo clearly communicate a commonly agreed upon definition of openness with customers and users.  While certification is not a condition for openness, obtaining certification is a way to make it clear to others that a given project is open source hardware.

Second, the certification benefits creators of open source hardware.  By giving creators specific guidelines, certification allows open source hardware creators to confidently declare their projects and products as open source hardware.  Certification also allows creators to defend that declaration by pointing to compliance with specific criteria defined in the certification process.

Users will self-certify compliance in order to use the certification logos.  Self-certification will give creators the right to use the OSHWA open source hardware certification logo.  As part of the self-certification process, creators will agree to subject themselves to penalties for non-compliance.  OSHWA will be responsible for enforcing those penalties.

Open Hardware Summit

In addition to the documentation days and certification, as always OSHWA will be hosting our annual Open Hardware Summit in Portland, OR on October 7th. Tickets to the Summit are available and we’re currently looking for speakers and sponsors.

Join OSHWA Today!

The Open Source Hardware Association is a 501(c)3 non-profit organization dedicated to being the voice of the open hardware community, ensuring that technological knowledge is accessible to everyone, and encouraging the collaborative development of technology that serves education, environmental sustainability, and human welfare. Become a member of OSHWA today!

Mach 30 Reimagines The Martian with Open Source

 logo-large-trans
by

Spoiler Alert: This post discusses several key details of The Martian.  If you haven’t seen the movie or read the book, you have been warned.

It might be argued that Rich Purnell, “steely-eyed missile man“, is the true hero of The Martian. But you know what else could have helped save Mark Watney (in a much smarter, more efficient way)? Open sourcing.

Let’s back the story up a bit before we get into the details. Mark Watney, played by Matt Damon, is an astronaut stranded on Mars after a dust storm forces his crew to leave him behind. As he does his best to signal to Earth for help and stay alive, NASA and a team of scientists work together to bring him home.

Read More on Mach 30’s Blog.

OSHWA Board Nominees

Become a member to vote on board members today! The vote will go out by email 9/29 and be open for 48 hours. Here are your nominees in no particular order.

Joel Murphy

My career and work have been supported by open-source hardware. I have benefitted greatly from the smart, creative products and tools made by open hardwarians. I would not be in the position that I am in today without the community. I am already giving back by offering two well received open hardware tools, and I would like to be more involved in helping Open Source Hardware organization build on its successes.

What qualifies you to be a board member?

I have had a close relationship with Open Source hardware for the past 10 years. I taught Physical Computing from 2006 to 2014, and saw the exponential rise in open-source hardware use and availability. I built a successful consulting company, Solutions Design, by providing design services to artists and inventors with open-source hardware products, and I am co-founder and owner of two open-source hardware startups: World Famous Electronics, LLC, maker of Pulse Sensor, and optical heart rate monitor for Arduino, and OpenBCI, Inc., a low cost, high quality EEG system. My experience as a teacher and evangelizer as well as an open hardware entrepreneur gives me multiple perspectives on the challenges and opportunities that the open source hardware community faces.
I have been to every summit, and have watched the organization grow toward a definition, and I’m excited to see and be a part of a successful implementation of the new certification.

I do not serve on any other boards at this time.

I will you be able to commit at least 10 hours a month to being on the board.

Katherine Scott

I believe Open Source Hardware can rapidly accelerate the development of art, science and technology, improve the education of engineers and lay people, and empower individuals to solve the world’s most pressing issues. We are quickly approaching the point where Open Source hardware designs are becoming much like their software counterparts; this is to say that smaller Open Source hardware projects often become the building blocks of much grander systems. I believe that the free, easy, and repeatable exchange of these designs, along with a distributed means of production, can dramatically improve the life of every person on the planet.

I believe these goals are ambitious, important, and revolutionary. I want to get into the nuts and bolts of making them happen; and I want to do it in a way that is bigger than what I can achieve on my own. In particular, I want to figure out how to make Open Source hardware projects, developers, and manufacturing easier to find and use. I also want to develop a pool of financial, legal, and practical resources that directly and actively promote the creation of great Open Source hardware. Finally, I want to work with a bunch of other awesome people who want to do the same thing.

What qualifies you to be a board member?

* I started an electronics manufacturing company / contractor manufacturer called Tempo Automation that uses both Open Source hardware and software. This means I am intimately involved with a large number of hardware projects (both open and closed). I have a pretty good view of where Open Source hardware presently fits in the world, and what strategic actions OSHWA can take to encourage wider adoption.

* In the course of my life I’ve been been a student, an autodidact, a researcher, a business woman, and an educator. I believe I can be an advocate for all of these groups and effectively articulate their needs.

* I’ve taken a few start-ups from nascent ideas on the back of a napkin to working businesses rather quickly. I want to use these same skills to increase OSHWA’s budget and further the adoption of Open Source hardware.

* I used to run a pacifist co-op while working as a research engineer for a defense contractor. I have a great deal of experience mediating between disparate views to find consensus.

* I’ve reached the point in my personal growth where I feel my time is best used helping others realize their own projects rather than working on my own.

I do not serve on any other boards at this time.

I will you be able to commit at least 10 hours a month to being on the board.

Dan Grigsby

If the messages at this year’s Open Hardware Summit from Joshua Pearce on making open hardware the new standard in science and Tom Igoe on expanding open hardware from “for us by us” to the mainstream are themes you’d worked on by the Association then I’m the board member for you.

What qualifies you to be a board member?

Making open hardware the new standard is science is largely a matter of policy. My work to influence public policy includes Federal issues such as defeating SOPA/PIPA, patent reform and net neutrality. At the state level, I was appointed to terms on the E-Government Advisory Council by the Speaker of the Minnesota House and to the Advisory Commission to the Minnesota Science and Technology Authority by the Commissioner of the Minnesota Department of Employment and Economic Development.

Mainstreaming open hardware is an initiative for businesses. I have a twenty-year track record of building successful businesses using — and having those businesses contributing to — Open Source Software. I’m a business guy that shares your values.

What’s more, I’ve given back to my communities as a mentor and advisor; by teaching a tech-startup class that I authored at the University of Minnesota; and by co-founding what’s become a thousand member strong community of developers and entrepreneurs with Minnesota’s BarCamp and DemoCamp.

Plus, I sent a balloon with my kids picture to the edge of space and retrieved it. A selfie in space! How cool is that? Picture or it didn’t happen: https://www.dropbox.com/s/3jcdyvdn3x8h1qh/IMG_3731.jpg?dl=0

I currently serve on the Board of Directors for the Minnesota High Tech Association.

I will you be able to commit at least 10 hours a month to being on the board.

Tim Shepherd

To make sure that Open Source hardware gets the recognition that it deserves. I’m passionate about hardware development and feel lucky to be able to try and be apart of the Open Source Hardware community.

What qualifies you to be a board member?

 

Years of hardware development experience, both in industry and at home. This will be a key issue in making sure we all can access open source hardware.

I do not serve on any other boards at this time.

I will you be able to commit at least 10 hours a month to being on the board.

Alex (acme) D’Elia

To provide support for discussions, organisation, proposals and development of new Open Standards regarding Hardware.
Specially in relation to Future Internet Technologies and IoT arguments,
and in particular related to the layers of Network and Energy Infrastructures. We have started a Technical Table on IoT and we are open to suggestions and exchange of knowledge and work: http://www.cetri-tires.org/press/technical-tables/r-i-o-t-rifkins-internet-of-things/?lang=en

What qualifies you to be a board member?

The work I am doing every day, the projects I’ve started and the partners I am working with and which are involved in the projects are also really operative in the Open Hardware and Open Source Initiatives, in some cases, the groups are already actively working since decades for FLOSS. We are all actively involved in promoting an Open IoT Infrastructure to protect freedom and knowledge sharing, specially in respect to our future generation taking the burden of developing a more open society. For a short BIO consider http://root.acme.com

Regarding the commitment I believe I can devote 10+ hours from January 2016, while at the moment I don’t know how much time I have, depending on the tasks requested I can get organized, but now I select NO to the following box.

I am “Smart Grid director” for the CETRI-TIRES No-Profit Organisation and member of the IoT Council.

No, I will not be able to commit 10 hours a month to being on the board.

Michael Knowles

In my personal life I’m a “maker” and sculptor and frequently making use of open hardware to create new works, many of which simply wouldn’t be possible without some of the great open source works I’ve been able to leverage.

Professionally, I’m the IT Director of Fulcrum Technologies, an enterprise software company based in Seattle. I continue to see the IT industry being transformed by the advances of open source, both hardware and software, and find it genuinely exciting to be a part of.

Joining the board of OSHWA is an opportunity to take my twenty years of IT experience and use it to give back to an organization that is poised to advance an underutilized piece of the larger open source movement.

What qualifies you to be a board member?

I feel specifically qualified to be a successful board member of OSHWA for three main reasons:

* Having served on non-profit boards in the past, I understand the varied responsibilities that board membership requires in addition to having experience organizing, advocating and fund-raising.

* Working in the IT industry with both open and closed source products for more than 20 years, I understand the business impact that open source platforms can provide.

* I have personally benefitted from open source hardware in my art and feel I can appreciate the difference in advocating benefits between what works well for a business and what works well for non-business work. Being able to work with both of those audiences is a strength.

I served two years on the board of the Seattle Fringe Theater Festival, and participated on both their outreach and volunteer organizing committees.

Later I served two years on the board of Circus Contraption, and worked with their fund-raising committee though I am not participating on the boards of any organizations currently.

I will you be able to commit at least 10 hours a month to being on the board.

 

Jeffrey Warren

I’ve involved in many discussions at OSHWA about the open hardware community and open hardware intellectual property and legal matters — most recently in the discussions around an Open Hardware Certification model. I feel that my perspective on open source hardware strikes a balance between the functional argument that open hardware is a better way to create hardware, and the ethical position that we should have the right to examine/copy/modify/distribute designs — that open collaboration is a better model for our society. I believe deeply in community-driven processes, while also believing that for-profit organizations can — and stand to benefit greatly from — being “good open hardware citizens.”

Most of all, I believe strongly that the key to a healthy open source hardware movement is culture. We must continue and improve upon our open, discursive approach to open hardware, and to build strong norms to guide our work, so that we can continue to invent, collaborate, and benefit from one anothers’ work. This spans from good documentation to standards of design file publication, to refining the pace and practices of the actual collaboration in online forums, publication platforms, and even in-person meetings.

What qualifies you to be a board member?

I’ve served on the OSHWA board for 2 years, and have been deeply interested in open hardware both through my work at Public Lab, and as part of the broader free/libre/open source movement. Public Lab, a community of thousands of people engaged in collaboratively developing affordable and accessible environmental testing techniques and equipment, has been using the CERN Open Hardware License for several years, and I participated in the discussions and comment period which led to version 1.2 of that license. I am a producer and consumer of open source hardware and free/libre/open source software, notably as a lead developer of Public Lab’s DIY Spectrometer and associated SpectralWorkbench.org software suite (http://publiclab.org/wiki/spectrometer), as well as the Infragram multispectral camera (http://publiclab.org/wiki/infragram) and associated Infragram.org image compositing system. Since 2011, using our published designs and kits, over six thousand people have constructed their own spectrometers, and many have contributed back their refinements and additions. The size and scope of this project gives me key insight into how a diverse community of contributors can collaboratively tackle complex hardware design, and into the challenges of scaling such a model.

I’ve also served as the secretary of OSHWA, taking minutes on board meetings, and have missed almost none of the meetings over the past two years — making mine one of the best attendance records among current board members. I would be excited to continue to represent the interests of community-based open hardware contributors everywhere during an additional two years of service.

I am on the board of Parts & Crafts, a makerspace for kids in Somerville, MA, and on the advisory board of Personal Democracy Media’s WeGov project.

I will you be able to commit at least 10 hours a month to being on the board.

 

Members, please be on the lookout for the link to vote in your inbox today!

 

Nominations for OSHWA board member positions

OSHWA is looking for 5 new faces to join the board of directors for the Open Source Hardware Association. This form is for self-nominations only. Please fill out this form to become a nominee or forward the link to the person you wish to nominate for them to fill out. The purpose of this form will be to tell voting members a bit about yourself. We will be publish the nominees and their answers on Sept. 26th. Board members hold a 2-year position. Once board members have been chosen by the community, the board will appoint a President, VP, and Secretary. Board responsibilities include fundraising, advising on goals and direction and carry out compliance with the organizations purposes and bylaws. Board members are expected to attend all board meetings and come prepared having read the board packet. Board members are expected to spend 10 hours of time per month on OSHWA. Nominees can meet current board members who are present at the Summit during lunch on Sept. 19th. Board members Michael Weinberg, Toni Klopfenstein, Rose Swan Meacham and Addie Wagenknecht will remain on the board. Nominations will be open until Sept. 25th.

Nominee form.

Member voting will take place Sept 29-30. Want to vote in the election? Become a member if you’re not already! Please note that only individuals can vote, corporate members cannot.

2014 OSHWA Board Nominations Open until Oct. 15

OSHWA is looking for 2 new faces to join the board of directors for the Open Source Hardware Association. Please fill out this form to become a nominee or forward the link to the person you wish to nominate for them to fill out. The purpose of this form will be to tell voting members a bit about yourself. We will be publishing the nominees and their answers on Oct. 15th. Board members hold a 2-year position. Once board members have been chosen by the community, the current board will appoint a new President, VP, and Secretary. Board responsibilities include fundraising, advising on goals and direction, and carrying out compliance of the organization’s purposes and bylaws. Board members David Mellis, Star Simpson, Emile Patron, Jeffery Warren, and Addie Wagenknecht will remain on the board. We thank Danese Cooper and Windell Oskay for their years of service. Nominations will be open until Oct. 15th.

Nominee form.

Member voting will take place Oct. 20th and 21st. Want to vote in the election? Become a memberif you’re not already! Please note that only individuals can vote, corporate members cannot.