diff options
| author | Jorge O. Castro <jorge.castro@gmail.com> | 2018-12-14 08:12:19 -0800 |
|---|---|---|
| committer | Jorge O. Castro <jorge.castro@gmail.com> | 2018-12-14 08:12:19 -0800 |
| commit | 8dad47b371e696e53f65861f2ae509d71e293d4a (patch) | |
| tree | db099726247c8caa5af7303e85d49d90f7d8c9ef | |
| parent | 8a3e543bad64d53e45274d286c2a3f1101e646c9 (diff) | |
Update my email address
| -rw-r--r-- | communication/moderation.md | 2 | ||||
| -rw-r--r-- | sig-governance.md | 4 |
2 files changed, 3 insertions, 3 deletions
diff --git a/communication/moderation.md b/communication/moderation.md index 3a8d688e..daf030fe 100644 --- a/communication/moderation.md +++ b/communication/moderation.md @@ -44,7 +44,7 @@ These guidelines are for tool-specific policies that don't fit under a general u ### Moderating a SIG/WG list -- SIG and Working Group mailing list should have parispittman@google.com and jorge@heptio.com as a coowner so that administrative functions can be managed centrally across the project. +- SIG and Working Group mailing list should have parispittman@google.com and jorgec@vmware.com as a coowner so that administrative functions can be managed centrally across the project. - Moderation of the SIG/WG lists is up to that individual SIG/WG, these admins are there to help facilitate leadership changes, reset lost passwords, etc. - Users who are violating the Code of Conduct or other negative activities (like spamming) should be moderated. diff --git a/sig-governance.md b/sig-governance.md index 8a80302a..39779146 100644 --- a/sig-governance.md +++ b/sig-governance.md @@ -35,7 +35,7 @@ Guidelines for drafting a SIG Charter can be found [here](/committee-steering/go * Ask a repo maintainer to create a github label, if one doesn't already exist: sig/foo * Request a new [kubernetes.slack.com](http://kubernetes.slack.com) channel (#sig-foo) from [@parispittman](https://github.com/parispittman) or [@castrojo](https://github.com/castrojo). New users can join at [slack.kubernetes.io](http://slack.kubernetes.io). * Organize video meetings as needed. No need to wait for the [Weekly Community Video Conference](community/README.md) to discuss. Please report summary of SIG activities there. - * Request a Zoom account by emailing Paris Pittman(`parispittman@google.com`) and Jorge Castro(`jorge@heptio.com`). You must set up a google group (see below) for the SIG leads so that all the SIG leads have the ability to reset the password if necessary. + * Request a Zoom account by emailing Paris Pittman(`parispittman@google.com`) and Jorge Castro(`jorgec@vmware.com`). You must set up a google group (see below) for the SIG leads so that all the SIG leads have the ability to reset the password if necessary. * Read [how to use YouTube](/communication/K8sYoutubeCollaboration.md) for publishing your videos to the Kubernetes channel. * Calendars 1. Create a calendar on your own account. Make it public. @@ -110,4 +110,4 @@ The process for closing a SIG/WG is as follows: - Migrate/Remove/Deprecate any SIG/WG labels in [labels.yaml](https://git.k8s.io/test-infra/label_sync/labels.yaml) - Ensure that the YouTube Collaboration links are removed - Remove SIG Calendar and events from the community calendar -- Update `sigs.yaml` to reflect the removal of the SIG/WG
\ No newline at end of file +- Update `sigs.yaml` to reflect the removal of the SIG/WG |