Kubeflow User Group Contributor Role for Kubeflow 1.5 Release

[jbottum]

Kubeflow User Group Contributor Role for the Kubeflow 1.5 Release

Goals: The goals of the Kubeflow User Group Contributor position(s) are:

• The User Group Contributor is a short term position (~12-17 weeks), which allows Kubeflow users to provide input and important contributions to the next Kubeflow Release.
• The User Group Contributors will help the Working Groups by providing a user’s perspective to the upcoming software deliveries and documentation.
• The Community would like to have at least (1) User Group Contributor for each Kubeflow Working Group.

Responsibilities: Kubeflow User Group Contributors will have the following responsibilities:

• Identify a Working Group that they would like to support for the next release
• Make reasonable efforts to attend and/or listen to the Working Group meetings
• Help in the design, testing and documentation of at least (1) Pull Request for the upcoming release
• Provide a short update to the Community on the PR that they supported

Prerequisites: The following is a list of prerequisites for User Group Contributors:

• Have working knowledge of Kubeflow, Kubernetes and GitHub
• Willingness to collaborate with others
• Have capabilities and infrastructure to conduct a unit test on a new Kubeflow feature

Sign-up process: To sign-up as a Kubeflow User Group Contributor, please follow this process:

Overview - Create a GitHub Issue in the appropriate Working Group Repo requesting that you would like to be a contributor.

Details - Where you should open your issue and what should be included:

1. Pick a Working Group Repo

• Training-operator is in https://github.com/kubeflow/training-operator
• Pipelines is in https://github.com/kubeflow/pipelines
• Hyperparameter Tuning / AutoML is in https://github.com/kubeflow/katib
• Kfserve is in https://github.com/kserve/kserve
• Notebooks, Manitests, Central Dashboard, and Webapps (Tensorboard, Volume Manager) are in https://github.com/kubeflow/kubeflow

2. Create a Title for your GitHub issue (submission request)

• Example : Request to be User Group Contributor for Kubeflow 1.5 for the Notebooks Work Group

3. Add content to your request

• Include a few sentences on your background and ability to satisfy the prerequisites
• If you have a PR that you would like to work on, please include it.

4. Alert the Working Group leads of your issue / submission: @kubeflow/wg-automl-leads @kubeflow/wg-notebooks-leads @kubeflow/wg-pipeline-leads @kubeflow/wg-manifests-leads

5. Submit Issue and request review and approvals /lgtm from approvers

6. Attend the next Working Group Meeting and request that your issue be approved

Important - Approval Process

1. Kubeflow User Group Contributors submissions must be reviewed and approved by the Working Group leads within two weeks of submission.
2. Although submission does not guarantee acceptance, it is expected that the vast majority of qualified submissions will be approved.
3. If the Working Group rejects the submission, they should provide a reason and/or an alternative, especially if the proposed PR does not fit into the 1.5 plan.

[jbottum]

All - The above outlines the proposed Kubeflow User Group Contributors Role for Kubeflow 1.5. I think this will help to set expectations for the User contributors and of the Working Groups. I expect it will help us to grow our community of contributors i.e. 4-5 user contributors per release.

It would be great to get feedback/approval on this process from the Working Group Leads. Thanks.

@kubeflow/wg-automl-leadsm @kubeflow/wg-manifests-leads @kubeflow/wg-notebooks-leads @kubeflow/wg-training-leads @kubeflow/wg-pipeline-leads @theadactyl

[james-jwu]

Thanks Josh for the proposal. Is there a limit on size of KF User Group per Working Group?

[jbottum]

@james-jwu Currently, there is not a pre-defined limit. The Leads of each Working Group will accept User Group Contributor Role submissions, so each Working Group Leads will decide how many. I think 1-2 contributors per WG would be success.

[thesuperzapper]

I think this idea is great (getting users more directly involved in owning new features of components they use).

I think that changing the name to "User Feature Sponsor" would help clarify the purpose of this role, that is, to sponsor a specific feature/change for one of the components.

This change would clarify that the role is for a specific feature and (in my mind) people who become "User Feature Sponsors" would act sort of like "product managers" for the feature they are "sponsoring".

[theadactyl]

I think that changing the name to "User Feature Sponsor" would help clarify the purpose of this role, that is, to sponsor a specific feature/change for one of the components.

I like this idea. I'm also wondering how we can simplify this to reduce overhead, or try it as a more informal pilot before adopting a lot of formal structure. WDYT @jbottum

[jbottum]

@theadactyl I propose that the Kubeflow Community will become stronger as we increase user contributions. From the Release Handbook implementation, we have seen that defining process, roles and responsibilities has improved the Community's quality and deliveries. It helps set expectations. I think:

• that user contribute so that their ideas are implemented.
• being specific (at least one contributor with one PR, for one release with each Working Group) helps to set expectations that can be delivered upon.
• that having a process / title for an ephemeral position enables contributors to report & validate their investment (to their management, the industry and themselves).
• that the process should enable the WG to select which projects should be worked on and who/how contributors can help.

This is a program designed for Kubeflow 1.5 that can be extended or disbanded as the WG determine.

[anencore94]

Is this program fixed ?

[jbottum]

@anencore94 This program is being used informally by a few contributors to the AutoML/Katib WG. These folks raised their hands and said they wanted to help. They had a PR they wanted to write/merge. Are you interested in contributing ? Do you have a specific issue that you would like to work on ?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.