jsoxford / hubot

JSOxford

This is the source for JSOxford assets. Here you will find logos, promo images and general JSOxford stuff.

Places of interest

• The Website - http://jsoxford.com/
• The source code of the website - https://github.com/jsoxford/website
• Talk suggestions or proposals - https://github.com/jsoxford/events
• Slack invite - https://digitaloxford.herokuapp.com

hubot's Issues

Fix #meetup-buddies channel link in event announcement

#58 and #59 haven't worked :<

https://digitaloxford.slack.com/archives/events/p1486566411000076

Use fallback when dobot hears trigger word in #events

#90 (comment)

When Dobot hears it's trigger work in #events that doesn't include a meetup it should use the fallback and announce the next upcoming.

Listen for smart quotes

This is the third time this has happened.
Listen out for other quote types ', ’ and whatever else

Post event announcements to the relevant Slack rooms

At the moment, whenever Dobot detects a new Meetup event with any of the Digital Oxford Meetup groups, it posts a notification in the #Events channel.
Now that we have meetup-groups.json, it should be easy enough to get Dobot to post to the right slack channel.
The response from the API call comes back with the Group ID, which we can match up with the relevant object in meetup-groups.json. If we add a 'slack_channel' field to each object, Dobot can post to the specified room (if it is defined).

I'll probably have a go at this on Saturday, unless someone else wants to jump in beforehand.

Detecting if meetups clash?

PHPOxford and JSOxford are clashing again this month.

Would it be possible to use dobot to detect this and tell us of any clashing events? Would be mega handy if so.

Read Digitaloxford job feed and post to #jobs

Idea: pasted Meetup information

In order to get further information about a particular meetup, I could just click on the link.

But I'm very lazy. Instead, how about Dobot queries the Meetup API using the event ID in the link, then says something like That meetup is "marlow[dev] #5: VR/AR Talks and Tech", at Marlow Rowing Club, on the 2nd November 2016 at 7pm.

Could be triggered with something like robot.hear(/meetup\.com\/.*\/events\/(\d+)/)

Perhaps add to meetup.js?

Add logging to debug incorrect responses

We've had a few occasions of Dobot responding incorrectly when not actually wanted. It'd be useful to have a log of what was heard (the trigger) and what the response was so we can improve the detection.

Dobot does not indicate whether a meetup takes place outside of Oxford

In new-meetup.js, generateAnnouncement calls outOfOxford, which should take a group rather than an event.

I noticed this when reviewing another PR and I created this issue so I don't forget.

Update readme

Need to:

• Change name
• Explain how to contribute
• Explain how to get a meetup group ID

Remove the Meetup Info response

The link preview that Slack gives now contains the meetup name, location & date, so Dobot no longer needs to respond with that information when someone pastes a Meetup URL.

Respond to "When's the next meetup" in DMs

The way I understand it, DMs with Dobot are received with the prefix @dobot. It responds when you say thanks and it hears the word potato, so the reason why it isn't responding to When's the next meetup? is because the regular expression won't match messages beginning with @dobot. Removing the ^ character will do the trick, but maybe we should add \??$ at the end, which will only match if the phrase ends with 'meetup'/'event' etc. and may or may not have a question mark.

I realise now that in the time it took me to write this issue I could have fixed it already.

Add doxford

Someone remind me tomorrow to add doxford to hubot. :)

https://digitaloxford.slack.com/archives/general/p1460061730000962

Check year when announcing event

If year of event isn't current year we should include it in the annoucement.

Handle recurring meetups

When a recurring meetup is added all the events are announced at once.

It'd be nice if these could be announced individually after each previous event has passed.