You are not Logged in! Log in or register.

Goals for Media Mover 1.0

This is a rough list of goals for the 1.0 release of Media Mover. I'm putting this together to get feed back from other people and try to start setting some goals. Release by July 1, stable by June 1. Ok, now go!

Code Level

  • media_mover_api: change "configuration" language to "job"
  • media_mover_api: rename legacy function names
    • MOSTLY DONE
  • media_mover_api: add a "run jobs on this node now" button (need to update all harvest modules). There is already an option to reprocess an existing file, but for configurations that would have consistent harvests (ie, not email, ftp, etc) this should be an exposed option. I think a "local" vs "remote" flag should be set on harvest and storage
  • abstract ffmpeg wrapper
  • improve processing timeouts handling
  • change the $file array over to an object so it can be more cleanly passed by reference even in php 4
  • support media RSS at a core level
    • NOTE: Note there is some RSS support now
  • intelligent caching of node data, delete on new data harvest
  • cache configurations
    • DONE
  • create some kind of call back system that allows modules to tell storage operations what to do with specific data. This could also be useful for display. See: http://drupal.org/node/238666
  • Set a limit on harvest operations so that media mover performs better in a clustered environment. That's right *clustered*
    • Initial implementation is already started
  • Add weighting for each media mover job and run based on weight
  • Improve email harvest support
    • Now implements mail handler for email support

Functionality

  • provide import/export functionality like views
    • Initial implementation is done
  • supply views filter for filter by config type
    • DONE
  • improve file deleting and managing, particularly through the API
  • Cron options per configuration

Interface Level

  • move overview away from main screen
  • move files data over to admin/content/media_mover
  • improve the settings stuff
    • Configurations are now split off of the overview page

API Level

  • integrate with asset module to make MM files a choose option
    • Mostly done
  • integrate with em field
  • integrate with feedapi
  • move views functionality into separate module

New Modules (oh my!)

  • polythumbs from a movie
  • FTP support *
    • Mostly done
  • Harvest / Store to file system
    • Mostly done
  • Blip TV
    • Need to do some API changes to help this along,
  • Workflow NG integration
    • JacobSing did an awesome job with the first round of implementation

Tests

  • end to end tests for core API
  • s3 tests DONE
  • FFmpeg tests (should be done with FFmpeg Wrapper)

Documentation

  • users
  • developers

Random

  • do better testing and promotion of audio features

hello

You are absolutely right !!!

demo site

Can you provide some demo site to check the proper configuration, I'm doing my best to make it work, no result! i need to see the configurations, if you can please

Documentation

hey, will you be releasing any documentation soon?

Great goal for 1.0

Yeah, documentation is clearly needed for 1.0. I'd love help with it.

Some really short thoughts

* media_mover_api: change "configuration" language to "job"

totally!

* change the $file array over to an object so it can be more cleanly passed by reference

yes please

* support media RSS at a core level

i'm not sure what that means but sounds good anyway

Functionality
* provide import/export functionality like views

Wow. That would be very cool.

* improve file deleting and managing

Totally.

* improve the settings stuff

I don't think it's all that bad

Random
* do better testing and promotion of audio features

Agreed for promotion of audio features

Hi, Would it be possible to

Hi,

Would it be possible to give a brief update of the status of Media Mover and your planning for it? Where do you need help the most?