Github migration: an update

A small update on some changes I've been making to the sourceforge
project page, and short-term plans to continue the Github migration
effort:

1. Sourceforge

- all ticket sections should now read-only for regular users
(developers can still edit/close reports)
- I have been closing any obvious "low-hanging-fruit" tickets in
preparation for migrating live tickets over to Github
- I have added links to Github code and Github issues on the project's
toolbar, and updated the project's details to point users to Github
for code and bug reporting.

2. Github

- users are creating tickets, and they are getting resolved
- PRs are being created, and they are being merged
- I plan to auto-migrate the remaining live tickets from sourceforge
and tag them appropriately
- I'd like to make use of the Github wiki and migrate from the
standalone xmltv.org wiki
- We need to remove any remaining CVS $Id tags from scripts and update
any $VERSION vars that use them. I suggest updating a grabber's
version string to include its name and the core xmltv library version.
- we should ideally add an issue template to make it as easy as
possible for end users to report their issues

3. Build testing

- TravisCI seems to be working well testing new commits automatically.
Occasionally there can be network issues when spinning up a testing
container which can cause a test(s) to fail. Whilst this can make it
appear a commit is bad, rerunning the failed job usually clears any
failures due to network outages.

4. Updated user acceptance testing (WIP)

I have been working on local dockerised user testing of all current
grabbers on Debian. The plan is to automatically upload test results
to github pages to make them visible. This is still a work in progress
but most of the hard work is done.


Cheers,
Nick

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot