lbt/I2P_Website
1
0
Fork 0
forked from I2P_Developers/i2p.www
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

update get-involved and remove the bounties

Browse Source
This commit is contained in:
hankhill19580
2019-08-03 18:17:32 +00:00
parent 07b6a9966d
commit 790e3fbbbf
16 changed files with 94 additions and 700 deletions
Download Patch File Download Diff File Expand all files Collapse all files

66
i2p2www/blog/2019/07/29/august-conferences.rst
View File

@@ -1,48 +1,48 @@
.. meta:: .. meta::
:title: {% trans %}August 2019 Conference Schedule{% endtrans %} :title: August 2019 Conference Schedule
:author: sadie :author: sadie
:date: 2019-07-29 :date: 2019-07-29
:excerpt: {% trans %}I2P developers are attending multiple conferences this month{% endtrans %} :excerpt: I2P developers are attending multiple conferences this month
{% trans %}Conference Schedule August 2019{% endtrans %} Conference Schedule August 2019
======================================================== ===============================
{% trans %}Hi Everyone{% endtrans %}, Hi Everyone,
{% trans %}Next month will be busy! Meet up with I2P developers at two workshops at Next month will be busy! Meet up with I2P developers at two workshops at
Defcon 27, and connect with researchers who have been observing I2P censorship Defcon 27, and connect with researchers who have been observing I2P censorship
at FOCI '19.{% endtrans %} at FOCI '19.
{% trans %}I2P for Cryptocurrency Developers{% endtrans %} I2P for Cryptocurrency Developers
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|zzz| |zzz|
- {% trans %}Monero Village{% endtrans %} - Monero Village
- {% trans %}August 9, 3:15pm{% endtrans %} - August 9, 3:15pm
- {% trans %}Monero Village will be on the 26th floor of Bally's{% endtrans %} `map <https://defcon.org/html/defcon-27/dc-27-venue.html>`__ - Monero Village will be on the 26th floor of Bally's `map <https://defcon.org/html/defcon-27/dc-27-venue.html>`__
{% trans %}"This workshop will assist developers in designing applications to communicate This workshop will assist developers in designing applications to communicate
over I2P for anonymity and security. We will discuss common requirements for over I2P for anonymity and security. We will discuss common requirements for
cryptocurrency applications, and review each application's architecture and cryptocurrency applications, and review each application's architecture and
specific needs.Then, we will cover tunnel communications, router and library specific needs.Then, we will cover tunnel communications, router and library
selection, and packaging choices, and answer all questions related to selection, and packaging choices, and answer all questions related to
integrating I2P."{% endtrans %} integrating I2P.
{% trans %}"The goal is to create secure, scalable, extensible, and efficient designs that The goal is to create secure, scalable, extensible, and efficient designs that
meets the needs of each particular project."{% endtrans %} meets the needs of each particular project.
{% trans %}I2P For Application Developers{% endtrans %} I2P For Application Developers
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|idk| |idk|
- {% trans %}Crypto & Privacy Village{% endtrans %} - Crypto & Privacy Village
- {% trans %}Saturday August 10, 2pm - 3:30pm{% endtrans %} - Saturday August 10, 2pm - 3:30pm
- {% trans %}Planet Hollywood{% endtrans %} `map <https://defcon.org/images/defcon-27/maps/ph-final-public.pdf>`__ - Planet Hollywood `map <https://defcon.org/images/defcon-27/maps/ph-final-public.pdf>`__
- {% trans %}This workshop is not recorded. So don't miss it!{% endtrans %} - This workshop is not recorded. So don't miss it!
{% trans %}"The workshop provides an introduction to the ways an application can be made to The workshop provides an introduction to the ways an application can be made to
work with the I2P Anonymous Peer-to-Peer network. Developers should learn that work with the I2P Anonymous Peer-to-Peer network. Developers should learn that
the use of anonymous P2P in their applications need not be that different than the use of anonymous P2P in their applications need not be that different than
what they are already doing in non-anonymous Peer-to-Peer applications. It what they are already doing in non-anonymous Peer-to-Peer applications. It
@@ -51,20 +51,20 @@ plugins set themselves up to do communication over I2P and what's good and bad
about each approach. Afterwards, we'll continue on to the programatically about each approach. Afterwards, we'll continue on to the programatically
controlling I2P via it's SAM and I2PControl API's. Finally, we'll take a dive controlling I2P via it's SAM and I2PControl API's. Finally, we'll take a dive
into the SAMv3 API by starting a new library utilizing it in Lua and writing a into the SAMv3 API by starting a new library utilizing it in Lua and writing a
simple application."{% endtrans %} simple application.
{% trans %}Measuring I2P Censorship at a Global Scale{% endtrans %} Measuring I2P Censorship at a Global Scale
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|sadie| |sadie|
- {% trans %}FOCI '19{% endtrans %} - FOCI '19
- {% trans %}Tuesday August 13th 10:30am{% endtrans %} - Tuesday August 13th 10:30am
- {% trans %}Hyatt Regency Santa Clara{% endtrans %} - Hyatt Regency Santa Clara
- {% trans %}Co-located with USENIX Security '19{% endtrans %} - Co-located with USENIX Security '19
- `{% trans %}Workshop Program{% endtrans %} <https://www.usenix.org/conference/foci19/workshop-program>`__ - `Workshop Program <https://www.usenix.org/conference/foci19/workshop-program>`__
{% trans %}"The prevalence of Internet censorship has prompted the creation of several The prevalence of Internet censorship has prompted the creation of several
measurement platforms for monitoring filtering activities. An important measurement platforms for monitoring filtering activities. An important
challenge faced by these platforms revolves around the trade-off between depth challenge faced by these platforms revolves around the trade-off between depth
of measurement and breadth of coverage. In this paper, we present an of measurement and breadth of coverage. In this paper, we present an
@@ -80,7 +80,7 @@ period of one month, we conducted a total of 54K measurements from 1.7K network
locations in 164 countries. With different techniques for detecting domain name locations in 164 countries. With different techniques for detecting domain name
blocking, network packet injection, and block pages, we discovered I2P blocking, network packet injection, and block pages, we discovered I2P
censorship in five countries: China, Iran, Oman, Qatar, and Kuwait. Finally, we censorship in five countries: China, Iran, Oman, Qatar, and Kuwait. Finally, we
conclude by discussing potential approaches to circumvent censorship on I2P."{% endtrans %} conclude by discussing potential approaches to circumvent censorship on I2P.
.. |zzz| image:: /_static/images/monerovillageblog.png .. |zzz| image:: /_static/images/monerovillageblog.png
.. |idk| image:: /_static/images/cryptovillageblog.png .. |idk| image:: /_static/images/cryptovillageblog.png

