-
Notifications
You must be signed in to change notification settings - Fork 144
WG sponsorship for fairing #526
Comments
Issue-Label Bot is automatically applying the labels:
Please mark this comment with 👍 or 👎 to give our bot feedback! |
Issue Label Bot is not confident enough to auto-label this issue. |
Issue-Label Bot is automatically applying the labels:
Please mark this comment with 👍 or 👎 to give our bot feedback! |
1 similar comment
Issue-Label Bot is automatically applying the labels:
Please mark this comment with 👍 or 👎 to give our bot feedback! |
I’m happy to take ownership for this @jlewi |
@jinchihe your already an OWNER of fairing at least in my eyes.
+1 I think there's been discussion of a datascientist experience WG centered around notebooks; see kubeflow/community#379 I think @kimwnasptd, @StefanoFioravanzo, and @yanniszark have indicated they are interested in being part of such a WG. How do you feel about including fairing in that WG? Another possibility is that fairing has a lot of functionality similar to the KFP SDK/CLI e.g. the ability to fire of container builds. So if we wanted to try to merge/dedupe some of that functionality that might be another option. |
/cc @kubeflow/project-steering-group |
also |
@Bobgy We do not want to archive this since still some users. |
Send a PR for this: kubeflow/community#470 |
/kind process
Per the governance discussions. All projects need to find WG sponsorship or they will eventually be archived.
Opening this issue to begin discussions about what to do about fairing
/cc @jinchihe @animeshsingh
The text was updated successfully, but these errors were encountered: