continuum-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jesse McConnell" <jesse.mcconn...@gmail.com>
Subject Re: Solving the notification problem
Date Wed, 01 Aug 2007 02:01:52 GMT
well, 1.1 is in beta now so ideally no more features, but maybe we just call
this a bug fix for now..

I guess the first suggestion might be a batch email option with a summary
presented at the top of the mail...that would almost have to be on a per
notifier though, but that is made easier by the group level inherited
notifiers...That is another db schema change though :)

We could alter the notifications to prepare web reports that have the links
mailed out, and suppress mails based on time or if a given link has been
mailed recently.

what conditions do we find the highest lvl of easily ignorable mails go out?

I can think of things like SCM outage and things like that...out of memory
errors...

jesse

On 7/31/07, Brett Porter <brett@apache.org> wrote:
>
> Hi,
>
> I would like to see us address the problems of mass-notification
> which tends to be a blight on Continuum when dealing with projects
> with lots of modules in 1.1. I think with this simple usability
> improvement, the perception of the quality of the overall system
> would be greatly improved.
>
> So I wanted to start this thread to brainstorm ideas for what we
> might do to make it less noisy, but just as effective. I have some
> thoughts, but I'm interested to hear others first.
>
> What do others think? Should this be in 1.1, and if so how should it
> work?
>
> Cheers,
> Brett
>



-- 
jesse mcconnell
jesse.mcconnell@gmail.com

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message