epriestley 6e6ae36dcf Add a skeleton for Calendar notifications ... Summary: Ref T7931. I'm going to do this separate from existing infrastructure because: - events start at different times for different users; - I like the idea of being able to batch stuff (send one email about several upcoming events); - triggering on ghost/recurring events is a real complicated mess. This puts a skeleton in place that finds all the events we need to notify about and writes some silly example bodies to stdout, marking that we notified users so they don't get notified again. Test Plan: Ran `bin/calendar notify`, got a "great" notification in the command output. {F1891625} Reviewers: chad Reviewed By: chad Maniphest Tasks: T7931 Differential Revision: https://secure.phabricator.com/D16783		2016-11-01 10:41:15 -07:00
..
accountadmin
almanac
aphlict
audit
auth
cache
calendar	Add a skeleton for Calendar notifications	2016-11-01 10:41:15 -07:00
celerity
commit-hook
config
differential	Move diff extraction from commits to a separate test with a CLI command	2016-01-08 09:22:37 -08:00
diviner
drydock
fact	Add a basic "fact" application	2012-07-27 13:34:21 -07:00
feed	Push feed publishing deeper into the task queue	2013-06-25 16:29:47 -07:00
files
garbage
harbormaster
hunks
i18n
lipsum
mail
nuance	Provide bin/nuance import and ngram indexes for sources	2016-03-08 10:30:24 -08:00
phd
phortune
policy
remove
repository
search
sms
ssh-auth
ssh-auth-key
ssh-connect
ssh-exec
storage
trigger
worker