Hi Peter, I think we're hoping to hit on many of these issues in the 1.3 release (currently at RC5). We've got a working group dealing with install in particular, but I also think putting together a VM for use by others just to download would be good.
The tough thing here is some murkiness around patent licensing and shipping binaries of codecs. Just unclear what we are allowed to do and what we aren't. Thanks for the comments, Chris > Dear All, > > Apologies if this is the wrong place to post this. > > I asked a very experienced java programmer to help get a test version > of Matterhorn up a few days ago > > He tried to install it. Here are his comments. > > " I tried a matterhorn install last night and it built but > didn't startup correctly. > > Would be nice if there was a prebuild demo (as Sakai has, which > includes everything). > > An Ubuntu VM would be even nicer. > > Finding a copy of felix 3.0.x takes a little hunting as they only > promote the 4.0.x downloads. > > Tests failed when I was building 1.2.0 so ended up building with > tests disabled. > > Sun JDK isn't in Ubuntu/Other linux so install instructions should > probably suggest OpenJDK. > > " > > < BTW No negative criticism implied here ... but I've been asked to > post this to the list > > > On 16 Jan 2012, at 14:07, Tobias Wunden wrote: > > > Hi Ruben, > > > >> Fair enough, Tobias. You have just convinced me. A technical > >> question, though: with the episode service in place, would it > >> still be needed to put the recording "on hold"? Doesn't it appear > >> in the list just because it has been put into the media repository? > > > > It will only appear in the episode service if the "archive" > > operation has been added to the workflow. After that you are right > > that you could from there on start the mediapackage with any given > > workflow. > > > >> The discussion here becomes, then, changing the default workflow > >> from one that does the full processing to another that just puts > >> the mediapackage in the repository. I don't see many reasons to > >> changing it or leaving it like it is, giving the fact that it is > >> so easy to change the workflow triggered. Well, supposing the > >> inbox service is now working correctly, because the last time I > >> was messing with it (a while back), creating alternative inboxes > >> with alternative workflows didn't work, but I'm assuming this is > >> not the case anymore. > > > > I was always envisioning a workflow that would go on hold and then > > make use of the workflow's "append" method to append a selected > > workflow. But doing it this way seems to be a valid approach as > > well. > > > > Tobias > > _______________________________________________ > > Matterhorn mailing list > > [email protected] > > http://lists.opencastproject.org/mailman/listinfo/matterhorn > > > > > > To unsubscribe please email > > [email protected] > > _______________________________________________ > > Peter Robinson > Manager LTG Services > Learning Technologies Group, > Oxford University Computing Services, > 13 Banbury Road, Oxford, OX2 6NN. Tel: 01865 283282 > [email protected] > > Free lectures from Oxford University - http://itunes.ox.ac.uk > JISC Steeple project - http://steeple.oucs.ox.ac.uk > Open Education projects - http://openspires.oucs.ox.ac.uk/ > > _______________________________________________ > Matterhorn mailing list > [email protected] > http://lists.opencastproject.org/mailman/listinfo/matterhorn > > > To unsubscribe please email > [email protected] > _______________________________________________ -- Christopher Brooks, BSc, MSc ARIES Laboratory, University of Saskatchewan Web: http://www.cs.usask.ca/~cab938 Phone: 1.306.966.1442 Mail: Advanced Research in Intelligent Educational Systems Laboratory Department of Computer Science University of Saskatchewan 176 Thorvaldson Building 110 Science Place Saskatoon, SK S7N 5C9 _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
