Opened 8 years ago

Closed 5 years ago

#1082 closed task (fixed)

Update roadmap

Reported by: dg Owned by:
Priority: major Milestone: 0.9.24
Component: www/i2p Version:
Keywords: process, trac, revamp Cc: str4d, killyourtv
Parent Tickets: Sensitive: no


The project roadmap[0] is currently outdated. We should assess the state of affairs and update accordingly.

Is the roadmap still applicable? Have our goals changed?


Change History (4)

comment:2 Changed 8 years ago by dg

Cc: zzz added
Priority: minormajor
Type: defecttask

Several other pages should be updated:


Perhaps a meeting should be called?

Related: #1097

Last edited 8 years ago by dg (previous) (diff)

comment:3 Changed 8 years ago by zzz

Cc: str4d killyourtv added; zzz removed
Keywords: process trac revamp added
Milestone: 0.9.9

As with these process tickets #1119 #1120 this is important to formalize to meet requirements for funding, auditing, etc.

There's several distinct issues:

1) Where is the master roadmap? We have:

http://trac.i2p2.i2p/roadmap (tickets only)
http://trac.i2p2.i2p/wiki/Roadmaps/1.0 (good work by str4d)
http://www.i2p2.i2p/roadmap (ancient)
http://zzz.i2p/forums/10 (unused)
The one in my head - see below.

A Trac-based one may be better than a wiki- or website-based one. However can Trac effectively deal with date-based milestones or can it only handle releases? Any Trac plugins that may be helpful? Should a roadmap be based solely on tickets and releases or can it be more vague?

All existing roadmaps must be consolidated into The One True Roadmap.

2) Whose job is it to maintain the roadmap? Who is allowed to modify the roadmap?

3) What's the content of the current roadmap?

No idea. but here's what's in my head today. This is date-based, not release-based, since it's medium-to-long term. This is certainly different than any of the other documented roadmaps.

Continuing throughout
Website improvements
Android improvements
Syndie improvements
Usability improvements
Documentatiom improvements
More marketing
More translations
Restart C++ port / start other ports
Dev recruitment

Early 2014
All updates via torrent
All updates using su3
Reseed using su3
Class M floodfill
Susimail fixes / improvements (needs maintainer)
Prerequisites for new signing algo (addressbook)
Update to izpack 4.3.5?
Possibly rebuild jbigi with latest libgmp and new archs
I2CP message status codes router->i2cp->streaming->proxy

Mid 2014
Require Java 6
Jetty 8 + Tomcat 7
Prerequisites for new signing algo (shared tunnels)
Select new signing algo + curve
NetDB DHT improvements
Plugins move to su3 packaging and keys
Bittorrent UDP announce
NTCP handshake obfuscation
Fix transport DH

Late 2014
New leaseset signing algo
Get into Debian wheezy+1
DUST-like transport?
Class L floodfill?

Early 2015
Require Java 7

4) What about the far future?

Our docs have referenced things like 1.0, 2.0, 3.0, mixing/batching/padding, restricted routes, full auditing, full confidence, no bugs, etc. forever. A lot of that won't ever happen. But which ones won't happen? Which are still important? We've gotten criticism in the past for alleged handwaving and claims of stuff like this. Who can go through and make the decisions and scrub our docs?

comment:4 Changed 5 years ago by zzz

Milestone: 0.9.24
Resolution: fixed
Status: newclosed

ref: http://zzz.i2p/topics/2026

Currently all over the place, none official, none current:

Various posts on this site

I'm declaring the following location to be The One True Roadmap;


It will be a release roadmap. Project goals that are not part of the Java desktop I2P release will be put somewhere else.

We've tried several times over the years to have a blue-sky roadmap meeting. It never works. So I'm taking a shot at updating it based on what we're actually doing, plus what's in my head.

We will review and update the roadmap in one or more meetings March 4-6.

Pushed complete rework of roadmap.

Note: See TracTickets for help on using tickets.