Hi Matthias,
thank you for the detailed feedback on the comms strategy. I can definitely
help with the Youtube channel revamp and social media copy to promote that
content. I will connect off-list with you about this.
All: given that we are moving forward with this strategy, I created a pull
reque
To make things more concrete, we could start by giving the YouTube channel
more structure & drafting Tweets to go out on the different channels. Is
this something you'd be able to help out with?
Thanks!
Matthias
On Sun, 16 Feb 2020 at 10:29, Matthias Baetens
wrote:
> Hey Maria,
>
> Great work!!
Hey Maria,
Great work!! This provides a nice overview of all the channels and how they
contribute to the overall project.
I will comment on the sections I am most familiar with:
- Website / blog: +1 for reducing the number of outlets to 1. The Beam
Summit website repository could use a clean-up a
Hi Kenn,
We had workshop on this very topic (how to contribute to Beam) at our
Berlin Summit: https://www.youtube.com/watch?v=PtPslSdAPcM There's is
certainly room for me (or anyone) to cleanup and formalize that a bit
more. Though, the views of that are relatively small, which either indeed
poi
Wow, this is great work. I looked at the graphical maps when you sent them
but forgot to reply on thread. They really distill a lot of possibilities
and help to think about the current state.
These three action items seem good and doable. Thanks for highlighting
those. The only one that isn't obvi
Hi everyone,
I'm writing to send an update about the communication strategy for Beam. In
a nutshell, I have 3 proposed changes (copied from the md file here:
https://github.com/macruzbar/beam/blob/master/Communication-strategy-DRAFT.md
).
While all the channels are connected to a specific function
Hi Maria,
thanks for putting this together. It's large, so a bit hard to follow - but
that's probably just an indication of the complexity of Beam's
communication channels.
FWIW, I found that reading from the top down was useful (or rather, from
the top, backwards from the arrows).
It is an intere
Hi everyone,
sorry for the tardiness in responding to this, and thank you to everyone
who shared comments.
I have adjusted the initial graphic, and taken a step further to develop
the Apache Beam Communications Logic Model. This type of visualization is a
hypothesized description of the chain of ca
It probably makes sense to separate official project channels from external
ones like Beam Summit and meetups. Beam Summit is about Beam, but it is
"third party" and not under the project umbrella. Operation of the youtube
channel might also need clarification.
On Wed, Oct 9, 2019 at 4:35 PM Robe
Probably worth mentioning Slack and StackOverflow as well.
On Wed, Oct 9, 2019 at 3:59 PM María Cruz wrote:
>
> Hi all,
> sorry for multiple messages. I realized after sending the first email that a
> new thread with a different subject was probably more efficient.
>
> I created a communication
Hi all,
sorry for multiple messages. I realized after sending the first email that
a new thread with a different subject was probably more efficient.
I created a communication strategy draft. To start, I did a map of Beam
channels and content, and I have some questions for you:
https://github.com/
11 matches
Mail list logo
