Comment 10 for bug 336863

That was me, sorry, should have let you know.

--Paul

On Mar 4, 2009, at 10:31 AM, Chris Rossi wrote:

> Yep, someone was trying to triage my only half checked in code. Sorry
> about that! Fixed now.
>
> --
> Implement basics of blogentry-alert
> https://bugs.launchpad.net/bugs/336863
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Porting KARL to a new architecture: In Progress
>
> Bug description:
>
> Implement the basics of sending an alert when a new blog entry is
> posted in the community.
>
> Details
> =========
>
> - Read the UAT at https://bugs.launchpad.net/karl3/+bug/336495
> (which leads to the writeup at http://carlos.agendaless.com/dko/policies/blog.html#blog-entry-alert)
>
> - First success case is: create a new blog entry via a browser, all
> users in the community get an email per the formatting rules in the
> UAT
>
> - Second success case is: ditto, but with attachments on the blog
> entry
>
> Implementation Details
> ==================
>
> - Blog is in src/karl.content
>
> - Use get_setting for system name, system email domain
>
> Postpone
> ===========
>
> To keep this task manageable, let's carve parts out so we can get to
> a known success point without overload.
>
> - Handling per-user, per-community tri-state (now, digest, never)
> preferences on alert sending