Commit af393905 authored by Todd Gamblin's avatar Todd Gamblin
Browse files

README: Tighten up text, mention the Code of Conduct in the README.

parent 9c37a4c9
......@@ -26,55 +26,45 @@ Then:
$ git clone
$ cd spack/bin
$ ./spack install libelf
$ ./spack install zlib
[**Full documentation**]( for Spack is
the first place to look.
[**Full documentation**]( is available, or
run `spack help` or `spack help --all`.
Try the
[**Spack Tutorial**](,
to learn how to use spack, write packages, or deploy packages for users
at your site.
We maintain a
[**hands-on tutorial**](
It covers basic to advanced usage, packaging, developer features, and large HPC
deployments. You can do all of the exercises on your own laptop using a
Docker container.
See also:
* [Technical paper]( and
[slides]( on Spack's design and implementation.
* [Short presentation]( from the *Getting Scientific Software Installed* BOF session at Supercomputing 2015.
Feel free to use these materials to teach users at your organization
about Spack.
Get Involved!
Spack is an open source project. Questions, discussion, and
contributions are welcome. Contributions can be anything from new
packages to bugfixes, or even new core features.
### Mailing list
If you are interested in contributing to spack, join the mailing list.
We're using Google Groups for this:
* [Spack Google Group](
### Slack channel
Spack has a Slack channel where you can chat about all things Spack:
packages to bugfixes, documentation, or even new core features.
* [Spack on Slack](
[Sign up here]( to get an invitation mailed
to you.
### Twitter
You can follow [@spackpm]( on Twitter for
updates. Also, feel free to `@mention` us in in questions or comments
about your own experience with Spack.
### Contributions
* **Slack workspace**: [](
Open to anyone; visit
[]( to have an
invitation emailed to you automatically.
* **Mailing list**:
* **Twitter**: [@spackpm]( Be sure to
`@mention` us!
Contributing to Spack is relatively easy. Just send us a
[pull request](
When you send your request, make ``develop`` the destination branch on the
......@@ -92,6 +82,13 @@ branching model. The ``develop`` branch contains the latest
contributions, and ``master`` is always tagged and points to the latest
stable release.
Code of Conduct
Please note that Spack has a
[**Code of Conduct**](.github/ By participating in
the Spack community, you agree to abide by its rules.
Many thanks go to Spack's [contributors](
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