[Design] Re: [strategy] driving adoption

[Mimi Yin]

Just to clarify,

Are we saying we want to have 3 levels of Notifications for Changes?

A. A user can check their Activity Log or go look at a Shared  
Collection to see what changes have been made.

B. A user subscribes to an RSS feed for change notifications and/or a  
publisher puts a sharee on a RSS feed change notifications. (Scenario  
described below).

C. A user actively PINGS sharees about a significant update. (What we  
do today when we email people about a new wiki page.)

I'm not sure I see much of a difference between A and B? But I might  
be missing something? It seems like anyone who is subscribed to a  
shared collection should be able to inspect an Activity Log to see  
Recent Changes. People shouldn't have to sign up or be signed up for it?

Hmmm, I think this is really a design list issue.

Mimi :o)

>> Stamping the item as email also would send an invitation.  Changes  
>> would create an RSS feed.  This would be a lightweight way of  
>> enabling collaboration among a group of people.
> We definitely need to make our Notification story (RSS, email, SMS)  
> stronger. The publisher of an item should be able to add "people to  
> be notified" on modification, the users of an item should be able  
> to add / substract themselves and choose their preferred way of  
> being notified.