i2p.www/www.i2p2/pages/getinvolved.html

{% extends "_layout.html" %}
{% block title %}Get Involved!{% endblock %}
{% block content %}
<h1>We need your help!</h1>
<p>To get involved, please feel free to join us on the #i2p IRC channel (on
irc.freenode.net, or within I2P on irc.freshcoffee.i2p or irc.postman.i2p).</p>
<p>If you're interested in joining our <a href="team">team</a>, please get in
touch as we're always looking for eager contributors!</p>    
<p>
We need help in many areas, and you don't need to know Java to contribute!
Here's a list to help you get started!</p>
<ul>
<li><b>Spread the Word!</b> &mdash;
Tell people about I2P on forums, blogs, and comments to articles.
Fix up the Wikipedia article about I2P in your language.
Tell your friends.
</li><li><b>Testing</b> &mdash;
Run the latest builds from <a href="monotone.html">monotone</a>
and report results on #i2p or as bugs on <a href="http://trac.i2p2.de/report/1">Trac</a>.
</li><li><b>Documentation</b> &mdash;
Help fix the parts of the website that are outdated or incomplete.
Translate pages into other languages.
</li><li><b>Pictures</b> &mdash;
Make some more pictures, fix the old ones on the website
</li><li><b>Content</b> &mdash;
Make an eepsite! Add some content! Contribute to the community!
</li><li><b>Services</b> &mdash;
Run a service on an eepsite. It could be a proxy, a forum, a tracker,
a naming service, a search engine, an eepsite monitor... many of these
aren't that hard.
</li><li><b>Applications</b> &mdash;
Write or port applications for I2P! There's some guidelines and
a list of ideas on the <a href="applications.html">applications page</a>.
</li><li><b>Coding</b> &mdash;
There's plenty to do if you know Java or are ready to learn.
Check for open tickets on <a href="http://trac.i2p2.de/report/1">Trac</a>
or the TODO list on <a href="http://zzz.i2p/">zzz.i2p</a> for
some ideas on where to start.
See the <a href="newdevelopers.html">new developer's guide</a> for details.
</li><li><b>Translation</b> &mdash;
Help translate the website and the software into your language.
See the <a href="newtranslators.html">new translator's guide</a> for details.
</li><li><b>Analysis</b> &mdash;
Study or test the code to look for vulnerabilities.
Both anonymity vulnerabilities from the various
<a href="how_threatmodel.html">threat models</a>,
and DOS and other weaknesses due to securities holes,
need researching.
</li><li><b><a href="donate.html">Donate</a></b>

</li></ul>
{% endblock %}