Category Archives: conceptual

Build The Enterprise Is The Biggest Open Hardware Project Ever

If you dream big, dream REALLY big. Dream spacecraft big. Build The Enterprise is a website devoted to laying out, in detail, how a primitive version of the USS Enterprise from Star Trek could be built in 20 years.


There’s a petition up on the White House’s website to assign NASA the task of a feasibility study. Only 20,000 more signatures to go! Interestingly, they decided to go with a promotional graphic that is eerily similar to that scene from Independence Day when a spacecraft blew up the white house.

BuildTheEnterprise-White-House-Petitionindependence day white house


Tagged , , , , , , , , , , ,

Help OSE Refine The Design Of Their Backhoe

Open Source Ecology is gradually evolving their process for open source engineering. This latest installment is a Google Doc that anyone can jump in and view/edit. They’ve posted several questions so all you have to do is comment. You can also download the CAD files and a viewer if you don’t have anything to open them with at the blog post. The wiki page for the backhoe is here.

Tagged , , , , , , , , , , , , , , , , , ,

The Fixer’s Manifesto v1.0- From The Inventors Of Sugru

If you like the Fixer’s Manifesto then you can also look at pictures of people holding it here, if that’s your thing. If you want to fork/hack/improve it you can do that on the github page. If all of that is just to “free as in beer” for you then you can also buy a print from Sugru (it comes with a pink pen for making edits…yeah).

Tagged , , , , , , , , , , , , , , , , , , , , , , , , ,

The Amp Hour #114

I think this episode of The Amp Hour is a nice segue from Makerbot’s open/closed source fiasco.

After an introduction about winter and new jobs they discuss the Replicator 2 and Pettis’ abysmal message control. Then they talk about how Kickstarter has recently changed their rules for hardware projects.

In the blog post Kickstarter Is Not a Store we find that Kickstarter is getting a little tired of the vaporware shenanigans that have been going on.

Today we’re introducing a number of changes to reinforce that Kickstarter isn’t a store — it’s a new way for creators and audiences to work together to make things…Today we added a new section to the project page called “Risks and Challenges.” All project creators are now required to answer the following question when creating their project: “What are the risks and challenges this project faces, and what qualifies you to overcome them?”

Product simulations are prohibited. Projects cannot simulate events to demonstrate what a product might do in the future. Products can only be shown performing actions that they’re able to perform in their current state of development. Product renderings are prohibited. Product images must be photos of the prototype as it currently exists.

Offering multiple quantities of a reward is prohibited. Hardware and Product Design projects can only offer rewards in single quantities or a sensible set (some items only make sense as a pair or as a kit of several items, for instance). The development of new products can be especially complex for creators and offering multiple quantities feels premature, and can imply that products are shrink-wrapped and ready to ship.

There’s discussion about not allowing simulations over on Core77.

It’s possible that Kickstarter changed their rules in response to the LIFX LED lightbulb project. They asked for $100,000 and with 50 days to go they already have $1,311,863. However, they are claiming to be able to build and ship an LED lightbulb, which is something that established manufacturers have failed to do for a long time. It looks like Kickstarter is trying to protect themselves (and their users) from the implication that a project is much farther along then it actually is. Understandably they don’t want people dumping a million dollars into a project that simply can’t go anywhere because of the laws of physics. Reuters really took a magnifying glass to the LIFX project and their analysis wasn’t pretty.

Tagged , , , , , , , , , , , , , , , , , , ,

Bre Pettis Of Makerbot Tries Again (Emphasis On Try)

If anyone was suffering under the illusion that Makerbot had suddenly become an evil company that was plotting evil and evily being evil, then Pettis’ new post should put those fears to rest.

Pettis, on behalf of Makerbot, tried to rephrase his original message to the community.

For what it’s worth (I’ve never run a million dollar business), I agree with Makerbot’s business decision(s). The hacker community just isn’t big enough, by itself, to allow Makerbot to grow. Also for what it’s worth (I won’t pretend to speak for anyone else), I agree with Makerbot’s ethical decision(s). Open source means releasing your work for other people to do with as they will. There are no takesies-backsies. If you were a big enough person to use an open souce license (or no license) in the first place then don’t suddenly become a small person when somebody actually does something with the work you released.

What I have a problem with is the thing that illustrates that Makerbot actually IS fumbling their way through uncharted terrain: even with all of his experience as a teacher, and a geek-media personality, and the face of Makerbot, and with a couple days of feedback…Pettis still can’t figure out how to talk about the Replicator 2 being closed source.

  • He can’t decide if the Replicator 2 is “groundbreaking” because it’s brand new or if it’s exactly the same as the open source Replicator with a few minor alterations for mass production
  • He regularly conflates ethical decisions with financial ones
  • He implies that the customers who bought Cupcakes and whatnot when the Makerbot founders were eating Ramen don’t respect the machines because they’d rather “break” them than use them to make other things
  • He plays lip service to valuing the discussion, but only quotes people who agree with him
  • He has been intimately involved in open source hardware, and business, for as long as anyone relevant but he can’t come up with any specific “wonderful benefits” of corporate/community collaboration
  • Finally, he expresses a desire to be credited with “love and support for the sharers of the world” but also wants credit for making the Replicator 2 (and the implication is all subsequent printers) “more user friendly but less hacker friendly”

This shouldn’t be interpreted as a condemnation. I think these contradictions illustrate that Makerbot really is unsure of its position, both economically and philosophically. There are some real issues here. But, Pettis’ failure to deal with them clearly comes of as Machiavellian. I still put enough trust in Makerbot and Pettis to assume that they aren’t being Machiavellian, but apparently they jumped over that shark in the eyes of a significant percentage of the community.

I don’t think it was really the closed product that did it; I think it was the bush-league way Makerbot handled (and is still handling) the community’s concerns. There’s no way they would have done this much damage to their reputation on purpose; the only plausible explanation is that they are legitimately confused.

I think this quote sums it up, “If we are not entirely clear, it’s because we are searching ourselves!

However, Pettis should probably find someone else to write his Open Hardware Summit speech.

An interesting bit of history is this interview with Make Magazine right after that infamous $10M of VC funding. For what it’s worth, here is what Pettis had to say at the time:

  • Does funding change the commitment to open source hardware?
  • The funding doesn’t change our commitment to being open source. Why would we change a winning strategy?…In the future, people will remember businesses that refused to share with their customers and wonder how they could be so backwards…I think people worry on our behalf that as an open hardware company, we’ll get knocked off and undercut. First of all, that happens all the time to businesses that are not open hardware. In order to be truly competitive, we’ve got to keep rocking it!
  • What do the investors believe they are investing in? Since open source hardware “gives away” some of the IP usually associated with investments, do they understand that others could make MakerBots too?
  • The investors are investing in us as innovators and our ability to execute on a vision. Being open source means that our users are our best collaborators. Open source hardware is a viable business model!
  • The usual goal for VC firms is to have the company they invest in get acquired or go public. Where do they want to see MakerBot go? Where do you want MakerBot to go?
  • Our plan is to make the world a more innovative place filled with MakerBots.
  • Now that you’ve got “real money” at play, are you worried about people coming after you over patents? Is MakerBot mostly patent-free? Or are we going to see a good chunk of that 10 mil go towards lawyers? Before, you likely weren’t worth the trouble, but now?
  • It’s going to be hard to figure out how to be an open hardware company that lives in the open source future while protecting ourselves from the proprietary ways of the contemporary patent system.
Tagged , , , , , , , , , , , , , , , , , , , , ,

A Guide For Defeating Procrastination by Alex Vermeer

Open source revolves around The Project.

Without projects, there wouldn’t be an open source movement. If there’s no project then there’s nothing to be open about in the first place. Additionally, the projects are usually something new and interesting. That’s great for producing the motivation to finish, but a lot of the time “new and interesting” leads directly to the unknown. A learning curve, or a delay, can turn a promising project into something permanently on the back burner.

Alex Vermeer has put together a beautifully simple poster that is based on The Procrastination Equation. Basically, expectancy and value are good, impulsiveness and delay are bad, and the poster has a ton of different strategies for increasing the good and decreasing the bad.

Here’s what it looks like…

And here’s where you can download your own copy. Vermeer released it under the Creative Commons Attribution-NonCommercial-ShareAlike 2.5 license for Canada.

You can also buy a physical poster here.

Tagged , , , , , , , , , , , , ,

On Makerbot And Being Open (Or Not)

A lot of smart people have wasted a lot of time wondering what open means. At least…in my opinion a lot of the discussion is wasted…because I don’t think it’s all that complicated.

It’s a simple matter of priorities. You are open if your top priority is being open. If your top priority is anything else, then you’re not open. You might be a big fan of open, you might even make it a high priority, but if it’s not your top priority then you are open in name only. You’re openwashing.

For example, a year ago the three founders of Makerbot all signed a statement that opened with this:

We make it open source so that you will have all the information about the machine. Our goal is be as open about the machine as possible! If you want to improve or hack the machine, you can do so…

Today, Bre Pettis was the lone voice who’s statement opened with this:

…we are going to be as open as we possibly can while building a sustainable business.

The old team perspective was:

The possibilities that we can’t imagine yet are one of the wonderful things that makes us stay up all night hacking on code, working on prototypes, and dealing with supply chain issues.

We’re not big fans of anything proprietary

