Does UMS have to be in its own repository? It is a fork of pms and you seem to want to keep it up to date with the pms trunk. Seing happy.nekko's modifications
in the UMS repo
, it is not visible where the initial commit came from and the check in is being done with your user account.
If UMS was a fork of pms, it would be easier to merge changes for both directions and the history would be clear.
From my point of view, it seems like a big overhead to maintain 'good' changes in sync.
Since I've started adding changes for pms-mlx I've always wanted to use the powerful transcoding and streaming features of pms without having to worry about how the underlying functionalities work; I instanciate a RealFile, set the thumbnail and name and the pms magic does the job to stream the video as it has to to my ps3. Now this base is drifting apart and I can't tell which will be 'better'.
Now UMS has the external libraries in its own google code repo, the web page is almost the same and the code on GitHub is in its own repo without any link back to pms.
Hope we can find a way to minimize this kind of maintenance efforts.