The `workflow` and `package` paradigm
@jdhoffa is already working on this.
Since Jan 31, 2024.
- Dominant language
- No language data
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Packages are used to keep track of modular code that we intend to re-use multiple times, and want to have unit-tested and portable.
A template PACTA R package repository can be found here: https://github.com/RMI-PACTA/pacta.r.package
Workflows are much less structured, and are used to keep track of any kind of data analysis or data science type pipelines.
A template PACTA workflow repository can be found here (with some useful guidance on how to conduct reproducible data science): https://github.com/RMI-PACTA/workflow.template.pacta
I made both of these template repos with little to NO input from anyone, and they include all of my bull-headed assumptions.
It would be cool to align and document our ideas of useful practices for either type of repo
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.
Assessment
This issue has not been assessed yet.