Skip to content

Add WG liaisons to 1.5 release team #547

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

Conversation

kimwnasptd
Copy link
Member

To further improve the release team's communication effectiveness we will define WG liaisons. We will also be pinging liaisons to ensure WGs end up getting release updates.

This was triggered by kubeflow/manifests#2084 (comment)

We also have a checkbox for picking up liaisons early on in the release, but didn't ensure this was checked https://github.com/kubeflow/community/blob/master/releases/handbook.md#preparation.

Getting better step by step. We will ensure the liaisons are written down early on in the next release

cc @DomFleischmann

Signed-off-by: Kimonas Sotirchos <[email protected]>
@google-oss-prow
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kimwnasptd

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

| Working Group Liaison(s) | |
| Distribution Representative | |

| **Working Group** | **Liaison(s)** (**GitHub / Slack ID**) |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just curious, how were the liaisons selected for this release?

Copy link
Member Author

@kimwnasptd kimwnasptd Jan 3, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I took a quick look at the WG tracking issues of the previous release and included some of the people there. I only added one to not make this list too long, since we will be tagging these people a lot [aside from tagging the WG leads].

https://github.com/orgs/kubeflow/projects/46#column-15489669

@terrytangyuan would you also like to be a liaison for Training?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see. I cannot commit anything this time around. The main reason why I asked is to make sure the people you've included are responsive, especially given the holidays.

@kimwnasptd
Copy link
Member Author

I think this should be ready to merge

/cc @annajung @jbottum

@google-oss-prow google-oss-prow bot requested a review from annajung January 12, 2022 18:31
@annajung
Copy link
Member

lgtm, however can we also get a lgtm from the liaisons to confirm their role as well?

The role of the WG liaison are defined as follows

Person responsible for liaising between the release team and the WG. The will be the main contact point for the Release Team to figure out the progress of the WG as well as required component versions, throughout the release. If a Release Team Member is already part of a WG then they could also serve as the liaison.

cc @andreyvelich @zijianjoy @Jeffwan @Jeffwan @yuzisun

@zijianjoy
Copy link
Contributor

Confirming my liaison for Kubeflow Pipelines.

@stale
Copy link

stale bot commented Apr 17, 2022

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.

@stale stale bot closed this Apr 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants