Purpose of the 'help' command after progdisc/resources

[rgoliveira]

After progdisc/resources#10 there's no reason to keep those things here too...

So what should AB's help command do?

1. scrape that README to get something to display;
2. reply with a link to that repo; or
3. be removed entirely.

I think, at least for now, the 2nd option is the easiest and least disruptive. Ideas?

[lethargilistic]

I think 2 is good for the interim, but eventually 1 would be the best option. It's why we created that repo in the first place.

Perhaps AwesomeBot's help could link directly to the section they're after, even.

[ecoerod]

I vote for 1 as well. Having a help command to send somebody to an external link seems to be pointless overall.

[lethargilistic]

If we're going to do 1, we'd need to complete progdisc/resources#8. Perhaps there's a way to create a linter for that project with a CI service?

[ecoerod]

We can probably research and integrate this, using a Ruby instance on Travis: https://github.com/markdownlint/markdownlint

[ecoerod]

I took upon me to implement option 2 as a preliminary measure, in pull request #113.