I2P_Developers/i2p.www
3
0
Fork 5
Code Issues 27 Pull Requests Actions 1 Packages Projects Releases Wiki Activity

typo fix, new ipv6 bounty done

Browse Source
This commit is contained in:
echelon2
2014-02-17 09:11:02 +00:00
parent b71c676a97
commit 30d12a9c47
2 changed files with 8 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
i2p2www/pages/site/get-involved/bounties/ipv6.html
View File

@ -11,6 +11,12 @@ IPv6 connections like it does on IPv4.
{%- endtrans %}</p>
<br>
Bounty is done as of I2P 0.9.8 and money paid to the I2P team.
<br>
As a extension to this bounty, a new bounty was created out of this.
This new bounty included running a IPv6 router for some time in 2013.
That timeframe is already over and the participants were paid out.
Read more about this in the <a href="http://echelon.i2p/bounty/ipv6bounty.txt">
IPv6 bounty rules</a> on echelon.i2p.
{% endblock %}
{% block bountynotes %}

4
i2p2www/pages/site/get-involved/bounties/silc.html
View File

@ -3,7 +3,7 @@
{% block donatename %}{{ _('I2P silc server') }}{% endblock %}
{% block bountydetails %}
<!-- file version 2012.01.01.01 -->
<!-- file version 2014.02.17.01 -->
<p>{% trans -%}
For a future of I2P and attract more people
into I2P this bounty is to setup and host a I2P SILC server.
@ -11,7 +11,7 @@ This will allow people to send files over their messaging servers and have intri
{%- endtrans %}</p>
<p>{% trans -%}
A silc server needs to be set up and run for at least 3 month time to get payed.
A second server should be set up, to.
A second server should be set up, too.
{%- endtrans %}</p>
<p>{% trans -%}
Bounty was withdrawn and money donated to returningnovice and general fund.