1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
|
Implementable right now (but not necessarily important), with caveats
(unavailable components that will limit what can be implemented right
away), in order in which they will likely be done:
* TESTING-TESTBED [Nate]
* SETUP
* DV [Nate]
* TBENCH
* TRACEKIT
* FRAGMENTATION [Ji Lu]
* HTTP transport
* MySQL / Postgres plugins (datastore, datacache)
* UPNP [Milan]
* ARM [Safey]
Urgent items (before announcing ng.gnunet.org):
* TRANSPORT:
- nondeterministic transport testcase failures [Nate]
* CORE:
- test currently fails
- request connect not working [Christian, need transport first]
* TOPOLOGY:
- needs testing [need transport first]
* HOSTLIST:
- needs testing [need transport first]
* FS (basic anonymous FS only)
- test multi-peer search/download [needs core first]
* new webpage
- run peer => have a 0.9.x hostlist
- improve basic documentation (configure, dependencies, what works, etc.)
- write minimal welcome/introduction to 0.9.x-development/webpage/status
=> Deploy(able) development network
0.9.0pre0:
* UTIL:
- load: need way to determine network load (up/down)
- trust: need *fast* way to check/update trust in peers
(async peerinfo would not be right)
- OS: existing waitpid call is not nice (not integratable with scheduler! fix this!)
=> should 'scheduler' support SIGCHILD explicitly? Always?
* STATISTICS:
- synchronous/asynchronous API (& implementation) is not nice;
=> provide notification-based API
- does not seem to work with timeouts (especially if service is not running)
* ARM:
- need to get rid of synchronous API for service starts (cause all kinds of problems)
[=> eliminate for need to tell ARM about service starts most of the time!] [Safey]
* HELLO:
- need function to test "equivalency" of HELLOs; use in topology!
* Module features to implement:
- advanced FS API parts
+ namespaces: fundamental namespace API
+ search: SBlocks, KSBlocks, probes, notify FS-service of known results
+ collection
+ location URIs (publish, search, download)
+ persistence support (publish, unindex, search, download)
+ indexing: index-failure-cleanup
+ download: management/bounding of parallel downloads (for recursive dl.)
+ datastore reservation (publishing)
+ gnunet-publish (URI args)
+ gnunet-download (directory)
+ gnunet-search (options, incl. namespace search)
+ gnunet-download (many options)
+ gnunet-directory (man page, options)
+ gnunet-pseudonym (all of it)
+ gnunet-service-fs (remove failing on-demand blocks, stats, hot-path routing, load-based routing, nitpicks)
+ datastore: do active migration support here?
- implement adv. FS testcases
+ getopt API
+ insert: sblocks, loc uris
+ download: loc uris
+ search: sblocks, skblocks, loc uris
+ namespaces
+ collection
- implement FS performance tests (needs TESTING)
+ insert
+ download
+ search
+ unindex
- non-anonymous FS service (needs DHT)
+ basic DHT integration
+ CS-DHT-functions (DHT-put of LOC)
+ P2P-functions (DHT-get)
- setup (RC-pre0)
+ default generation
+ need to settle basic design; do we want to keep guile?
- testing (RC-pre0)
+ modify configuration to allow controlling connections for non-local starts
+ testbed creation with topology (needs working F2F topology) [Nate]
+ testbed with churn [Nate]
+ implement library for distributed testing [Nate]
+ implement testcases for distributed testing [Nate]
+ test basic peer re-configure [Nate]
+ test topology creation [Nate]
+ test churn generation [Nate]
0.9.0pre1:
* Module features to implement:
- tbench (RC-pre1)
+ good to have for DV evaluation!
- DV (RC-pre1)
+ write DV API
+ implement DV service [Nate & CG]
+ implement DV library [Nate]
+ implement DV transport plugin [Nate & CG]
+ implement testcases [Nate]
+ implement performance tests [Nate]
* GUIs to implement:
- gtk (RC-pre1)
+ how to integrate scheduler with GTK event loop!
0.9.0pre2:
* Module features to implement:
- tracekit (RC-pre2)
+ good to have for DV/DHT evaluation!
- DHT (RC-pre2)
+ implement DHT service (needs DV, DATACACHE)
+ implement DHT library
+ implement testcases
+ implement performance tests
* GUIs to implement:
- fuse (RC-pre2)
* Plugins to implement:
- UDP backend (RC-pre2)
+ Fragmentation library
+ actual plugin
- HTTP backend (RC-pre2)
0.9.0pre3:
* GUIs to implement:
- qt (RC-pre3)
+ see discussions @ FISL about integration with event loop!
* Determine RC bugs and fix those!
0.9.0:
* Documentation
- update man pages
- update webpage documentation
* new webpage:
- expand bibliography
- convert documentation pages to books
- update books (especially for developers)
- create good Drupal theme for GNUnet
- make a NICE download page and figure out how to
enable developers to publish TGZs nicely
- port "contact" page
- add content type for "todo" items?
- DNS activation
* Plugins to implement:
- MySQL database backends
+ datacache
+ datastore
- Postgres database backends
+ datacache
+ datastore
- vpn
* Determine RC bugs and fix those!
0.9.x:
* Plugins to implement:
- SMTP transport backend
- HTTPS transport backend
+ improved HTTPS support in MHD
+ actual plugin
* Remove KBlocks in gnunet-unindex (see discussion with Kenneth Almquist on gnunet-devs in 9/2009)
* Allow checking of presence of search results and/or content via command-line tools
(add options to gnunet-search / gnunet-download to limit search to local peer)
* STATISTICS:
- should use BIO instead of mmap
* PEERINFO:
- expire 'ancient' HELLOs (those without valid addresses AND that
we have not 'used' (for their public keys) in a while; need a way
to track actual 'use')
- make sue we also trigger notifications whenever HELLOs expire
|
