You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: This is a reflexion that is directly linked to #7.
The thing is that this is a folder containing specific, customised instructions used during workshops, whereas the data-catalog is more for general instructions (and models).
One solution would be to move the workshop folder into the Digipower organisation, the other solution would be to put them in the corresponding folders (see #5 & #7) along the README.
A first discussion with @alexbfree (question is "How should I handle the workshop folder ?"):
Hmm that is a good question.
I feel like the workshop folder shouldn't be split up. It is stuff collected together that belongs together.
That said, we should also avoid duplication of data and of folder trees.
Maybe the thing to do is if the workshop uses data that could also live elsewhere, then a .md file could link the the data within the normal organised data tree..
Ie the workshop folder "points to" data it uses
The thing is that this is a folder containing specific, customised instructions used during workshops, whereas the data-catalog is more for general instructions (and models).
One solution would be to move the workshop folder into the Digipower organisation, the other solution would be to put them in the corresponding folders (see #5 & #7) along the README.
A first discussion with @alexbfree (question is "How should I handle the workshop folder ?"):
cc. @alexbfree @foucault-dumas
The text was updated successfully, but these errors were encountered: