Plumi is a video-sharing web-app built using Plone. It extends Plone with various features, customisations and add-on products to create what we think an average video-sharing site might need. However every site is different, and we also model this largely on the engagemedia.org use-case.

How can we make Plumi more useful to other video-sharing projects, by optimising its feature-set? We think we should split it into three lists of features:

• Plumi Default - these features and configurations are those we think the average video community might want to use, tending towards the minimal feature-set
• EngageMedia.org specific - these are stripped out of the Plumi package, and put into EM specific code, as we think only EM will really find them useful
• Plumi Options - these are optional extras, which will be factored out as configurable add-on functionalities, using a control panel

In addition to this, we may include notes in the Plumi Manual about tips for extra add-ons or common extensions, such as Captchas.

Let's start splitting features and customisations into these three basic areas. This list is a to-do, not a survey of current availability.

Plumi Default

• * * * * *

EngageMedia.org Specific

• EngageMedia theme
• EngageMedia taxonomies - genres, topics & country list specific to EM
• * * * *

Plumi Options

• Callouts
• Captcha - refer ticket #511. Not even sure it fits here as it probably should at best just be mentioned in the book. Plumi should not promote one version of captcha over another or restrict users to one captcha. It is a simple matter to install captcha for any admin. * * * * *