Great to hear from you. I’m moving this to the kobo-developers group which we recently created for this kind of discussion.
We would definitely love your input and code changes through pull requests. But we can definitely work together and should discuss in advance on specific issues to make sure you’re in the loop with our current and planned work.
On i18n (as mentioned in your other message): We definitely want to implement this rather sooner than later and would welcome your patches. For dkobo and the forthcoming new API this has already been considered but let’s see how we can move on this more quickly with your help.
To confirm, all of KoBoToolbox is published under open source licenses, see individual repos on github.
For the other issues I’ll let Alex respond to your specific questions.
On Mon, Jun 8, 2015 at 4:46 AM, Chroma mhazadma...@gmail.com wrote:
Hi KoBo community!
For a data collecting project we are going to install the kobotoolbox stack on our own servers. We have quite a few questions after our initial testing.
Please confirm the licenses are Affero/BSD/Apache for koboform/kobocat/enketo-express respectively.
What is the current relationship of kobocat with onadata project? They have announced a beta version recently, but it seems you haven’t pulled their commits since the time you have forked the project, nor pushed anything upstream. They’ve done some bugfixing as well. Do you plan to update onadata-related parts in kobocat or is it used as a base you are not going to do major updates on?
Do you release occasionally? Your dist-kobo-devel installation method pulls the latest code from git repos. Assuming we start our server using just that, is it safe to pull to the newest changes whenever we want to update our server software (after probably reviewing commits and testing things ourselves)?
A concern for us is, if you change the database schema, do you release patches or database migration scripts that will handle the changes in database handling?
Your dist-kobo-devel scripts have issues; e.g Chris Lea’s repos are now being replaced by NodeSource’s repos, postgres 9.4 is already out. And user name is fixed to ‘vagrant’ which is a problem if the kobo stack is going to be used outside vagrant. Do you plan updating these or accept pull requests?
Do you have a roadmap on what are you going to implement next? With our requirements we may have to implement additional features. Would you like us to discuss and send pull requests for you?
Sorry for the length in advance and the uncertain tone in our questions!
You received this message because you are subscribed to the Google Groups “Kobo Users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to kobo-users+...@googlegroups.com.
To post to this group, send email to kobo-...@googlegroups.com.
Visit this group at http://groups.google.com/group/kobo-users.
For more options, visit https://groups.google.com/d/optout.