Fix the processing of rooms.

[178inaba]

• Update rename the room name Hubot's msg.message.room doesn't handle room renames #196

Can get the name of the after the rename.
msg.message.room

• Join newly created rooms Hubot does not join newly created rooms #182
• Room specified message messageRoom still does not work #268

messageRoom was also to make it work.

Help specifies the private room in the user's name.
https://github.com/hubot-scripts/hubot-help/blob/master/src/help.coffee#L76

Hubot user have only the name.
https://github.com/github/hubot/blob/master/src/user.coffee#L9

So I get the JID from the name.

@rbergman I'd like a merge and npm release!

[rbergman]

My ability to actively maintain this is practically nil now. If someone wants to fork this repo, curate the open PRs by merging and manually testing them in a production Hubot so we can be sure they're well vetted, I'd be happy to accept aggregate PRs here and publish to npm. I don't have an effective way to test on a production Hubot any more with the (lack of) time I have available for side projects, unfortunately.

[178inaba]

@rbergman Thanks for the reply!
I do not even have time to test the other pull request.
But, I have tested this pull request by production Hubot.

Test was carried out by editing the package.json as follows:

{
  ...
  "dependencies": {
    ...
    "hubot-hipchat": "178inaba/hubot-hipchat#rooms",
    ...
  },
  ...
}

I was sure that my pull request is not a problem.

[Wilfred]

@rbergman there's a great PR at #303 that does exactly that: it's merged the PRs, tested them against a production instance and proposed a new release. Would you be able to merge them and/or give @benhanzl commit powers?