Update repo links and crufty docs

INSTALL

@@ -20,7 +20,7 @@ To build an RPM, you can run:
 virt-manager generally requires the latest upstream version of
 python-virtinst, which checked out with
 
-hg clone http://hg.fedorahosted.org/hg/python-virtinst
+git clone git://git.fedorahosted.org/git/python-virtinst.git
 
 If you want to replace your system installed virt-manager version,
 add --prefix=/usr to ./configure. Please see the INSTALL.autotools file

README

@@ -40,7 +40,7 @@ please report any success to the mailing lists
 
 The latter is available from
 
-http://hg.et.redhat.com/virt/applications/virtinst--devel
+http://git.fedorahosted.org/git/python-virtinst.git
 
 Contact
 -------
@@ -71,17 +71,19 @@ Patches should be submitted either as unified diffs:
    diff -ruN virt-manager-X.Y.Z virt-manager-X.Y.Z-myfeature \
       > myfeature.patch
 
-Alternatively use Mercurial and submit a changeset bundle against
-the main source repository:
+Alternatively use git and submit a diff against the main source repository:
 
-   hg clone  http://hg.et.redhat.com/virt/applications/virt-manager--devel
+   git clone git://git.fedorahosted.org/git/virt-manager.git
    cd virt-manager--devel
-   ... make some changes & commit them locally...
-   hg export -r my_feature_revision > my_feature.patch
+   ... make your changes ...
+   git commit -a -m "Some changelog message"
+   git show > my_feature.patch
 
 Then mail the 'myfeature.patch' file to the virt-tools-list@redhat.com list,
 with [PATCH] and a brief description in the subject.
 
+Using git format-patch and/or git send-email is also fine.
+
 Related software
 ----------------
 

TODO

@@ -1,4 +1,4 @@
     Virt Manager TODO list
     ----------------------
 
-Please see http://virt-manager.et.redhat.com/page/Roadmap
+Please see http://virt-manager.org/page/Roadmap

docs/RELEASE-PROCESS.txt

@@ -3,7 +3,7 @@
 
 Before release:
     verify virt-manager runs fine on RHEL5 (older gtk)
-    Make sure distcheck passes, make rpm works fine
+    Make sure distcheck passes, 'make rpm' works fine
     All virtinst/virt-manager tests and pylint checks
 
 Preparing the source tree:
@@ -12,14 +12,13 @@ Preparing the source tree:
  2. Change release number in configure.ac
  3. Update virtinst version requirement in configure.ac
  3. Update NEWS file (and spec with release info)
- 4. Re-generate ChangeLog with 'hg log --style changelog > ChangeLog'
  6. Update virt-manager.spec.in changelog & reset Release to '1'
  5. Checkin changes
- 6. Run 'hg tag RELEASE-X.Y.Z-1'
+ 6. Run 'git tag RELEASE-X.Y.Z-1'
 
 Preparing the build:
 
- 1. Get a fresh checkout from  http://hg.et.redhat.com/virt/applications/virt-manager--devel
+ 1. Get a fresh checkout from git://git.fedorahosted.org/git/virt-manager.git
  2. Run 'autobuild.sh'
  3. Upload build/virt-manager-X.Y.Z.tar.gz  to website download area
  4. Update the website download.html page

po/README.txt

@@ -1,28 +1,14 @@
   Notes on translation process
   ============================
 
-The translations for virt-manager are currently handled by the Fedora translations
-team. Thus the translators work on .po files which are in the master Fedora CVS
-repo for i18n stuff. Before each new release, the latest translated .po files are
-pulled back into the master HG repo for virt-manager, and a new virt-manager.pot
-file pushed out.
+The translations for virt-manager are handled by the fedora community
+via transifex. Translations are committed directly to the repo, so the
+maintainers job is quite easy :)
 
-The process for updates is this:
+To update the virt-manager translation template, run
 
+  make update-po
 
- - Get checkout of 'virt-manager' from hg.et.redhat.com/virt/ repo
- - Get checkout of 'virt-manager' from elvis.redhat.com:/usr/local/CVS repo
- - Copy all the .po files from CVS repo into the po/ directory from HG
- - Run 'make update-po'. This
-     - Rebuilds the virt-manager.pot to pull in latest strings from source
-       code files
-     - Runs 'msgmerge' on each .po file to add entries for new messages
-       and disable old ones, etc
- - Commit this to HG repo
- - Copy the virt-manager.pot & msgmerge'd  .po files back to CVS repo
- - Commit the CVS repo
+Translators can easily sign up to contribute:
 
-Running this only at time of release isn't entirely ideal since translators 
-will always be one release behind the latest source strings. Thus ideally
-the sync-up should be done on a weekly basis, as well as immediately before
-release.
+https://translate.fedoraproject.org/