1 Implementable right now (but not necessarily important), with caveats
2 (unavailable components that will limit what can be implemented right
3 away), in order in which they will likely be done:
4 * TESTING-TESTBED [Nate]
9 * FRAGMENTATION [Ji Lu]
11 * MySQL / Postgres plugins (datastore, datacache)
15 Urgent items (before announcing ng.gnunet.org):
16 * FS (basic anonymous FS only)
17 - test multi-peer search/download
18 + existing bandwidth-reservation code does not work with FS: don't get
19 DBLOCK size bandwidth for reply for a while => trouble for testcase
20 => need to more aggressively increase bandwidth per connection
21 => need to check that bandwidth is assigned properly to begin with
22 + Even with bandwidth-reservation code restricted, message is not
23 delivered to other core/peer/fs. Why?
24 + Same query is sent to the same peer in rather rapid succession (10x/minute?),
25 should tune code to reduce repetition...
27 - run peer => have a 0.9.x hostlist
28 => Deploy(able) development network
33 - load: need way to determine network load (up/down)
34 - trust: need *fast* way to check/update trust in peers
35 (async peerinfo would not be right)
37 - disconnect notifications from TCP not always as nice as we might want
38 them to be (but how can we do this cleanly given that UDP is connectionless?)
39 - TCP not used bi-directionally (especially important also for PONG!)
40 - hostlist testcase shows that (randomly) we jump to an address that
41 seems to be a plugin function *after* the plugin has been unloaded
42 (directly from scheduler); check that *all* plugin tasks are cancelled
43 after plugin is unloaded! (need better testcases for that...)
45 - synchronous/asynchronous API (& implementation) is not nice;
46 => provide notification-based API
47 - does not seem to work with timeouts (especially if service is not running)
49 - need to get rid of synchronous API for service starts (cause all kinds of problems)
50 [=> eliminate for need to tell ARM about service starts most of the time!] [Safey]
52 - need function to test "equivalency" of HELLOs; use in topology!
54 - needs more testing (especially F2F topology)
57 * Module features to implement:
58 - advanced FS API parts
59 + namespaces: fundamental namespace API
60 + search: SBlocks, KSBlocks, probes, notify FS-service of known results
62 + location URIs (publish, search, download)
63 + persistence support (publish, unindex, search, download)
64 + indexing: index-failure-cleanup
65 + download: management/bounding of parallel downloads (for recursive dl.)
66 + datastore reservation (publishing)
67 + gnunet-publish (URI args)
68 + gnunet-download (directory)
69 + gnunet-search (options, incl. namespace search)
70 + gnunet-download (many options)
71 + gnunet-directory (man page, options)
72 + gnunet-pseudonym (all of it)
73 + gnunet-service-fs (remove failing on-demand blocks, stats, hot-path routing, load-based routing, nitpicks)
74 + datastore: do active migration support here?
75 - implement adv. FS testcases
77 + insert: sblocks, loc uris
79 + search: sblocks, skblocks, loc uris
82 - implement FS performance tests (needs TESTING)
87 - non-anonymous FS service (needs DHT)
88 + basic DHT integration
89 + CS-DHT-functions (DHT-put of LOC)
90 + P2P-functions (DHT-get)
93 + need to settle basic design; do we want to keep guile?
95 + modify configuration to allow controlling connections for non-local starts
96 + testbed creation with topology (needs working F2F topology) [Nate]
97 + testbed with churn [Nate]
98 + implement library for distributed testing [Nate]
99 + implement testcases for distributed testing [Nate]
100 + test basic peer re-configure [Nate]
101 + test topology creation [Nate]
102 + test churn generation [Nate]
105 * Module features to implement:
107 + good to have for DV evaluation!
110 + implement DV service [Nate & CG]
111 + implement DV library [Nate]
112 + implement DV transport plugin [Nate & CG]
113 + implement testcases [Nate]
114 + implement performance tests [Nate]
117 + how to integrate scheduler with GTK event loop!
120 * Module features to implement:
122 + good to have for DV/DHT evaluation!
124 + implement DHT service (needs DV, DATACACHE)
125 + implement DHT library
126 + implement testcases
127 + implement performance tests
130 * Plugins to implement:
131 - UDP backend (RC-pre2)
132 + Fragmentation library
134 - HTTP backend (RC-pre2)
139 + see discussions @ FISL about integration with event loop!
140 * Determine RC bugs and fix those!
145 - update webpage documentation
147 - expand bibliography
148 - convert documentation pages to books
149 - update books (especially for developers)
150 - create good Drupal theme for GNUnet
151 - make a NICE download page and figure out how to
152 enable developers to publish TGZs nicely
153 - port "contact" page
154 - add content type for "todo" items?
156 * Plugins to implement:
157 - MySQL database backends
160 - Postgres database backends
164 * Determine RC bugs and fix those!
168 * Plugins to implement:
169 - SMTP transport backend
170 - HTTPS transport backend
171 + improved HTTPS support in MHD
173 * Remove KBlocks in gnunet-unindex (see discussion with Kenneth Almquist on gnunet-devs in 9/2009)
174 * Allow checking of presence of search results and/or content via command-line tools
175 (add options to gnunet-search / gnunet-download to limit search to local peer)
177 - should use BIO instead of mmap
179 - expire 'ancient' HELLOs (those without valid addresses AND that
180 we have not 'used' (for their public keys) in a while; need a way
181 to track actual 'use')
182 - make sue we also trigger notifications whenever HELLOs expire