Change policies on sending alerts for blog content

[Paul Everitt]

Backlog IDs: 7, 8, 9 (Est: 8 hours)

This refers to the following items in the backlog:

- Send email alert option on blog comments (no support via email)
- Remove send email notification on blog entry edit
- Change send email notification on blog entry to only affect initial notification, not comments

When meeting with OSI, here were the notes. As you can see, we're taking a consolidated view of the changes and putting in place a pretty clear, consistent set of rules:

- Problem

  - Edit Blog Entry has a field for sending alerts

  - People don't realize this is persistent and inherited

  - They think it applies only to this editing action

- *For now* alerts will never go out on edits of any kind of resource. Users
  will not be presented with the option to send an alert. This might be
  revisited in a future backlog enhancement.

- When adding a new blog entry, the choice to send an alert will not
  apply to subsequent comments (or edits). Thus, the sendalert value
  does not need to be saved.

- For blog comments via a browser, there will now be an alert option
  for sending or not sending an alert when adding a comment. This
  will be just under where you add attachments to the comment.

- For blog entries/comments via email, this is the equivalent to answering
  "yes" on "send alert" via a browser.

- Remove the ZPT snippet that shows "Email alerts: on" as this will
  no longer have any meaning.

Notes
=======

- Please spend some extra time refactoring to make the code sane: have a default that can run without an adapter to thus simplify tests, clean up the tests so they don't have to wire this up, make the adapter a callable. Or, eliminate the adapter. [wink]

[Shane Hathaway (shane-hathawaymix)]

Let me see if I understand correctly.

The software currently provides a way to subscribe to email alerts whenever people add comments to a blog entry. We no longer want a subscription capability, so no alert states will be persisted anymore. Instead, when people add a blog entry or comment, they will have the option to send a single alert to all members of the community. No such option will be provided when editing blog entries or comments. Adding a blog entry or comment by email will always cause an alert to be sent.

Is that right? Also, do the other Karl sites want persistent alerts, or do they want to match the new OSI policy?

[Paul Everitt (paul-agendaless)]

Documenting a phone conversation:

1) KARL currently doesn't make any persistent statements about alerts
on a resource. People subscribe to alerts on a community.

2) An author creating a resource can make a statement that an alert
should go out to whomever is subscribed for that community.

3) The author's choice on creating a blog entry does not impact any
choices made on comments to that entry.

4) This is a change for all KARLs.

--Paul

On Jul 14, 2009, at 6:46 PM, Shane Hathaway wrote:

> Let me see if I understand correctly.
>
> The software currently provides a way to subscribe to email alerts
> whenever people add comments to a blog entry. We no longer want a
> subscription capability, so no alert states will be persisted anymore.
> Instead, when people add a blog entry or comment, they will have the
> option to send a single alert to all members of the community. No
> such
> option will be provided when editing blog entries or comments.
> Adding a
> blog entry or comment by email will always cause an alert to be sent.
>
> Is that right? Also, do the other Karl sites want persistent
> alerts, or
> do they want to match the new OSI policy?
>
> --
> Change policies on sending alerts for blog content
> https://bugs.launchpad.net/bugs/399427
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Porting KARL to a new architecture: New
>
> Bug description:
> Backlog IDs: 7, 8, 9 (Est: 8 hours)
>
> This refers to the following items in the backlog:
>
> - Send email alert option on blog comments (no support via email)
> - Remove send email notification on blog entry edit
> - Change send email notification on blog entry to only affect
> initial notification, not comments
>
> When meeting with OSI, here were the notes. As you can see, we're
> taking a consolidated view of the changes and putting in place a
> pretty clear, consistent set of rules:
>
> - Problem
>
> - Edit Blog Entry has a field for sending alerts
>
> - People don't realize this is persistent and inherited
>
> - They think it applies only to this editing action
>
> - Alerts will never go out on edits of any kind of resource. Users
> will not be presented with the option to send an alert.
>
> - When adding a new blog entry, the choice to send an alert will not
> apply to subsequent comments (or edits). Thus, the sendalert value
> does not need to be saved.
>
> - For blog comments via a browser, there will now be an alert option
> for sending or not sending an alert when adding a comment. This
> will be just under where you add attachments to the comment.
>
> - For blog entries/comments via email, this is the equivalent to
> answering
> "yes" on "send alert" via a browser.
>
> Notes
> =======
>
> - Please spend some extra time refactoring to make the code sane:
> have a default that can run without an adapter to thus simplify
> tests, clean up the tests so they don't have to wire this up, make
> the adapter a callable. Or, eliminate the adapter. [wink]

[Paul Everitt (paul-agendaless)]

Move to next week (M24). Also, assign to me as I need to provide some orientation on what needs to be done.

[Paul Everitt (paul-agendaless)]

Triage to M25.

[Paul Everitt (paul-agendaless)]

Move to beyond next week. Quite possible that these 3.2 feature enhancements get de-prioritized for work on peopledir and work on calendar.

[Jason Lantz (jasontlantz)]

The part of the specification about not showing the send alerts option when editing a blog entry does not appear to have been implemented. We just got a support call from a user who was confused about this. When editing a blog entry, there should not be an option to send alerts as no alerts will ever go out from a blog edit.

[Paul Everitt (paul-agendaless)]

Jason's right, editing a blog entry does indeed show the send alert field at the bottom. Slotted for next week.