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 - outbound message monitoring not supported [Christian]
25 - test currently fails spectacularly [segv of transport service]
26 => need transport to work first!
27 - request connect not working [Christian, need transport first]
29 - needs testing [need transport first]
31 - needs testing [need transport first]
32 * FS (basic anonymous FS only)
33 - implement FS service (P2P operations)
34 + how to send queries (soliciting is not there in core; do we
35 also want to do pushing sometimes?)
36 + need to bound queueing of replies for other peers
37 - test multi-peer search/download
39 - run peer => have a 0.9.x hostlist
40 - improve basic documentation (configure, dependencies, what works, etc.)
41 - write minimal welcome/introduction to 0.9.x-development/webpage/status
42 => Deploy(able) development network
47 - load: need way to determine network load (up/down)
48 - trust: need *fast* way to check/update trust in peers
49 (async peerinfo would not be right)
50 - OS: existing waitpid call is not nice (not integratable with scheduler! fix this!)
51 => should 'scheduler' support SIGCHILD explicitly? Always?
53 - synchronous/asynchronous API (& implementation) is not nice;
54 => provide notification-based API
55 - does not seem to work with timeouts (especially if service is not running)
57 - need to get rid of synchronous API for service starts (cause all kinds of problems)
58 [=> eliminate for need to tell ARM about service starts most of the time!] [Safey]
60 - need function to test "equivalency" of HELLOs; use in topology!
61 * Module features to implement:
62 - advanced FS API parts
63 + namespaces: fundamental namespace API
64 + search: SBlocks, KSBlocks, probes, notify FS-service of known results
66 + location URIs (publish, search, download)
67 + persistence support (publish, unindex, search, download)
68 + indexing: index-failure-cleanup
69 + download: management/bounding of parallel downloads (for recursive dl.)
70 + datastore reservation (publishing)
71 + gnunet-publish (URI args)
72 + gnunet-download (directory)
73 + gnunet-search (options, incl. namespace search)
74 + gnunet-download (many options)
75 + gnunet-directory (man page, options)
76 + gnunet-pseudonym (all of it)
77 + gnunet-service-fs (remove failing on-demand blocks, many other nitpicks/features/optimizations)
78 + datastore: do active migration support here?
79 - implement adv. FS testcases
81 + insert: sblocks, loc uris
83 + search: sblocks, skblocks, loc uris
86 - implement FS performance tests (needs TESTING)
91 - non-anonymous FS service (needs DHT)
92 + basic DHT integration
93 + CS-DHT-functions (DHT-put of LOC)
94 + P2P-functions (DHT-get)
97 + need to settle basic design; do we want to keep guile?
99 + modify configuration to allow controlling connections for non-local starts
100 + testbed creation with topology (needs working F2F topology) [Nate]
101 + testbed with churn [Nate]
102 + implement library for distributed testing [Nate]
103 + implement testcases for distributed testing [Nate]
104 + test basic peer re-configure [Nate]
105 + test topology creation [Nate]
106 + test churn generation [Nate]
109 * Module features to implement:
111 + good to have for DV evaluation!
114 + implement DV service [Nate & CG]
115 + implement DV library [Nate]
116 + implement DV transport plugin [Nate & CG]
117 + implement testcases [Nate]
118 + implement performance tests [Nate]
121 + how to integrate scheduler with GTK event loop!
124 * Module features to implement:
126 + good to have for DV/DHT evaluation!
128 + implement DHT service (needs DV, DATACACHE)
129 + implement DHT library
130 + implement testcases
131 + implement performance tests
134 * Plugins to implement:
135 - UDP backend (RC-pre2)
136 + Fragmentation library
138 - HTTP backend (RC-pre2)
143 + see discussions @ FISL about integration with event loop!
144 * Determine RC bugs and fix those!
149 - update webpage documentation
151 - expand bibliography
152 - convert documentation pages to books
153 - update books (especially for developers)
154 - create good Drupal theme for GNUnet
155 - make a NICE download page and figure out how to
156 enable developers to publish TGZs nicely
157 - port "contact" page
158 - add content type for "todo" items?
160 * Plugins to implement:
161 - MySQL database backends
164 - Postgres database backends
168 * Determine RC bugs and fix those!
172 * Plugins to implement:
173 - SMTP transport backend
174 - HTTPS transport backend
175 + improved HTTPS support in MHD
177 * Remove KBlocks in gnunet-unindex (see discussion with Kenneth Almquist on gnunet-devs in 9/2009)
178 * Allow checking of presence of search results and/or content via command-line tools
179 (add options to gnunet-search / gnunet-download to limit search to local peer)
181 - should use BIO instead of mmap
183 - expire 'ancient' HELLOs (those without valid addresses AND that
184 we have not 'used' (for their public keys) in a while; need a way
185 to track actual 'use')
186 - make sue we also trigger notifications whenever HELLOs expire