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):
17 - server/service API change for ARM inetd'ing
18 (listen as well as support for start with multiple, already
19 bound & listening sockets!) [Christian]
21 - main service not implemented [Nate]
22 - testcases crash & burn (no surprise)
24 - request disconnect not implemented [Christian]
25 - various notification options not implemented [Christian]
26 - outbound message monitoring not supported [Christian]
27 - test currently fails spectacularly [segv of transport service]
28 => need transport to work first!
29 - request connect not working [Christian, need transport first]
31 - needs testing [need transport first]
33 - test fails (looks like it works, but that's because of a bad
34 connectivity notification; somehow core is unable to send
35 messages successfully via transport) [need transport first]
36 * FS (basic anonymous FS only)
37 - implement FS service (P2P operations)
38 + how to send queries (soliciting is not there in core; do we
39 also want to do pushing sometimes?)
40 + need to bound queueing of replies for other peers
41 - test multi-peer search/download
43 - run peer => have a 0.9.x hostlist
44 - improve basic documentation (configure, dependencies, what works, etc.)
45 - write minimal welcome/introduction to 0.9.x-development/webpage/status
46 => Deploy(able) development network
51 - load: need way to determine network load (up/down)
52 - trust: need *fast* way to check/update trust in peers
53 (async peerinfo would not be right)
54 - OS: existing waitpid call is not nice (not integratable with scheduler! fix this!)
55 => should 'scheduler' support SIGCHILD explicitly? Always?
57 - synchronous/asynchronous API (& implementation) is not nice;
58 => provide notification-based API
59 - does not seem to work with timeouts (especially if service is not running)
61 - need to get rid of synchronous API for service starts (cause all kinds of problems)
62 [=> eliminate for need to tell ARM about service starts most of the time!] [Safey]
64 - need function to test "equivalency" of HELLOs; use in topology!
65 * Module features to implement:
66 - advanced FS API parts
67 + namespaces: fundamental namespace API
68 + search: SBlocks, KSBlocks, probes, notify FS-service of known results
70 + location URIs (publish, search, download)
71 + persistence support (publish, unindex, search, download)
72 + indexing: index-failure-cleanup
73 + download: management/bounding of parallel downloads (for recursive dl.)
74 + datastore reservation (publishing)
75 + gnunet-publish (URI args)
76 + gnunet-download (directory)
77 + gnunet-search (options, incl. namespace search)
78 + gnunet-download (many options)
79 + gnunet-directory (man page, options)
80 + gnunet-pseudonym (all of it)
81 + gnunet-service-fs (remove failing on-demand blocks, many other nitpicks/features/optimizations)
82 + datastore: do active migration support here?
83 - implement adv. FS testcases
85 + insert: sblocks, loc uris
87 + search: sblocks, skblocks, loc uris
90 - implement FS performance tests (needs TESTING)
95 - non-anonymous FS service (needs DHT)
96 + basic DHT integration
97 + CS-DHT-functions (DHT-put of LOC)
98 + P2P-functions (DHT-get)
101 + need to settle basic design; do we want to keep guile?
103 + modify configuration to allow controlling connections for non-local starts
104 + testbed creation with topology (needs working F2F topology) [Nate]
105 + testbed with churn [Nate]
106 + implement library for distributed testing [Nate]
107 + implement testcases for distributed testing [Nate]
108 + test basic peer re-configure [Nate]
109 + test topology creation [Nate]
110 + test churn generation [Nate]
113 * Module features to implement:
115 + good to have for DV evaluation!
118 + implement DV service [Nate & CG]
119 + implement DV library [Nate]
120 + implement DV transport plugin [Nate & CG]
121 + implement testcases [Nate]
122 + implement performance tests [Nate]
125 + how to integrate scheduler with GTK event loop!
128 * Module features to implement:
130 + good to have for DV/DHT evaluation!
132 + implement DHT service (needs DV, DATACACHE)
133 + implement DHT library
134 + implement testcases
135 + implement performance tests
138 * Plugins to implement:
139 - UDP backend (RC-pre2)
140 + Fragmentation library
142 - HTTP backend (RC-pre2)
147 + see discussions @ FISL about integration with event loop!
148 * Determine RC bugs and fix those!
153 - update webpage documentation
155 - expand bibliography
156 - convert documentation pages to books
157 - update books (especially for developers)
158 - create good Drupal theme for GNUnet
159 - make a NICE download page and figure out how to
160 enable developers to publish TGZs nicely
161 - port "contact" page
162 - add content type for "todo" items?
164 * Plugins to implement:
165 - MySQL database backends
168 - Postgres database backends
172 * Determine RC bugs and fix those!
176 * Plugins to implement:
177 - SMTP transport backend
178 - HTTPS transport backend
179 + improved HTTPS support in MHD
181 * Remove KBlocks in gnunet-unindex (see discussion with Kenneth Almquist on gnunet-devs in 9/2009)
182 * Allow checking of presence of search results and/or content via command-line tools
183 (add options to gnunet-search / gnunet-download to limit search to local peer)
185 - should use BIO instead of mmap
187 - expire 'ancient' HELLOs (those without valid addresses AND that
188 we have not 'used' (for their public keys) in a while; need a way
189 to track actual 'use')
190 - make sue we also trigger notifications whenever HELLOs expire