We need to describe the overall goal we're trying to achieve with DM2, break it up into manageable small steps and come up with a realistic timeframe / amount of hours to make it happen.
- Look through lanyrd and ask people we know if they can spread the word about our campaign at conferences
- Contact popular podcasts and ask if they're willing to feature our campaign and ask people to contribute
- rubyrogues
- changelog
- ...
- Contact companies known for a history of funding OSS development
- Post on popular sites
- hackernews
- ...
- Put the word out on twitter, encourage our networks to spread the word
- Have a project page that provides a quick overview about the development status, and makes it easy to contribute to the campaign
- Contact previous/current employers if they'd be willing to chip in
I strongly believe in documentation. If you we do a good job of demo examples and great docs, other geeks will write and talk about DM2 in newsletters, social media etc.
To set off you have to present something to the community. I believe if we put in the time to come up with great docs, demos, screen-casts etc, we will win the community over in a night.
Do it like Steve Jobs ;)