TOPIC: github version

I'm not sure of the best way of getting our changes back to the Limesurvey team, I guess diff files. Fortunately, git supports svn, so we able to integrate yesterday's changes in subversion easily, so it shouldn't be hard to keep this repository current.

Tac

The administrator has disabled public write access.

JavaScript is currently disabled.Please enable it for a better experience of Jumi.

That was my original intention, but I think we'll also be adding our fixes in here.

If you'd like, I can transfer this repository to you, and then it can be the official one, and I'll fork that for my changes.

FWIW, I find git MUCH easier to incorporate fixes from other contributors, or for people to make their own forks. For example, I'd like to revive the API, if that were in git I'd be much more confident that the changes would make it back into the master branch.

I spent several weeks trying to integrate the Limesurvey code with an application we were doing to allow Limesurvey surveys to be done over the phone via IVR (Interactive Voice Response). Then I realized the GPL was going to require I open-source my code, so I rewrote our code from scratch, with no association with LS.

What I would have wanted to do was use the LS API, but that hasn't worked for a few years now.

I have a client now that is probably best served by LS (which pains me, because I wanted to sell them my software!), and so I'm reviving my interest in it.

Among the things that drive me crazy about LS is its dependence on numeric indexes. When you import a survey, you do so with a survey id, and all the field names of the responses have survey_id, section_id, and question_id, plus a possible subquestion code. This is not an easy structure to integrate with other systems. And the survey id's aren't even in order!

Fundamentally, sure, I'd love it if my ideas were incorporated directly into the final product. But I like the github approach, which allows me to experiment with something that might not work or only be applicable to me.

What's the status of the API, btw? Is that going to wait until 2.0, or might something work in 1.92? Currently I'm working on some other code that reads the database directly (and therefore isn't infected by GPL).