1
i2p2www/pages/global/nav.html
View File

@@ -122,7 +122,6 @@
<li><a href="{{ site_url('get-involved/guides/new-translators') }}"><div class="menuitem"><span>{{ _('New translators') }}</span></div></a></li> <li><a href="{{ site_url('get-involved/guides/new-translators') }}"><div class="menuitem"><span>{{ _('New translators') }}</span></div></a></li>
</ul> </ul>
</li> </li>
<li><a href="{{ site_url('get-involved/bounties') }}"><div class="menuitem"><span>{{ _('Bounties') }}</span></div></a></li>
<li><a href="{{ site_url('get-involved/donate') }}"><div class="menuitem"><span>{{ _('Donate') }}</span></div></a></li> <li><a href="{{ site_url('get-involved/donate') }}"><div class="menuitem"><span>{{ _('Donate') }}</span></div></a></li>
<li><a href="{{ get_url('meetings_index') }}"><div class="menuitem"><span>{{ _('Meetings') }}</span></div></a></li> <li><a href="{{ get_url('meetings_index') }}"><div class="menuitem"><span>{{ _('Meetings') }}</span></div></a></li>
<li><a href="{{ site_url('get-involved/roadmap') }}"><div class="menuitem"><span>{{ _('Roadmap') }}</span></div></a></li> <li><a href="{{ site_url('get-involved/roadmap') }}"><div class="menuitem"><span>{{ _('Roadmap') }}</span></div></a></li>

39
i2p2www/pages/site/get-involved/bounties/arabic-trans.html
View File

@@ -1,39 +0,0 @@
{% extends "global/bounty.html" %}
{% block title %}{{ _('Bounty Arabic translation of webpage and router console') }}{% endblock %}
{% block donatename %}{{ _('Arabic translation') }}{% endblock %}
{% block bountydetails %}
<p>{% trans -%}
To improve I2P usage and attract more people
into I2P echelon set out this bounty for translation
of the I2P web page and I2P router console into Arabic.
{%- endtrans %}</p>
<p>
{{ _('This bounty is set into 2 subparts:') }}
<br>
{{ _('Part 1 is translation of the webpage.') }}<br>
</p>
<p>
{{ _('For collecting the bounty of 20 BTC you need to translate the following pages:') }}<br>
http://www.i2p2.de/index.html<br>
http://www.i2p2.de/download.html<br>
http://www.i2p2.de/intro.html<br>
http://www.i2p2.de/faq.html<br>
http://www.i2p2.de/bounties.html<br>
http://www.i2p2.de/getinvolved.html<br>
http://www.i2p2.de/donate.html<br>
{{ _('This job was done by hamada and the bounty of 20 BTC was paid to hamada.') }}<br>
</p>
<p>{% trans -%}
Part 2 is the translation of the router console. The router console was
partly translated and the bounty of 80 BTC was paid to hamada.
{%- endtrans %}</p>
{% endblock %}
{% block bountyjudge %}
<p>{% trans -%}
Judge is echelon.
{%- endtrans %}</p>
{% endblock %}
{% block bountynotesouter %}{% endblock %}

20
i2p2www/pages/site/get-involved/bounties/btc-client.html
View File

@@ -1,20 +0,0 @@
{% extends "global/bounty.html" %}
{% block title %}{{ _('Bounty creating a I2P native Bitcoin client') }}{% endblock %}
{% block donatename %}{{ _('BTC I2P native client') }}{% endblock %}
{% block bountydetails %}
<p>{% trans -%}
For a future of I2P and attract more people
into I2P this bounty is to create a I2P native Bitcoin client.
It should integrate with other client via the I2P network and via gateways to
the existant bitcoin network.
{%- endtrans %}</p>
{% endblock %}
{% block bountyjudge %}
<p>{% trans -%}
Judge is psychonaut who donated the first 30 &euro; to this bounty.
Bounty was almost fullfilled with <a href="http://echelon.i2p/btci2p/">btci2p</a>, only a small
part of creating a plugin is leftover. User giv has been paid for the work.
{%- endtrans %}</p>
{% endblock %}

42
i2p2www/pages/site/get-involved/bounties/datastore.html
View File

