Author: michael

This blog post is an update for the OSHWA community about the 2019 Open Hardware Summit in Shenzhen, October as Open Hardware Month, and how OSHWA will think about Summits going forward.

The tl;dr version of this post is:

1. OSHWA will not be holding the Open Hardware Summit in 2019
2. OSHWA will be encouraging locally-organized events and gatherings across the globe as part of Open Hardware Month this October (email us at info@oshwa.org if would like to host one!)
3. OSHWA will shift the Summit to the spring starting in 2020. The Summit will also be held in the same city for at least 3 years starting in 2020.

There is a lot to unpack here, so let’s get to it.

2019 Open Hardware Summit in Shenzhen

At the end of the 2018 Summit OSHWA announced that it would be holding the 2019 Open Hardware Summit in Shenzhen, China.  Shenzhen has a vibrant local community of open source hardware enthusiasts. Many members of the OSHW community were also very excited for the opportunity to travel to a location that is so central to manufacturing innovation.

Unfortunately, in 2017 China implemented a law governing the activities of non-Chinese NGOs operating in China.  This law created a number of bureaucratic hurdles for organizations like OSHWA that were interested in holding events in China.

Among other things, the law requires OSHWA to find a local Chinese Partner Unit (CPU) willing to act as our sponsor for the Summit.  CPUs can only be certain types of organizations, such as universities or registered Chinese NGOs. Companies cannot serve as CPUs. The CPU must also be willing to undertake a significant number of bureaucratic steps to officially register the event and coordinate with local authorities.  In addition to the process required of the CPU, OSHWA itself would have to undertake a significant and burdensome number of steps to collect, verify, and provide paperwork to Chinese authorities (see this article “Reams of Paperwork: Preparing Documents to Get Official Status in China” and the checklist we prepared here for a sense of what is involved).

OSHWA has spent the last few months trying to identify a suitable CPU.  We have been unsuccessful, and do not have confidence that we will be successful in the future.  Furthermore, even if we were able to find a suitable CPU, OSHWA cannot justify the time and resources required to comply with the various filing requirements associated with the law.

As a result, OSHWA decided that it was better to cancel the 2019 Summit now, before speakers and attendees had made commitments and travel arrangements.

That being said, OSHWA is still committed to supporting the OSHW community.  That is why we are pairing this announcement with two additional announcements.

October as Open Hardware Month

OSHWA has traditionally supported October as Open Hardware Month.  Open Hardware Month is an opportunity for the community to hold local events, hackathons, and  documentation days as part of an international movement.

OSHWA wants to take this opportunity to expand Open Hardware Month events.  We will work to provide resources for the community to create to local events, aggregate information to make it easy to find events in your area (or know that you need to organize one), and collect stories, video, and images of the events as they occur.  These events will not be OSHWA run or carry the formal OSHWA name. We believe that Open Hardware Month will provide us an opportunity to shine a light on open source hardware events happening around the world. It will also provide an opportunity for local communities to raise their hand and be recognized by the global OSHWA community.  Please email info@oshwa.org to learn more and volunteer to be involved.

Spring Summit 2020

Cancelling the Shenzhen Summit and focusing on Open Hardware Month will also allow us to shift the Summit to the spring.  Over the years a number of Summit participants have told us that the spring is generally less crowded with events and obligations, so this shift should make it easier for more community members to attend.

Starting with the 2020 Summit OSHWA also intends to commit to a single US host city for at least three years.

For the past year the OSHWA board has been debating two alternative paths for the Summit.  The first path would continue the pattern of moving the Summit every year. The benefits of this path is that it allows the Summit to come to the many different communities that support OSHW.  The costs of this path are that it makes the Summit more expensive to operate because OSHWA needs to spend time and resources learning a new city every year. Switching cities also makes it hard to capitalize on the enthusiasm of local attendees in order to convert them into full community members.

Conversely, the alternative path is to commit to a single city for multiple years of the Summit.  The benefits of this path is that it allows OSHWA to run the Summit significantly more efficiently and makes it easier for community members to plan.  Holding the Summit in a single city allows OSHWA to grow the number of attendees by turning opportunistic local attendees into more permanent members of the community.   The cost of this path is that it prevents us from moving the Summit to all of the communities that support OSHW.

After significant discussion, OSHWA has decided to adopt the single city approach.  This decision was easier because we paired it with the expanded Open Hardware Month.  We believe that Open Hardware Month will help fill at least part of the gap created by a stationary Summit.

—-

While none of these decisions are being made lightly, OSHWA believes that combined they allow us to create a rhythm that is more supportive of the vibrant OSHW community.  Open Hardware Month in the fall will shine a spotlight on all of the local OSHW communities around the world. The Summit in the spring will provide those communities a single place to come together and meet in person.

As always, OSHWA exists because of its community and we want to hear from you.  Please let us know what you think in the comments below or in the forums.

OSHWA has just filed an amicus brief in a case regarding design patents. OSHWA urged the court to uphold a rule that a design patent covers only what the patent itself says it covers. This rule allows everyone to understand what is and is not protected by a design patent. A clear understanding of the scope of design patent protection is particularly important for open source hardware creators who share their design files for use and modification by others because they need to know when a patent would – and would not – apply to their design.

The Case

The case in U.S. court, called Curver Luxembourg SARL v. Home Expressions, Inc., is actually about furniture patterns. Curver applied for a design patent on a wicker pattern similar to one found in ancient Islamic designs. The pattern looks like this:

Design patents don’t protect abstract designs as represented in all things at all times. (Copyrights do that.) When you apply for a design patent you need to identify the “article of manufacture,” the actual thing that embodies the design. Curver initially failed to identify the thing that embodies the design, but eventually identified a “pattern for a chair.”

Curver’s designation of a “pattern for a chair” is important for what comes next. Another houseware manufacturer, Home Expressions, started selling a basket with a wicker pattern similar to Curver’s. Curver accused Home Expressions of infringing on Curver’s design patent. Curver believes that now that its patent for a “pattern for a chair” has been issued, the patent should be interpreted much more broadly to cover baskets, or any other object embodying the wicker design.

OSHWA’s Amicus Brief

From OSHWA’s standpoint, it does not really matter if the patterns on Curver’s and Home Expressions’ baskets are the same or not. What is important is that Curver’s patent is for the design embodied in chairs and baskets are not chairs (feel free to post your chair-basket venn diagrams in the comments). Curver should not be able to select arbitrarily or strategically the thing that embodies its design in order to get the patent, and then turn around and apply the patent well beyond the scope of that selection in the real world. Our brief asks the court to adopt a rule preventing that kind of behavior.

Regardless of what you think about the design patent system more broadly (and there are many opinions about it in the open source hardware community), the system can work only if patents give notice of what they cover. The “article of manufacture” (in this case, a chair) is essential to providing that notice because it shows how an otherwise abstract design applies to a particular object. It also places a reasonable limit on the scope of a design patent’s protection. Home Expressions should have been able to confidently ignore a chair-based patent in designing their basket.

The trial court agreed, and found for Home Expressions, but Curver has appealed the case. OSHWA has filed an amicus brief urging the appellate court to uphold the trial court. Our brief is in support of the rule that patents should be read to cover what they say they cover – and only what they say they cover.

This is important to the open source hardware community in at least two ways. First, creators cannot avoid infringing on existing patents if they do not have a way to understand what those patents do and do not cover. The patent system works only if people can figure out from patents themselves what those patents cover. This is important for maintaining a healthy environment for open source hardware creators to share design files with others without exposing themselves or other creators to unknown risks.

Second, some open source hardware creators rely on licenses to impose openness obligations on future users of their hardware. Those creators cannot understand when the openness obligations apply to future users or how far those obligations extend if they cannot understand when the design patents included in the license are being used.

Curver actually took the fairly unusual step of opposing our request to file our amicus brief. Fortunately, the court recognized that the open source hardware community could be impacted by the decision in this case and denied Curver’s attempt to keep us out.

OSHWA will continue to keep an eye on this case and provide updates as they develop. We would also like to say a big thank you to Kyle McLorg, George Laiolo, Erik Stallman, and Jennifer Urban at the Samuelson Law, Technology, & Public Policy Clinic at Berkeley Law for representing OSHWA in this case. They drafted the original brief, as well as the argument that convinced the court to accept it over Curver’s objections.

Today, for the first time in the history in the Open Source Hardware Certification Program, OSHWA is revoking the certification for hardware.  OSHWA is revoking the certification for the MOTEDIS XYZ 3D printer, with the UID ES000001, because the documentation is no longer publicly available.  We have attempted to contact Motedis with a request to re-post the documentation but they have not been responsive.

Since this is the first time OSHWA has revoked a certification, we want to explain what happened, as well as what we will do in order to help prevent this type of situation in the future.

What happened

A few weeks ago, a community member wrote in and noted that the documentation link for the XYZ was no longer live.  After reaching out to the contact person listed in the certification application, we have been unable to obtain a copy of the documentation to post publicly.   Without the documentation, the XYZ is no longer in compliance with the program. Therefore OSWHA revoked the certification.

What it means

Revoking the certification means that going forward the XYZ can no longer be advertised as being certified open source hardware.  It does not mean that Motedis’ failure to provide documentation today makes them retroactively in violation of the certification rules.  The certification requires that the documentation be available at the time of certification. It does not require the certifying party to commit to making a copy of that documentation available in perpetuity.  This is a burden that is unreasonable to expect of a party applying for certification.

What now

When the Certification program was being developed, there was a debate over whether or not OSHWA should try and host a repository of all of the certified hardware.  One advantage of such a centralized repository would have been to allow OSHWA itself to maintain archive copies of documentation.

However, that approach also comes with costs.  Developing and maintaining a feature-complete documentation hosting solution is beyond OSHWA’s core competency.  Many good solutions for developing and maintaining software and documentation already exist online. Requiring certifiers to update and maintain yet another repository of documentation in order to certify was determined to be unnecessarily burdensome.  Instead, the certification directory supports links which point to the place where the developers already host and maintain their documentation.

OSHWA continues to believe that this decentralized approach is correct.  Nonetheless, the first revocation of certification provides us with an opportunity to consider improvements.  OSHWA has started to investigate a process that would allow us to archive a version of all documentation. This archive would not be used at the primary documentation storage location.  Instead, it would only be used in the event that the original documentation was no longer available. That would allow users of hardware to access documentation even after the responsible party stops supporting it as open.

If you have thoughts about this, please let us know in the forums.

We at OSHWA are excited to announce that the OSHWA Certification process has an officially registered trademark. This registration will make it easier for OSHWA to prevent people from using the OSHWA Open Source Hardware Certification logo if they have not actually gone through the certification process. We hope this will give the community more confidence when they see the OSHWA certification logo on hardware out in the world.

While there are many good faith ways to describe something as “open source hardware,” OSHWA considers certified projects to have met the gold standard of open source hardware by formally committing to comply with all of the elements of the community definition.

Are Trademarks Compatible with Open Source Hardware?

Trademarks are not in conflict with open source hardware. Trademarks are designed to indicate the origins of goods, not to control their reproduction. Knowing who produced something is especially important with hardware, because who actually manufactured hardware can be just as important to its reliability as who designed it.

Trademarks also do not prevent someone else from building on or using hardware that is protected by the mark. Companies like Lulzbot, Evil Mad Scientist, Adafruit, and Sparkfun all make open source hardware that anyone can copy, improve, or build upon. What people cannot do is pretend that their version of the hardware came from one of those companies by selling their version under the brand name of the original creator. That makes sense, because the original creator is no longer responsible for the new versions.

When creators have invited the world to make use of their open hardware, trademarks are how we know which pieces of hardware still come from the original designer. OSHWA believe that strong brand identities are compatible with a vibrant open source hardware ecosystem.

What OSHWA’s Trademark Means

The OSHWA Open Source Hardware Certification process is designed to make it easy for end users to quickly tell if their hardware meets the community definition of Open Source Hardware.  When you see the OSHWA certification logo, you know what “open source hardware” really means.

The trademark will allow us to control how people use the certification logo out in the world. In concrete terms, it means that someone who fraudulently uses the OSHWA certification logo on hardware that does not meet the community definition is infringing on the OSHWA trademark.  That means that OSHWA could bring a trademark infringement action against that person. This will allow OSHWA to protect the integrity of the certification mark.

What  OSHWA’s Trademark Doesn’t Mean

As we noted in a post at the outset of the certification development process, OSHWA has no interest in controlling, nor ability to control, who gets to use the term “open source hardware.”  Similarly, OSHWA does not have, nor desire, any control over who gets to use the Gear Logo and when they get to use it. Open Source Hardware is a concept that was developed by the community and continues to evolve as the community evolves.

Instead, OSHWA’s trademark will allow OSHWA to control the OSHWA-specific certification process.  If the community definition of open source hardware is important to you, the OSHWA certification logo will be an easy way to know that the hardware you are holding matches that definition.

What is Next?

We are getting excited to launch version 2.0 of the certification process at the Summit this September.  One of the big goals of 2.0 is to make it even easier to understand how licensing works with open source hardware, and make it easy to explore hardware that has already been certified.  If you are at the Summit you will be able to see that launch in person. If you can’t make it, keep an eye on this space for updates.

Also, a huge thank you to the students of the Juelsgaard Intellectual Property and Innovation Clinic at Stanford University Law School for guiding OSHWA through the registration process.

Thoughts?  Questions? You can always find OSHWA on Twitter, Facebook, and in the forums.

After almost a year and a half of community discussion, OSHWA unveiled the Open Source Hardware Certification Program at the 2016 Open Hardware Summit.  Today, with the help of a major grant from the Sloan Foundation, we are excited to announce that we are taking major steps towards Certification 2.0.

The original certification program has some fairly straightforward goals.  It is designed to make it easy for creators to identify their hardware as compliant with the community definition of open source hardware, as well as make it easy for users to know that hardware that is advertised as “open source” meets  their expectations.  The certification process gives a creator confidence that they have done everything required to call their hardware open source.  The certification logo gives users confidence that they will be able to access, build upon, and hack any hardware that they receive.

We didn’t know what to expect when we launched the certification program and have been blown away by the results.  There are currently 170 certified hardware projects from 18 countries on 5 continents participating in the program.

While we are excited about the certification program, shortly after it launched we started thinking of ways to improve it.  The current interface built on a combination of google forms and wordpress is functional, but not necessarily elegant.  Once the process was live, we also started getting feedback from users on ways to make it better.  One major concern was that the registration process exists in a bit of a vacuum.  It asks the creator to verify that she has complied with all of the requirements but does not provide very much guidance on the best ways to comply or the various choices that can be made and still comply.

For the past year we have been working with the Technology Law and Policy Clinic at the New York University School of Law to create more robust guidance to help creators navigate the licensing, documentation, and other decisions that creators must make when they are working towards certification.  We have also been working with the team at Objectively to turn that guidance into an interactive process that draws on examples from the community.

The grant from the Sloan Foundation allows us to take that work and turn the certification into a much more robust and useful resource.  We are hoping to have the new site ready to launch by the 2018 Summit.  Until then, please let us know if you have thoughts, ideas, or concerns.  We are very excited about the next chapter of the Certification Program and hope you will be too.

Become an OSHWA member today to vote on nominees!

This year, we have 3 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. 14th through Oct 21st. Members will be emailed a link to vote. Here are the nominees in alphabetical order:

Akiba

Why do you want to be on the board?

I’ve been involved and worked with many nonprofits and NGOs doing projects like monitoring illegal waste dumping, monitoring water quality in the Himalayas, radiation monitoring in Japan, etc. All of those projects have used open source hardware in some form because the designs could be rapidly put together, deployed, and assessed. Crises are becoming the norm and I believe open source hardware will play a crucial role to prevent, mitigate, or assist aid workers and victims during those times. I’d like to give back to the open source hardware community for all the benefits I’ve received as well as help guide OSHW and OSHWA towards more cooperation with nonprofit humanitarian and aid agencies.

What qualifies you to be a board member?

I’ve been designing open source hardware for the past ten years and have run an open source hardware company for the same amount of time. I think it’s important for OSHWA board members to understand the value of OSHW and how that translates into commercial value for their companies. I’ve put together or have been involved putting together four hackerspaces (Tokyo Hackerspace, Mothership Hackermoms, Knowledge Garden Dharamsala, and HackerFarm) and understand the importance of building, maintaining, and growing community. I’ve also worked with, consulted, and put together open hardware projects for groups like UNESCO, World Bank, and IAEA and believe that it’s important to reach out and educate NGOs doing important work to the benefits of open source hardware.

Will Caruana

Why do you want to be on the board?

I want to be part of something bigger then my self. I feel that I will add an outside perspective. I don’t work in any industry that produces goods but I live in that maker space of the communitte.

What qualifies you to be a board member?

I served as president of a non profit for 5 years it’s the Friends of Wilbraham Public Access. I was the chairmen if the Board Band Committee which was able to set up a municipal corporation that sell fiber optic services to ISP’s. I also love make things currently I like making high voltage projects like my demo fusion reactor which currently produces a ball of plasma in a vacuum. I am also running the fun with high voltage workshop at the Hackaday Superconference because I like helping people learn and work with high voltage.

Arielle Hein

Why do you want to be on the board?

I work and engage with a vastly diverse range of different communities, but one of the primary overlaps between these groups is that they all rely heavily on open source tools, hardware in particular. I am extremely passionate about building bridges between the arts and engineering, and making this cross-disciplinary work more accessible to a broad range of makers – to artists and women especially. I love to create, hack, and teach all things open source – but as much as I’m excited about exploring emerging technologies, the thing that drives me most is the way that sharing knowledge is an opportunity to build connections between people. I am excited about the prospect of more direct engagement within the Open Source Hardware community, and eager to assist in continuing to extend the mission of this organization.

What qualifies you to be a board member?

Since my time as a graduate student at ITP NYU, I have worked extensively with Open Source Hardware and have engaged with the community consistently since then. In my current role as an Instructor at the University of Colorado, I teach interaction design and physical computing courses that rely heavily on open source tools. Beyond skill acquisition, my philosophy as an educator focuses on the importance of knowledge sharing, documentation, and collaboration – notions that I will bring to my contributions on the board of OSHWA. I also have extensive community organizing experience through my ongoing work as the Coordinator of ITP Camp. I am a strong communicator (and listener!) and very organized and responsive in all correspondence. I am extremely excited about the opportunity to serve not he OSHWA board and am hopeful to deepen my contributions within this community. I am glad to answer any questions via email from anyone in the community regarding my qualifications or interest in this role!

David Li

Why do you want to be on the board?

I am currently the executive director of Shenzhen Open Innovation Lab which is a government supported platform to promote and facilitate the collaboration between the Shenzhen open hardware ecosystem and the global makers and open source hardware groups. Prior to SZOIL, I also started the research hub Hacked Matter with two collaborators to study global maker movement and open hardware ecosystem in Shenzhen and publish our findings. Shenzhen open hardware ecosystem is currently a 100 billion industry and the insight into how this ecosystem was developed and structured could contribute the future growth of the global open source hardware development.

What qualifies you to be a board member?

I have been an open source and free software contributor since 1990 on various of projects. Ardublock I developed in 2012 is one of the most popular graphical development environments for Arduino. I have been doing research in the area of open hardware ecosystem in China since 2011. In my previous role as the director of ObjectWeb an European based open source software consortium in 2003-2006, I contributed to the joint effort between ObjectWeb and major Chinese open source software projects. I can bring new insights to the board and help bridge the global open hardware and the open ecosystem in China.

Narcisse Mbunzama

Why do you want to be on the board?

I want to bring my experience and knowledge on open hardware and related issues with a special view on technical and organizations development. As a citizen of the democratic republic of Congo, I wish to represent the global south in the board, to bring valuable contribution and inputs finally to help achieve the open hardware association mission.

What qualifies you to be a board member?

I hold a master degree in computer science and technology innovation and I am a fellow of the international telecommunication union and member of several technology innovation organizations around the world. I’m a serial award winning tech innovator and I conduct researches on standards for open hardware, design of system and related issues. With my background and experience, I personally believe that I am a qualified candidate to join the board and i will bring valuable inputs and contribution in the board.

Joel Murphy

Chris Osterwood

Why do you want to be on the board?

I am a longtime user of Open Source Hardware and have benefited from it greatly. I want to return that favor and help others benefit from OSHW. I’m a mechanical engineer by training and I chose that educational path because I was fascinated and captivated by the mechanical world. I gained tremendous design insight and experience by taking apart my toys as a child — in fact my favorite store sold broken junk by the pound. Being able to see how my toys worked gave me interest in designing new products. Since college, I’ve learned electrical design through study of open source hardware schematics, bills of materials, and design journals. I now see that I’m repeating my childhood but in digital circuit design — learning new skills and design strategies by interrogating what others have made. And without OSHW, without published schematics, this kind of interrogation and subsequent learning is much more difficult. What I’ve learned has allowed me to start my own company, Capable Robot Components, which will be releasing a line of OSHW products aimed at changing the make vs buy decisions that makers of unmanned ground robots currently face. I want to be on the OSHWA board to further its mission and to help others benefit from OSHW as I have.

What qualifies you to be a board member?

