Skip to content
New issue

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

Move osm-fieldwork core functionality to FMTM as workspace package #2208

Open
spwoodcock opened this issue Feb 18, 2025 · 0 comments
Open

Move osm-fieldwork core functionality to FMTM as workspace package #2208

spwoodcock opened this issue Feb 18, 2025 · 0 comments
Labels
devops Related to deployment or configuration effort:medium Likely a day or two enhancement New feature or request help wanted Extra attention is needed priority:low Backlog of tasks that will be addressed in time

Comments

@spwoodcock
Copy link
Member

Is your feature request related to a problem? Please describe.

  • osm-fieldwork has our ODK API wrappers, plus XLSForm manipulation.
  • Many API methods could be replaced with pyodk.
  • Some are unique and we need to keep them, particularly the Async stuff.
  • However managing a separate package that is so tied to FMTM has complications: continual need for new releases.
  • We also want the package to remain available standalone for other users.

Describe the solution you'd like

  • Create a uv workspace for osm-fieldwork in FMTM - manage in a monorepo.
  • Still keep publishing of osm-fieldwork to pypi.
  • I will be easier to mount and test functionality in FMTM.
  • It also simplifies tests that rely on the full ODK stack.

Additional context

  • This should be the best of both approaches.
@spwoodcock spwoodcock added devops Related to deployment or configuration effort:medium Likely a day or two enhancement New feature or request help wanted Extra attention is needed priority:low Backlog of tasks that will be addressed in time labels Feb 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
devops Related to deployment or configuration effort:medium Likely a day or two enhancement New feature or request help wanted Extra attention is needed priority:low Backlog of tasks that will be addressed in time
Projects
None yet
Development

No branches or pull requests

1 participant