@@ -1,42 +0,0 @@
{% extends "global/bounty.html" %}
{% block title %}{{ _('Bounty datastorage') }}{% endblock %}
{% block donatename %}{{ _('datastore') }}{% endblock %}
{% block bountydetails %}
<p>{% trans -%}
To improve I2P's usage and to be independent of routers
online status we want a datastorage as a extension to I2P.
Like in Freenet the datastorage should be distributed and every
participating node should be able to configure his options.
The files should be saved in chunks and at least 2-3 times to
obtain redundancy. Usage of storage space should be auto balanced.
As it is a extra application, it should work flawless within I2P and
cooperate nice with the I2P router. Maybe a integration within the
webpage/router could be done.
{%- endtrans %}</p>
<p>{% trans -%}
This bounty cooperates with the 2 other bounties "frost for I2P" and
"eepsites in datastorage".
{%- endtrans %}</p>
<p>{% trans -%}
The frost for I2P datastorage bounty is paid for a frost like program
with which files/messages are stored into database and got from database.
It needs to work with a GUI.
{%- endtrans %}</p>
<p>{% trans -%}
The eepsite served out of I2P datastorage extends a I2P router to send
out eepsites out of the I2P datastorage. All files for eepsites need to be
saved inside of datastorage and are taken from it.
Extension:
For better integration all datastorage participants could serve that eepsite.
{%- endtrans %}</p>
{% endblock %}
{% block bountynotes %}
<li>{% trans -%}
For bounties to be declared done and paid, we need the program AND the source.
Source and code need to be licensed under a free license (free to change and
free to distribute).
{%- endtrans %}</li>
{{ super() }}
{% endblock %}

17
i2p2www/pages/site/get-involved/bounties/deb-pack.html
View File

@@ -1,17 +0,0 @@
{% extends "global/bounty.html" %}
{% block title %}{{ _('Bounty I2P package in Debian and Ubuntu mirrors') }}{% endblock %}
{% block donatename %}{{ _('I2P Ubuntu/Debian package') }}{% endblock %}
{% block bountydetails %}
<p>{% trans -%}
For the future of I2P and in order to attract more people
to I2P, this bounty was set for including an I2P package into the Ubuntu and Debian
archive mirrors.
To claim this bounty, the I2P router package needs to be available from
Ubuntu and Debian archive mirrors and Debian bug
<a href="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=448638">448638</a>
needs to be closed successfully.
Done in 2017 by mhatta.
{%- endtrans %}</p>
{% endblock %}

13
i2p2www/pages/site/get-involved/bounties/i2phex.html
View File

@@ -1,13 +0,0 @@
{% extends "global/bounty.html" %}
{% block title %}{{ _('Bounty I2PHex code implementation') }}{% endblock %}
{% block donatename %}{{ _('i2phex code implementation') }}{% endblock %}
{% block bountydetails %}
<p>{% trans -%}
To improve I2P usage and attract more people
into I2PHex P2P ArneBab setout the bounty for implementing actual
Phex code onto I2PHex.
{%- endtrans %}</p>
{% endblock %}
{% block bountynotesouter %}{% endblock %}

94
i2p2www/pages/site/get-involved/bounties/index.html
View File

@@ -1,94 +0,0 @@
{% extends "global/layout.html" %}
{% block title %}{{ _('Bounties for I2P') }}{% endblock %}
{% block content %}
<!-- file version 2013.03.31.01 -->
<p>{% trans -%}
While we always gratefully accept any contributions of code,
documentation, and the like, there are other ways to help I2P move
forward. As with any open source project, our goals would be achieved more
rapidly if we were able to support all of our contributors to work on
I2P full time. However, as with any open source project, that's not a
possibility. Instead, we are making use of a bounty system, whereby
anyone can get support for working on something that people want
implemented, and people who want to contribute to I2P can be assured that
their support goes to what they care about.
{%- endtrans %}</p>
<p>{% trans -%}
We are also keeping open the ability for people who want to support I2P
but don't have strong feelings about the bounties available. Those people
can simply put their trust in the I2P team to do what we feel is best by
donating to a catch-all general fund that will be used as deemed
necessary - allocated to various bounties, covering incidentals (hosting,
etc), and the like.
{%- endtrans %}</p>
<h2>{{ _('Claimed bounties') }}</h2>
<table border="1">
<tr><td><p><b>{{ _('Name') }}</b></p></td><td><p><b>{{ _('Status') }}</b></p></td><td><p><b>{{ _('Dev team') }}<sup>*</sup></b></p></td></tr>
<tr>
<td><p><b><a href="{{ site_url('get-involved/bounties/deb-pack') }}">{{ _('I2P package in Debian and Ubuntu mirrors') }}</a></b></p></td>
<td><p>Claimed by mhatta for 148 &euro;</p></td>
<td><p>h2ik</p></td>
</tr>
<tr>
<td><p><b><a href="{{ site_url('get-involved/bounties/ipv6') }}">{{ _('Make I2P IPv6 native') }}</a></b></p></td>
<td><p>Claimed by I2P dev team for &euro;100 EUR and 50BTC</p></td>
<td><p>Amiga4000</p></td>
</tr>
<tr>
<td><p><b><a href="{{ site_url('get-involved/bounties/silc') }}">{{ _('Setting up a SILC server') }}</a></b></p></td>
<td><p>withdrawn and bounty divided between ReturningNovice and the general fund</p></td>
<td><p>An Anonymous Secret Society, society@mail.i2p</p></td>
</tr>
<tr>
<td><p><b><a href="{{ site_url('get-involved/bounties/arabic-trans') }}">{{ _('Arabic translation') }}</a></b></p></td>
<td><p>both parts were taken by hamada for 100 BTC</p></td>
<td><p>hamada</p></td>
</tr>
<tr>
<td><p><b><a href="{{ site_url('get-involved/bounties/datastore') }}">{{ _('Datastore over I2P') }}</a></b></p></td>
<td><p><a href="http://{{ i2pconv('killyourtv.i2p') }}/tahoe-lafs/install/">CLAIMED</a> for 700 &euro;</p></td>
<td><p>duck, smeghead</p></td>
</tr>
<tr>
<td> <p><b><a href="{{ site_url('get-involved/bounties/russian-trans') }}">{{ _('Russian translation') }}</a></b></p></td>
<td><p>claimed for $230 USD sponsored by russian sponsor</p></td>
<td><p>4get</p></td>
</tr>
<tr>
<td><p><b>{{ _('Swarming file transfer') }}</b></p></td>
<td><p><a href="http://{{ i2pconv('i2p-bt.postman.i2p') }}">CLAIMED</a> for &euro;250 EUR</p></td>
<td><p>duck, ragnarok, dinoman, connelly, drwoo</p></td>
</tr>
<tr>
<td><p><b>{{ _('Streaming library window size') }}</b></p></td>
<td><p><a href="http://web.archive.org/web/20070404110818/http://dev.i2p.net/pipermail/i2p/2004-November/000491.html">Claimed (archived link)</a></p></td>
<td><p>jrandom</p></td>
</tr>
<tr>
<td><p><b>{{ _('IRC connect time monitor') }}</b></p></td>
<td>CLAIMED for $10 USD</td>
<td><p>hypercubus</p></td>
</tr>
<tr>
<td><p><b>{{ _('Unit tests (part 1)') }}</b></p></td>
<td>CLAIMED for $300 USD</td>
<td><p>Comwiz</p></td>
</tr>
<tr>
<td><p><b><a href="http://gcc.gnu.org/java/">GCJ</a> support</b></p></td>
<td><p><a href="https://github.com/i2p/i2p.i2p/tree/master/Makefile.gcj">Claimed</a></p></td>
<td><p>jrandom</p></td>
</tr>
</table>
<p><i><sup>*</sup> {% trans -%}
Dev lists anyone who may already be working on the bounty - collaboration is
preferred, so if you're interested in working on it, please contact one of the
people listed!
{%- endtrans %}</i></p>
{% endblock %}

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

@@ -1,29 +0,0 @@
{% extends "global/bounty.html" %}
{% block title %}{{ _('Bounty I2P IPv6 native') }}{% endblock %}
{% block donatename %}{{ _('native IPv6 I2P') }}{% endblock %}
{% block bountydetails %}
<p>{% trans -%}
For a future of I2P and attract more people
into I2P I withdrawal the vuze bounty and offer a IPv6 bounty.
To claim this bounty, the I2P router needs to run full on native
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 %}
<li>{% trans -%}
For bounties to be declared done and paid, we need the plugin AND the source.
Source and code need to be licensed under a free license (free to change and
free to distribute).
{%- endtrans %}</li>
{{ super() }}
{% endblock %}

108
i2p2www/pages/site/get-involved/bounties/netdb.html
View File

@@ -1,108 +0,0 @@
{% extends "global/bounty.html" %}
{% block title %}{{ _('NetDB Backend') }}{% endblock %}
{% block donatename %}{{ _('netDB backend') }}{% endblock %}
{% block bountydetails %}
<!-- file version 2013.05.28.01 -->
<p>{% trans -%}
The current NetDB implementation (namely the FloodFill system)
needs to be extended with another backend to improve reliability,
reduce attack surface and solve the scalability issue for the
coming years.
{%- endtrans %}</p>
<p>{% trans -%}
A solution likely based on a DHT will be investigated and
finally implemented.
{%- endtrans %}</p>
<h2>Requirements</h2>
<dl>
<dt><b>Lookup speed</b></dt>
<dd>Lookup time is crucial since request will be done in real time
and destinations can't be communicated with until a lookup has
completed and should therefore be minimized.
</dd>
<dt><b>Attack resilience</b></dt>
<dd>The solution should ideally be (or be extensible to be)
resilient against
<a href="{{ site_url('docs/how/threat-model') }}#sybil">sybil and eclipse</a> attacks.
</dd>
<dt><b>Scalability</b></dt>
<dd>The solution need to scale from the current number of nodes
to at least one million nodes without major modifications and
still maintain an unlimited search horizon.
</dd>
</dl>
<h2>Bounty</h2>
<table border="1">
<tr><td><p><b>Item</b></p></td><td><p><b>Description</b></p></td><td><p><b>Result</b></p></td><td><p><b>Value</b></p></td></tr>
<tr>
<td><h4>Investigate alternatives</h4></td>
<td>
<dl>
<dt><b>Find candidates</b></dt>
<dd>Find decentralized distributed systems that is fulfill our reuiqrements.</dd>
<dt><b>Select alternative</b></dt>
<dd>Select the best viable alternative.</dd>
</dl>
</td>
<td><a href="https://trac.i2p2.de/wiki/NetDB/NextBackend">Trac</a></td>
<td><p>162.5&euro;</p></td>
</tr>
</tr>
<tr>
<td><h4>Investigate implementation</h4></td>
<td>
<dl>
<dt><b>Investigate refactoring</b></dt>
<dd>Investigate I2P NetDB refactoring strategy.</dd>
<dt><b>Investigate and fix MultiRouter</b></dt>
<dd>Investigate the usability of MultiRouter, and fix issues found. MultiRouter will simplify further development.</dd>
<dt><b>Select base implementation</b></dt>
<dd>i2p.zzz.kademlia / i2psnarkdht is the most likely base implementation.</dd>
</dl>
</td>
<td><p><a href="https://trac.i2p2.de/changeset/0f0a99298bfbd4652d3dad2885ee1f0e1472c156">Trac</a></p></td>
<td><p>162.5&euro;</p></td>
</tr>
<tr>
<td><h4>Begin implementation of the most basic DHT</h4></td>
<td>
<dl>
<dt><b>Investigate I2CP</b></dt>
<dd>Investigate and design/select an I2NP message.</dd>
<dt><b>Implement iterative DHT lookups</b></dt>
<dd>Implement support for iterative DHT lookups</dd>
</dl>
</td>
<td><p>None yet</p></td>
<td><p>325&euro;</p></td>
</tr>
<tr>
<td><h4>More to come</h4></td>
<td>...</td>
<td><p></p></td>
<td><p></p></td>
</tr>
</table>
{% endblock %}
{% block bountynotesouter %}{% endblock %}

42
i2p2www/pages/site/get-involved/bounties/russian-trans.html
View File

@@ -1,42 +0,0 @@
{% extends "global/bounty.html" %}
{% block title %}{{ _('Bounty russian translation of webpage and router console') }}{% endblock %}
{% block donatename %}{{ _('Russian translation') }}{% endblock %}
{% block bountydetails %}
<p>{% trans -%}
To improve I2P usage and attract more people
into I2P a anonymous donator set out the bounty for translation
of the I2P web page and I2P router console into russian language.
{%- endtrans %}</p>
<p>
{{ _('This bounty is set into 2 subparts:') }}
<br>
{{ _('Part 1 is translation of the webpage.') }}<br>
</p>
<p>
{{ _('For collecting the bounty of $115 USD you need to translate the following pages:') }}<br>
http://www.i2p2.de/index.html<br>
http://www.i2p2.de/download.html<br>
http://www.i2p2.de/intro.html<br>
http://www.i2p2.de/faq.html<br>
http://www.i2p2.de/bounties.html<br>
http://www.i2p2.de/bounty_datastore<br>
http://www.i2p2.de/bounty_i2phex<br>
http://www.i2p2.de/bounty_vuzeplugin<br>
http://www.i2p2.de/getinvolved.html<br>
http://www.i2p2.de/donate.html<br>
</p>
<p>{% trans -%}
Part 2 is the translation of the router console. The whole router console needs
to be translated to collect the bounty of $115 USD.
{%- endtrans %}</p>
{% endblock %}
{% block bountyjudge %}
<p>{% trans -%}
Judge is the russian donor.
{%- endtrans %}</p>
{% endblock %}
{% block bountynotesouter %}{% endblock %}

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

@@ -1,26 +0,0 @@
{% extends "global/bounty.html" %}
{% block title %}{{ _('Bounty migrate I2P IRC to SILC') }}{% endblock %}
{% block donatename %}{{ _('I2P silc server') }}{% endblock %}
{% block bountydetails %}
<!-- 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.
This will allow people to send files over their messaging servers and have intrinsic security built into the protocol.
{%- 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, too.
{%- endtrans %}</p>
<p>{% trans -%}
Bounty was withdrawn and money donated to returningnovice and general fund.
{%- endtrans %}</p>
{% endblock %}
{% block bountyjudge %}
<p>{% trans -%}
Judge is An Anonymous Secret Society, society@mail.i2p.
{%- endtrans %}</p>
{% endblock %}

45
i2p2www/pages/site/get-involved/bounties/syndie-2012.html
View File

@@ -1,45 +0,0 @@
{% extends "global/bounty.html" %}
{% block title %}{{ _('Syndie development') }}{% endblock %}
{% block donatename %}{{ _('Syndie development') }}{% endblock %}
{% block bountydetails %}
<!-- file version 201.06.19.01 -->
<p>{% trans -%}
Beside of I2P we want to encourage users
to care more about anonymity and security. As I2P is a low
latency network with its natural limits, the software SYNDIE
can overcome some of these limits and provide better anonymity
for people who really need it.
{%- endtrans %}</p>
<p>{% trans -%}
For our bad sake the syndie project was out of development for
quite a long time yet (5 years) and has been updated just with
small fixes to keep it running. To get a fresh and new built
with needed bugfixes we set out this bounty. Also syndie needs
some enhancements and a better GUI for users to work with it.
Current bounty sum is 3 Bitcoin.
{%- endtrans %}</p>
<p>{% trans -%}
The latest Syndie coding rally did improve the situation of the
Syndie package dramatically. A new Syndie package with bugfixes
was created and made available on different webpages.
As a result of this work, the bounty sum was reduced and
the withdrawn money moved to the IPv6 bounty.
{%- endtrans %}</p>
<p>
Still some jobs are left to be done:<br>
1. Fix most, if not all GUI bugs (this relates to the first point somewhat) <br>
2. Be the maintainer for Syndie over a period of time (an amount per month or per quarter) and do the usual
tasks like accepting and fixing minor bugs, promote Syndie in the wider world than just I2P, maintaining
good documentation <br>
3. Add some sort of 'File Archive' as a transport (for sneakernets) <br>
4. Add more transports from the introduction image to Syndie: Usenet, Gnutella, E-Mail, iMule, Tahoe-LAFS <br>
5. Get syndie into repos for major distros (at least, Debian, Fedora, Arch, Gentoo, FreeBSD ports, PkgSrc) <br>
6. Make the freenet archive work <br>
</p>
<p>
</p>
{% endblock %}
{% block bountynotesouter %}{% endblock %}

132
i2p2www/pages/site/get-involved/bounties/unit-tests.html
View File

@@ -1,132 +0,0 @@
{% extends "global/bounty.html" %}
{% block title %}{{ _('Bounty unittests') }}{% endblock %}
{% block donatename %}{{ _('unit test') }}{% endblock %}
{% block bountydetails %}
<!-- file version 2013.01.15.01 -->
<p>{% trans -%}
To improve I2P's maintainability, we want to have a solid set of
automated unit tests for the critical code. While we do have some
unit tests at the moment, they are ad-hoc and partly unfinished.
This bounty is for someone to check the existing tests and move over
old ones to jUnit, automate their execution, extend them to provide
better code coverage, and publish the report online. Its a massive
effort, but can be broken down into phases, listed below (phase 2
must occur first, but further phases may happen in any order).
As this needs some reading of code, it is the best start point for
new devs to get a good overview of I2P code and coding. A good job
for college students, interns or anyone who is just interested.
{%- endtrans %}</p>
<p>{% trans -%}
Take care! Jobs and bounties shuffled a bit!
Phase 6,7 and 8 are still open!
{%- endtrans %}</p>
<h2>{% trans phase=1 %}Phase {{ phase }}:{% endtrans %}
<a name="jenkins">{{ _('CI jenkins and IRC bot') }}</a></h2>
<b>{% trans euro=500 %}Bounty: {{ euro }} &euro;
{%- endtrans %}</b> <i>{{ _('server runs and this section is blocked') }}</i><br />
<p>{% trans -%}
To collect this bounty, a continuous integration server (Jenkins,
old name was Hudson) must be set up and a connected IRC bot needs
to set up in the channel #i2p-dev on IRC2p network to print out
results of build tests.<br>
The server needs to be run long term.
{%- endtrans %}</p>
<br />
<h2>{% trans phase=2 %}Phase {{ phase }}:{% endtrans %}
<a name="sdk">{{ _('Check existing SDK tests') }}</a></h2>
<b>{% trans euro=150 %}Bounty: {{ euro }} &euro;
{%- endtrans %}</b> {{ _('paid to str4d') }}<br />
<p>{% trans clover='https://www.atlassian.com/software/clover/overview' -%}
To collect this bounty, the existing SDK tests must be checked
and made to work again. The need to be integrated into the ant
build scripts ("ant test"), and tied in with a code coverage tool (e.g.
<a href="{{ clover }}">Clover</a>). The ant script
must be capable of generating test status results as a web page,
which will be published online.
{%- endtrans %}</p>
<br />
<h2>{% trans phase=3 %}Phase {{ phase }}:{% endtrans %}
<a name="sdk_coverage">{{ _('SDK test coverage') }}</a></h2>
<b>{% trans euro=200 %}Bounty: {{ euro }} &euro;
{%- endtrans %}</b> {{ _('paid to unittests dev team') }}<br />
<p>{% trans -%}
To collect this bounty, the automated unit tests of the SDK
(i2p/core/java/src) must work again.
{%- endtrans %}</p>
<br />
<h2>{% trans phase=4 %}Phase {{ phase }}:{% endtrans %}
<a name="router">{{ _('Router test migration') }}</a></h2>
<b>{% trans euro=150 %}Bounty: {{ euro }} &euro;
{%- endtrans %}</b> {{ _('paid to str4d') }}<br />
<p>{% trans -%}
As with phase 2, the existing unit tests for the router must be
moved over to the automated system.
{%- endtrans %}</p>
<br />
<h2>{% trans phase=5 %}Phase {{ phase }}:{% endtrans %}
<a name="router_coverage">{{ _('Router test coverage') }}</a></h2>
<b>{% trans euro=200 %}Bounty: {{ euro }} &euro;
{%- endtrans %}</b> {{ _('paid to unittests dev team') }}<br />
<p>{% trans -%}
To collect this bounty, the automated unit tests of the router
(i2p/router/java/src) must work again.
{%- endtrans %}</p>
<br />
<h2>{% trans phase=6 %}Phase {{ phase }}:{% endtrans %}
<a name="streaming">{{ _('Streaming lib tests') }}</a></h2>
<b>{% trans euro=300 %}Bounty: {{ euro }} &euro;
{%- endtrans %}</b><br />
<p>{% trans -%}
To collect this bounty, a new set of unit tests must meet a
measured code coverage of 90&#37; of the streaming lib
(i2p/apps/ministreaming/ and i2p/apps/streaming/).
{%- endtrans %}</p>
<br />
<h2>{% trans phase=7 %}Phase {{ phase }}:{% endtrans %}
<a name="coverage">{{ _('Unit tests coverage') }}</a></h2>
<b>{% trans euro=500 %}Bounty: {{ euro }} &euro;
{%- endtrans %}</b><br />
<p>{% trans -%}
To collect this bounty, all above unit tests must meet the 100&#37;
coverage marker (except for log statements).
{%- endtrans %}</p>
<br />
<h2>{% trans phase=8 %}Phase {{ phase }}:{% endtrans %}
<a name="multirouter">{{ _('MultiRouter simulation') }}</a></h2>
<b>{% trans euro=1000 %}Bounty: {{ euro }} &euro;
{%- endtrans %}</b> {{ _('will be split in more sub-tasks') }}<br />
<p>{% trans -%}
To collect this bounty, the existing in-memory multi-router
simulation must be checked, made work again and extend to simulate
lots of routers in memory on a single machine. This bounty will
be split in more fine grained subworks.
{%- endtrans %}</p>
{% endblock %}
{% block bountyjudge %}
<p>{% trans -%}
Judge on all these works is the donor and donor decides if a phase is
called succesfull done and money can be paid.
{%- endtrans %}</p>
{% endblock %}
{% block bountynotesouter %}{% endblock %}

26
i2p2www/pages/site/get-involved/bounties/vuze-plugin.html
View File

@@ -1,26 +0,0 @@
{% extends "global/bounty.html" %}
{% block title %}{{ _('Bounty I2P vuze plugin') }}{% endblock %}
{% block donatename %}{{ _('vuze plugin') }}{% endblock %}
{% block bountydetails %}
<p>{% trans -%}
To improve I2P usage and attract more people
into I2P torrent P2P I setout the bounty for a working I2P vuze
plugin.
The plugin needs to be official and submitted to vuze for publication
on their webpage/repository for plugins.
It should be easy to install and configured, work smooth and flawless.
Configuration should be friendly to starters and made easy to be anonymous.
It should work with *.b32.i2p destinations as with signed (516++ bits)
destinations.
{%- endtrans %}</p>
{% endblock %}
{% block bountynotes %}
<li>{% trans -%}
For bounties to be declared done and paid, we need the plugin AND the source.
Source and code need to be licensed under a free license (free to change and
free to distribute).
{%- endtrans %}</li>
{{ super() }}
{% endblock %}

92
i2p2www/pages/site/get-involved/index.html
View File

@@ -1,10 +1,14 @@
{% extends "global/layout.html" %} {% extends "global/layout.html" %}
{% block title %}{% trans %}Get Involved!{% endtrans %}{% endblock %} {% block title %}{% trans %}Get Involved!{% endtrans %}{% endblock %}
{% block content %} {% block content %}
<h2>{% trans %}We need your help!{% endtrans %}</h2> <h2>{% trans %}There are many ways you can help I2P!{% endtrans %}</h2>
<p>{% trans -%} <p>{% trans -%}
To get involved, please feel free to join us on the #i2p-dev IRC channel (on To get involved, please feel free to join us on the #i2p-dev IRC channel (on
irc.freenode.net, irc.oftc.net, or within I2P on irc.echelon.i2p, irc.dg.i2p or irc.postman.i2p). irc.freenode.net, irc.oftc.net, or within I2P on irc.echelon.i2p, irc.dg.i2p or
irc.postman.i2p). We also have a forum, which is available at <a href="https://i2pforum.net">i2pforum.net</a>
on the clearnet and at <a href="http://i2pforum.i2p">i2pforum.i2p</a> inside the network. If you don't want to
create an account on our forum, some of our developers are active Redditors who
will talk to you on <a href="https://reddit.com/r/i2p">r/i2p</a>.
{%- endtrans %}</p> {%- endtrans %}</p>
<p>{% trans team=site_url('about/team') -%} <p>{% trans team=site_url('about/team') -%}
If you're interested in joining our <a href="{{ team }}">team</a>, please get in If you're interested in joining our <a href="{{ team }}">team</a>, please get in
@@ -14,39 +18,74 @@ touch as we're always looking for eager contributors!
We need help in many areas, and you don't need to know Java to contribute! We need help in many areas, and you don't need to know Java to contribute!
Here's a list to help get you started! Here's a list to help get you started!
{%- endtrans %}</p> {%- endtrans %}</p>
<h3>{% trans %}Grow the Community{% endtrans %}</h3>
<ul> <ul>
<li><b>{% trans %}Spread the Word!{% endtrans %}</b> &mdash; <li><b>{% trans %}Spread the Word!{% endtrans %}</b> &mdash;
{% trans -%} {% trans -%}
Tell people about I2P on forums, blogs, and comments to articles. Tell people about I2P on forums, blogs, and comments to articles. Fix up the
Fix up the Wikipedia article about I2P in your language. Wikipedia article about I2P in your language. Tell your friends, and more
Tell your friends. importantly, use I2P to communicate with your friends! We have many tools that
can help you keep your private conversations private.
{%- endtrans %}
</li><li><b>{{ _('Translation') }}</b> &mdash;
{% trans newtrans=site_url('get-involved/guides/new-translators') -%}
Help translate the website and the software into your language. Translators are
a very important part of this decentralized project and your work is always
appreciated.
See the <a href="{{ newtrans }}">new translator's guide</a> for details.
{%- endtrans %} {%- endtrans %}
</li><li><b>{{ _('Testing') }}</b> &mdash; </li><li><b>{{ _('Testing') }}</b> &mdash;
{% trans monotone=site_url('get-involved/guides/monotone'), {% trans monotone=site_url('get-involved/guides/monotone'),
trac=i2pconv('trac.i2p2.i2p') -%} trac=i2pconv('trac.i2p2.i2p') -%}
Run the latest builds from <a href="{{ monotone }}">monotone</a> Run the latest builds from <a href="{{ monotone }}">monotone</a> or a recent
build from the <a href="https://github.com/i2p/i2p.i2p">unofficial github mirror</a>
and report results on #i2p or as bugs on <a href="http://{{ trac }}/report/1">Trac</a>. and report results on #i2p or as bugs on <a href="http://{{ trac }}/report/1">Trac</a>.
{%- endtrans %} {%- endtrans %}
</li><li><b>{{ _('Documentation') }}</b> &mdash; </li><li><b>{{ _('Documentation') }}</b> &mdash;
{% trans -%} {% trans -%}
Help fix the parts of the website that are outdated or incomplete. Suggest changes to the website, or help fix the parts of the website that you
Translate pages into other languages. notice outdated or incomplete. We also always appreciate our wonderful
translators, join one of our Transifex teams and help translate pages into other
languages.
{%- endtrans %} {%- endtrans %}
</li><li><b>{{ _('Pictures') }}</b> &mdash; </li><li><b>{{ _('Multimedia') }}</b> &mdash;
{% trans -%} {% trans -%}
Make some more pictures, fix the old ones on the website Create promotional materials, infographics, and videos about I2P. Create guides
to setting up your favorite services on I2P, and take screenshots as you go. If
your guide is helpful, we'd love to mirror it on our blog.
{%- endtrans %} {%- endtrans %}
</li><li><b>{{ _('Content') }}</b> &mdash; </li><li><b>{{ _('Content') }}</b> &mdash;
{% trans -%} {% trans -%}
Make an eepsite! Add some content! Contribute to the community! One of I2P's greatest strengths as a peer-to-peer network is that anyone can
run their own website, it's actually a built-in feature. Create an eepSite,
talk about something you're passionate about, or just interested in. It's easy,
and it's getting easier every single day. Announce it on <a href="https://reddit.com/r/i2p">r/i2p</a>
and <a href="http://i2pforum.i2p">i2pforum.i2p</a>/<a href="https://i2pforum.net">i2pforum.net</a>
you will have visitors in no time.
{%- endtrans %} {%- endtrans %}
</li><li><b>{{ _('Services') }}</b> &mdash; </li></ul>
<h3>{% trans %}Host Services for Yourself and Others{% endtrans %}</h3>
<ul>
<li><b>{{ _('Services') }}</b> &mdash;
{% trans -%} {% trans -%}
Run a service on an eepsite. It could be a proxy, a forum, a tracker, Running many kinds of services on eepSites is very easy. You could self-host
a naming service, a search engine, an eepsite monitor... many of these almost anything, from an SSH server for yourself to an ActivityPub forum for
aren't that hard. everyone and anything in between. Almost anything you can think of can be made
to work with I2P, and your service is valuable to the network.
{%- endtrans %} {%- endtrans %}
</li><li><b>{{ _('Applications') }}</b> &mdash; </li><li><b>{{ _('Reseeding') }}</b> &mdash;
{% trans reseed=site_url('get-involved/guides/reseed') -%}
Getting new users onto the network is a very important task, and that task is
handled by our reseed servers. The more reseed servers we have, the more
de-centralized and redundant our infrastructure is. It's a big responsibility,
but it's pretty easy to set up a reseed server for new routers to bootstrap
from. Detailed instructions are on our <a href="{{ reseed }}">reseed server page</a>.
{%- endtrans %}
</li>
</ul>
<h3>{% trans %}Develop Software{% endtrans %}</h3>
<ul>
<li><b>{{ _('Applications') }}</b> &mdash;
{% trans apps=site_url('get-involved/develop/applications') -%} {% trans apps=site_url('get-involved/develop/applications') -%}
Write or port applications for I2P! There's some guidelines and Write or port applications for I2P! There's some guidelines and
a list of ideas on the <a href="{{ apps }}">applications page</a>. a list of ideas on the <a href="{{ apps }}">applications page</a>.
@@ -61,25 +100,14 @@ or the TODO list on <a href="http://{{ zzz }}">{{ zzz }}</a> for
some ideas on where to start. some ideas on where to start.
See the <a href="{{ newdevs }}">new developer's guide</a> for details. See the <a href="{{ newdevs }}">new developer's guide</a> for details.
{%- endtrans %} {%- endtrans %}
</li><li><b>{{ _('Translation') }}</b> &mdash;
{% trans newtrans=site_url('get-involved/guides/new-translators') -%}
Help translate the website and the software into your language.
See the <a href="{{ newtrans }}">new translator's guide</a> for details.
{%- endtrans %}
</li><li><b>{{ _('Analysis') }}</b> &mdash; </li><li><b>{{ _('Analysis') }}</b> &mdash;
{% trans threatmodel=site_url('docs/how/threat-model') -%} {% trans threatmodel=site_url('docs/how/threat-model') -%}
Study or test the code to look for vulnerabilities. Study or test the code to look for vulnerabilities.
Both anonymity vulnerabilities from the various Both anonymity vulnerabilities from the various
<a href="{{ threatmodel }}">threat models</a>, <a href="{{ threatmodel }}">threat models</a>, and DOS and other weaknesses due
and DOS and other weaknesses due to securities holes, to security holes, benefit from ongoing research.
need researching.
{%- endtrans %} {%- endtrans %}
</li><li><b>{{ _('Reseeding') }}</b> &mdash; </li><li><b>
{% trans reseed=site_url('get-involved/guides/reseed') -%} <a href="{{ site_url('get-involved/donate') }}">{{ _('Donate') }}</a>
Set up a reseed server for new routers to bootstrap from. </b></li></ul>
Detailed instructions are on our <a href="{{ reseed }}">reseed server page</a>.
{%- endtrans %}
</li><li><b><a href="{{ site_url('get-involved/donate') }}">{{ _('Donate') }}</a></b>
</li></ul>
{% endblock %} {% endblock %}