I’m not sure quite how to answer this question. But, I understand and am interested in organization building — for example I’m on the steering committee of the Pittsburgh Robotics Network, which is becoming a 501c6 organization. I am embracing OSHW with the products I’m designing at my company. I have functional knowledge in hardware design, embedded software, web software, marketing, and law. I enjoy teaching and speaking — I’ve given talks on law & robots (Practicing Law Institute) and how we tested 3D sensors at my previous company (Embedded Vision Summit and ROSCON). I listen. I try to make well reasoned decisions.

Jeff Paranich

Why do you want to be on the board?

My low-level coding interests for the past 20 years have led me to hardware design, and the colossal reward of holding a tangible, physical item, in your hands that can be shared with others to extend upon and use in their designs. While programming low-level in itself is still fulfilling, the thought that everyday consumers can build their own commercial grade products with all the distributor resources available today is truly phenomenal. Curiously, the knowledge that such a movement exist is not known by the general population. One simply envisions big factories, assembly lines, and blue-chip organizations being the sole innovator and originator; when in reality there are compelling and pioneering designs being done by small organizations and private individuals in their own homes. I believe this is a tragic mindset; the homebrew and maker community was strong in the eighties, there was a general knowledge it existed by all and anticipation of an upcoming wave to pave the future to new technology. I can attest that today open hardware has, and will continue to gain, a lot of momentum – and is strongest it has been in two decades – but may continue to be eclipsed by large organizations that keep much of their business proprietary. Canada, my home country, has a very strong post-secondary system; world-class Computer Science and Engineering schools, however outside of BioWare and BlackBerry there has not been much traction in STEM corporations, small business’, nor makers in the nation, I believe due in part to organizations such as OSHWA not having a strong enough presence to inform and encourage innovation and open source/hardware from early on and to general masses. Thus, I desire to be on the board to expand awareness of the Open Source Hardware Association and inform and educate those who are not aware of what it represents. I pledge to attend fairs or events, fundraise well beyond the expected $300 as it is not enough, and provide meaningful input on the Board of Director meetings. I also believe the best protection for OSHWA’s future is committing resources to youth at early ages, expanding their mind into hardware before they move onto post-secondary or private studies – even presenting hardware as a valid field of self-study that can merit much personal success with all the open source resources available today. OSHWA is the strongest association and best bet right now to incite change, grow the movement further, and ensure the hardware community story remains a rich and colorful one. It would be an absolute honor to be part of the team and ensure its continued success.

What qualifies you to be a board member?

I hold dual degrees from the University of Alberta- Bachelor of Science in Computer Science & Bachelor of Science in Actuarial Mathematics, with a minor in Business. I have been a projects controls manager for over two billion dollars in heavy oil projects; managing revenue, cost, margins, scheduling and progress completion. When I am not managing projects, I am designing hardware in my workshop. My most common projects typically involve power supplies, FPGA boards, video processing ADC/DAC boards, and audio amplifiers. Furthermore, I have coded a multitude of company software programs – software as simple as employee in/out of office interfaces, to estimating software for piping fabrication, to invoicing software which neared that of a full ERP system. I have a thorough knowledge of C++, C and the Unix tool set (Awk, Sed, etc), and believe in the Unix philosophy of building simple, short, clear, modular, and extensible code that can be easily maintained and repurposed by developer’s other than its creators. I can operate under tight deadlines and sometimes unrealistic deliverables, accepting the challenge and looking forward to the feeling of reward once finished. Lastly, I am co-founder of a successful videography company in Alberta (J&C Media Corporation), managing employees and finances and scheduling – also doing occasional filming myself in the field for corporate and private events. All said my past is very multi-faceted, I have a multitude of exposure to many elements at various business levels and have been successful to date with a clear, structured framework to how I approach things and would apply all my techniques to ensure the continued success of the Open Source Hardware Association.

Nick Poole

Why do you want to be on the board?

I’ve always been a proponent of OSHW and other Free and Open initiatives and I believe I finally have the free time and bandwidth to get involved with steering the ship. I’m also interested in talking to other board members and learning from their perspectives.

What qualifies you to be a board member?

I’ve worked for SparkFun Electronics for almost 7 years where I’ve had the opportunity to see open hardware from a number of perspectives: as a marketing professional, a community discussion leader, and a designer and maintainer of open hardware projects. I believe that my work experience combined with my unique personal perspective and affinity for facilitating and mediating discussions could make me a valuable member of the board.

OSHWA is looking for 3 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 (deactivated October 14) 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 serve 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. 5th to ask questions or submit questions to info@oshwa.org. Nominations will be open until Oct. 12th.

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