Introduction

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
Steve Hanson's picture
Posted by Steve Hanson on October 29, 2007 at 12:04am

Hi -
I'm Steve Hanson, the principal at Cruiskeen Consulting LLC. We're in the process of contracting with a community access group to re-do their web site. I noticed this project on the web, and was about to start a group here when I realized there already was one. I'm still kind of getting my bearings in this part of the Drupal world - but we're interested in helping out here. At the moment we're looking at modifying parts of the Station module, which already does a good deal of what we're interested in doing for program scheduling, etc.

Just thought I'd introduce myself - I see that this project seems to have been fairly stalled for the past year (at least it looks that way). We might be able to help out here, at least from a project management viewpoint if anyone needs that.

One question I have, though - all of this development seems to be aimed at 4.7 - why would that be?

Comments

Not stalled...

Posted by lego1974 on November 12, 2007 at 4:34pm
lego1974's picture

Hi steve, thanks for reaching out! OpenFlows (on behalf of MNN) is in the process of developing the on-air scheduling and playout module for use at MNN (and beyond).

Currently, Denver Open Media has completed some work on a playout module as well, and we're going to coordinate our efforts. If your team would be interested in managing the features, that'd be a huge help to us all.

You can download our latest modules further down the page. Matt Goins from OpenFlows posted them. Warning: they require a lot of work at this point and rely a lot on CiviCRM as well.

-Andy

Also...

Posted by lego1974 on November 12, 2007 at 4:35pm
lego1974's picture

Joe Golden has done some work on scheduling. See comments on my previous post.

4.7

Posted by lego1974 on November 12, 2007 at 4:39pm
lego1974's picture

Steve, the reason we are targetting 4.7 is because the project began over a year ago when 4.7 was the norm. The goal is to migrate everything to 5.x once we've got the modules working. The scope of the work we have with OpenFlows is 4.7 To change midstream would create havoc.

agreed

Posted by ericG on November 12, 2007 at 11:00pm
ericG's picture

Just to chime in on the why 4.7 question.

Drupal development is very fast, this project's development is very complex.

We started writing the spec for this project when 4.7 was the current version and we committed at that point to remain on 4.7 until the completion of the project.

Once the final modules are done (which I expect will be sometime in March 08), there will be the need for a group effort to upgrade everything to whatever the current version is at that time (most likely drupal 6).

Then we can find groups willing to take responsibility for keeping the modules at least close to current.

welcome!

Posted by ericG on November 12, 2007 at 11:04pm
ericG's picture

Steve, thanks for joining the group and introducing yourself.

You'll find that there are some modules that we've released via this group and not the drupal modules page.

The logic behind this decision is that the modules are still in a young/beta phase and we did not want to add to the bad side of the signal-to-noise ratio that is happening on the drupal modules page. Since there is no way of explicitly marking a module as not-ready-for-prime-time we felt that releasing the modules on the drupal modules page could confuse novice users and lead to confusion and negative feelings, instead of growing the collaboration via this group.