@crichID I think this looks great! I would just add @brntbeer's suggestion:

What about starting a PR to even be able to talk about something more concrete when wanting to make something better?

@crichID What are your thoughts on including badges at the top of the Readme, similar to those found on Atom?

I like it because if we decide to add a Slack channel then we can also include that badge. Also, badges are fairly consistent in the Open Source community, and it would be cool to be an exemplary repository in every nuance that we can.

Also, this isn't a blocker for now, but this might be a ✨ place for a banner based on the title card that @loranallensmith is in the process of designing for our videos (brand strengthening!) 😄

Here's the link to our Travis build if yes (I'm also happy to commit this in):

@hollenberry I like the Travis badge so 👍 from me 😄

Here's the link to our Travis build if yes (I'm also happy to commit this in):

@hollenberry I may only speak for myself, but from what I understand, please feel free to go ahead and make these types of commits (both now and in the future) and if there is opposition to it, we can always remove it later. As hubot would say, you are trusted. 🤖

Update:

• I created a Heroku server for Slack invitations, as well as a Slack group. This process was super easy (though misconceptions on my end made this a massive time-wasting endeavor), and I'd ❤️ if a few of you can test this by joining the channel via the button instead of a direct invite.
• I spent a little while attempting to add this badge : , but for our server
  • Spoiler alert: It doesn't work. We need a package.json file to list our dependencies. Currently, that file appears to be a bower.json file.
• I added an image. ✨ to @loranallensmith

Woohoo! Slack channel button works!

@hollenberry Not a criticism, just a general thought: Do we want to maintain both a Gitter community and a Slack community, or does it make sense to keep the chat to the same service?

Do we want to maintain both a Gitter community and a Slack community, or does it make sense to keep the chat to the same service?

The original reasoning behind Gitter was to reduce the number of accounts needed by someone to join, and the integration with where we can easily link to issues/PRs, and the support of Markdown. In either case, if we start using Slack I don't think it makes sense to keep both chat services and we should then stop using Gitter.

@github/services-training based on #430 I thought it might be a good idea to go ahead and 🚢 this. I removed the chat link while we decide whether to stick with Gitter or switch to Slack. I also reduced the scope of this PR to the README since the CONTRIBUTING guide still needs some ❤️! Please feel free to open a new PR if you see additional changes we need to make.