Over the last couple of months the Mach 30 community has been talking more about the concept of virtual Makerspaces. I’m guessing that most of our readers know what a Makerspace (a.k.a. Hackerspace) is, but just in case, I’ll give you a definition I might use.
Makerspace (n.) – A space, normally a physical room or building, where people come together to share resources such as expertise, manpower and tools. This is done to help complete projects that the makers might not otherwise have the resources for.
Some people come just to hang out and see what’s going on, but most come to work on projects. Whether you’re working on arts and crafts or spaceflight hardware, I have yet to find a Makerspace that didn’t welcome all kinds of projects.
The Mach 30 spaceflight hardware developers are spread across the U.S. and we’re always looking for better ways to collaborate on protects. Traveling would be one way to work together, but that gets expensive. We recently changed our Thursday night Google+ Hangout schedule so that we could have a dedicated hardware (a.k.a. “#EngineerSpeak”) Hangout. This will allow us to partially address our collaboration needs.
The intent was to make it free form so that the things the attendees wanted to work on was what would be worked on. Just like a Makerspace. The first week ended up being more of a normal meeting where I asked for feedback on the Shepard Test Stand software. That was a great Hangout that really helped but the second week’s hardware Hangout ended up feeling much more like a Makerspace, partly because of an engineering challenge that J. Simmons gave us.
The engineering challenge was to see if we could convert the Shepard Test Stand application from Processing to Python in 10 days. That way we could test Python’s viability for use in our Shepard 2.0 kits. As we started that second week’s #EngineerSpeak Hangout, we discovered the need to make some significant changes to the sample code that I wrote to meet part of that challenge.
There were 5 of us in attendance, but Chris Sigman and I were the only two who had accepted J’s challenge. This diversity of interests and focuses had the makings of a great Makerspace environment. Here are a couple of reasons why:
- Even though Chris and I weren’t in the same room, we were able to work on the code collaboratively in real time. We worked through the code, sharing solutions to some problems and talking through possible fixes for others. The only thing that would have made it better is if we had both been logged into a shared code editor so we could have been editing “over each other’s shoulders.”
- Even though they weren’t working on the engineering challenge, the 3 other Hangout members hung around to work on their own projects. This allowed them to comment on what Chris and I were working on and share things about their activities as well.
It was 5 people sharing a space and resources, working together and independently in true Makerspace style. The Hangout ran long, but before it was over Chris and I had fixed the code and I was left with the feeling that this Hardware Hangout stuff might have some major potential. Couple that with the ability to work on our projects collaboratively on Open Design Engine, and we have a couple of powerful tools to allow us to do distributed development.
As time goes on we’ll be developing and refining our methods of distributed collaboration. It’s a critical part of our mission and we hope you’ll join us on the ride. Stay on the lookout for a future post on how we’re starting to use Open Design Engine as a virtual Makerspace as well. If you’re interested in learning more about Mach 30 and our hardware projects, please add Mach 30 to your Google+ circles and request an invite when you see Thursday night Hangout announcements.
Gravitas (n.) – An ancient Roman virtue that denotes seriousness and dignity. It encompasses the depth of knowledge and/or personality that comes with experience. A very old word, but a modern circumstance.
So, how do you decide who’s got it all together in a field of endeavour as broad as ‘Space’? In any situation, you look for the survivors. Those who’ve been in the ‘game’ the longest with the most success. In something as new as the Open Source Space Movement, it can be a little more difficult. This is because a good web presence or a flashy marketing video can imply credence, sometimes more than actual content can. You have to dig past the ‘vaporware’ to find the real foundations. Another telltale sign is the language. Not the difference between German or Swedish or English, but the language of the non-tech, the space enthusiast, and the astronautical engineer.
Open Source is a confusing maze for newcomers. It is a difficult paradigm to wrap the brain around when all of your existence has been cocooned in a proprietary existence. Add “Space” to that and life gets interesting. Out of the 754,000,000 hits on a search engine, where do you start? What values, what gravitas do you look for? How does this relate to Mach 30?
Here are some of the things that we have done to promote gravitas.
- Mach 30 is a 501(c)(3) public charity. We’ve built a solid foundational base on which we established the organization, with the IRS paperwork to prove it
- Strong business processes including openly shared documentation, meeting minutes, strategic plans, etc. These provide transparency.
- We seek out like minded organization and work with other non-profits, makers spaces, government entities, and the broader aerospace industry.
Technological stepping stone approach
- Being biased towards mature technology means we can build and test now.
- Having learned from the misatkes of others, we avoid the “death spiral” of giant development projects that will cost large fortunes.
- Pursuing a technology “Road Map” development plan instead of jumping-in to shiny and fun projects
- Tackling the true barrier to safe, sustainable, routine, and reliable spaceflight: Namely affordable and reusable spacelift.
Open hardware development and Open Design Engine
- True open source hardware projects (space-related or otherwise) need to share their WHOLE project, from inception to disposal. Mach 30 does this on ODE.
- In fact, Mach 30 is responsible for the development and operations of the opendesignengine.net because we identified this as an unfulfilled need, then filled it.
- Mach 30 conducts its work using open systems engineering processes. Open source hardware development with distributed collaboration is different, as we’ve learned from past projects.
Identified need to deal with Export Controls, ITAR and more
- Working to understand Export Controls
- Having an Export Control Task Force
- Meeting regularly to expand our knowledge and compliance of Export Controls
Each of these works combine to build gravitas. We’ve been at this for four years. We ask ourselves these questions frequently, “Are we doing this right?” “Are we true to our vision?” “Is this right/correct/needed?”. We strive to complete our goals. We work to make our little corner of the Open Source Space Movement a little better each day. We don’t have all the answers, but we are willing to share what we know.
Mach 30 is gaining gravitas, little by little. Each conference we attend, every event we hold, and every failure we review and improve upon adds to that weight. We are by no means perfect, but well will continue to work towards bringing humanity into a spacefairing civilization.
~ ad astra per civitatem ~
to the stars through community
It’s been fifty-two years. No, not of Mach 30 (well, not yet anyway)… It’s been fifty-two years since the first human spaceflight. And for the last twelve years people around the world have celebrated the anniversary of Yuri Gagarin’s first flight (and the first US Space Shuttle flight) with Yuri’s Night parties.
Starting last year, with a great deal of encouragement and support from our volunteers, Mach 30 celebrated Yuri’s Night with an online party. Each year, we choose a theme and hold a space trivia contest, complete with prizes for our guests out in cyberspace. As a distributed organization we find the online format gives our volunteers, partners, board members, and fans a chance to celebrate human spaceflight together without the need for a transporter.
We just held our 2013 party this weekend. Check it out in the video above. The theme was Rocket Science: Live! During the party we demonstrated two of our open source spaceflight projects (the Shepard Test Stand and our first ground station prototype). Both were a big hit with our guests including makers from Bucketworks and Club Cyberia, and students from John Mall High School.
From all of us at Mach 30, I want to thank our volunteers, guests, and partners who helped make this year’s party a huge success. We had a blast! And we can’t wait to celebrate fifty-three years!
ad astra per civitatem