There is already a thread comparing ODK Collect to ODK Survey, but I am
still unclear on what the direction of the project is.
Is ODK Survey supposed to (after it is ready for production use) replace
ODK Collect entirely? Or is ODK Collect going continue to be developed in
parallel with ODK Survey?
Once 2.0 is released, the core team will be focusing primarily on the 2.0
tools -- ODK Survey, ODK Tables, the new 2.0 data storage features on ODK
Aggregate, plus a suite of additional tools -- ODK Scan, ODK Sensors, ODK
Diagnostics.
The 1.x functionality will transition into community-supported maintenance
releases. That means the core team:
will coordinate and review changes and extensions proposed by the
community,
will manage and produce releases for the software ( XLSForm, ODK Collect,
ODK Briefcase, ODK Aggregate ).
will ensure that the active code tips still build with the newer
development tools released by Eclipse and Google.
will update the set of third party libraries that the tools depend upon
on an as-needed basis (not proactively)
will NOT be producing its own extensions to these tools.
Mitch
···
On Wed, Jan 15, 2014 at 3:03 PM, Rey Rodrigues wrote:
Hi everyone,
There is already a thread comparing ODK Collect to ODK Survey, but I am
still unclear on what the direction of the project is.
Is ODK Survey supposed to (after it is ready for production use) replace
ODK Collect entirely? Or is ODK Collect going continue to be developed in
parallel with ODK Survey?
Nafundi is committed to continuing development of the 1.0 generation
of tools for the foreseeable future. So don't worry, ODK Collect isn't
going anywhere.
Yaw
···
--
Need ODK services? http://nafundi.com provides form design, server
setup, professional support, and software development for ODK.
Once 2.0 is released, the core team will be focusing primarily on the 2.0
tools -- ODK Survey, ODK Tables, the new 2.0 data storage features on ODK
Aggregate, plus a suite of additional tools -- ODK Scan, ODK Sensors, ODK
Diagnostics.
The 1.x functionality will transition into community-supported maintenance
releases. That means the core team:
will coordinate and review changes and extensions proposed by the
community,
will manage and produce releases for the software ( XLSForm, ODK Collect,
ODK Briefcase, ODK Aggregate ).
will ensure that the active code tips still build with the newer
development tools released by Eclipse and Google.
will update the set of third party libraries that the tools depend upon on
an as-needed basis (not proactively)
will NOT be producing its own extensions to these tools.
There is already a thread comparing ODK Collect to ODK Survey, but I am
still unclear on what the direction of the project is.
Is ODK Survey supposed to (after it is ready for production use) replace
ODK Collect entirely? Or is ODK Collect going continue to be developed in
parallel with ODK Survey?