community
community copied to clipboard
Create Comms-Events.md
Creating a Event coordinator role handbook
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: AvineshTripathi
Once this PR has been reviewed and has the lgtm label, please assign kaslin for approval by writing /assign @kaslin in a comment. For more information see:The Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
Thanks for your suggestions, @jberkus! I added my perspectives on them. We'll discuss the point on external events at our upcoming meeting.
Update name to Comms Event Lead or something like that to differentiate from other roles in ContribEx.
Ping! This PR needs an updated name (something like "Comms Event Lead") and Josh had some comments, particularly around shadowing.
@kaslin sorry for the delay and I have done the necessary changes let me know if we need something else
Shadows section could maybe still use some fleshing out, but let's sort that out as we go. /lgtm /approve
oh yeah I don't have approver in community anyway. @jberkus
I think we need to build out the shadow role a bit more but this is a good start.
/lgtm
/approve
ohhh this is still under marketing-team! Needs rebase.
/retest
/retest
/lgtm /approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: AvineshTripathi, chris-short, jberkus, kaslin
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~communication/contributor-comms/OWNERS~~ [jberkus,kaslin]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment