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

Should the "workshop" folder be put in the Digipower GitHub organization? #8

Open
Amustache opened this issue Jul 27, 2022 · 1 comment

Comments

@Amustache
Copy link
Contributor

Amustache commented Jul 27, 2022

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

cc. @alexbfree @foucault-dumas

@alexbfree
Copy link
Contributor

possibly might make sense to move it over to the digipower academy org, yes. @foucault-dumas do you have a view?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants