In my opinion, the advantage of workflow is that any script can be freely combined.
Now that the freedom of scripts is limited to the project, can you consider letting the project developers decide which scripts can be shared with others’ projects?
01/15/2021, 8:18 AM
The reason for limiting to scripts within the project is that projects are git versioned, meaning that the whole project and all pipeline definitions and code are versioned.
So when someone wants to work on the same project they only have to clone/import your project and they are guaranteed that they have all source code necessary to run your project.
Furthermore when you schedule an experiment (soon to be renamed to jobs) it creates a snapshot of your project (and thus all code) to make sure when you continue editing your project while it’s running, that the code being used for the experiment doesn’t change.
01/15/2021, 1:18 PM
Importing projects as a way to share scripts doesn't solve the problems I mentioned, such as
1. the user may only need one script under one project but must import all the projects
2. What if he needs to use scripts from multiple projects?
My idea is to create a script r*epository concept* named (script hub or script store).
Each developer can upload or download his favorite scripts here.
Do you have any idea?
Looking forward to your reply.
01/15/2021, 3:22 PM
This is a very interesting idea, thanks for clarifying what you have in mind. We’ll use your input when we discuss code sharing/re-use in our next feature review.
I’ll let you know if we have any further questions about it.
(and I’ll update you here on what we come up with to make your use case possible)