| User | Post |
|
11:44 am November 19, 2009
| Rocket-To-The-Moon
| | Altus, Oklahoma, USA | |
| Member | posts 685 | |
|
|
Do we need some sort of design doctrine that guides decisions?
- Inexpensive
- Off the shelf if possible
- Light weight
- Easy to manufacture
- Simple to design
- Reliable
- Innovate at all oportunities
Sort of common sense, but if we want to stay on budge we need somethign to follow. We can write a full up wiki article on our design doctrine once we have a better idea of what we want.
|
Main Workgroups: Propulsion & Spacecraft Engineering
|
|
|
4:41 am November 20, 2009
| Luke Maurits
| | Adelaide, Australia | |
| Admin
| posts 1483 | |
|
|
You, sir, have read my mind! I think we definitely need a page like this on the Wiki, I have been meaning to bring it up for a while. I don't think we are likely to succeed at our ambitious projects without sticking fairly tightly to a doctrine like the one you have outlined. I think this culture was fairly pervasive amongst the original team at Reddit, but now that we have welcomed a whole lot of new members (which is great!) it would probably help to come up with an explicit formulation of our design philosophy so that everybody is on the same page.
I think the old standard maxim "Keep it simple, stupid" should make an appearance somewhere, and perhaps also something along the lines of "do the simplest thing that could possibly work".
We need to be careful, though, that we don't come across as advocating a position of "cutting corners" or "near enough is good enough" or anything like that, because that's not accurate and it doesn't place us in a good light.
Really very excited to see this under discussion!
|
Main CLLARE workgroups: Mission Planning, Navigation and Guidance. I do maths, physics, C, Python and Java.
|
|
|
7:39 pm November 21, 2009
| Luke Maurits
| | Adelaide, Australia | |
| Admin
| posts 1483 | |
|
|
I've created a page in the Wiki for figuring out a proper statement of these philosophies.
|
Main CLLARE workgroups: Mission Planning, Navigation and Guidance. I do maths, physics, C, Python and Java.
|
|
|
7:41 pm November 21, 2009
| Rocket-To-The-Moon
| | Altus, Oklahoma, USA | |
| Member | posts 685 | |
|
|
Luke Maurits said:I've created a page in the Wiki for figuring out a proper statement of these philosophies.
I'll work on expanding it later. How do I create sub-bullets? I'm not fully up to speed on wiki code.
|
Main Workgroups: Propulsion & Spacecraft Engineering
|
|
|
8:19 pm November 21, 2009
| Luke Maurits
| | Adelaide, Australia | |
| Admin
| posts 1483 | |
|
|
I've just put in a three-deep hierarchy of bullets that you can copy, paste and modify as you need.
|
Main CLLARE workgroups: Mission Planning, Navigation and Guidance. I do maths, physics, C, Python and Java.
|
|
|
8:35 pm November 21, 2009
| Rocket-To-The-Moon
| | Altus, Oklahoma, USA | |
| Member | posts 685 | |
|
|
|
|
Main Workgroups: Propulsion & Spacecraft Engineering
|
|
|
3:25 am November 22, 2009
| Luke Maurits
| | Adelaide, Australia | |
| Admin
| posts 1483 | |
|
|
A little bit of inspiration relevant to writing out our design philosophies, from the FAQ of Armadillo Aerospace:
How is your approach to building rockets different from government space programs
We approach rocket design much like software design – build many different incremental designs that we can test constantly and work out all the kinks as we go. Build, test, fix, then test again.
Following a typical Big Aerospace design approach would be like programming a software design for months or years without ever being able to compile and test your code. And then getting only one chance to let 'er rip, crossing your fingers and hoping all your mountains of paper studies will pay off and nothing will go wrong the first time out. NASA has shown that such an approach can work, but at such great cost and time that a great many of its projects never move beyond the paper study stage. We'd rather actually fly everything we design, and see in the real world what works and what doesn't, so we can build off that first-hand experience on future designs.
|
Main CLLARE workgroups: Mission Planning, Navigation and Guidance. I do maths, physics, C, Python and Java.
|
|
|
10:51 pm December 6, 2009
| Luke Maurits
| | Adelaide, Australia | |
| Admin
| posts 1483 | |
|
|
Out of all the major defining documents that I think we should endeavour to finalise and Wiki-lock within a week, this is the one that has received the most attention and is looking the most complete. Nevertheless, it isn't necessarily finished. Does anybody want to clarify anything that is currently on the wiki page or add anything new?
|
Main CLLARE workgroups: Mission Planning, Navigation and Guidance. I do maths, physics, C, Python and Java.
|
|
|
1:12 am December 11, 2009
| Luke Maurits
| | Adelaide, Australia | |
| Admin
| posts 1483 | |
|
|
Now that we have a mission statement people seem largely happy with, and the finalisation of the social contract is going very well and seems almost finished, this is the last defining document to see some last minute polish and discussion. Can everyone please have a look at the current design philosophy page and raise any concerns they have?
|
Main CLLARE workgroups: Mission Planning, Navigation and Guidance. I do maths, physics, C, Python and Java.
|
|
|
8:05 pm December 15, 2009
| Luke Maurits
| | Adelaide, Australia | |
| Admin
| posts 1483 | |
|
|
Since there has been no comment on the current version of the Design Philosophy for some time now, I am going to assume that everybody interested in it is happy with the current version. So, this shall become our Design Philosophy 1.0! I will moderator-lock the Wiki page after making this post. This will be the Design Philosophy adopted at our first meeting after incorporation and any changes to it will have to happen in accordance with the bylaws (i.e. changes will be voted on and adopted only if more than a certain percentage of members want them).
Since the current Mission Statement and Social Contract have also gone a long time without comment, it makes sense to moderator-lock these too (again, these documents should be modifiable after incorporation in accordance with bylaws). With these documents polished and finalised, along with good recent Wiki work, we can present a fairly organised and official looking face to other groups. I think now would be a great time to push ahead with contacting other groups. Some plans for how to do this are in a Friends of CSTART thread elsewhere, which have so far received very little comment. Whether you love or hate those plans, make some noise so we can figure out what to do. If we can lock in our documents and make contact with a few other groups (especially Copenhagen Suborbital) in the same week it will make that week a big achievement for us – worthy of the first post to our neglected blog, I should think!
|
Main CLLARE workgroups: Mission Planning, Navigation and Guidance. I do maths, physics, C, Python and Java.
|
|
|
8:28 pm December 15, 2009
| Rocket-To-The-Moon
| | Altus, Oklahoma, USA | |
| Member | posts 685 | |
|
|
Post edited 2:29 am – December 16, 2009 by Rocket-To-The-Moon
I am happy with the design philosophies, mission statement, and social contract. What we really need is one page (a blog post here on cstart.org) that provides a narrative along with links to wiki pages and integrated images and charts. Just something that will take 10 minutes to read through so that a newcomer can get the big picture.
We can whip up a Google Docs document for collabortion on this.
|
Main Workgroups: Propulsion & Spacecraft Engineering
|
|
|
8:43 pm December 15, 2009
| Luke Maurits
| | Adelaide, Australia | |
| Admin
| posts 1483 | |
|
|
All 3 of the official documents are now Wiki-locked with a fancy little notice at the top.
Your idea is a good one, we do need to have something like this, although I'm not sure where it would be best to put it. Anyway, let's start a thread for this idea and get to work on it.
If you have some spare time at the moment, I would very much appreciate your input on the Friends of CSTART stuff, too.
|
Main CLLARE workgroups: Mission Planning, Navigation and Guidance. I do maths, physics, C, Python and Java.
|
|
|
10:11 pm December 15, 2009
| noumena
| | |
| Member | posts 36 | |
|
|
Let's get rolling then :-) For what it's worth, I am satisfied with all of it.
|
|
|
10:14 pm December 15, 2009
| Luke Maurits
| | Adelaide, Australia | |
| Admin
| posts 1483 | |
|
|
noumena said:Let's get rolling then :-) For what it's worth, I am satisfied with all of it.
That's the spirit! And good to hear!
Have you read the Friends of CSTART info page and Offer of Friendship template? There is a thread in the "Similar Organizations" subforum for discussing / improving them. I know you've already mentioned you don't like the name "Friends of CSTART", and at this point we can still change that – just imagine something appropriate going in its place when you read the draft documents and worry at this stage more about what those documents say.
|
Main CLLARE workgroups: Mission Planning, Navigation and Guidance. I do maths, physics, C, Python and Java.
|
|