Ticket #541 (closed task: fixed)
Refactoring of Plumi - Plumi Video, Plumi App
| Reported by: | anna | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 4.8 |
| Component: | Refactoring | Severity: | New Ticket |
| Keywords: | Cc: | ||
| Who will test this: | And |
Description (last modified by anna) (diff)
Rename plumi.content to plumi.video.
plumi.app can be the whole video-sharing suite, including plumi.video and plumi.callouts.
People can just install plumi.video for a trimmed-down version of transcoding and the content types (or extended schemas).
Attachments
Change History
comment:2 Changed 2 years ago by anna
During this process, we should decide some guidelines about what will go into Plumi by default, what into EM-only code, and what could be Plumi-optional, controllable via a panel.
Here is a wiki page for this discussion: https://plumi.org/wiki/PlumiLite
Please make notes in this page about things we configure/add in Plumi that could be made optional, or removed into EM.
comment:3 Changed 2 years ago by anna
- Description modified (diff)
- Summary changed from Refactoring of Plumi - "Plumi Lite" to Refactoring of Plumi - Plumi Video, Plumi App
Have moved the stuff re. configlet / Plumi settings to this ticket: https://plumi.org/ticket/595
Callouts are addressed here: https://plumi.org/ticket/527
comment:5 Changed 2 years ago by anna
- Milestone changed from 4.2 Beta (Features and Refactoring) to 4.5Beta (New Features and Fixes)
comment:6 Changed 2 years ago by anna
- Milestone changed from 4.6 Beta (New Features and Fixes) to 4.5 Beta Refactoring
comment:7 Changed 2 years ago by and
Dimo/Mike? - with the separation of plumi.content is this done? Or is there a difference I'm not seeing here?
Perhaps some of this can be stripped out and put into a control panel, so site admins can pick and choose what they want included:
http://plone.org/documentation/kb/how-to-create-a-plone-control-panel-with-plone.app.registry