Clearly stated goals help projects run more smoothly
State Your Intentions
"maddog" advises designers and developers to state their project goals up front and in writing, to avoid confusion and conflict later.
I am following a flame war on a mailing list about a certain piece of hardware – a design project that has been going on for a long time. I am not going to name the project, because I don't want to embarrass the people working on it, all of whom I am sure are discussing it in good faith.
This flame war, like many flame wars, has to do with a long-standing set of expectations, based on a loose dialogue between various groups of people who have joined and left the project at different times.
Some people have called the device in question an "Open" hardware device, and others have called it a "Free" hardware device. Each person has a different definition in mind as to what this particular project is and what that definition means with regard to the project.
The issue comes down to the point where one of the main drivers of the hardware project is not willing to release all of the manufacturing information of the hardware, such as the commands to the surface mount technology (SMT) machine that places the parts on the printed circuit board and other information that would make it easy for some other company or entity to copy and manufacture the design. This person is willing to release the circuit diagram and programming interfaces to the various chips and other pieces of technical information of interest to programmers. He is taking this approach because he wants to manufacture the board and perhaps make some money off it.
It is reasonable for this person to make some money off the manufacture of the board – or even to make a profit, which might allow him to recover the expense of the design of the board. Even if the design of the board is donated by volunteers, with their great expertise given to the project gratis, typically large expense is still involved in trying to get the board manufactured and working.
Most board designs today are sophisticated enough that they cannot be wire-wrapped to prototype a solution, and even if they could be, the real savings in generating boards via SMT lines is too great to ignore. Eventually, the boards will need to be manufactured on an SMT line, or else they will cost thousands of dollars rather than hundreds or tens of dollars each.
Thus, somewhere in the manufacturing time line, the boards need to be prototyped on an SMT line, which is designed to manufactured tens of thousands of boards a week. To stop a line long enough to set up a sophisticated board and buy the components to manufacture a small run (perhaps, 100 units) and test for quality, capabilities, preliminary radio frequency emissions, power utilization, and other issues is very expensive. Just buying small amounts of components from companies who are used to selling in huge numbers is difficult and expensive.
After manufacturing these few boards, you might find mistakes in your printed circuit board layout or find "hot spots" that must be corrected, which requires more programming and additional testing at the manufacturing stage. While the SMT line is being used for this, it cannot be used to manufacture other items that are known to create revenue for the manufacturing company.
Three main areas determine which products and services are produced and come to market. Simplistically, they are:
A. Is there a market value for the product or service, and can that market (called a "channel") be reached?
B. What is the cost to produce the project or service?
C. What is the cost to design the product or service?
If B+C > A, then typically a product or service does not appear.
People who contribute their time and energy to the design cut down on the design cost C, so then only A and B really determine whether something appears.
In software, the cost of B is typically minimal, wherein people contributing their time and energy can have a dramatic influence on the price, with minimal "unit" cost. Thus, A can be extremely small, or even non-existent and still be cost effective for software creation and distribution.
In hardware, however, the cost of components, cost of the SMT line, and cost of testing and certification end up being real costs that must be met another way. "Kickstarting" and "crowdsourcing" are modern ways of dealing with these costs, but the people who contribute their time and money to a project need to know exactly, and from the beginning, what to expect.
Therefore, an Open/Free hardware project would do well to have a charter from the very beginning that spells out exactly the goals of the project, including what will or will not be published both to members of the team/community and to outsiders and under what conditions.
Buy this article as PDF
(incl. VAT)
Buy Linux Magazine
Subscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Subscribe to our ADMIN Newsletters
Support Our Work
Linux Magazine content is made possible with support from readers like you. Please consider contributing when you’ve found an article to be beneficial.
News
-
Gnome 47.1 Released with a Few Fixes
The latest release of the Gnome desktop is all about fixing a few nagging issues and not about bringing new features into the mix.
-
System76 Unveils an Ampere-Powered Thelio Desktop
If you're looking for a new desktop system for developing autonomous driving and software-defined vehicle solutions. System76 has you covered.
-
VirtualBox 7.1.4 Includes Initial Support for Linux kernel 6.12
The latest version of VirtualBox has arrived and it not only adds initial support for kernel 6.12 but another feature that will make using the virtual machine tool much easier.
-
New Slimbook EVO with Raw AMD Ryzen Power
If you're looking for serious power in a 14" ultrabook that is powered by Linux, Slimbook has just the thing for you.
-
The Gnome Foundation Struggling to Stay Afloat
The foundation behind the Gnome desktop environment is having to go through some serious belt-tightening due to continued financial problems.
-
Thousands of Linux Servers Infected with Stealth Malware Since 2021
Perfctl is capable of remaining undetected, which makes it dangerous and hard to mitigate.
-
Halcyon Creates Anti-Ransomware Protection for Linux
As more Linux systems are targeted by ransomware, Halcyon is stepping up its protection.
-
Valve and Arch Linux Announce Collaboration
Valve and Arch have come together for two projects that will have a serious impact on the Linux distribution.
-
Hacker Successfully Runs Linux on a CPU from the Early ‘70s
From the office of "Look what I can do," Dmitry Grinberg was able to get Linux running on a processor that was created in 1971.
-
OSI and LPI Form Strategic Alliance
With a goal of strengthening Linux and open source communities, this new alliance aims to nurture the growth of more highly skilled professionals.