Difference between revisions of "Talk:People needed"

From OpenLuna
Jump to: navigation, search
Line 15: Line 15:
 
3) Cut and SWIP.  You have not said where the money is coming from to do this project and yet you have laid out a very complex and extensive array of 'required' missions and technologies.  This is hurting your credibility.  Reduce this down to a single booster concept, for example, and re-examine the need for some of the unmanned flights.  This will give the project a more manageable feel.
 
3) Cut and SWIP.  You have not said where the money is coming from to do this project and yet you have laid out a very complex and extensive array of 'required' missions and technologies.  This is hurting your credibility.  Reduce this down to a single booster concept, for example, and re-examine the need for some of the unmanned flights.  This will give the project a more manageable feel.
  
4) Auto-response.  Do not let posted items go unacknowledged for more than two days.  This includes e-mails sent to you or anyone on your team.  It is less about people's ego than it is about their enthusiasm.  You will start to see things accelerate in a good way when communications are at least responded to.  The response does not have to be a full-blown assessment of the writer's super-coo; new idfea; just a frendly acknowledgement will go a long way towards keeping their interest.
+
4) Auto-response.  Do not let posted items go unacknowledged for more than two days.  This includes e-mails sent to you or anyone on your team.  It is less about people's ego than it is about their enthusiasm.  You will start to see things accelerate in a good way when communications are at least responded to.  The response does not have to be a full-blown assessment of the writer's super-cool new idea; just a frendly acknowledgement will go a long way towards keeping their interest.
  
 
5) As for the wiki, I would go so far as to deliberately seek out someone who provides webmaster services to manage it.  If you work a deal you can possibly get a year or two of their support for a fairly small fee.  It is absolutely vital to your organization's goals, it needs to be done right the first time.  Hard cash will solve that problem.
 
5) As for the wiki, I would go so far as to deliberately seek out someone who provides webmaster services to manage it.  If you work a deal you can possibly get a year or two of their support for a fairly small fee.  It is absolutely vital to your organization's goals, it needs to be done right the first time.  Hard cash will solve that problem.

Revision as of 09:49, 11 November 2008

This is a place for people to discuss what they can and are willing to do.

It is read every time there is a change, so, please, let us know what you can do, and we will help you do it.

11/11/08 Hopefully this will boost your recruitment a little: on the 'Myspace' there is a group called Lunar Base with a man named 'Holio' as the moderator. It is not a design group per se, more like a free association chat room. Since membership is open to public and totally free, its worth it to join, post an invitation bulletin and then, periodically, post a progress report. I'm pretty sure Holio (that is his screen name) would be o.k. with this and offer some helpful ideas. He's pretty sharp.

That said, there are a couple of other pointers you may want to consider:

1) Exchange work. Offer your team's talents to other similar projects in exchange for assistance with key issues. Management of the wiki is a case in point.

2) Do not wait for volunteers to open up about what they want to do. Ask them to tell you a little about themselves and, from the info they give you, suggest a number of specific areas they could help you with. Most of the interested parties will be non-professionals who can still do great quality work.

3) Cut and SWIP. You have not said where the money is coming from to do this project and yet you have laid out a very complex and extensive array of 'required' missions and technologies. This is hurting your credibility. Reduce this down to a single booster concept, for example, and re-examine the need for some of the unmanned flights. This will give the project a more manageable feel.

4) Auto-response. Do not let posted items go unacknowledged for more than two days. This includes e-mails sent to you or anyone on your team. It is less about people's ego than it is about their enthusiasm. You will start to see things accelerate in a good way when communications are at least responded to. The response does not have to be a full-blown assessment of the writer's super-cool new idea; just a frendly acknowledgement will go a long way towards keeping their interest.

5) As for the wiki, I would go so far as to deliberately seek out someone who provides webmaster services to manage it. If you work a deal you can possibly get a year or two of their support for a fairly small fee. It is absolutely vital to your organization's goals, it needs to be done right the first time. Hard cash will solve that problem.

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox