The specific repo in which the R data package is documented is used as an issue tracker specific to the tasks for that data resource: data sharing (WP2), data cleaning (WP3), data publishing (WP4): https://github.com/openwashdata/fsmglobal/issues
Benefit of this setup:
We have central place to for people to add ideas for open data and scroll through the existing ideas
Once we decide to work on this data, we use the specific issue tracker of respective package.
Problem
The process of receiving data and publishing it as an R data package spans all three work packages: WP2, WP3, and WP4.
Goal
The goal of this task is to define specifically when to use which WP to tage an issue.
Suggestion
We have a main issue in our core issue tracker for collecting ideas for open data resources: https://github.com/openwashdata/data/issues/2 -> Milestone tag: WP4. Label tag: data
The specific repo in which the R data package is documented is used as an issue tracker specific to the tasks for that data resource: data sharing (WP2), data cleaning (WP3), data publishing (WP4): https://github.com/openwashdata/fsmglobal/issues
Benefit of this setup: