propagate from branch 'i2p.www' (head e168251b9c2e6757fe883e570e2afcc1a23bfdc7)

to branch 'i2p.www.revamp' (head 7c8c7a1ed7d62a3dbda52c6af1df085e7d1c69da)
This commit is contained in:
str4d
2012-12-14 04:27:29 +00:00
6 changed files with 93 additions and 4 deletions

View File

@@ -5,8 +5,7 @@
{%- endblock %}
{% block content %}
<h1>Logs of past I2P meetings</h1>
<p>Regularly scheduled meetings are not being held at this time.
If you have something to discuss, please find the developers on IRC in #i2p-dev.
<p>If you have something to discuss, please find the developers on IRC in #i2p-dev.
<a href="{{ url_for('blog_index', lang=g.lang) }}">Status updates</a> from developers are also available.
</p><div class="underline"></div>
<ul class="infolist">

View File

@@ -7,5 +7,25 @@ This page lists often-used terminology when discussing I2P and cryptography.
<td>I2P</td>
<td>Invisible Internet Project: a project meant to provide an anonymity layer, so user can communicate anonymously using a range of applications.</td>
</tr>
<tr>
<td>Router</td>
<td>The core I2P software, which routes encrypted packets on the I2P network. All routers by default participate in the network, which both helps the network and provides cover traffic for any clients or servers connecting to the I2P network through the router.</td>
</tr>
<tr>
<td>RouterIdentity</td>
<td>A collection of information required to communicate directly with a router, such as its IP address and listening port, public signing and encryption keys etc.</td>
</tr>
<tr>
<td>Tunnel</td>
<td>An anonymous communication pathway between a client or server and the I2P network. Tunnels are unidirectional, so any one client or server must have at least two Tunnels - one for inbound traffic and one for outbound traffic.</td>
</tr>
<tr>
<td>Destination</td>
<td>The cryptographic identity of a tunnel. These are the identities of clients and servers within the I2P network, and are analogous to the IP:port of a computer on the normal internet.</td>
</tr>
<tr>
<td>LeaseSet</td>
<td>A collection of information required to communicate with a client or server at a particular Destination, such as the gateways of the inbound Tunnels for that Destination.</td>
</tr>
</table>
{% endblock %}

View File

@@ -1,7 +1,7 @@
{% extends "global/layout.html" %}
{% block title %}Bounties{% endblock %}
{% block content %}
<!-- file version 2012.04.16.01 -->
<!-- file version 2012.12.11.01 -->
<h1>Bounties for I2P</h1>
<p>While we always gratefully accept any contributions of code,
documentation, and the like, there are other ways to help I2P move
@@ -73,6 +73,13 @@ etc), and the like.</p>
<td><p>str4d,hottuna</p></td>
<td><p>3000 &euro;, of which 300 &euro; already paid for done jobs</p></td>
</tr>
<tr>
<td><p><b><a href="bounty_syndie2012">Syndie</a></b></p></td>
<td><p>Proposal in development</p></td>
<td><p>I2P team</p></td>
<td><p>[vacant]</p></td>
<td><p>100 BTC</p></td>
</tr>
</table>
<h2>Hold bounties, set on hold due to jrandom AWOL and missing funding</h2>

View File

@@ -0,0 +1,25 @@
{% extends "_layout.html" %}
{% block title %}Syndie development{% endblock %}
{% block content %}
<!-- file version 2012.12.11.01 -->
<p>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. </p>
<p>
For our bad sake the syndie project is out of development for
quite a long time yet (5 years). 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 100 Bitcoin.
</p>
<p>
Note:
<p><i>bounty amounts may be increased by further donations. Do
you think these are important? <a href="donate">Add in your donation</a>,
marking the amount for the syndie development bounty!</i></p>
{% endblock %}

View File

@@ -0,0 +1,31 @@
{% extends "_layout_de.html" %}
{% block title %}Syndie Entwicklung{% endblock %}
{% block content %}
<!-- file version 2012.12.11.01 -->
<p>
Neben I2P k&uuml;mmern wir uns auch um die weitere
Anonymit&aum;t und Sicherheit der Nutzer. Da I2P als Netzwerk
mit geringer Latenz naturbedingt einige Limits und Grenzen hat,
f&ouml;rdern wir die Entwicklung von SYNDIE, welches einige
dieser Limits &uuml;berwinden kann. Dank der hohen Latenz
von Syndie bietet es eine bessere Sicherheit und Anonymit$auml;t
f&uuml;r Leute, die dieses ben&ouml;tigen.</p>
<p>
Leider wurde die Software seit 5 Jahren nicht mehr aktiv
weiter entwickelt und gepflegt. Um diesen Mi&szlig;stand zu
beheben und eine aktuelle Version von Syndie anbieten zu
k&ouml;nnen setzt das I2P Team eine Belohnung von 100 Bitcoin
f&uuml;r die Weiterentwicklung von Syndie aus. Ebenso braucht
Syndie weitere Verbesserungen und eine bessere Benutzerschnittstelle.
</p>
<p>
Hinweis:
<i>Die H&ouml;he des Betrags kann durch weitere Spenden steigen.
Findest Du Syndie wichtig? <a href="donate_de">Spende einen Betrag</a>
f&uuml;r diese Syndie Belohnung!</i>
</p>
{% endblock %}

View File

@@ -1,7 +1,7 @@
{% extends "_layout_de.html" %}
{% block title %}Belohnungen{% endblock %}
{% block content %}
<!-- file version 2012.04.16.01 -->
<!-- file version 2012.12.11.01 -->
<h1>Belohnungen f&uuml;r I2P</h1>
<p>W&auml;hrend wir jederzeit dankbar jeglichen Beitrag an Quelltext,
Dokumentationen und &auml;hnlichen entgegennehmen, gibt es noch
@@ -76,6 +76,13 @@ etc.) benutzt wird.</p>
<td><p>str4d,hottuna</p></td>
<td><p>3000 &euro;, davon 300 &euro; schon ausgezahlt</p></td>
</tr>
<tr>
<td><p><b><a href="bounty_syndie2012_de">Syndie</a></b></p></td>
<td><p>Entwickler gesucht</p></td>
<td><p>I2P team</p></td>
<td><p>[vacant]</p></td>
<td><p>100 BTC</p></td>
</tr>
</table>
<h2>Auf Pause gesetzte Belohnungen, bedingt durch jrandoms Abwesenheit und fehlender Finanzen</h2>