On Feb 2, 2009, at 11:23 AM, Donohoe, Mark wrote: > The first draft of the email notification design is ready for review. > Please review and provide feedback. You can find it at: > > http://fossology.org/email-design
"The FOSSolgy process of discovering licenses can be a lengthy process ..." This applies to any agent, since agents run in the background. Even a very fast agent may be down in the queue and not executed for a while. If you run e-mail notification as an agent, presumably it will have a dependency on another agent (the one you want to be notified about). Is that right? If so, what if the other agent fails? In this case, dependent jobs are not run. The users table does have an email address but that doesn't mean that email notification is desired. So are you saying that you will add a field to indicate if email notifications should be sent by default (but potentially overridden during upload time)? You say to enhance user pages to include and optional list of email addresses. How is that different from the email field that is there now? I think the email address in the users table can contain comma separated addresses. Is this correct? The email agent initialize option could check that it can indeed send email. Like Mary said, the users table isn't the right place to add an email timestamp. I think that field should be in the job table. If someone uploads for license analysis + pkgmetagetta + specagent + ... Those run as multiple jobs. Are you going to send multiple emails? You don't say what content is in the email. It seems there should be success or error message + enough to identify to the user what file and job is being referred to. What tests are you including? Can other users subscribe to an upload so they are notified on any new analysis? Is there any user desire for this? bobg _______________________________________________ fossology mailing list [email protected] http://fossology.org/mailman/listinfo/fossology
