This bug covers moving the bug tracker from bugs.foocorp.net to our
own server.

I asked on the mailing list whether people wanted to switch bug
trackers and there were no strong opinions.

My current problems with redmine are:


1. can't tag bugs -- useful for marking bugs as bitesized (bug
   `#382 </issues/382>`_)
2. mediocre search
3. I'm concerned it won't scale to hundreds of contributors

It's possible I can solve issue 1 if we had our own redmine
instance using a plugin or something. We can push off issue 3. No
one else seems to have problems with issue 2, so we can push that
off, too.

Given that, this bug covers:


1. researching redmine to learn how to set it up and run it
2. figuring out what to do about tags
3. getting a dump of the data from foocorp
4. importing the data into the new bug tracker
5. changing all the urls in the docs and web-site to point to the
   new instance
6. creating some kind of automated something that watches the old
   bug tracker for activity and tells people to use the new one

I'm going to try to get this done for 0.0.4.

There are a few scripts that are in the repository now and probably
more to come. We should reorganize them so they get "installed"
when using builtout and setup.py install. Also, they should follow
a similar structure and have header information.

Maybe it's interesting to create a gmg command that has a series of
sub commands like PyBlosxom and git both have.

Regardless, the following things should be done:


1. administration/management scripts should be collected and put in
   a centralized place
2. they should be tweaked so they follow the same conventions
   (which means we should create a set of conventions for scripts)
3. we should fix the install process to "install" these scripts as
   well

It's probably worth doing this for 0.0.4, but it's something
someone can think about towards the end of the 0.0.4 cycle.

The manual is in docs/. To jive with GNU project standards, we need
to build a texinfo version of the docs for release tarballs (and we
should do html and pdf versions, too).

The thing this requires us to do is get a texinfo output thing for
the docs set up and making sure the infrastructure is there to do
it going forward.