MerginMaps / MerginMaps/work-packages
Synchronize non spatial data between master and wp
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Currently after workpackages are initialized we only synchronize data changes in configured gpkg. All other changes (e.g. QGIS project file) are ignored.
We can propagate more changes, e.g.
- QGIS file update in master would propagate to wp but not the other way around
- photos or other assets collected in wp would be only propagated to master but not spread across all child projects
TODO: come up with other use cases and rules.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by tracing work-package initialization and the existing configured GPKG synchronization, then document the additional use cases and propagation rules for QGIS files, photos, and other assets. Done means the rules and supported synchronization behavior are explicitly defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100