wiki:gsoc

Version 46 (modified by zzz, 10 years ago) (diff)

Organization application

  1. Link ID?
    i2p
  2. Group name?
    Invisible Internet Project
  3. Home Page URL?
    http://www.i2p2.de/
  4. Public email?
    press@…
  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 http://chemnitzer.linux-tage.de/2009/vortraege/detail.html?idx=93 and Pet-Con http://www.pet-con.org/index.php/PET_Convention_2009.1 this month. One of the lead developers recently gave an interview to gulli.com http://www.gulli.com/news/i2p-an-anonymous-network-2009-03-09/ . 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. These I2P services are generally faster and better-suited to anonymous communication than Tor hidden services.

The project is a large and complex Java application with almost 200KLOC. The project will be of interest to those exploring networking, cryptography, distributed databases, multiple transport protocols, anonymity, and debugging widely distributed, networked applications.

  1. Why is your organization applying to participate in GSoC 2009? What do you hope to gain by participating?
    We wish to attract more developers to the project to increase our development speed. In addition, we wish to gain publicity for I2P to create a larger community (which also improves the anonymity of the users).
  2. Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.
    No.
  3. If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?
    Not applicable.
  4. 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 http://www.i2p2.de/licenses.html
  5. What is the URL for your ideas page?
    The official page can be found at http://trac.i2p2.i2p/wiki/gsoc inside the I2P network. It can also be reached without running I2P from the following links (warning: they may be slow): http://trac.i2p2.i2p.to/wiki/gsoc or http://trac.i2p2.i2p.tin0.de/wiki/gsoc
  6. What is the main public mailing list for your group?
    http://forum.i2p2.de/
  7. What is the main development mailing list or forum for your organization?
    http://zzz.i2p/ (or http://zzz.i2p.to/ for outside of I2P)
  8. Where is the main IRC channel for your group?
    freenode|irc2p|ein: #i2p Not many people are in the Freenode channel, most are on #i2p in irc2p (inside I2P).
  9. Does your organization have an application template you would like to see students use? If so, please provide it now.
    Yes. See below.
  10. Who will be your backup organization administrator? Please include Google Account information.
    echelon
  11. Who will your mentors be? Please include Google Account information.
    • welterde
    • echelon [ echelon@… ]
    • zzz
  12. 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)
  13. 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.
  14. 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).
  15. 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.
  16. 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.

Links