Hornet is a flexible, modular, bug tracking system, consisting of
three parts: a "backend" module interfacing with a database system; a
library that provides a wrapper around the backend modules and
provides a consistent interface; and a set of applications
("frontends") which provide the user interface.

This release is in a very unstable pre-alpha; the API and database
schemas are not even thoroughly planned out, nor has any code been
written.  This system will also be dependant on a couple of other
libraries, although the final release will ship those as well.  Some
libraries may have to be written from scratch, however, notably an
implementation of the com_err library, which will be used for error
reporting.

The current plan calls for two backend modules; one will interface
with PostgreSQL through libpq, and the other will be a network
interface that may use libxml or something similiar.  There are also
intended to be three frontends:  A CGI-based frontend will allow bug
reports to be viewed and manipulated via the web; a TCP server
provides the other end of the network interface (and will itself use a
backend to communicate with the actual database); and finally, a
client will allow direct manipulation of the bug database.

It is expected that the database will require the use of transactions
in order to ensure data integrity, which is the main reason PostgreSQL
has been chosen in favor of MySQL; fortunately, PostgreSQL is a free
database (under a BSD-style license), and passes the ACID test.  Of
course, nothing will prevent anyone from developing a backend module
that makes use of MySQL, mSQL, or even Oracle.  It may even be
possible to use something as simple as gdbm; but a RDBMS should
provide the most efficient searching capabilities, will be important
for large databases.

This code and all code bundled under this tree will be released under
the GPL unless otherwise stated.