first commit! HACKING

Cool, looks like savannah is behaving as expected:

http://git.savannah.gnu.org/cgit/serveez.git/commit/?h=next&id=68184295f

Some questions:

- The file HACKING incorporates and obsoletes TODO and RELEASE, so i will
  delete those files soon (and patching references).  Any objections?

- The "next" section in HACKING corresponds with the ‘next’ branch just
  created in the repo.  I composed it w/ an eye towards a small point
  release (0.1.8) in the next month or so, but am open to changes in its
  scope or contents.  Any ideas?  (See also "other stuff to do".)

- Under "coding standards" in HACKING, i describe several practices for
  Serveez maintenance that i intend to follow, some of which are new to
  Serveez.  Before i go ahead full-speed and start hacking in that
  manner, i'd like to either get a thumbs up from everyone, or
  participate in some discussion (w/ eventual amendment of HACKING, if
  need be), on those practices.  In particular, i know whitespace changes
  can be controversial; i don't want to step on any toes effecting them.
  What do people think?

In the meantime, here are the uncontroversial (i hope) changes i plan to
do in the immediate future:

- [maint] Remove CVS $Id$ et al; nfc.
- [maint] Update FSF street address in copyright notices; nfc.
- [maint] Replace all .cvsignore files with top-level .gitignore; nfc.
- Move to GPLv3+.

Let me know if i am missing anything.