You are not logged in.
I'm not sure if I'll be able to make it ... cost is an issue for me, as is my family situation (my wife will be 6 1/2 months pregnant at the time). I'd really like to though.
“The Northrop Grumman Corporation has completed a feasibility study of new commercial lunar lander configurations for the Golden Spike Company, conceiving of a novel low-mass ascent stage concept for Golden Spike, dubbed Pumpkin.”
The press release has a sketch of the proposed lander fitting within a 5m payload fairing:
On the topic of ITAR, it looks like non-military spacecraft systems will be taken off the munitions list (fingers crossed):
It's already begun! For sure I'll be busy in the next couple of weeks setting up wiki spaces, code repositories, mailing lists, and the foundation itself. But you shouldn't wait for that to add your contribution - it'd be sufficiently on-topic to use the NewMars forum or IRC channel to discuss the project, I think. I'd be very interested to hear your contributions (this thread is fine, or another one if you think it appropriate).
Regarding the Foundation, IP, and common courtesy: that goes without saying. There's two things worth pointing out: (1) copyleft licenses can't be revoked - if you contribute while the project is GPL, then the foundation relicenses under something you don't like, you are free to fork and continue development on the GPL branch; (2) the Foundation would only relicense the project if doing so closes legal loopholes, thereby restoring the intent of the original license. An example would be relicensing to a newer GPL version if/when the FSF updates it, or switching to a specifically open-hardware version if the GPL if/when such a thing is developed.
I would certainly be willing to aid in whatever way I can. What format would you use for intellectual property? CC, GNU, traditional copyright?
CERN has an open hardware license that in principle is similar to the GPL - it's a bit of an tenuous stretch to use software (GPL) or artistic (CC) licenses for hardware projects. However even having said that, I am personally more comfortable with using GPLv3+ instead, as it is a much better understood and legally tested license, provides the necessary copyright, design, and patent releases, allows commercial use of manufactured hardware, is widely used in the open-hardware community, etc.
But part of why I'm starting a foundation is so that it can retain the legal standing necessary to enforce the copyright, patent, and design claims which give the license legal weight, and to allow us to switch licenses or cross-license in the future without having to get the permission of every contributor. So to an extent the choice right now doesn't matter too much.
Further, would you do M-4 first, then M-100, or do them concurrently?
It's really not my decision, but almost certainly they'd be worked on concurrently. It's an open-source / crowd-sourced project, so people contribute what they can to whatever portion of whichever project interests them. Maybe gardening is their hobby so they get involved in the greenhouse project, or maybe they are an architect and want to take a stab at designing Martian living spaces. In either case the work they do would be applicable to either the M-4 or M-100 mission profile.
Another way to think about it is that the vast majority of the work required is not specific to a particular mission, although there will be a few people who concern themselves with making sure the parts assemble within the mass and space budgets of the M-4 or M-100 baseline profile.
This is an open-hardware project. We are not designing an actual mission, but rather a hypothetical mission profile. That baseline profile is then customized by industry or government to suit their own purposes, allowing specific missions to be launched at low cost since only the mission-specific tweaks need to be made, and with economies of scale due to shared components.
And honestly, I don't see the Compendium being constrained to the mission profiles I described. Rather I would like to eventually see open-hardware designs for O'Neil colonies, domed cities on the Moon, asteroid prospecting missions, etc. It's just that I believe the M-4 and M-100 missions are much easier to explain and rally people behind.
M-4 is “send 4 human beings and their science equipment to the surface of Mars, and return them safely home.” M-100 is “establish permanent, self-sufficient human habitation on another world.” I think these two reference projects are simple enough to be easily explained and understood by the general populous, yet compelling enough to attract wide-spread public participation, and general enough to be used in practice as a basis for a variety of actual mission profiles.
What kind of guidelines would be set with regards to mission architectures?
I will set none as I am not dictator of this project. However I hope to work with anyone here who is interested in creating a manifesto both explaining the rationale of the project and providing a baseline set of requirements with justifications. None of it will be set in stone, however, as I hope that we will follow the bottom-up development by consensus mechanism that has worked so well in the open source software world.
Edit: I am at the moment working on a rather closely related project of my own, regarding the development of a robust space infrastructure to support extensive colonization efforts in an economical way. It is very much complementary to a revived Tsiolkovsky Compendium.
We're off topic, but I would love to hear more about what you're working on. I too am working on other projects focused on the economics of space development in cislunar space and NEOs.
Mark Friedenbach wrote:we are seeking to construct a bill of materials and set of blueprints ready to be machined,
I imagine this might be subject to export restrictions. Especially if it included software.
Ah, you're making assumptions about what kind of software. Most of the software written will be simulation & validation work, not flight software. And of the software that actually sees use in the mission, most of the original stuff would have to do with the various gadgets and environmental controls, greenhouse automation, the rover, science lab, Mars habitation module, etc. It's not at all obvious any of that would fall under ITAR regulations.
But even so, some small parts of it might be. In those cases there may end up having to be some compartmentalization, such as having those parts be contributed by non-U.S. persons and not fully integrated with the rest of the project, or otherwise exploiting some legal loophole to maintain compliance. This is similar to how PGP was developed in the 90's, when cryptography was on the U.S. munitions list. There might also be ways to avoid such classification such as the recently created executive branch waiver.
But really, we'd have to be very successful to get far enough that ITAR is a serious problem. Until then, it's not worth worrying about. ITAR is killing American competitiveness, and this is getting recognized at the political level. By the time we encroach on ITAR territory, the situation with non-military applications will probably be very different. But even if it isn't, there are ways we can deal with that.
a) Have you had a chat with Mars One about working with them?
I will, and hopefully they will choose to collaborate. But contributing to or using an open-source effort would mean giving up design and patent rights otherwise held by them or their contractors, so don't hold your breath.
b) How do you plan to make sure that everyone who has access to the project is a U.S. citizen (or not a U.S. Citizen if this is a non-US project)?
Why would that be necessary? If you're talking about ITAR compliance, that's way, way overkill. What's the issue?
c) Would this be governed by the Mars Society or similar if Mars One is keeping everything internal?
It's completely separate from both organizations, although I welcome collaboration with either. I'm in the process of setting up a 501(c)(3) not-for-profit to be the legal steward of the IP rights and to provide supporting services such as virtual workshops and conferences further down the line (modeled after the Python Software Foundation).
(reserved)
Back in early 2011 and before the great crash, there was the Tsiolkovsky Compendium. The purpose was to flesh out in detail a complete reference human mission to Mars, based on Mars Direct / JSC's DRM-3. Progress was made, then a combination of events including said crash and my own newfound responsibilities as a father led to an unfortunate decline of activity and eventual hiatus. Time has passed, but with it has come the advances of SpaceX, Planetary Resources, Mars-One, and Inspiration Mars. In this context I believe the compendium project to be more relevant than ever.
With your help, I would like to restart and finish this great work. The goal of the project is to create two reference mission architectures, which I am tentatively naming M-4 and M-100:
M-4 has basically the same design requirements as Mars Direct, and both Mars Direct and NASA/JSC's third Design Reference Mission (DRM-3) will provide the initial starting points for this mission profile. It will be a conjunction-class mission with a crew of four, a stay of 18 months on the surface, ISRU propellant production for the return trip, and modest but safe equipment lifespans. An M-4 exploration programme would consist of a new mission launched at each window of opportunity until such time that Mars is adequately explored to provide context for the M-100 site selections.
M-100 is a permanent settlement expedition, sending enough people and equipment to build a permanent human settlement and industrial base on Mars. Demonstrable 100% self-sufficiency is the design requirement of this reference mission profile, including dwelling and equipment construction from in-situ resources. (M-100 is a literary allusion to the “first 100” of Kim Stanley Robinson's epic Mars trilogy, but that is all - there is no reason to assume that the actual mission crew size or any aspect of the mission profile will match that described in Robinson's stories.)
Let me be clear: the goal of this project is not yet another paper study and powerpoint slide set. Rather, we are seeking to construct a bill of materials and set of blueprints ready to be machined, rigorous tests and simulations of the equipment and mission profile, operating manuals for all participants, and detailed risk analysis and mitigation strategies.
The key to this project is understanding how we can leverage the thinking and knowledge of 10's of thousands of people (or more) to collectively work for a shared common goal of significant complexity, and to coordinate and collaborate on that scale in a way that creates incredible outcomes.
Is this a huge undertaking? Yes. In part this is an experiment in testing the limits of volunteer projects. However projects of this size are not unheard of: the Linux kernel is probably of similar complexity, having 15 million lines of code and an estimated cost to re-create in the billions of U.S. dollars.
Not long ago I was a contractor at NASA-Ames Research Center, where I worked alongside individuals who contributed to the original NASA design reference mission and the robotic exploration rovers. I will do what I can to call on that social network to provide hard-earned wisdom about Mars mission engineering. I am now a professional open-source software developer, working on a project with 500 contributors and over ten thousand stakeholders. I have experience managing open source software development at scale, and will transfer that experience to coordinating this new open hardware project.
This thread will be the starting point: please post questions and discussion points. In the weeks to come I will setup a dedicated wikispace & mailing list, source code repository, and other coordination/collaboration tools. Please consider joining me in the great endeavor!
Ad astra,
Mark Friedenbach
Yes, Io.
Sulphur volcanoes - why stop them at all. Most of all ( only ) 400-500 Io's volcanoes form distinct volcanic DEPRESSIONS. Hence they'll remain underwater which gives good conditions for various type of biota to eat away / utilize the surphur.
...Highly volcanic and habitable world is not an oximoron , indeedd pretty useful feature volcanism on habitable world shall be - lots of fertilizing, chemicals and energy flow...
Ok, you intrigued me. But where does the water come from?
Midoshi, I just saw the URL. Are you out at Ames now? I just left Ames for the private sector, but I'm still in the valley. Maybe we could get a coffee sometime.
Food for thought:
NASA has stated that MSL is seeking signs of life but that it's not a life detection mission. Does that mean that if NASA detects life on Mars it won't say anything since it is not looking for life to begin with? Sounds an awful lot like a repeat of Gil Levin's labelled release experiment from the Viking landers.
No, it means that none of the instruments on MSL are capable of definitively identifying the presence of the type of microorganisms that we might expect to be in Gale crater if there is life on Mars. If there is life near the surface of Mars, MSL will very likely pick up chemical signatures of it. But in this hypothetical situation, the data would be inconclusive until we get a sample back or send an even more capable rover.
EDIT: Just so that no one gets their hopes up, this landing won't be like MER. MSL will be landing on the far side of Mars, so we will get little more than a confirmation from Mars Odyssey that it has landed and reported home. The mast deployment won't be for a few days, so don't expect any pictures until the end of the week.
7 minutes of terror, followed by a week of check-out boredom.
...I'm surprised there hasn't been more response to this given the massive worldwide media attention this plan has got (more than all Mars groups combined PR power)...
It's probably because this project is all PR. It's vaporware, based on back-of-the-envelope feasibility estimates no actual technical team behind it, as far as I can tell.
The basic idea is workable. But that's just the problem--there's no more technical substance to this than the "basic idea" summed up in a few sentences.
EDIT: However, I of course look forward to being proven wrong.
@louis, I don't think you're wrong per se, just extraordinarily optimistic. Those extrapolations are mostly reasonable for a mature lunar economy many decades down the road, but it is completely unrealistic to assume that a first product would get even within the order of magnitude of full-market penetration.
That market would implode or become inaccessible the moment you bring back a sample with the promise of more on the way. Meterites are fetch high prices because they are a rare, naturally limited product. The people who are paying $20-30 a gam for pallasite have no interest in buying it from you (trust me, I know many of them). Either the entire collectors market will disappear, or more likely it will be come like diamonds: only 'natural' meteorites will continue to have value, and rigorous documentation of the fall is required to sell one.
The NASA Lunar Science Forum, a scientific conference, is being webcast right now. Thought some people might be interested (the link is about a screen down):
Well, that's ironic.
Is there any way you can reasonably work the numbers to get it down to a century or less (0.2c)? Any longer than that and it is possible that regular technological progress would allow a later generation to leave after you and get there first (using, say antimatter propulsion).
What's SpaceX valued at now? If/when it goes public, how much could Musk get while still retaining a majority stake?
I'm not sure what it's currently valued at, but I find it highly unlikely that they will go public any time soon, at least prior to their first manned mission to Mars. Investors could always cash out via secondary markets, and between the Tesla and Solar City IPO's Elon will have no shortage of cash.
Going public would be a burden for SpaceX--they would have new shareholder pressures to focus on quarterly growth, which doesn't align well with being a nimble long-term growth company with an eye on Mars.
Well, SpaceX sending anything other than the Red Dragon demonstrator to Mars in less than eight years is pretty unlikely, but 2045 is pretty far out too. NASA could certainly send humans there in the 2020's if there was enough of a shake-up, so I don't see why SpaceX couldn't do the same with enough resources. NASA footing the bill would be nice, but not at all necessary. Keep in mind that many of the people who pioneered the latest generation of space tech now work for SpaceX. As long as there's money coming in the door, there's nothing they can't do as good or better and faster.
That incident was on Mir not ISS, I believe.
Anyway, way to go SpaceX! Ad Ares!
The key point is that claims of sovereignty is different from claims of property/exclusive use rights. The article by Jeff Faust goes over this issue pretty well.
Right, so the OST doesn't prohibit space colonies, it only prohibits calling them that...
Pretty much And when the former colonies on Earth figured that out, they created the Moon Treaty to close those loopholes.. and no one of consequence ratified it.
Touché.
However, maybe louis is right - things which aren't specifically forbidden are therefore allowed, and as he says, there is nothing in the treaty outlawing asteroid mining... so therefore it is permitted?
Precisely. The OST in this regard is a proscriptive document--it only makes firm claims about what can't be done in space (militarization, nuclear weapons, national claims of sovereignty, etc.). It makes limited prescriptive claims about what must be done in the case of emergency landings on foreign territory, rendering emergency assistance in space, discovery of mutual threats, and other similar concerns.
Claims that the OST disallows whole categories of economic activity are based on Article I, which has the “for the benefit and in the interests of all countries” language and, I think, conflation with the language and purpose of the Moon Treaty which was not ratified by any major space player. The text of the OST makes clear that the “for the benefit...” language is meant to be proscriptive of large countries bullying smaller countries in space, to mandate tolerance of space programs in developing countries, and to offer a vague mandate for collaboration on scientific endeavors. That's it. Heck, it's not very long, so I'll just quote it in its entirety:
Article I
The exploration and use of outer space, including the moon and other celestial bodies, shall be carried out for the benefit and in the interests of all countries, irrespective of their degree of economic or scientific development, and shall be the province of all mankind.
Outer space, including the moon and other celestial bodies, shall be free for exploration and use by all States without discrimination of any kind, on a basis of equality and in accordance with international law, and there shall be free access to all areas of celestial bodies.
There shall be freedom of scientific investigation in outer space, including the moon and other celestial bodies, and States shall facilitate and encourage international co-operation in such investigation.
The very existence of the Moon Treaty and its lack of ratification by major players shows intent that this limited (and currently, official) interpretation of the OST is what the signatory governments had in mind at the time of its ratification. And that's ignoring the copious information available about the negotiations accompanying the drafting of the OST which make clear that its purpose was demilitarizing space and ensuring the safety of astro/cosmonauts--not to place restrictions on private enterprise, use, or claims of property, which is why the Moon Treaty was later drafted (and failed).