devict / promobot

Automated events promotion

promobot

This project aims to automate the promotion of devICT events, and events of local groups. It connects one or more sources to one or more channels.

Sources

A Source represents a source of events data from a specific organization. promobot will iterate through each defined source to get a list of upcoming events for promotion.

Channels

A Channel represents something that can have an event promoted through it. Examples are Slack or Twitter.

NotifyRules

A a list of NotifyRules describes when to send promotional messages about an event to various channels. A rule defines how many days out to promote the event, and what the message should look like for events promoted at that time.

promobot's Issues

Change messaging based on specific channel (not just type)

This will allow customizing the message sent to different channels of the same type.

For example, if we also send notifications to the OzSec slack, the message can be formatted differently or contain different content.

Explore iCal feeds as a source

Startup Wichita uses AirTable for their events. Look into how we can pull in this data and parse it.

Likely needs event filtering too (#5)

Link to org profiles in twitter messages

Mainly for ozsec

custom ical/gcal feed

See about putting together some collaborative/combined calendar feed including events that aren't DevICT but are promoted, like OzSec, etc - one calendar to rule them all

Deploy to fly.io

Fly does not appear to support cron runs, so implement this in app instead!

Event name filtering for sources

For some sources, we may want to be able to filter the events we promote to channels based on their name or some other data.

Add "weekly summary" functionality

It would be cool if promobot could also handle summary posts, that show all events upcoming for a given time period. This could be configurable, but the base use case would be showing the events for a week on a Monday.

Add a LinkedIn channel?

Add a facebook channel

Run at specific time of day, only once a day

Remove the sleep duration thing, since this system intrinsically should only run once a day. Instead, allow configuring a time of day that it should execute at.

Implement Twitter sending