Active
Project:
SCORM Cloud
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
16 Feb 2012 at 11:41 UTC
Updated:
11 Oct 2013 at 11:45 UTC
Jump to comment: Most recent file
Comments
Comment #1
webservant316 commentedYes a plan is forth coming - more details to come.
Comment #2
SimonShack commentedYes, we are planning a D7 migration immediately after reaching a stable D6 release, which should be any moment now.
Comment #3
webservant316 commentedvery easy patch for last known bug posted here http://drupal.org/node/1441344.
hope to commit this patch shortly.
Comment #4
webservant316 commentedpatch has been committed.
watch the project home page for updates on the D7 release.
Comment #5
tebb commentedHi Webservant 316,
Could you just mark this issue as 'fixed' when there is a 7 release? That way, anyone who wants informing can follow this issue and be alerted automatically rather than keep checking back to the project page.
Also, I can't remember why (doh!), but it's normal to set to fixed, then the system changes that to fixed(closed) after 2 weeks. Again, it's something about people being aware of the issue being completed.
Thanks.
Comment #6
webservant316 commentedno prob - thanks for the Drupal tips
Comment #7
dave bruns commentedJust checking in to see if a d7 version is imminent? I want to test this module, but if the 7 version is still a few weeks away I'll test on d6.
Comment #8
SimonShack commentedThe D7 migration is currently under way, but I wouldn't expect it overnight, a few weeks is more likely. We're going to take our time to make sure it's done well rather than rush it out.
Comment #9
bonobo commentedWill the development for this be centered here on d.o, or will the module be ported outside the d.o infrastructure?
If it's here on d.o (or at another publicly accessible spot like github) you could potentially get the the support/help of other interested parties who are looking for exactly this functionality in D7.
Comment #10
veleiro commentedhow is the progress on this release going?
Comment #11
webservant316 commentedThe original effort to port this module to D7 is facing a major set back and may not recover. It may be that an unforeseen miracle revives their effort. However, consider this post as an invitation for any other developers to contact me about porting this module to D7. Thanks.
Comment #12
fabianx commentedWe are probably taking over the porting.
Could you upload the last D7 version to a branch?
If not we will start from scratch.
Thanks,
Fabian
Comment #13
webservant316 commentedI'll contact 'Doghouse Media' who was working on the effort to get you anything they have.
Comment #14
ludo1960 commentedAny news of the D7 release?
Comment #15
webservant316 commentedThe @doghouse effort has failed. @Fabianx is beginning a D7 port from scratch. Contact @Fabianx for details.
Comment #16
ludo1960 commentedThank you for taking the time to answer my post, I will contact fabianx. Cheers!
Comment #17
webservant316 commentedSomeone told me that drupal.org/project/coder could be used to help port D6 code to D7. I don't know if this is true, but it is worth checking into.
Comment #18
ludo1960 commented@webservant316
Hello again, tried to contact Fabian without success, tried the drupal.org/project/coder thing and attached is the result, not sure what to do now... lol!! Thought it would have Drupal 7 written all over it!! If only eh, any ideas what I do now?
Thanks..
Comment #19
sheldon rampton commented@ludo1960, @webservant316: My company has a client who wants a Drupal 7 version of the SCORM Cloud module, and we have a developer with time available to work on it. It sounds like the work done to date is fairly minimal, but I want to make sure we avoid duplicating efforts. Can you contact me to discuss this so we can agree on the most efficient path forward? My phone number is (608) 206-2745.
Comment #20
webservant316 commentedCurrently there is no D7 code to forward to anyone. Read above to see that the initial D7 project by @Doghouse Media failed. @Fabian implied that he wants to lead out with a port and also others above. Anyone is welcome to download D6 and begin the conversion work. The D7 effort most likely to cross the finish line will likely need the same components that we had for the D6 effort. I can appreciate everyone's desire to avoid duplicated effort and perhaps save investment if someone else is already committed to doing the work. At this point a few people have said they plan to do a D7 port, BUT I've only heard words and not seen any code. Perhaps the best strategy would be to talk closely with the people at SCORM Cloud. The project cannot be successful without excellent coordination with them anyway.
Components for success:
1. Excellent Drupal/PHP knowledge as we had with @ronan of Gorton Studios
2. Financial backing to see the project through
3. Strong communication with the people at SCORM Cloud
4. Strong communication with the current maintainers, @webservant316
I'll be glad to add a D7 maintainer once someone has proven they will get the project across the finish line. Personally, if I needed the D7 version and I had the money I would simply hire Gorton Studios to port their own code. That would be the most efficient solution.
Comment #21
sheldon rampton commented@webservant316: I've had a couple of conversations with the folks at Scorm.com. I told them a couple of months ago that we were interested in getting the module updated to Drupal 7. They indicated at the time that they thought someone was already working on it, but it appears those efforts have stalled. I'm interested in getting involved now in developing the update (as opposed to just waiting for someone else to do it) because we have a developer resource who has just become available, and this seems like an excellent project for him.
I spoke with Ronan at Gorton Studios earlier today and agree that he is a talented developer who did a great job with the Drupal 6 version of the module. I think my team is prepared to do the D7 upgrade ourselves if no one else steps up, but obviously we don't want to step on anyone else's toes or waste developer time on duplicated effort. It appears that the two parties most interested in currently working on the project are ludo1960 and myself. (The others who have expressed interest have dropped off.)
I sent a note to ludo1960 and have gotten a response back, so hopefully we can find a way to divide up the project between ourselves and get it done sooner. Once I have code that seems worthy of adding to the project, I'll ask for maintainer status.
Comment #22
webservant316 commentedSounds great. This issue post is THE location I will be watching for status updates on any actual D7 work. As soon there is any substantial work I will gladly grant maintainer status. Best wishes!
Comment #23
acouch commentedI've been working with Sheldon and we have some code to commit. I've filed and issue to be able to add it to this project #1730254: Request to Co-Maintain this module for D7 Port
Comment #24
fabianx commented@acouch: How did you solve the field upload issue? We also have some code to commit by now. I was away on 9th so missed the update.
We will attach code here soon. I will then run a diff based on what you did vs. what we did so far ...
Comment #25
webservant316 commented@acouch added as maintainer of D7. @Fabianx you seemed to fall out of contact while @acouch stepped forwarded. Please coordinate with each other and let me know how you want to proceed in order to reach the D7 finish line with the best solution in the best time. Best wishes all.
Again this is THE issue I will be watching for all D7 related discussion.
Comment #26
acouch commented@Fabianx we will post what we have in a couple of days or so. If you have anything to share thus far please post on github or in a sandbox and we will look at how to merge. Initially we are just trying create a filefield that accepts only zip files and then hand the processing off to scorm cloud. It is a complex issue so it is great to hear there is a group that can help get this ship to sail. My skype name is aaron_couch if you want to confer in the meantime.
Comment #27
franz@acouch, I'm working with Fabianx on this upgrade, so far our efforts can be seen here: http://drupalcode.org/sandbox/franz/1736556.git/shortlog/refs/heads/7.x-1.x
http://drupal.org/project/1736556/
When cloning, checkout the 7.x-1.x branch, as the master was left pointing to the original scorm_cloud code.
Comment #28
fabianx commentedhttp://drupal.org/sandbox/franz/1736556/ is the right URL.
Comment #29
ludo1960 commentedAll gone quiet?? Suppose no news is good news!
Comment #30
sheldon rampton commentedludo1960: I met up with Fabianx at DrupalCon Munich and discussed the module with him. He feels that his version is working and ready for testing, but we just haven't gotten around to doing the git commits yet. If you want to try it out in the meantime, go ahead and download it from his sandbox at http://drupal.org/sandbox/franz/1736556/
Comment #31
webservant316 commented@acouch hopefully you are in touch with @Fabianx to get the D7 module uploaded to this project as soon as you feel it is alpha or beta worthy.
Comment #32
acouch commentedSorry for the delay. Will post code soon. @fabianx do you want to chat on IRC about this? Would like to try and merge our work in a way that makes sense to all parties.
One thing that has held me back for a bit is that the part we've built is just the scorm upload field while the D6 module also supported signing up to classes through the scorm cloud API. I was thinking of breaking that up into three separate modules scorm_cloud (just API integration), scorm_cloud_field (field upload), scorm_cloud_reg (scorm cloud registration). Would that make sense to folks?
Comment #33
webservant316 commented@ronan may be the best resource for counsel here as he is the primary developer and understands D6 and D7 architecture well. For myself if you break D7 into three modules I would recommend that the D7 version still remain one project download, but with three sub-modules. Then at least it remains parallel to the D6 version in that it is one module package to install. I probably don’t really understand your use case well enough to see why you would only need a piece of the module, but yes sub-modules would make that possible. However, wouldn’t it be a faster and more reliable plan to simply port the D6 module keeping as close to the original architecture as possible? The D6 version is thoroughly debugged with no outstanding issues and if you stay close to its architecture you will benefit more from the effort already put into D6.
Comment #34
acouch commented@webservant316 I would propose keeping it one module with three submodules.
Comment #35
webservant316 commentedany updates?
Comment #36
fabianx commentedWe found some minor bugs in the version that is creating the number of takes as "a" instead of "0".
Besides that we are mostly using the "preview" functionality as launching and not the course registration for now.
Best,
Fabian
Comment #37
webservant316 commentedare these bugs in your D7 version OR the current D6 version?
If the D6 version please forward details, filenames and line #s to @ronan and @webservant316.
Comment #38
fabianx commented@webservant316: Only in our port of the D7 version (sandbox version). If it was in D6 I would have opened another issue.
Thanks,
Fabian
Comment #39
webservant316 commentedok - thanks
Comment #40
ludo1960 commentedWish I was good at waiting!! :) Any news yet?
Comment #41
acouch commentedI want to apologize to everyone. We were doing this for a client. It was almost wrapped up then they decided they didn't want it until a later phase which we haven't started. I had things closer to commit ready when my virtual box hard drive died. I will try and post what I have so far this week. Again I apologize for grabbing the reins and falling asleep on the horse.
Comment #42
webservant316 commentedSo are you in for the distance or am I looking for another D7 maintainer?
Comment #43
fabianx commentedUnassigning
Comment #44
webservant316 commentedNow looking for another D7 developer to port the module.
Comment #45
pyxio commentedis this project dead?
Comment #46
webservant316 commentedThe project maintainers are eager for a D7 port. We've had a few step forward to make an effort at the port, but they have failed for various reasons. So there is currently no effort underway that the maintainers are aware of, but we are eager to support any volunteers. The project really should be quite simple. The D6 code is clean and more than thoroughly debugged. Any one with an interest in doing the port to D7 please post to this issue queue.
Comment #47
joshuautley commentedwebservant - The reason module is failing is because Rustici Software and its team are not maintaining the module. Why should anyone in the Drupal community support a "paid" service? Other paid services which are successful maintain their module counter parts themselves. They do not ask the community to "volunteer".
Drupal 8 is almost here and this module hasn't even caught up to Drupal 7. This says a lot about Rustici Software and its not a positive thing.
I worked in the DoD sector for 6 years designing and developing SCORM / ADL compliant courses and did fine with the many free resources available. It's seems this module is indeed "dead" or more appropriately a failure.
For developers looking for solutions here is a quick link to the ADL Resources > http://www.adlnet.gov/resources/
Comment #48
webservant316 commentedJust to be clear the maintenance of this module is my personal responsibility and not Rustici Software. Let the criticism above fall to me.
I coordinated the development of the module for a paying corporate customer and they are quite pleased with its performance. We felt the quality of the Rustici SCORM player was worth their fee. My corporate customer has also given the module away at drupal.org in the spirit of open source. I would also be glad to see the module ported to D7 by ourselves when have need or any other volunteer. Note that there are numerous other Drupal integrations to paid services so this is not an unusual practice.
There certainly are other free and premium solutions available if this one is unsatisfactory for your need.
Comment #49
pameeela commentedHi all,
Sorry to see that this has stalled. We may need to port the module this module to D7 for a client. Is anyone on this thread able to provide an update on the status of the sandbox linked in this issue? Would we be better off trying to use that or starting from scratch?
Comment #50
webservant316 commentedI am the sponsor of the D6 module which performs excellently and is fully debugged. That certainly would be an excellent starting point. You will have to contact the contributors above directly and examine their initial code yourself to determine the value of using their code as a starting point.