wiki:09roadmap

Version 6 (modified by anonymous, 9 years ago) (diff)

--

The real roadmap is here http://www.i2p2.i2p/roadmap.html but it is pretty vague about 0.9, and pretty modest, since we just released 0.8 in early July. We haven't put serious thought into 0.9 yet. We need some ambitious goals.

I guess the target for 0.9 would be mid-to-late 2011?

If you have any ideas for 0.9, add them here. If you are interested in getting paid to work on I2P (for example via Google Summer of Code 2011 or nlnet.nl funding.... not that we've ever gotten any funding, but it could happen) be sure to add your ideas here. Also look at the GSoC page here on the wiki.

For starters, below is the info copied from the website.

  • Include some seed data in the distribution so a central reseed location isn't required?
  • Reachability Mapping / handle peers partially reachable / enhanced restricted routes
  • Improve help pages and website
  • More translations
  • SSU disconnect message
  • Iterative floodfill lookups

Put additions below:

  • AJAX (jquery?) console
  • Simplified console
  • Chat plugin
  • Lots more plugins
  • Better handling of multiple outproxies (stay with one while it is working)
  • Outproxy plugin?
  • Android router working
  • Android UI
  • Other mobile platforms?
  • SSU analysis and improvements
  • Streaming improvements
  • Full proxy setup help pages in console for various proxy-switcher and browser combinations
  • Circumvention for various types of state firewalls
  • Much easier setup - bundled browser?
  • Official .deb packages and repo
  • 3 hop default for everything?
  • Better profile and netdb expiration / memory usage
  • Continue CPU and memory optimization
  • Update CPUID, JBigi
  • Update installer and i2prouter script, deal with non-x86 better
  • Official USB key package
  • Revisit split directory issues - go non-split for windows?
  • Encrypted netdb responses
  • Restrict file permissions
  • Use Java 1.6 features
  • Compact tracker responses
  • Tahoe-LAFS plugin
  • HTTPS reseeding
  • Backup release signers
  • More IPV6
  • TLS Transport?
  • Bigger I2NP Messages?
  • Susimail improvements
  • Streaming audio improvements and plugin
  • VOIP / voice chat plugin
  • Transport timeouts / fallback analysis and improvements
  • Congestion and WRED analysis and improvements
  • Lower default connection limits
  • Peer profiling formulas - analysis and improvements
  • Multicast?

Maybe the additions above need to be grouped into larger themes before putting them in the roadmap.

Pegasus goals for the next 18 months:

  • Establish official ties with I2P.
  • Introduce I2P the the academic community.
  • Get I2P peer reviewed.
  • Investigate funding options.