Tim Diggins

@jayroh not sure my solution will be that general purpose to be exportable as a gem -- but having some working practice seems like a good idea. I've started a...

@glebm Some thoughts: 1) agree generally, but maybe not submodule (this is a pain, and freezes the version into the plugin) --- instead some kind of configuration of which branches...

@glebm what do you think about including the /spec directory within the published gem so that other gems can use the spec files (particularly factories and dummy) -- without having...

NB - this would be only first step to integration test harness, but we can slowly make this happen. For the notifiers plugin I was initially thinking of using factories...

Thinking about this a bit further (after implementing) -- what we really want are objects which are like partial doubles for the key models which we can use as either...

better name for `thredded_mock` ==> `thredded_double`

PS - to make it clear: the system would wait until there is an unread followed post that is [desired-frequency] old, but then it would notifiy you about all the...

> All the other settings have a global and per-messageboard version (that defaults to global unless explicitly set), so it would be nice to keep it consistent. > > Would...

@glebm @jayroh Thinking a bit more about this implementation (the current option in my head, though the other alternative is setting future-timestamped scheduled jobs) , We could extend `UserTopicReadState` to...

[EDITED to fill out and make clearer] Here's a bit more detail on planned implementation of the delayed (max once per hour) email. When I have "max once per hour"...