Change trac references to github

[ahelsing]

multiple spots in the code say to look for downloads and further information at trac.gpolab.bbn.com/gcf

As we move to github, we'll have to change these. Look at:

• README-gcf.txt

• INSTALL.macos

• INSTALL.txt

• CONTRIBUTING.md

• README.md

• README-omniconfigure.txt

• README-omni.txt

• README-gcf.txt

• README-stitching.txt

• src/gcf/oscript.py

• TROUBLESHOOTING.txt

• windows_install/infoAfterFile.rtf

• windows_install/package_builder.iss

• agg_nick_cache.base

• acceptance_tests/AM_API/README-Accept-AMAPI.txt

• omni_config.sample

  Imported from trac ticket #814, created by ahelsing on 05-13-2015 at 16:47, last modified: 05-13-2015 at 16:47

[ahelsing]

updated docs to say issues are on github

[ahelsing]

The agg nick cache is pulled from trac. It is possible to pull it direct from github where the file is checked in, if we think that is the correct thing to do. But we want this file to change on a different schedule than the code, so I'd rather this be a wiki page. I have now posted this https://raw.githubusercontent.com/wiki/GENI-NSF/geni-tools/agg_nick_cache

[ahelsing]

My branch now removes references to trac.gpolab, and moves the agg_nick_cache.

However, there are references to instageni.gpolab.bbn.com, and the canonical RSpec location is on www.gpolab.bbn.com. See oscript.py and omni-configure.py and gib-rspec-examples/click-example.rspec

[ahelsing]

At Tom's request, moving the canonical agg_nick_cache location to just be the version of that file on the master branch. Simplifying the process of doing the update.