Revise Comms template

With a focus on ease of use and clarity around communication timeline. Also, we self-market ourselves, because we definitely should do that.

Signed-off-by: Matthew Broberg <matt@opensource.com>

.github/ISSUE_TEMPLATE/marketing-request.md

@@ -5,52 +5,23 @@ title: 'REQUEST: New communication about <topic>'
 labels: area/contributor-comms, sig/contributor-experience
 assignees: 
 ---
-<!--
-ATTENTION: the Upstream Marketing Team have classifications on how urgent and important a message to the community is outlined here: https://git.k8s.io/community/communication/marketing-team/multichannel-communications.md#mapping-type-to-tier
 
-Filling out this form to the best of your ability will speed up the team's ability to get the word out! 
--->
+**What do you want send out?** (Please include a link to a draft)
+<!-- Gists, Hackmd.io, or Google Doc preferred. Include any artwork, pics, diagrams, or any other assets with public links. 
 
-**What do you want send out?** 
-<!-- Include logos, artwork, pics, diagrams, or any other assets with public links whenever possible. -->
+We use a combination of mailing lists, Slack messages, and Twitter to get the word out. (Click the links below for more details.) -->
 
 
-**What’s the intended outcome?**
-<!-- Are you looking for people to get involved? Fill out a survey? See something of interest to them? Let us know why you care to share. -->
+- [] I agree that if this is urgent, I will @contributor-comms in #sig-contribex Slack.
+<!-- The team looks at these at least once a week during its meeting, but we're happy to help when a message is urgent. -->
 
 
-**What is the sponsoring SIG or community group?**
-<!-- What SIG or group is this message on behalf of? What is the best way to contact them? -->
+<!-- Want to learn more about Contributor Comms? 
 
-**Is this time-sensitive?** 
-<!-- You can delete or skip this if it's not relevant. -->
+We started the Upstream Marketing Team to focus on contributor-to-contributor communication throughout Kubernetes.
 
-- [ ] Yes, it is **due by** <$DATE> <$TIME>
-- [ ] Yes, it **must be sent** <$DATE> <$TIME>
-- [ ] No, but I'd prefer <$DATE> <$TIME>
+Read about our charter here: https://github.com/kubernetes/community/blob/master/communication/marketing-team/CHARTER.md
 
-**Where do you want it to be visible?**
-<!-- Note that email via our mailing list is the default choice for all messages. See our
-multichannel communication strategy for more details. Note that blogs and social
-media must meet our guidelines.
+Or about the team: https://github.com/kubernetes/community/blob/master/communication/marketing-team
 
-Multichannel communication strategy: http://git.k8s.io/community/communication/marketing-team/multichannel-communications.md#mapping-type-to-tier
-
-Blog and Social Media Guidelines: https://git.k8s.io/community/communication/marketing-team#purpose -->
-
-- [ ] Everywhere 🌍
-- [ ] Email (kubernetes-dev@googlegroups.com)
-- [ ] Blog post (with help from a [Storyteller](https://github.com/kubernetes/community/tree/master/communication/marketing-team#purpose))
-- [ ] Twitter (via [@k8scontributors](https://twitter.com/k8scontributors))
-- [ ] YouTube ([Kubernetes](https://www.youtube.com/channel/UCZ2bu0qutTOM0tHYa_jkIwg))
-- [ ] Slack (assumes `#kubernetes-dev` unless otherwise mentioned)
-- [ ] Contributor Calendar event entry (available [here](https://calendar.google.com/calendar/embed?src=calendar%40kubernetes.io))
-- [ ] Other (fill this out)
-
-**Where is your first draft available?**
-<!-- Please provide a first draft of your message for all channels requested. Take your best shot and we are here to support you through getting it ready for publication (it's appreciated). Links to Google Docs or Hackmd.io pages are best for easy editing.
-
-Also, include any social media tags of relevant people (e.g. Twitter handles of people you want to give a shout out on Twitter)-->
-
-**Lastly, who's the best point of contact?** 
-<!-- If you are the point of contact, please confirm it's you. Please include both GitHub username and Slack username. -->
+And thanks for reaching out! We're here to help. -->