Changes between Version 32 and Version 33 of gsoc


Ignore:
Timestamp:
Mar 9, 2009 10:13:24 PM (10 years ago)
Author:
Mathiasdm
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • gsoc

    v32 v33  
    1313 1. Why is your organization applying to participate in GSoC 2009? What do you hope to gain by participating?[[BR]]
    1414 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).
    15  1. What is the main public mailing list for your group?[[BR]]
    16  http://forum.i2p2.de/
    17  1. Where is the main IRC channel for your group?[[BR]]
    18  freenode|irc2p|ein: #i2p
    1915 1. Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.[[BR]]
    2016 No.
     
    3228 No.
    3329 1. Who will be your backup organization administrator? Please include Google Account information.[[BR]]
    34  echelon [??? - link_id of that app]
     30 echelon
    3531 1. Who will your mentors be? Please include Google Account information.[[BR]]
    3632  - welterde
     
    8076
    8177
    82 == I2P seeding for applications (so central reseed locations are no longer required) ==
    83 === Required skills ===
    84  * Java
    85 
    86 
    87 == Improving the Message Priority System and looking into QoS ==
    88 === Required skills ===
    89  * Java
    90 
    91 
    9278== IPv6 support for I2P ==
    9379Currently I2P only supports IPv4 TCP and UDP, so this would involve adding another field to the ntcp/ssu routerInfo entries and possibly adding some restricted route functionality to support communication of IPv4-only peers with IPv6-only peers.
     
    11399=== Notes ===
    114100 * There is already a Kademlia implementation in I2P that used to work, but it was abandoned for a floodfill implementation due to the Kademlia system not working efficiently enough.
     101
     102
     103== I2P seeding for applications (so central reseed locations are no longer required) ==
     104A lot of I2P applications use their own reseed implementation (pointing to specific 'reseed nodes' to get information about other nodes using the application). Reseed functionality in the I2P network itself could avoid reinventing the wheel in the future.
     105=== Required skills ===
     106 * Java
     107
     108
     109== Improving the Message Priority System and looking into QoS ==
     110=== Required skills ===
     111 * Java