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 interesting logical map. I am curious to see what we can derive from it : ) My comments: - All of the factors that contribute to project transparency, when put together, add up to increased use of Beam, but I feel like 'increased knowledge of how to use beam' is the single largest contributor to that. Is 'knowing how to use' completely captured by transparency? (I can try to rephrase what I mean...) - I'm sure you've considered this, as you've received the feedback; but not all of these channels are 'owned' by Beam. Some of these are 'independently organized'. It may help to mark them as such. - From the Artifacts section, Blog appears twice, while other artifacts appear only once with multiple arrows pointing at them (e.g. tech talks). Maybe this is on purpose, but just checking. Thanks! -P. On Fri, Dec 6, 2019 at 5:12 PM María Cruz <macruz...@gmail.com> wrote: > 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 causes and effects leading to an > outcome of interest [1]. The goal of making this graphic is to identify how > Apache Beam's channels and content work towards project goals. > > The logic model graphic is attached and has also been uploaded [2] to the > repo I've been working on. I also added it to comms-strategy-DRAFT.md [3]. > If you have any questions or comments about this graphic, please add them > here [4]. > > Step 3 in this process includes describing areas where we can be more > strategic about the content we produce for Apache Beam. I would like to > deliver this by December 17. > > Looking forward to your comments and feedback! > > Thanks, > > María > > > [1] https://en.wikipedia.org/wiki/Logic_model > [2] https://github.com/macruzbar/beam/blob/master/comms-logic-model.svg > [3] > https://github.com/macruzbar/beam/blob/master/Communication-strategy-DRAFT.md > [4] https://github.com/macruzbar/beam/issues/4 > > On Wed, Oct 9, 2019 at 7:09 PM Thomas Weise <t...@apache.org> wrote: > >> 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 Robert Bradshaw <rober...@google.com> >> wrote: >> >>> Probably worth mentioning Slack and StackOverflow as well. >>> >>> On Wed, Oct 9, 2019 at 3:59 PM María Cruz <macruz...@gmail.com> 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 strategy draft. To start, I did a map of >>> Beam channels and content, and I have some questions for you: >>> https://github.com/macruzbar/beam/blob/master/Communication-strategy-DRAFT.md >>> > >>> > In order to create these files, I forked the repo. Once this looks >>> good, and if everyone agrees, we can merge the changes to apache/beam. >>> > >>> > I didn't assign reviewers for this file because I don't know if there >>> is someone who usually looks at these kinds of documents. So everyone: >>> please feel free to pitch in! I will give this a week for comments. >>> > >>> > Looking forward to your comments! >>> > >>> > María >>> >>
