-
Notifications
You must be signed in to change notification settings - Fork 49
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
Identify upstream/pipelines issues to work on #423
Comments
Would suggest adding this task to the list: |
I know I am not from RedHat, but I would like to highlight kubeflow/pipelines#10309 As support for ARM64 in KFP would be great. |
@thesuperzapper Thank you for your issue! I'll work with the team to see how can we contribute with that. |
Hi @HumairAK as of issue [feature] Add deletePipelineByName endpoint #7334 - I have created this issue, but it was put in a lower priority with the pipeline v2 implementation. So, if this issue is still wanted I could help implement it. |
Hey @difince apologies for the delayed response, holidays and all. It is certainly a useful feature, I wouldn't say it's a high priority task for us just yet compared to some of the other issues listed. Iirc I added it here since it had the help wanted label and thought it was a potential good first issue candidate. If there is upstream interest and you would like to tackle it, please feel free! |
Migrated to Jira: https://issues.redhat.com/browse/RHOAIENG-1679 |
Re-opening this issue, it gives transparency to the community where we are interested in contributing, whilst also allowing folks from the community to provide suggestions. |
Acceptance criteria:
Identify at a minimum 4 issues that the dsp team can work on. Issues should have interest from upstream community, and add strategic value to dsp.
The text was updated successfully, but these errors were encountered: