These calls bring together the Technical Advisory Board for the ODK suite (@TAB) to discuss roadmaps, working groups, and other issues of technical governance. Everyone is welcome to come to these calls, but only TAB members may talk.
The calls are held every four weeks in our Dialpad room. We put the agenda, audio, and transcript of every call in this document.
Our next call will be Wed, May 11th, 2022. The meeting time should be shown in your timezone above.
There are indeed some things I'd appreciate feedback on if there's time, @TAB. In order of priority for me:
Enketo
relevance and perf changes. @yanokwa gave a status update last time. We're ready to get more feedback. Current plan is to put on https://getodk.org/xlsform/ and post about it here + Enketo mailing lists. Other ideas? Would also be helpful to get your feedback on how we're thinking about when we're ready to release.
deviations. Any new additions and/or specific ones you want to see documented?
roadmap. Current plan: add geoJSON attachment support, do another round of trying to generally clarify state management with goal of fixing remaining two high-priority deviations.
Governance
It's not explicit that Team ODK is maintaining Enketo, XLSForm standard, pyxform. I think about this periodically but I always end up prioritizing working on the tools over figuring governance out. As far as I can tell it hasn't affected much. Any strong reason to prioritize?
Collect select one from map. Next up: improve bottom sheet, improve perf, add other geometry. Any other feedback we should consider?
I don't want to be unpopular but there are still 2 points I would like to talk about:
Export to CSV from Collect (A small master's student project cannot afford a server or occurs in a remote location with no connectivity. I would like to export directly and analyze the data.)
Ability to send incomplete data from Collect (use case: I have a long form and the interviewee halfway decides that he has no more time and leaves. I wish I could send at least the partial record instead of losing the information collected up to that moment)
the above are the last 2 use cases that won't make me regret the passing away of briefcase
@ARIF_AZAD_KHAN did we see you briefly join and leave? Please do join these calls if you'd like! They're open for anyone to listen in. We don't typically pause when someone joins in later but you are very welcome.
@aurdipas thanks for bringing up the needs of small projects that are totally offline. Hopefully what I said about Briefcase reassures you that you can keep using it for workflows you already have. I think we should consider changing some of the wording that was updated recently to reflect that. Will discuss with @yanokwa.
)
but there are still 2 points I would like to talk about: