Draft guidelines on something becoming an ODK tool
- The code MUST BE used as a pipeline in the processing of the ODK XForm schema or ODK submission data at any point - from form design to data export. For example, the code may be used to create an XForm, or converting XML submission data to a different format.
- The code MUST BE useful to 3 or more organizations within the ODK community.
- There MUST BE willingness within the developer community to continue contributing and supporting the project. The community is willing to define a roadmap with issues to complete the transformation of the tool to a desired stable state and a minimal set of ODK processes.
- Version Control: The code MUST BE under version control preferably using git e.g. on Github. This should allow public review of the code, public contribution to the project.
- Bug/Issue Tracking: The code MUST HAVE issues tracking supported for bugs, feature request discussions.
- Documentation: The code MUST HAVE at least 80% do