Hi Rubén, Now I know what caused that Matterhorn is workflow centric. And it's really bad. Take a look at upcoming events, that are all stored as PAUSED Schedule operations.
I do not want to know is there are actually PAUSED instances of a Schedule Operation in the memory, or maybe somebody just created fake entries in "workflows" endpoint. What you are saying (and what I have heard earlier) the general answer is yes, we need it, but maybe later. Here is what you have doubts about: =============================== 1. Perhaps your proposal is not coming in the best moment. 2. I guess what I try to say is that I find it difficult to get to do such an ambitious proposal for the time being, though it's something to consider in the long run. Here is what I am trying to say: =================== 1. it's not the best moment. It should be done much much earlier, at the moment when Matterhorn turned into Video content server. 2. Ambitious proposal? It will be something like a large diagram and 20 pages of text. I have to pick tools (DIA + LaTeX, huge tiff + Microsoft office? ) Seriously, all time spend on developing right now will be like 3 or 5 times more efficient. First version should be ready in about a month. ============== Imagine, you have to carry 4 books from studenthouse to the library. You grabbed them under you shoulder and carry them.... after 300 meters, you meet your friend that gives you another 36 books under your second shoulder and you carry those. However, carring 4 books is a different tasks than carring 40 books. Especially if they have different sizes. If Matterhorn was a pipline processing tool, developed by a team that lived in a same location and had a lot of time to talk together, now it's an international video content server project, with people from all over the world working on it. What you are saying right now is --> I wil get a bag, and put the books into the bag, but... let me do 10 more meters... no 20 more... When I looked at recent changes (I wanted to upgrade from 1.3 to 1.4): (a) felix.jar is on svn. cool! I think it's a huge step in wrong direction. I can't think what forced you to do this, but there must be a different way of doing it. (b) Configuration files moved to "/etc" directory. Seriously? I am not an expert on Matterhorn - but why o why? I cannot understand that. I can ask dozens of questions like this, but all those will be inrevelant until we carry 40 books under our shoulder and do not want to get a backpack. I am not complaining. It's a good job that was done on Matterhorn, I am forcing a plan to speed things and organize. And --- it's not like I want to do this. I would like to see it done, and I can do this if nobody else can do that. Rubén, so you are saying yes to the idea of creating a diagram with Matterhorn Entities + 30 pages of description of what is there inside server's core?
_______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
