SignPages: Made the fingerprint label selectable to allow c&p
Moved all the code to a keysign directory
Renamed README to README.rst as we don't do Markdown, but ReStructured Text
Renamed the ".sh" file to a .py file

Also import from the "keysign" package as we have a proper library now
Added a Logo

This is a bit preliminary though and was done very quickly.
It uses elements from Seahorse GPLv2+ licensed.
It also uses element from the GnuPG logo, downloaded from
http://upload.wikimedia.org/wikipedia/commons/a/a3/GnuPG-Logo.svg
and, according to the corresponding page:
http://commons.wikimedia.org/wiki/File:GnuPG-Logo.svg
is in the public domain.
It also uses the GNOME logo obtained from
http://commons.wikimedia.org/wiki/File:GnuPG-Logo.svg
licensed under the LGPLv2+.
Made "keysign" a python module by creating __init__.py

Also, due to the __main__.py, you can call "python -m keysign" and it should
work.
keysign: Moved the imports to the main() function

Because setup.py will import the module to get the __version__.
And at that time, the dependencies might not yet be installed.
Added a .desktop file

One problem I encountered was that gnome-shell (rightfully) wants to
be able to exec() the program in the Exec line.
That, however, requires either the binary to be in the path or
an absolute path to the binary.
The former is hard to achieve as ~/.local/bin/ does not seem to be
in the PATH by default.
The latter is also a bit hard as I don't know how to make setuptools
rewrite the Exec line with the prefix it installed to.
Now, we simply call python with the module's name.
This is a bit of a hack but should work when the user installs the
application via pip, i.e. pip install --user. As a bonus, this
should work equally well for system wide installations.
Installing to virtualenvs is not supported in the sense that the .desktop
file won't show up in GNOME Shell automatically. One would have to
convince GNOME Shell first to look into the new directory for the .desktop
file and then convince python to find the module.  But I consider that
to be an esoteric case for now.
Added preliminary appdata

Note that currently neither the homepage nor the screenshot exists.
Added a setup.py for easier installation

This should enable you to do a pip install --user and have a
launcher in your desktop.
Updated copyright for each file
Merge branch 'fingerprint_selectable' into package
MainWindow: Set a title to "Keysign"
Merge remote-tracking branch 'origin/copyrights' into package
SignPages: Added a log call when processing signatures
SignPages: Made the signature extraction a bit more robust

By not extracting all values from the record.

From the documentation:

 5. Field:  KeyID
 6. Field:  Creation Date (in UTC).  For UID and UAT records, this is the
            self-signature date.  Note that the dae is usally printed
            in seconds since epoch, however, we are migrating to an ISO
            8601 format (e.g. "19660205T091500").  This is currently
            only relevant for X.509, A simple way to detect the format
            is be scannning for the 'T'.
 7. Field:  Key or user ID/user attribute expiration date or empty if none.
 8. Field:  Used for serial number in crt records (used to be the Local-ID).
            For UID and UAT records, this is a hash of the user ID contents
            used to represent that exact user ID.  For trust signatures,
            this is the trust depth seperated by the trust value by a
            space.
 9. Field:  Ownertrust (primary public keys only)
            This is a single letter, but be prepared that additional
            information may follow in some future versions.  For trust
            signatures with a regular expression, this is the regular
            expression value, quoted as in field 10.
setup.py: Added include_package_data = True in order to ship the data files

I am a bit confused as to whether we need a MANIFEST.in or not.
I think I just want the stuff in data/ to be put in the tarball when
running setup.py sdist.
Merging a more robust signature parser
Merging the distributable package branch

Now a release is immanent.
README: Commented on the installation and running process

Note that this is a bit in flux right now. But this should enable us
to release very soon now.