Closed astrofrog closed 10 years ago
Fine with me -- just make sure dendrograms.org still works! In fact, I think we should set up a dummy redirect repository at dendro-core, in case someone follows an old link. It can just have a README pointing them to the new location
I think GitHub will automatically redirect: https://github.com/blog/1508-repository-redirects-are-here
Ah but you mean if they follow a manual link, not a git remote.
References to dendro-core:
beaumont@beaumont-3:~/dendro-core$ find . -name "*.py" | xargs grep dendro-core *.py
setup.py:setup(name='dendro-core',
./setup.py:setup(name='dendro-core',
beaumont@beaumont-3:~/dendro-core$ find . -name "*.rst" | xargs grep dendro-core *.py
setup.py:setup(name='dendro-core',
./docs/index.rst:<https://github.com/dendrograms/dendro-core/issues>`_.
./docs/installing.rst: git clone https://github.com/dendrograms/dendro-core.git
./docs/installing.rst: cd dendro-core
./docs/migration.rst:<https://github.com/dendrograms/dendro-core/issues>`_.
Done!
The repository name doesn't currently reflect the name of the package, which may be confusing - shall I rename the repository name to
astrodendro
? (since in the end, we included the analysis and visualization code in the same package?)cc @ChrisBeaumont @low-sky