I (as Yaw, not as a member of the PMC) currently define the ODK suite as tools maintained by the core team of contributors, under the governance and preferred licenses of this community, and stored under the ODK Github organization.
- Confuses users (e.g., this forum gets odkmeta support questions)
- Has potential conflicts of interest (e.g., Nafundi charges money for the ODK Aggregate VM)
- Is dangerous for organizations (e.g., ODK Hamster has no license, so it's not actually open source)
While the use of ODK in a product name does provide advertising for ODK, there can be real confusion in the community about what exactly an ODK tool and who is responsible for said tool. Historically, the core team has defaulted to not policing use of the term ODK, but I think that stance is untenable in the long term.
I am not a lawyer, and I don't know what the right approach is, but I'm guessing we will have to:
- Trademark Open Data Kit and ODK
- Write up clear guidelines on how to use the ODK brand and how we will enforce those guidelines
- Ask projects that have ODK in the name to comply with those guidelines
I'm curious if others see this as a problem, and if so, what their proposed solution and what potential risks are with that solution.