Spack has a Slack channel #4542
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alalazo
approved these changes
Jun 19, 2017
README.md
Outdated
|
|
||
| * [Spack Google Group](https://groups.google.com/d/forum/spack) | ||
|
|
||
| ### Slack channel | ||
|
|
||
| Spack has a Slack channel where you can about all things Spack: |
There was a problem hiding this comment.
Is something missing in this sentence?
tgamblin
force-pushed
the
features/spack-slack
branch
2 times, most recently
from
76e6901
to
694b3d5
Compare
- Added a badge to show who's online. - Added a section under "Get involved!"
tgamblin
force-pushed
the
features/spack-slack
branch
from
694b3d5
to
76199f4
Compare
EmreAtes
pushed a commit
to EmreAtes/spack
that referenced
this pull request
Jul 10, 2017
- Added a badge to show who's online. - Added a section under "Get involved!"
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've been hesitant to set up a chat channel for Spack simply because I worried that we wouldn't know how to deal with all the traffic. After seeing a few other projects use Slack successfully, I'm a bit less worried, and I think this will be useful for folks who want to work together on new features or coordinate across sites on all things Spack-related. I think it's also another way to get to know folks who are using Spack. Also, I piped GitHub notifications over there.
So now there is Spack on Slack. (Splack!?)
I deployed a little Heroku app (based on rauchg/slackin) so that people can sign up automatically. Hopefully this will be pretty easy for people to join.
I also added a badge to
README.mdthat shows how many people are online. Currently, if you click the badge, you're taken to the signup page, which has a link to sign in if you're already registered. We could also point it directly to Slack, but then new people would have to scroll down to see how to sign up. I suspect that most people will just keep Slack running after they sign up (since that is what I do) so I optimized for people who still need to sign up. Thoughts?@alalazo @adamjstewart
README.mdunder "Get involved!"