From 95ddb6c1694f22a43b53a458b8469cf08c3b59fe Mon Sep 17 00:00:00 2001 From: Avinesh Tripathi <73980067+AvineshTripathi@users.noreply.github.com> Date: Fri, 19 Aug 2022 20:56:58 +0530 Subject: Create Events.md --- .../marketing-team/role-handbooks/Events.md | 42 ++++++++++++++++++++++ 1 file changed, 42 insertions(+) create mode 100644 communication/marketing-team/role-handbooks/Events.md diff --git a/communication/marketing-team/role-handbooks/Events.md b/communication/marketing-team/role-handbooks/Events.md new file mode 100644 index 00000000..b7560501 --- /dev/null +++ b/communication/marketing-team/role-handbooks/Events.md @@ -0,0 +1,42 @@ +# Event Co-ordinator Role Handbook + +## Overview + +As Event Co-ordinator Lead, you are responsible for +- connecting with organizers of contributor events such as the monthly community meeting or contributor summits +- working with the Contributor Comms team to ensure communications about events are being created and promoted through various means including email (k-dev), slack (slack bot, etc), twitter (K8sContributors), etc. + +Time Commitment: + +1-3 hours a week from 0-1.5 months in +2-5 hours a week from 1.5 months-to event + +## Minimum skills and Requirements + +- Kubernetes github org [membership](https://github.com/kubernetes/community/blob/master/community-membership.md) +- familiarity with the workflow of [#sig-contributor-comms](https://github.com/kubernetes/community/tree/master/communication/marketing-team) +- has understanding of the [social guidlines](https://github.com/kubernetes/community/blob/master/communication/marketing-team/storytelling-resources/social-guidelines.md) +- Good grasp on general marketing activities surrounding events +- Understanding of common forms of marketing communications +- Event planning experience is a plus +- Willing and able to directly coordinate across timezones and contributor groups +- commitement for the role is relative and would vary depending upon events + +## Expectations and tasjs + +The core task for the role would be to stay current on [upcoming]() events. Planning should be done with the team about the event, target audience, mode of communication, timeline, etc. This could be coordinated via a call or async conversatios. Sometimes, some big events might require you to join a weekly or bi-weekly call. The following are the possible tasks to perform (may vary depending upon the event). + +- Creating a communication schedule - what, when, how, who +- Promoting on different platforms like + - emailing on [kdev](https://github.com/kubernetes/community/blob/master/communication/mailing-list-guidelines.md) + - twitting from main or k8scontributor accounts + - coordinating with CNCF(if required) + - sending slack notification to various channels(depending on the target audience) +- Assisting in the entire blog process +- Coordinating with Contributor Comms team members to ensure above tasks are completed + +Timeline for the communication can be crucial parameters so ideally timelines should at least begin to be decided weeks before the event. + +## Shadowing the Event Coordinator Role + +This role can include one or more shadows. The Event Coordinator Lead can delegate/assign tasks to the shadows. The expectation from a shadow is to work with the lead to develop a plan to adopt ownership of the role over time, including all tasks listed in the "Expectations and Tasks" section. The shadows to the Event Coordinator Lead are responsible for handling all Event Coordinator lead related activities in the absence of the Lead. -- cgit v1.2.3 From 38c1e81aa4d5404ab3389ef54c77642ca84c1166 Mon Sep 17 00:00:00 2001 From: Avinesh Tripathi <73980067+AvineshTripathi@users.noreply.github.com> Date: Sat, 8 Oct 2022 01:05:49 +0530 Subject: Update and rename Events.md to Comms-Events.md --- .../marketing-team/role-handbooks/Comms-Events.md | 42 ++++++++++++++++++++++ .../marketing-team/role-handbooks/Events.md | 42 ---------------------- 2 files changed, 42 insertions(+), 42 deletions(-) create mode 100644 communication/marketing-team/role-handbooks/Comms-Events.md delete mode 100644 communication/marketing-team/role-handbooks/Events.md diff --git a/communication/marketing-team/role-handbooks/Comms-Events.md b/communication/marketing-team/role-handbooks/Comms-Events.md new file mode 100644 index 00000000..f11f3c23 --- /dev/null +++ b/communication/marketing-team/role-handbooks/Comms-Events.md @@ -0,0 +1,42 @@ +# Comms Events Lead Role Handbook + +## Overview + +As Event Co-ordinator Lead, you are responsible for +- connecting with organizers of contributor events such as the monthly community meeting or contributor summits +- working with the Contributor Comms team to ensure communications about events are being created and promoted through various means including email (k-dev), slack (slack bot, etc), twitter (K8sContributors), etc. + +Time Commitment: + +1-3 hours a week from 0-1.5 months in +2-5 hours a week from 1.5 months-to event + +## Minimum skills and Requirements + +- Kubernetes github org [membership](https://github.com/kubernetes/community/blob/master/community-membership.md) +- familiarity with the workflow of [#sig-contributor-comms](https://github.com/kubernetes/community/tree/master/communication/marketing-team) +- has understanding of the [social guidlines](https://github.com/kubernetes/community/blob/master/communication/marketing-team/storytelling-resources/social-guidelines.md) +- Good grasp on general marketing activities surrounding events +- Understanding of common forms of marketing communications +- Event planning experience is a plus +- Willing and able to directly coordinate across timezones and contributor groups +- commitement for the role is relative and would vary depending upon events + +## Expectations and tasjs + +The core task for the role would be to stay current on [upcoming](https://www.kubernetes.dev/events/) events. Planning should be done with the team about the event, target audience, mode of communication, timeline, etc. This could be coordinated via a call or async conversatios. Sometimes, some big events might require you to join a weekly or bi-weekly call. The following are the possible tasks to perform (may vary depending upon the event). + +- Creating a communication schedule - what, when, how, who +- Promoting on different platforms like + - emailing on [kdev](https://github.com/kubernetes/community/blob/master/communication/mailing-list-guidelines.md) + - twitting from main or k8scontributor accounts + - coordinating with CNCF(if required) + - sending slack notification to various channels(depending on the target audience) +- Assisting in the entire blog process +- Coordinating with Contributor Comms team members to ensure above tasks are completed + +Timeline for the communication can be crucial parameters so ideally timelines should at least begin to be decided weeks before the event. + +## Shadowing the Event Coordinator Role + +This role can include one or more shadows. The Event Coordinator Lead can delegate/assign tasks to the shadows. The expectation from a shadow is to work with the lead to develop a plan to adopt ownership of the role over time, including all tasks listed in the "Expectations and Tasks" section. The shadows to the Event Coordinator Lead are responsible for handling all Event Coordinator lead related activities in the absence of the Lead. diff --git a/communication/marketing-team/role-handbooks/Events.md b/communication/marketing-team/role-handbooks/Events.md deleted file mode 100644 index b7560501..00000000 --- a/communication/marketing-team/role-handbooks/Events.md +++ /dev/null @@ -1,42 +0,0 @@ -# Event Co-ordinator Role Handbook - -## Overview - -As Event Co-ordinator Lead, you are responsible for -- connecting with organizers of contributor events such as the monthly community meeting or contributor summits -- working with the Contributor Comms team to ensure communications about events are being created and promoted through various means including email (k-dev), slack (slack bot, etc), twitter (K8sContributors), etc. - -Time Commitment: - -1-3 hours a week from 0-1.5 months in -2-5 hours a week from 1.5 months-to event - -## Minimum skills and Requirements - -- Kubernetes github org [membership](https://github.com/kubernetes/community/blob/master/community-membership.md) -- familiarity with the workflow of [#sig-contributor-comms](https://github.com/kubernetes/community/tree/master/communication/marketing-team) -- has understanding of the [social guidlines](https://github.com/kubernetes/community/blob/master/communication/marketing-team/storytelling-resources/social-guidelines.md) -- Good grasp on general marketing activities surrounding events -- Understanding of common forms of marketing communications -- Event planning experience is a plus -- Willing and able to directly coordinate across timezones and contributor groups -- commitement for the role is relative and would vary depending upon events - -## Expectations and tasjs - -The core task for the role would be to stay current on [upcoming]() events. Planning should be done with the team about the event, target audience, mode of communication, timeline, etc. This could be coordinated via a call or async conversatios. Sometimes, some big events might require you to join a weekly or bi-weekly call. The following are the possible tasks to perform (may vary depending upon the event). - -- Creating a communication schedule - what, when, how, who -- Promoting on different platforms like - - emailing on [kdev](https://github.com/kubernetes/community/blob/master/communication/mailing-list-guidelines.md) - - twitting from main or k8scontributor accounts - - coordinating with CNCF(if required) - - sending slack notification to various channels(depending on the target audience) -- Assisting in the entire blog process -- Coordinating with Contributor Comms team members to ensure above tasks are completed - -Timeline for the communication can be crucial parameters so ideally timelines should at least begin to be decided weeks before the event. - -## Shadowing the Event Coordinator Role - -This role can include one or more shadows. The Event Coordinator Lead can delegate/assign tasks to the shadows. The expectation from a shadow is to work with the lead to develop a plan to adopt ownership of the role over time, including all tasks listed in the "Expectations and Tasks" section. The shadows to the Event Coordinator Lead are responsible for handling all Event Coordinator lead related activities in the absence of the Lead. -- cgit v1.2.3 From 52b7a2e29444836d52c10b7e61f58d676873d7b0 Mon Sep 17 00:00:00 2001 From: AvineshTripathi Date: Wed, 23 Nov 2022 13:46:26 +0530 Subject: rename file path --- .../role-handbooks/Comms-Events.md | 42 ++++++++++++++++++++++ .../marketing-team/role-handbooks/Comms-Events.md | 42 ---------------------- 2 files changed, 42 insertions(+), 42 deletions(-) create mode 100644 communication/contributor-comms/role-handbooks/Comms-Events.md delete mode 100644 communication/marketing-team/role-handbooks/Comms-Events.md diff --git a/communication/contributor-comms/role-handbooks/Comms-Events.md b/communication/contributor-comms/role-handbooks/Comms-Events.md new file mode 100644 index 00000000..f11f3c23 --- /dev/null +++ b/communication/contributor-comms/role-handbooks/Comms-Events.md @@ -0,0 +1,42 @@ +# Comms Events Lead Role Handbook + +## Overview + +As Event Co-ordinator Lead, you are responsible for +- connecting with organizers of contributor events such as the monthly community meeting or contributor summits +- working with the Contributor Comms team to ensure communications about events are being created and promoted through various means including email (k-dev), slack (slack bot, etc), twitter (K8sContributors), etc. + +Time Commitment: + +1-3 hours a week from 0-1.5 months in +2-5 hours a week from 1.5 months-to event + +## Minimum skills and Requirements + +- Kubernetes github org [membership](https://github.com/kubernetes/community/blob/master/community-membership.md) +- familiarity with the workflow of [#sig-contributor-comms](https://github.com/kubernetes/community/tree/master/communication/marketing-team) +- has understanding of the [social guidlines](https://github.com/kubernetes/community/blob/master/communication/marketing-team/storytelling-resources/social-guidelines.md) +- Good grasp on general marketing activities surrounding events +- Understanding of common forms of marketing communications +- Event planning experience is a plus +- Willing and able to directly coordinate across timezones and contributor groups +- commitement for the role is relative and would vary depending upon events + +## Expectations and tasjs + +The core task for the role would be to stay current on [upcoming](https://www.kubernetes.dev/events/) events. Planning should be done with the team about the event, target audience, mode of communication, timeline, etc. This could be coordinated via a call or async conversatios. Sometimes, some big events might require you to join a weekly or bi-weekly call. The following are the possible tasks to perform (may vary depending upon the event). + +- Creating a communication schedule - what, when, how, who +- Promoting on different platforms like + - emailing on [kdev](https://github.com/kubernetes/community/blob/master/communication/mailing-list-guidelines.md) + - twitting from main or k8scontributor accounts + - coordinating with CNCF(if required) + - sending slack notification to various channels(depending on the target audience) +- Assisting in the entire blog process +- Coordinating with Contributor Comms team members to ensure above tasks are completed + +Timeline for the communication can be crucial parameters so ideally timelines should at least begin to be decided weeks before the event. + +## Shadowing the Event Coordinator Role + +This role can include one or more shadows. The Event Coordinator Lead can delegate/assign tasks to the shadows. The expectation from a shadow is to work with the lead to develop a plan to adopt ownership of the role over time, including all tasks listed in the "Expectations and Tasks" section. The shadows to the Event Coordinator Lead are responsible for handling all Event Coordinator lead related activities in the absence of the Lead. diff --git a/communication/marketing-team/role-handbooks/Comms-Events.md b/communication/marketing-team/role-handbooks/Comms-Events.md deleted file mode 100644 index f11f3c23..00000000 --- a/communication/marketing-team/role-handbooks/Comms-Events.md +++ /dev/null @@ -1,42 +0,0 @@ -# Comms Events Lead Role Handbook - -## Overview - -As Event Co-ordinator Lead, you are responsible for -- connecting with organizers of contributor events such as the monthly community meeting or contributor summits -- working with the Contributor Comms team to ensure communications about events are being created and promoted through various means including email (k-dev), slack (slack bot, etc), twitter (K8sContributors), etc. - -Time Commitment: - -1-3 hours a week from 0-1.5 months in -2-5 hours a week from 1.5 months-to event - -## Minimum skills and Requirements - -- Kubernetes github org [membership](https://github.com/kubernetes/community/blob/master/community-membership.md) -- familiarity with the workflow of [#sig-contributor-comms](https://github.com/kubernetes/community/tree/master/communication/marketing-team) -- has understanding of the [social guidlines](https://github.com/kubernetes/community/blob/master/communication/marketing-team/storytelling-resources/social-guidelines.md) -- Good grasp on general marketing activities surrounding events -- Understanding of common forms of marketing communications -- Event planning experience is a plus -- Willing and able to directly coordinate across timezones and contributor groups -- commitement for the role is relative and would vary depending upon events - -## Expectations and tasjs - -The core task for the role would be to stay current on [upcoming](https://www.kubernetes.dev/events/) events. Planning should be done with the team about the event, target audience, mode of communication, timeline, etc. This could be coordinated via a call or async conversatios. Sometimes, some big events might require you to join a weekly or bi-weekly call. The following are the possible tasks to perform (may vary depending upon the event). - -- Creating a communication schedule - what, when, how, who -- Promoting on different platforms like - - emailing on [kdev](https://github.com/kubernetes/community/blob/master/communication/mailing-list-guidelines.md) - - twitting from main or k8scontributor accounts - - coordinating with CNCF(if required) - - sending slack notification to various channels(depending on the target audience) -- Assisting in the entire blog process -- Coordinating with Contributor Comms team members to ensure above tasks are completed - -Timeline for the communication can be crucial parameters so ideally timelines should at least begin to be decided weeks before the event. - -## Shadowing the Event Coordinator Role - -This role can include one or more shadows. The Event Coordinator Lead can delegate/assign tasks to the shadows. The expectation from a shadow is to work with the lead to develop a plan to adopt ownership of the role over time, including all tasks listed in the "Expectations and Tasks" section. The shadows to the Event Coordinator Lead are responsible for handling all Event Coordinator lead related activities in the absence of the Lead. -- cgit v1.2.3