Here we will document the user stories driving vice

• 1. Georgia Tech has sites organized by department. Some users would like to listen to everything that changes in their department or on their team, but not to other departments or teams. This requires recursing containers and gathering items, so that users don't have to subscribe to a different feed for every container.

• In a plone-ish-way-of-thinking, this seems to be the-reinventing-of-the-smart-folders? We need the feed to be available on the container (folderish object), and not some other place.
• NB - at this date we are making no attempt to allow a user to configure which portions of the items gathered via recursion will be fed.  (Assuming at the moment that the UI is too hard for the payback)
• NB - we are not attempting to confront secure feeds at this time.
  

• 2. GT wants some containers to be syndicated and others not, though they may be of the same type. need to be able to enable/disable syndication on a per-container-instance basis
  
• 3. On a single container, some subscribers may want a recursive feed and others may not. We could hardcode both options, but, preferably, we'd have the ability to create multiple named feeds of different types. (Atom Recursive, RSS1.0 non-recursive) on a single container and make them all available for syndication.

• Naming the feed allows a publisher to clarify to subscribers the available RSS feeds available from any single point, i.e. [RSS 2.0] [Atom Recursive]
  

• 4. Georgia Tech wants to move content from one plone site to another over syndication. This requires RSS2.0 and/or Atom for rich content. Since FeedFeeder works with Atom, that is their first priority.

• NB - this is only to move content, not the workflows and other plone specifics.

• 5. UofL provides podcast-able media folders for its Plone users, and would like to remove the slapped-together XML template from our product and allow underlying syndication technology to take over.

• This use case can be resolved (and I've done it), using basesyndication-fatsyndication pair. (erral)

• 6. Many of our products provide notifications via smart folders' RSS and news readers on users' machines.  These smart folders have to be created manually.  If we could enable RSS feeds on our product based on the state of the plone workflow, that's several less steps for us / anyone who wants to implement our products.  The goal is to avoid needing to make a smart folder, you just get the desired result when publishing the RSS feed.

• 7. As per Plone Plip 128, one needs to be able to extend syndication beyond the common object attributes (i.e. Title, description, body etc.)