Commit 05b791a6 authored by Todd Gamblin's avatar Todd Gamblin
Browse files

Add citation information to README

parent 7383bd39
...@@ -29,8 +29,14 @@ To install spack and install your first package: ...@@ -29,8 +29,14 @@ To install spack and install your first package:
Documentation Documentation
---------------- ----------------
[Full documentation](http://scalability-llnl.github.io/spack) [**Full documentation**](http://scalability-llnl.github.io/spack) for Spack is
for Spack is also available. the first place to look.
See also:
* [Technical paper](http://www.computer.org/csdl/proceedings/sc/2015/3723/00/2807623.pdf) and
[slides](https://tgamblin.github.io/files/Gamblin-Spack-SC15-Talk.pdf) on Spack's design and implementation.
* [Short presentation](https://tgamblin.github.io/files/Gamblin-Spack-Lightning-Talk-BOF-SC15.pdf) from the *Getting Scientific Software Installed* BOF session at Supercomputing 2015.
Get Involved! Get Involved!
------------------------ ------------------------
...@@ -66,6 +72,15 @@ Many thanks go to Spack's [contributors](https://github.com/scalability-llnl/spa ...@@ -66,6 +72,15 @@ Many thanks go to Spack's [contributors](https://github.com/scalability-llnl/spa
Spack was originally written by Todd Gamblin, tgamblin@llnl.gov. Spack was originally written by Todd Gamblin, tgamblin@llnl.gov.
### Citing Spack
If you are referencing Spack in a publication, please cite the following paper:
* Todd Gamblin, Matthew P. LeGendre, Michael R. Collette, Gregory L. Lee,
Adam Moody, Bronis R. de Supinski, and W. Scott Futral.
[**The Spack Package Manager: Bringing Order to HPC Software Chaos**](http://www.computer.org/csdl/proceedings/sc/2015/3723/00/2807623.pdf).
In *Supercomputing 2015 (SC’15)*, Austin, Texas, November 15-20 2015. LLNL-CONF-669890.
Release Release
---------------- ----------------
Spack is released under an LGPL license. For more details see the Spack is released under an LGPL license. For more details see the
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment