Pyzor website and bug/feature tracker changes

[Tony M. <to...@sp...>]

SourceForge is in the process of discontinuing their documentation
manager and tracker system, in favour of 'hosted applications' that do
the same task.  As a result, we've had to make some changes to the way
that you report and monitor bugs, patches, and feature requests for
Pyzor.  (We've done this a little in advance of the SourceForge
shut-down, so that we're not rushed into it).

The changes are:

 * Bug reports, patches, and feature requests will be managed via a
new system.  You can report a new bug, or open a new feature request,
by going to http://p.sf.net/pyzor/newticket and you can look at the
existing tickets by going to http://p.sf.net/pyzor/report/ .  You
should find this system as easy to use as the old SourceForge one, if
not easier.

 * Documentation has been moved to a wiki system - the big advantage
here is that anyone (with a SourceForge account) is able to contribute
by editing and creating pages.  You can find the documentation at
http://p.sf.net/pyzor/wiki

 * The http://pyzor.org address will take you to the front page of the
wiki, where you can easily find links to tickets, downloads, and other
documentation.

All of the old content has been migrated to this system, including all
closed bug reports, patches, and feature requests (dates of ticket
changes and submitter information has not been preserved, but can be
corrected once SourceForge officially drops the old system, if
required).  We'll continue to add more information (particularly
documentation) as time allows.

The new system uses the Trac management software, which is fairly
widely used, especially among projects implemented in Python, so
hopefully many of you are already familiar with the system.

We'd like to emphasise that the website, documentation, and tickets
are still hosted by SourceForge (just a different part), and that the
project is still completely open and welcomes contributions from the
community.  In fact, we hope that these changes make it easier to take
part.

Please let us know if you have any difficulties with the new site, or
have any suggestions!

--
Tony Meyer, on behalf of the Pyzor team.