We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
As discussed in #1325 and on slack threads, we might want to migrate ENVO over to an ODK style layout, as well as bring in some of the ODK tooling.
I believe @matentzn would be the best man for the job, and might even be convinced to help us with it if we decide to go down this route.
Is this something we all want to do moving forward?
The text was updated successfully, but these errors were encountered:
Sure - as long as this task also includes updating the Makefile so production is maintained.
Sorry, something went wrong.
We should also have a top-level directory for mappings, where we can store our SSSOMs noted in issues like #1129.
I think that would be a good update for ODK itself.
No branches or pull requests
As discussed in #1325 and on slack threads, we might want to migrate ENVO over to an ODK style layout, as well as bring in some of the ODK tooling.
I believe @matentzn would be the best man for the job, and might even be convinced to help us with it if we decide to go down this route.
Is this something we all want to do moving forward?
The text was updated successfully, but these errors were encountered: