[feature] Should we move components to a new repository?

[diegolovison]

Feature Area

/area components

What feature would you like to see?

The overall idea of this issue is to discuss the pros and cons of keeping https://github.com/kubeflow/pipelines/tree/master/components inside kubeflow/pipelines or moving to a new repository.

We are expecting each company RH/Google/others to explain their opinions to have a final agreement.

[HumairAK]

Today's KFP call, @chensun et al preferred to keep the components folder around.

I would like to see us take a more aggressive stance on removing unmaintained components. IMO we should identify components that are:

1. Very old
2. Unmaintained

And just remove these from the repo. Keeping them around adds tech debt that we do not have the bandwidth to maintain today. I suggest removing the following folders in https://github.com/kubeflow/pipelines/tree/master/components:

• ibm-components
  • this is empty
• azure
  • has not been updated in 3 years
• great-expectations/validate
  • has not been updated in 3 years
• local
  • has not been updated in 3 years

I'm not sure what the intention of contrib folder was, but it also has not been touched in a long time, and we should consider moving it. My preference is to simply remove these folders and not put them in any sort of archived type folder.

[diegolovison]

@chensun no updates from your side. I think it is fine and we can start by removing.