Hi Mark,
as one of the persons in charge for the engage player, I must say that I
would be very interested in the share option. Although I am not really
understand where you want to go with the player that you want for VoV.
From the mails that we exchanged with Phuong it seems to me that you
are interested in a very minimal player that you can embed very easy in
a page and that you provide an URL to the video you want to display.
This is not quite the direction we are heading with the engage player
currently, where we are planning to add more and more features
(multi-streams with 3+ streams, annotations, learning analytics, video
editor/clip show). For sure these features should be optional.
We have for sure have some common interests like HTML5 video compatibility.
So I guess it would be helpful to get a better understanding what the
requirements of a VoV player are. Maybe get some user stories.
I would say any commiter who works on the engage player [1] will be
happy to discuss your plans, review the patches that your team submits.
Thanks
Rüdiger
[1] Denis Meyer, Markus Moormann, Markus Ketterl, Greg Logan, Benjamin
Wulff, Rüdiger Rolf, ...
Am 26.04.2012 23:28, schrieb Notess, Mark H:
Opencast Community,
On March 30^th , we had a call to discuss the video player
requirements of the Variations on Video project
<http://www.variationsonvideo.org/>and how the Matterhorn Engage might
be used by our VoV project. We are already planning to use Matterhorn
for our media processing pipeline, though we will be storing metadata
and stream URLs in a Fedora repository <http://fedora-commons.org/>.
As we've looked into the Engage player code and thought about our
requirements, we are considering the following possibilities.
1.*Share*. In this model, functionality of shared interest to
Matterhorn, VoV, and other projects would be factored out and
maintained by the larger community. Matterhorn, VoV, and other
projects could then add capabilities to this shared core as needed for
their applications.
2.*Borrow*. In this model, the VoV project identifies those pieces of
the Engage player that can be used in our development, borrows the
code, and tries to keep this code as unchanged as possible so that
updates to the Engage player can be more easily included in VoV.
3.*Fork*. Similar to the Borrow option, we identify the useful code,
but we don't bother trying to keep our code in sync with the Engage
code in the future.
4.*Look elsewhere*---use no Engage code.
We'd prefer to *share* code, but it's not clear that the Opencast
community desires to develop and offer shared components in this way.
Thus, our current working assumption is to *borrow*, and we are
investigating to that end.We'd like to avoid, if possible, forking or
looking elsewhere.
We'd love to hear people's thoughts about these options and our
current path.
Thanks,
Mark
--
Mark Notess
Manager, Teaching & Learning Systems Development
Library Technologies and Digital Libraries
IU Bloomington Libraries / University Information Technology Services
Indiana University
Bloomington, Indiana 47405
812.856.0494 (w)
[email protected] <mailto:[email protected]>
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________
--
________________________________________________
Rüdiger Rolf, M.A.
Universität Osnabrück - Zentrum virtUOS
Heger-Tor-Wall 12, 49069 Osnabrück
Telefon: (0541) 969-6511 - Fax: (0541) 969-16511
E-Mail: [email protected]
Internet: www.virtuos.uni-osnabrueck.de
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________