We’ve been in the “eating ramen” stage of building a business this year because we want to get as many of these out there and grow the community…

We are doing this because we are dedicating our lives and our savings and our minds to the dream of bringing the tools of manufacturing to all.

The new Makerbot perspective is:

I’m looking forward to having conversations with folks at the Open Hardware Summit to talk about how MakerBot can share as much as possible, support it’s 150 employees with jobs, make awesome hardware, and be sustainable.

From a business perspective, we’ve been absurdly open, more open than any other business I know.

I don’t plan on letting the vulnerabilities of being open hardware destroy what we’ve created.

This isn’t the first change we’ve made to become more of a professional business, and it won’t be our last.

That’s absolutely a shift in top priorities and, to be fair, it makes perfect sense. Back before their $10M round of funding nobody knew if Makerbot would even be around in a year. But they are, and they’re doing more and better, and that’s all thanks to the money that was invested with them. Investment isn’t charity. Makerbot didn’t grow because the community gave them money in exchange for printers; Makerbot grew because they kept managing to convince professionals that they would be able to produce a significant return on seed capital.

It doesn’t really matter what their original priorities were, because the only way for them to be successful now is to focus on maximizing profit. You have to play the ball where it lies.

Yes, it is possible that they could be successful while remaining devoted to open, but it would be a hell of a gamble. There aren’t any relevant case-studies that I’m aware of; Makerbot is the first. New businesses, and new business models, are notoriously likely to fail. When you’re just a little guy plugging away at an idea, failure isn’t a big deal. When you’re using $10M of someone else’s money, failure becomes a real issue.

The thing is that I don’t see how anyone loses. Even if Makerbot goes totally closed source, and cuts off all the old printers, the community still benefits. Whether we like it or not the community suffers as long as 3D printing remains an unknown niche for a specific subset of geeks. There isn’t anything about the current state-of-the-art in open 3D printing that is inherently expensive or complicated. What is keeping it in a place where it costs too much and breaks too often is the lack of a market. Grow the market so that scale will bring prices down and quality up. That will help the open hobby community do more and more exciting things because there will be a bigger supply of commodities to work with.

And I don’t think Makerbot will go totally closed source. I think what they’re doing is moving up-market as fast as possible so that they can establish themselves as a brand that non-hackers buy. Believe it or not, but even most geeks get tired of wrenching on their projects and would appreciate it if they’d just freaking work for long enough to get something else done. There are an order of magnitude more people ready to buy a turn-key 3D printer than a turn-allen-wrench 3D printer. Those people are not being served by existing 3D printing companies. It would be fiscally foolish of Makerbot to ignore that market in favor of the tiny hacker market. But that doesn’t mean they will abandon open source designs. I think they will keep doing open source work, it will just slip into second or third place.

They need to pay their investors back, which means they need to establish a brand and cash flow that is lucrative. The open source hobby community is not lucrative. Of course it would be nice if they would be more up front about their shift in priorities, but I suppose using corporate double-speak is part of that shift.

Give it time. The open hardware movement is still very young and, unlike software, there is no way to ignore money. You can’t pay for hardware by eating cheap food and staying in front of your computer; you have to actually turn a profit. Even if Makerbot closes up like a clam, they will still have proven that a successful company can start open. Then the next hardware guys will try to stay open longer.

Also…if Makerbot goes closed source, they will just get out-innovated by the remaining open source hardware community anyway…just like the companies they’re trying to beat to the prosumer 3D printing market. The only way for them to stay relevant is to stay at least somewhat open.

Tagged , , , , , , , , , , , , , , , , , , , , ,

Using Github To Track Hardware Projects By Gary Hodgson

Unlike software, hardware projects cannot be entirely defined, or contained within, the computer. That’s a shame because there are some really great tools for managing software projects.

Gary Hodgson has prototyped his proposal for using github to manage hardware projects. He called it githubiverse and, appropriately enough, hosted it on github. Here is an example of it functioning to track Mechanical Movement #27. All the files are on github and this custom webpage displays whatever is up to date.

If the name Gary Hodgson sounds familiar, that’s because he built a DLP resin printer, which Openalia covered previously. I don’t think I’m outing him as a true geek when I point to this…

An interesting advanced use case is the ability to use the same core template across many projects.  You could fork the githubiverse-template project and edit the html/css as you wish. Then, in each project’s gh-page branch create a submodule referring to this fork.  All that’s left would be to create a _config.yml file with the details in the root project gh-pages branch and an additional entry defining the source of the jekyll site as being the submodule folder.

…as reminding me of this Dilbert cartoon.

Tagged , , , , , , , , , , , , , , , , , , , , , ,

Get every new post delivered to your Inbox.

Join 55 other followers