== Krzysztof's take on OpenHatch.org ==
tough it is a very young project, has proven to deliver what it [https://openhatch.org/about/ promises] (take me as a perfect example). Like any other young project, however, it gets some things right from the very beginning, while some areas need time to evolve (plus a lot of effort). Recent [http://irclogs.jackgrigg.com/irc.freenode.net/openhatch/2011-01-31#i_2523847 feedback from glyph] is a proof of that.
The following content is my attempt to identify ideas and concepts that should work toward achieving OpenHatch's mission. Although the observation is not based on data of any kind (be it raw numbers or simple feedback), it can still prove useful as a visionary playground for future releases.
==== Game mechanics ====
Game mechanics is the new hotness. In our case, they
are the necessity - we want new contributors to feel that they are making progress, be it by completing missions, being promoted to project maintainer or by closing bugs.
I personally think that ''missions'' is a good place to start leveraging game mechanics. We could introduce ''badges'' or ''titles'' system based on mission completeness and difficulty. But first, we need more missions which are build with game mechanics in mind.
* A forum+mailing list where people discuss what they like and don't like about the site.
=== Problems with the volunteer opportunity finder (and suggested changes) ===
The purpose of the volunteer opportunity finder is to help people make their first open source contribution. I'm most interested in the target audience of people with no solid social connection to other contributors, largely because I believe that helping those people is the ticket out of the community's diversity problems.
** Use of the OpenHatch buildhelper
=== Most projects don't want to put in the time to encourage participation; how can we help projects that do want new contributors highlight that? ===
I think the above is the biggest question for OpenHatch. As a goal, it's not important that OpenHatch have a website at all. If all the projects could just communicate consistently, clearly, and instructively to new contributors, then they would all get more contributors.
In addition, there are things that not all project maintainers ''know''. Bitesize bugs are one cultural thing that some projects do that others probably haven't even thought about. Another is telling new contributors that their emails will get answered within four days.
=== Asheesh thinks people don't follow things they read ===
I think that IRC-based tutorials on "How to run your project well?" in which people chat with OpenHatch people about how they could run their project well would go a long way.