Version 14 (modified by Mathiasdm, 11 years ago) (diff)

Organization application

  1. Link ID?
  2. Group name?
  3. Home Page URL?
  4. Public email?
  5. Describe your organization.
    The I2P development team is an international group (with both anonymous and known participants) looking to provide anonymity for internet users through an overlay network. To achieve this goal, I2P uses onion routing (an encryption layer is added for each router messages need to pass) for this goal, somewhat similar to Tor. Multiple applications work directly on the network (web browsing, e-mail, IRC, …), while others are available by integrating into the I2P API (eg. Bittorrent, iMule …).
    The project was formed in 2003. There were eight official releases in 2008, and one so far this year. It has a rapidly growing user base of about 700-1000 users at any time and over 3000 unique users per month. Members of the group attended 25C3 in Berlin in 2008, and will give talks about I2P at Chemnitzer Linux-Tage and Pet-Con this month. One of the lead developers recently gave an interview to .
    While somewhat similar to Tor, the project has distinctly different goals. It is focused on the development of a internal network services ("hidden services" in Tor terms) rather than anonymous proxying to the regular internet. This allows more resistance against censorship by any possible adversaries. These I2P services are generally faster and better-suited to anonymous communication than Tor hidden services.
    These capabilities are important in a fast-changing society, where some governments wish to censor the internet. The problem with censorship is that it can and is easily abused. I2P provides a way around this problem, for example to help human rights activists.
    I2P is a large and complex Java application with almost 200KLOC. The encryption routines are implemented in optimised C and Assembly to ensure the best possible speed. Sophisticated peer selection/routing algorithms balance speed, anonymity and protection against DoS attacks to allow for the best and safest possible experience. The project will be of interest to those exploring networking, cryptography, distributed databases, multiple transport protocols, anonymity, and debugging widely distributed, networked applications.
    Amongst the main features of I2P are:
    1. Anonymity for sender and receiver of messages through onion routing and cover traffic provided by the network
    2. Internal anonymous services (websites, e-mail, torrent trackers, irc servers…)
    3. An active project, with regular releases worked on by multiple developers. A growing project as well, with increasing numbers in both developers and users.
    4. Multiple programs using the I2P API to provide extra services (anonymous blogging software, torrent applications,
    5. By default, users route traffic for each other, which adds cover traffic to the network, improving the anonymity of the users and the capacity of the network.
    6. Development of applications on top of I2P in any programming language, due to a simple socket interface for programs.
    7. An easy and user-friendly install, so anyone can be anonymous without too much trouble.
  6. Why is your organization applying to participate in GSoC 2009? What do you hope to gain by participating?
    Multiple developers work on the I2P project, but we would like to get some extra people involved. As I2P is an anonymity and security project, it's important for us to get a lot of peer review ('many eyeballs'-principle). Extra developers would also allow an increased focus on less 'evolved' parts of the project.
    Another important reason for us to apply is the publicity and community size. By drawing additional attention to the I2P project, we believe it's possible to increase the size of the community. This would in turn improve the anonymity of the users.
  7. What is the main public mailing list for your group?
  8. Where is the main IRC channel for your group?
    freenode|irc2p: #i2p (Not many people are in the Freenode channel, most are on #i2p in irc2p (inside I2P).)
  9. What criteria did you use to select these individuals as mentors? Please be as specific as possible.
    • Experience with I2P code in general, and with the suggested project proposals in particular.
    • Knowledge of the I2P community.
    • People skills: getting along with others and resolving conflicts. This includes helping new users (which, according to us, indicates a willingness to help GSoC students as well)
  10. Has your group participated previously? If so, please summarize your involvement and any past successes and failures.
  11. If your group has not previously participated, have you applied in the past? If so, for what sort of participation?
    Not applicable.
  12. What license(s) does your project use?
    I2P is a project containing multiple programs. As such, these are licensed under different licenses. All of the licenses are open source and detailed information is available at
  13. What is the URL for your ideas page?
  14. What is the main development mailing list or forum for your organization?
    http://zzz.i2p/ (or for outside of I2P)
  15. Does your organization have an application template you would like to see students use? If so, please provide it now.
    Yes. See here(top of the page).
  16. What is your plan for dealing with disappearing students?
    First of all, we'll try to avoid having students disappear, by keeping regular contact and trying to help them solve any problems they encounter. In the event a student should disappear, we will make sure we have their contact information already, so we can easily contact them and persuade them to carry on with the project (possibly with extra guidance). We will also try to notice early on when a student is no longer motivated, by checking on the progress they're making.
  17. What is your plan for dealing with disappearing mentors?
    The mentors are all long-time I2P community members, and, as such, not very likely to leave the project. If they do, we will try to contact them. If this is not possible, another mentor will take over their work (or we can perhaps divide the work between two other mentors).
  18. What steps will you take to encourage students to interact with your project's community before, during and after the program?
    We advise all students to get to know us by communicating on IRC and the forum. Setting up I2P and an I2P website (possibly with help on IRC) will also hand students some initial I2P knowledge.
  19. What will you do to ensure that your accepted students stick with the project after GSoC concludes?
    I2P is a project that has a lot of different topics to work on. This should ensure that any student can either build on what they've accomplished over the summer, or can shift their attention to an entirely new project inside (or on top of) I2P. We will try to keep interaction with the students to a high level, which should also keep motivation and 'community feeling' up.
  20. Who will be your backup organization administrator?