ODK TAB Call - 2022-02-02

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, 2 February. The meeting time should be shown in your timezone above.

The agenda is tentatively as follows:

  • Discuss next election.
  • How can the TAB provide more value to core?

The agenda can also be seen in the agenda document

If there are topics you would like to add to the TAB's agenda, please comment below. :point_down:

1 Like

Given GetODK has assumed maintenance of Enketo, perhaps we could have a quick discussion around priority/plans for addressing some of the XForm engine behavioral differences between the two ODK clients: ODK Collect and Enketo. There are a few differences, often subtle, that occasionally trip up (power?) users thinking they behave exactly the same (eg https://community.kobotoolbox.org/t/read-only-how-to-set-dynamically/6026/9). This may possibly become even more so now that both platforms have the same 'owner'.

It may make sense to now make a deliberate decision to address any/all differences, with the philosophy that (a) they should and will eventually behave identically, and (b) till they do all differences are clearly explicitly documented [perhaps more visibly than buried in XLSForm spec?]


If we discuss Enketo, @LN mentioned here a way of simplifying the Dockerfile by factoring out dynamically generated secrets. This would allow pre-building of images and simplify/speed up the ODK Central install. Images could be pre-built and pushed to ghcr.io as a GH action like Build. Relevant PR for Central here but with open issues to sort out.