OK, so, to get the ball rolling, here are a few that I think would be
interesting or useful to add to the "job jar":
* (Easy) Write man pages for freenet_insert, freenet_server,
freenet_request, etc.
* (Easy) Write Windows .hlp docs for finsert, frequest, etc.
* (Easy) Update the Logger interface so that it can take an
Exception (or Throwable) object and "log" it (do a getMessage() or
printStackTrace() based on logging verbosity).
* (Easy) Add javadoc documentation to any classes that lack them,
especially in the support and client directories.
* (Easy) Check for undocumented command-line or config-file params,
and document them.
* (Easy) Find and remove CVS expanded keywords ($Id:$), which make
branch merging a pain in the ass and thus are the bane of my
existence. B-)
* (Medium) Figure out a way to add version stamping (version # and
build # in Core & Client) to the ant build.xml file, in a way that
doesn't interfere with e.g. Makefile builds.
* (Medium) Figure out a way to generate documentation automatically
for the Web site from DocBook sources.
* (Medium) Figure out a way to add doc-building (as above) into the
build process -- with different doc types built for different
platforms.
* (Medium) Figure out how to add GCJ building to the ant build.xml
file.
* (Medium) Scan the code for writes to System.out and System.err and
change them to Logger calls (if appropriate).
* (Medium) Change printStackTrace() calls to Logger calls, as above.
* (Medium) Change the Logger implementation so that different priority
messages can go to different log files (Error -> error.log, Minor ->
minor.log).
* (Medium) Expand the Setup program so that it's a general
configuration engine.
* (Medium) Add hooks for a built-in monitor system (stats on data, how
active the node is, bandwidth usage, etc.)
* (Medium) Make it possible to optionally submit these stats
anonymously using e.g. IndexClient.
* (Medium) Find, report, and remove "dead code" -- classes and/or
directories in CVS that are not called and not used.
* (Hard) Make the configuration engine useful for GUI, command-line,
or even Web-based administration.
* (Hard) Add a GUI, cmd-line, and/or Web-based viewer for the
monitor data mentioned above.
* (Hard) Resurrect the GUI interface so that it's JDK1.1 compatible,
and so that it works with 0.3 and 0.4 Client interface.
* (Hard) Add experimental "search" capabilities to this GUI, using
in-Freenet key indices, along the lines of the Freegle search tool.
Not all of these are necessarily good ideas (I know there's some
resistance to the monitoring interface, for example), but it's a
start.
~Mr. Bad
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Mr. Bad <[EMAIL PROTECTED]> | Pigdog Journal | http://pigdog.org/
freenet:MSK@SSK@u1AntQcZ81Y4c2tJKd1M87cZvPoQAge/pigdog+journal//
"Statements like this give the impression that this article was
written by a madman in a drug induced rage" -- Ben Franklin
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
_______________________________________________
Devl mailing list
[EMAIL PROTECTED]
http://lists.freenetproject.org/mailman/listinfo/devl
