Closed (won't fix)
Project:
Open Media Airing
Version:
7.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Reporter:
Created:
1 May 2012 at 21:17 UTC
Updated:
12 Jun 2012 at 20:20 UTC
I have created a new release of the om airings module that differs significantly in approach from the 7.x-1.x branch of the module.
- Includes Playback Server Integration with the 7.x branch of OM Playback Servers.
- Includes content type and fields via the Features module rather than via custom code.
- Provides batch processes for updating airing records from Playback servers that are used in chain with the scheduling module (OM Timeslot Scheduler).
I would like administrative privileges for this project to create a 7.x-2.x branch, thus leaving the work done of the 7.x-1.x branch intact.
Comments
Comment #1
kreynen commentedom_airing was written specifically to keep the playback server specific code out of the code defining an airing . What you are describing isn't an upgrade, it's something radically different and not inline with this module...
"it defines a date based content type used to store and display events that have already been scheduled on the server"
Comment #2
darrick commentedThis module looks pretty much dead. I'm not sure why you created a separate project which does the same thing instead of just continuing to maintain this module. If you are not planning on further developing this module you should allow someone else the opportunity to do so.
Comment #3
kreynen commentedom_airing is still used on several D6 and D7 sites that I support. cm_airing defines the date as an entity instead of a node. This requires a patches to even work with Feeds and Views, so it is not ready for a supported release.
I'm not interested in an upgrade path for om_airing that requires playback server integration. I've already explained how cm_airing, cm_show, and cm_project were designed to allow everything that was in om_airing, om_show, and om_project to be configured on top of the cm_ layer just like the mnn_airing, mnn_show, and mnn_project modules do.
If you are not interested in that approach, that's fine. I'm willing to revisit this when cm_airing is stable and there is a migration path from om_airing to cm_airing, but that will depend in large part on #1033202: [Meta] Generic entity processor.
Comment #4
lkacenjaSince our vision for this module seems to differ from what kreynen expressed above and there doesn't seem to be an interest in integrating what we've written in a new branch we've created a new project focused on API level integration with playback servers and the broadcast schedule here: OM Broadcast Schedule. We will continue to focus our development efforts there.
Comment #4.0
lkacenjaAdding link to features module.