StatCan
Create repo for reusable pipeline components
Might make sense for us to curate a small collection of yaml pipelines. Especially ones for loading/unloading from MinIO and such.
CC @ca-scribner
Isn't this what kubeflow-mlops does? It is all reusable plugins for pipelines
Oh fair enough, can just build off that.
I was thinking about these kinds of standalone yaml files example, but can have both
If we're talking about reusable components I'm with @blairdrummond that a specific repo for them is a good idea. Agreed that the kubeflow-mlops repo has things that are reusable, but I don't know if someone would notice our reusable components here (especially if they didn't know what mlops was). I think it would be more approachable if we had a repo for reusable components, and then kubeflow-mlops could pull anything they share from there.
Reusable yaml components specifically (like here or here) that people can directly load_component_from_url(path_to_yaml_in_gh) feel like a great candidate for a repo that has a light readme up front and some categorization
(whether we do this here or in StatCan/kubeflow-mlops#36 doesn't matter to me. They amount to the same task, but feels like it should be actioned in a separate repo)
I find the more repo sprawl we have the more we are apt to let things not be maintained.
10/10 comment from Will about repo sprawl and content maintenance. If we revisit this for Argo components or MLOps then maybe aaw-contrib would be the place to put it?
