EngageMedia is pleased to announce a Plone Video sprint at this years Plone Conference in Budapest, Hungary. We’ll be partnering with Aspiration and Plone4Artists to put on a 4 day sprint for developers to collaborate on open video technologies on the Plone CMS. The sprint will take place from 31st October 2009 to 3rd November 2009, directly after the conference.

Online video has exploded in recent years, being a major source of the “web 2.0” boom. YouTube, Yahoo Video and other video sharing spaces have been celebrated for making major advances in facilitating citizen media. Despite their success however there are many limitations to these proprietary platforms, such as YouTube’s limit on video size, its frequent censorship, the difficulty in downloading the video, the low quality of the flash video employed, the terms of use that allows YouTube to do near anything with your video, etc.

The ability to host and manage your own content using free, libre and open source (FLOSS) tools is essential for independent media organisations and non-profits.

Read more →

The second alpha release of the Plumi 3.0 buildout is out!

Check it out on Plone.org: http://plone.org/products/plumi/releases/3.0

The Plumi 3.0 will be released using the same procedure as Plone 3.2 – that is, as python eggs, and buildouts not tarballs of product code. [*]

The tagged buildout SVN is here: http://plumi.org/browser/plumi-buildout-plone3/tags/plumi-3.0-alpha2 and the SVN url to use to get the code is https://svn.engagemedia.org/project/plumi-buildout-plone3/tags/plumi-3.0-alpha2

We are getting back into the swing of regular releases of Plumi.  We will release alpha versions, until full Plumi 0.2.x functionality is achieved, and then start on a Beta release cycle – which will include code/docs for migrating from plumi 0.2.x sites.

Developers will want to see the Tracker and the Plumi 3.0 workplan.

[*]
“Beginning with Plone 3.2, Plone will be available as a Python package and via installers. It will no longer be distributed as a tarball of old-fashioned Zope products. The change to standard Python packaging will improve dependency handling and make future installations easier. But, it will require some adjustments for those used to installing via a tarball of products. The 3.2 installation will also require some slight changes in the buildout configuration file for those who have already been using buildout configuration management in the 3.x series.”
from http://plone.org/products/plone/releases/3.2