So I've been working on this for the past days. Still a work-in-progress,
and will need at least another week of development hours (read: 2-4 weeks
of actual time) before we can really think about migrating to wave.
The apache mailing list is rejecting the emails from my bot, it thinks
they're spa
Bruno,
This looks quite cool.
The main thing I am thinking is how 'big' an event has to be before
triggering sending an email. (A spelling correction is hardly worth
it)
We also don't want a large sequence of emails being sent for changes
happening within a few seconds of each other (think simult
sounds like a very interesting bridge to keep the community both efficient
and in formed. Thanks!
John
On Fri, Jun 7, 2013 at 5:48 PM, Bruno Gonzalez (aka stenyak) <
sten...@gmail.com> wrote:
> So I've been working on this for the past days. Still a work-in-progress,
> and will need at least an
Right now, in part due to its alpha state, and in part due to bugs (I can't
receive newBlip notifications, etc), emails are only sent when the user
writes "bot:send\n". At that very moment, the bot sends a single email.
Regarding synchronization schedule, we could keep a list of "blips not yet
syn
This needs to be done today. Any volunteers? It would be a shame to miss
a report at a point when the project is looking up. I'd say this doesn't
need to be done by a committer. Someone who is prepared to review other
reports on the below mentioned wiki page and write something similar.
Note, the
