== 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.
* The "Reach out to university students to teach them about open source" task force
(Why have them require
=== Rambling: 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? ===
When running the Penn workshop, I saw that there was a huge amount of interest from students who wanted to do something neat with open source.