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

Planning and architecture #1

Open
bertday opened this issue Mar 21, 2023 · 2 comments
Open

Planning and architecture #1

bertday opened this issue Mar 21, 2023 · 2 comments
Labels
documentation Improvements or additions to documentation good first issue Good for newcomers

Comments

@bertday
Copy link
Collaborator

bertday commented Mar 21, 2023

No description provided.

@npappin-wsu npappin-wsu added the documentation Improvements or additions to documentation label Mar 21, 2023
@npappin-wsu
Copy link
Collaborator

As an initial suggestion, I think we should consider using the wiki to keep track of canonical information as an alternative we could use readme files in the appropriate folder, i.e. project should be described in the root readme, data products in a sub folder. As for new data products I think we should add an issue and a folder in the project to contain the specific timeline. I am sure there are other things to add to this.

@npappin-wsu npappin-wsu added the good first issue Good for newcomers label Mar 21, 2023
@npappin-wsu
Copy link
Collaborator

In thinking about this more today, I think that keeping track of problem statements, input data, general processing procedures, and output data and formats in a readme in the folder containing the data pipeline may work best.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants