Since the end of Dan Meyer’s SLV SCAV, it’s been in the back of my mind to get the source code available to more people, and there was at least some interest from others about running their own copies.
As a result, I took the time to go through the code, remove any references to the school, students, or teachers that I could find, and generally cleaned the code up for release. I changed the name to “scavhunt,” and made a working version that I can release. I’m happy to say that the code is now available as open source (AGPL v3), from GitHub as scavhunt.
Unfortunately, I haven’t yet had the time to properly document things. As it is, if you pull the code down (either use git if you’re comfortable with it, or download a tarball/zipball with the “Downloads” button in the upper-right corner of the GitHub page), it should be a working scavenger hunt, although a bit sparse. There are a number of files you should modify, and some directories that need to be writable by the web server, but those are all documented on the README.md file (and also on the GitHub page for the project). It comes with two example questions as a basis for writing your own, although additional question types exist in the code as well.
So, the code is now available for your use, however you see fit (as long as it complies with the AGPL v3, which is pretty relaxed in terms of usage). If anyone has any questions, feel free to contact me at andy [dot] schmitz [at] gmail [dot] com, or potentially file an issue on GitHub (although I’m new to GitHub, so it may take me a while to figure out how to respond). Unfortunately, at the moment, I don’t have enough time to necessarily improve the code in the ways I would like to, but I can certainly answer questions and respond to pull requests from those who would like to improve it on their own. Contributing your improvements back would be greatly appreciated. And hey, if you use it, I’d appreciate an email or tweet (@aschmitz) to see where it’s in use.
P.S. This is indeed where the scoreboard movement tracking code came from, so that section is rather well-commented. Unfortunately, the rest is less documented, but hopefully understandable.