-
Notifications
You must be signed in to change notification settings - Fork 89
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
Determine demotion process of dataset contributions #582
Comments
My suggestion for demoting datasets is as follows: Demotion process of datasetsWe should consider demoting a dataset from a “regular” contribution back to the experimental contribution space when:
The Kedro team should consider regular datasets as our responsibility just as the majority of the Kedro codebase, and demoting a dataset shouldn't be done lightly as it basically means discontinuing formal support. |
It's brilliant that you're thinking of this! |
Just throwing it out there—is it possible primary maintainer leaves, and there isn't anybody on the TSC who wants to commit to maintaining it? Or we just force it upon somebody/collective responsibility at that point? :) |
I wonder what the order of steps should be. So, for example, we can mark those datasets as candidates for moving to "experimental" in release X.X.X and give some time for contributors to update and move them in case no changes were made. Alternatively, we can move those datasets in the following release and expect them to follow "graduation rules" to be moved back to "regular". |
Closing this in favour of continuing the discussion in #583 Bottom line is that the following make up the demotion process:
|
Description
Datasets within the regular
kedro_datasets
contributions folder may deterioriate and get outdated over time. We might then need to decide to demote these datasets back to the experimental contributions space.We need to establish clear criteria and guidelines for determining when a regular contribution needs to be demoted.
Task
The text was updated successfully, but these errors were encountered: