As I understand you are requesting us to move our current patches on the UC Davis SCORM player to contrib. Let me explain why we did not do this until now, and why this task is not as trivial as it seems.
We started off testing with the SCORM player long before we had write access to the SVN repository. For that reason we pulled our own copy. The initial bugs we found we reported in JIRA together with patch files. In the mean time, James Renfro and his team @ UC Devis continued their development, and also started to apply the patches. As soon as we got SVN access we stopped providing patches, because we assumed we could merge back to contrib soon. What turned out is that the merge back wasn't as straightforward as we assumed, for the following reasons:
- James applied some of our patches, causing merge conflicts.
- Some patches where applied in another fashion, and issues where fixed in simultaneously, making merging even more complex. In some cases patching requires deep understanding of the problem at hand.
- We did our patches on the 2.5.x branch, but James continued to work on trunk / 2.6 at some point.
- We targeted and tested 2.5.x, and we are not sure what the status is of trunk and the branches and what version should be targeted.
- All the above causes this not to be a simple merge job, it also consists of some testing.
This does not mean merging is impossible, it will just take me 2 to 3 days to work trough each change individually and apply it to the contrib space. We're pressed for time to do this right now. We could do a couple of things:
- Find someone who could do the merge job.
- We could drop our version as a branch of the SCORM tool or maybe in the Edia space. This does not solve the problems above, it will merely change https://svn.edia.nl/edia-sakai/ into http://source.sakaiproject.org/contrib/
- Wait for / help us to acquire resources to merge our code, or even better: maintain the SCORM tool.
Our version is available at:
Our work is done at:
Roland MS Groen
Edia Educatie Technologie