Re: [RESULT][VOTE] Accept the Firefly design donation as Beam Mascot - Deadline Mon April 6

[María Cruz]

Hi everyone!
It is amazing to see how this process developed to collaboratively create
Apache Beam's mascot. Thank you to everyone who got involved!
I would like to write a blogpost for the Beam website, and I wanted to ask
you: would anyone like to offer their testimony about the process of
creating the Beam mascot, and what this means to you? Everyone's testimony
is welcome! If you witnessed the development of a mascot for another open
source project, even better =)

Please feel free to express interest on this thread, and I'll reach out to
you off-list.

Thanks,

María

On Fri, Apr 17, 2020 at 6:19 AM Jeff Klukas  wrote:

> I personally like the sound of "Datum" as a name. I also like the idea of
> not assigning them a gender.
>
> As a counterpoint on the naming side, one of the slide decks provided
> while iterating on the design mentions:
>
> > Mascot can change colors when it is “full of data” or has a “batch of
> data” to process.  Yellow is supercharged and ready to process!
>
> Based on that, I'd argue that the mascot maps to the concept of a bundle
> in the beam execution model and we should consider a name that's a play on
> "bundle" or perhaps a play on "checkpoint".
>
> On Thu, Apr 16, 2020 at 3:44 PM Julian Bruno 
> wrote:
>
>> Hi all,
>>
>> While working on the design of our Mascot
>> Some ideas showed up and I wish to share them.
>> In regard to Alex Van Boxel's question about the name of our Mascot.
>>
>> I was thinking about this yesterday night and feel it could be a great
>> idea to name the Mascot "*Data*" or "*Datum*". Both names sound cute and
>> make sense to me. I prefer the later. Datum means a single piece of
>> information. The Mascot is the first piece of information and its job is to
>> collect batches of data and process it. Datum is in charge of linking
>> information together.
>>
>> In addition, our Mascot should have no gender. Rendering it accessible to
>> all users.
>>
>> Beam as a name for the mascot is pretty straight forward but I think
>> there are many things carrying that same name already.
>>
>> What do you think?
>>
>> Looking forward to hearing your feedback. Names are important and I feel
>> it can expand the personality and create a cool background for our Mascot.
>>
>> Cheers!
>>
>> Julian
>>
>> On Mon, Apr 13, 2020, 3:40 PM Kyle Weaver  wrote:
>>
>>> Beam Firefly is fine with me (I guess people tend to forget mascot names
>>> anyway). But if anyone comes up with something particularly cute/clever we
>>> can consider it.
>>>
>>> On Mon, Apr 13, 2020 at 6:33 PM Aizhamal Nurmamat kyzy <
>>> aizha...@apache.org> wrote:
>>>
 @Alex, Beam Firefly?

 On Thu, Apr 9, 2020 at 10:57 PM Alex Van Boxel 
 wrote:

> We forgot something
>
> ...
>
> ...
>
> it/she/he needs a *name*!
>
>
>  _/
> _/ Alex Van Boxel
>
>
> On Fri, Apr 10, 2020 at 6:19 AM Kenneth Knowles 
> wrote:
>
>> Looking forward to the guide. I enjoy doing (bad) drawings as a way
>> to relax. And I want them to be properly on brand :-)
>>
>> Kenn
>>
>> On Thu, Apr 9, 2020 at 10:35 AM Maximilian Michels 
>> wrote:
>>
>>> Awesome. What a milestone! The mascot is a real eye catcher. Thank
>>> you
>>> Julian and Aizhamal for making it happen.
>>>
>>> On 06.04.20 22:05, Aizhamal Nurmamat kyzy wrote:
>>> > I am happy to announce that this vote has passed, with 13
>>> approving +1
>>> > votes, 5 of which are binding PMC votes.
>>> >
>>> > We have the final design for the Beam Firefly! Yahoo!
>>> >
>>> > Everyone have a great week!
>>> >
>>> >
>>> >
>>> > On Mon, Apr 6, 2020 at 9:57 AM David Morávek >> > > wrote:
>>> >
>>> > +1 (non-binding)
>>> >
>>> > On Mon, Apr 6, 2020 at 12:51 PM Reza Rokni >> > > wrote:
>>> >
>>> > +1(non-binding)
>>> >
>>> > On Mon, Apr 6, 2020 at 5:24 PM Alexey Romanenko
>>> > mailto:aromanenko@gmail.com>>
>>> wrote:
>>> >
>>> > +1 (non-binding).
>>> >
>>> > > On 3 Apr 2020, at 14:53, Maximilian Michels
>>> > mailto:m...@apache.org>> wrote:
>>> > >
>>> > > +1 (binding)
>>> > >
>>> > > On 03.04.20 10:33, Jan Lukavský wrote:
>>> > >> +1 (non-binding).
>>> > >>
>>> > >> On 4/2/20 9:24 PM, Austin Bennett wrote:
>>> > >>> +1 (nonbinding)
>>> > >>>
>>> > >>> On Thu, Apr 2, 2020 at 12:10 PM Luke Cwik
>>> > mailto:lc...@google.com>
>>> > >>> >>
>>> wrote:
>>> > >>>
>>> > >>>+1 (binding)
>>> > >>>
>>> > >>>On Thu, Apr 

Re: Please comment on draft comms strategy by Oct 16

[María Cruz]

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
request <https://github.com/apache/beam/pull/10958> to add this work to
Beam's repository. Please let me know if the PR is missing information.

Thanks,

María


On Tue, Feb 18, 2020 at 10:51 PM Matthias Baetens 
wrote:

> 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!! 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 and this can be part of that
>> effort.
>> - Workshops: Pablo & Austin have done some great work in this space, but
>> even more dedicated time & attention to this would greatly benefit the
>> project - and as Pablo raised this might be separate from project
>> transparency but directly contribute to increased usage.
>> -- For topics/format, it's split up in how to use and how to contribute.
>> How to use I would split up in a beginner training ("set-up and write your
>> first pipeline"), advanced training ("use some of the more exotic Beam
>> features / optimise your pipeline") and office hours (solve specific
>> problems people have which can feedback to the development team as well in
>> terms of missing features or potential improvement of documentation). Imho,
>> classroom style with an intro to Beam and concepts / advanced topics,
>> combined with do-it-yourself where people actually do some coding with
>> something to walk away is good for onboarding. A more fun and game-like
>> set-up can be done for users that already use Beam where we can accommodate
>> discussions or have them solve a specific use-case in groups.
>> - +1 for increased distribution of the talks. We should actively engage
>> the speakers as well to share it on their personal channels, and surface
>> the talks on the website and Twitter handles. Also a curated list as
>> blogpost would be a great addition.
>>
>> I think a more consistent feedback mechanism and maybe idea box at events
>> might also benefit the community.
>>
>> Cheers,
>> Matthias
>>
>>
>> On Wed, 15 Jan 2020 at 22:46, Austin Bennett 
>> wrote:
>>
>>> 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
>>> points to a lack of appetite and/or that it wasn't well publicized (I
>>> suspect both).
>>>
>>> Cheers,
>>> Austin
>>>
>>> On Thu, Jan 9, 2020 at 6:53 PM Kenneth Knowles  wrote:
>>>
>>>> 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 obvious to me is "workshop on how to
>>>> contribute to Beam". Is there enough appetite / audience to make this a
>>>> workshop? What forms could this take? A live coding demonstration in a
>>>> normal talk slot at an OSS or data conference seems like a possibility.
>>>> Whatever we do, we should record and distribute for sure, because when
>>>> someone wants to contribute, they need to find the resources at that 
>>>> moment.
>>>>
>>>> Kenn
>>>>
>>>> On Wed, Jan 8, 2020 at 1:01 PM María Cruz  wrote:
>>>>
>>>>> 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://

Re: [REQUEST] Workshop at Data Day in Mexico City - March 26th

[María Cruz]

Thank you for sharing these resources, Austin. Agree, no need to reinvent
the wheel. This will be very useful for the upcoming event in Mexico City.

Ismael, gracias por ofrecerte a dar el taller. Te contacto offlist para
coordinar.

Cheers,

María

On Sun, Feb 16, 2020 at 5:48 PM Austin Bennett 
wrote:

> Ismael,
>
> I'm also putting together training exercises for O'Reilly (ex:
> https://conferences.oreilly.com/strata-data-ai/stai-ca/public/schedule/detail/83505),
> and to offer online versions and extensions as well.  My criteria for
> involvement with them has been ability to reuse and share produced
> materials.
>
> I am not a competent enough Spanish speaker (among other things, an area I
> should retrain or study more!).  Happy to figure out ways to help/share the
> things am putting together.  No need to reinvent the wheel.
>
> Cheers,
> Austin
>
>
>
> On Fri, Feb 14, 2020, 3:57 PM Ismaël Mejía  wrote:
>
>> Hello,
>>
>> I am interested and I can make it in spanish if it is easier for the
>> audience.
>>
>> Regards,
>> Ismaël
>>
>> On Sat, Feb 15, 2020 at 12:42 AM María Cruz  wrote:
>>
>>> Hello everyone,
>>>
>>> There is an opportunity to host an Apache Beam workshop at the next Data
>>> Day in Mexico City *[1]*. The event will take place on Thursday, March
>>> 26th. This is a great opportunity to expand the reach of Apache Beam in a
>>> growing market like Latin America!
>>>
>>> If you are looking for more leadership opportunities, this is the
>>> perfect opportunity for you. The workshop can be presented either in
>>> English or in Spanish. If you are interested, Google will help you create
>>> the content for the workshop, drawing on some available training resources,
>>> like Apache Beam Katas *[2]* and previous workshops that have already
>>> been developed.
>>>
>>> This workshop is an important contribution that will bring more
>>> diversity to the project, making it more accessible and expanding its user
>>> and potentially its contributor base as well. Google Open Source will cover
>>> the cost of sponsorship. More information about Data Day below. Please
>>> contact us if you have any questions or comments.
>>>
>>> ---
>>>
>>> About Data Day in Ciudad de México
>>>
>>>
>>>-
>>>
>>>What: A one-day conference focused on data science in enterprise
>>>scenarios. The event has been organized since 2016; this will be the 6th
>>>edition. Data Day has become the leading event for Data Professionals in
>>>Mexico.
>>>-
>>>
>>>When: March 26, 2020
>>>-
>>>
>>>Where: Mexico City, Mexico.
>>>-
>>>
>>>Who will you find there: business executives, data professionals, IT
>>>professionals.
>>>-
>>>
>>>2019 attendance: 440 participants (36% data scientist / analyst, 6%
>>>executive level C, 15% data manager, 43% developer or other)
>>>-
>>>
>>>2020 expected attendance: 450 participants.
>>>
>>> Looking forward to hearing from you all!
>>>
>>> Thanks,
>>>
>>> María
>>>
>>> [1] https://sg.com.mx/dataday/agenda/
>>>
>>> [2] https://beam.apache.org/blog/2019/05/30/beam-kata-release.html
>>>
>>>

Re: Google's support framework for community-led meetups

[María Cruz]

HI Austin,
thank you for offering support. I'll follow up with you privately for that.
Answering your questions in line.

On Wed, Feb 12, 2020 at 5:14 PM Austin Bennett 
wrote:

> Hi Maria,
>
> This might be useful in user@ as well?
>
> Happy to walk you through editing webpage submitting a PR.  Then up to
> appropriate committer as to whether to approve.  Write me off list and we
> can find time.  A less focused walkthrough (including way more than you
> need just for that, in case wanting to get an independent start):
> https://www.youtube.com/watch?v=PtPslSdAPcM (will reoffer a more polished
> version at next summit).
>
> Some questions for clarity:
> * What is an Amplifier and how distinguished from contributor?
>

The definitions are in the email. There are 2 criteria for contributor, and
there are 3 criteria for contributor and amplifier. The one extra is about
engaging other contributors in becoming community organizers, for example,
by starting a new meetup group.


> * Do you have some examples of how Google Open Source contributing
> content?  Is that different than what Google does and it's engineers?  Or
> that's just the branding of it?
>

I'm not sure what you refer to with what Google does now (I am aware of
different current and past attempts, but not sure which one you are
referring to. If you gave an example, I could answer more specifically).
What it means is that we will work with engineering teams to distribute
latest updates on features, and create new content requested, for example,
for educational purposes.

I don't know what you mean by "the branding of it". We are intending to
formalize all kinds of support that are currently ongoing for meetups, some
of these things may already be happening for different events; the
intention of this process is to centralize request and offer transparency
about the type of support that is available.


> * When talking about company and/or Google Open Source sponsorships, are
> we talking about Money (ex: Meetup sometimes solicits to broker companies
> to pay for an advertising slot in a venue when can gather bodies in a room
> -- same as conference sponsorships)?  Or other/open?
>

Are you asking about Meetup.com fees? I don't fully understand this example.

Financial support for meetups is available now only for catering services
and swag.
This process IS NOT for conference sponsorship.


>
> Overall this is helpful, as someone trying to help build
> local communities in a number of cities.
>
> Cheers,
> Austin
>
>
> On Wed, Feb 12, 2020 at 11:40 AM María Cruz  wrote:
>
>> Hi everyone,
>>
>> I have been working closely with Gris Cuevas to develop a framework to
>> increase transparency on how Google Open Source supports community-led
>> events.  Below you will find a table that identifies different event goals,
>> community roles, and the type of support Google Open Source can offer in
>> each case.
>>
>> If you would like to request support from Google for your meetup, please
>> follow the meetup support request process
>> <https://docs.google.com/document/d/1mT5RVdyo_g19O-6LFtXb0H2Z5OXZ9_BLtDIho4Q3b7I/edit#heading=h.b44lcgnpxffu>.
>> Can someone help me put this information, along with the support framework
>> below, under the Community tab [1] of the Apache Beam website?
>>
>> We look forward to continuing partnering with our community organizers to
>> help Beam grow even more! If you have any questions, please let me know.
>> Support frameworkCommunity Roles
>>
>>-
>>
>>Project contributor AND community amplifier:
>>-
>>
>>   Contributes code, documentation, project management, etc, to the
>>   project
>>   -
>>
>>   Organizes meetups
>>   -
>>
>>   Engages other contributors in becoming organizers
>>   -
>>
>>Project contributor
>>-
>>
>>   Contributes code, documentation, project management, etc, to the
>>   project
>>   -
>>
>>   Organizes meetups
>>   -
>>
>>Company that wants to co-sponsor a meetup
>>-
>>
>>   A company that is an independent entity from Google that expressed
>>   interest in co-sponsoring a meetup
>>
>> Framework
>>
>>
>>
>> Community Goal
>>
>> Community Role Requesting Support
>>
>> Support Google Open Source can provide
>>
>>
>>
>>
>>
>> Raise awareness about project / increase reach of project / maximize
>> exposure
>>
>> E.g. Launch a new Meetup series in a new city.
>>
>> Project contributor AND amplifie

[REQUEST] Workshop at Data Day in Mexico City - March 26th

[María Cruz]

Hello everyone,

There is an opportunity to host an Apache Beam workshop at the next Data
Day in Mexico City *[1]*. The event will take place on Thursday, March
26th. This is a great opportunity to expand the reach of Apache Beam in a
growing market like Latin America!

If you are looking for more leadership opportunities, this is the perfect
opportunity for you. The workshop can be presented either in English or in
Spanish. If you are interested, Google will help you create the content for
the workshop, drawing on some available training resources, like Apache
Beam Katas *[2]* and previous workshops that have already been developed.

This workshop is an important contribution that will bring more diversity
to the project, making it more accessible and expanding its user and
potentially its contributor base as well. Google Open Source will cover the
cost of sponsorship. More information about Data Day below. Please contact
us if you have any questions or comments.

---

About Data Day in Ciudad de México


   -

   What: A one-day conference focused on data science in enterprise
   scenarios. The event has been organized since 2016; this will be the 6th
   edition. Data Day has become the leading event for Data Professionals in
   Mexico.
   -

   When: March 26, 2020
   -

   Where: Mexico City, Mexico.
   -

   Who will you find there: business executives, data professionals, IT
   professionals.
   -

   2019 attendance: 440 participants (36% data scientist / analyst, 6%
   executive level C, 15% data manager, 43% developer or other)
   -

   2020 expected attendance: 450 participants.

Looking forward to hearing from you all!

Thanks,

María

[1] https://sg.com.mx/dataday/agenda/

[2] https://beam.apache.org/blog/2019/05/30/beam-kata-release.html

Google's support framework for community-led meetups

[María Cruz]

Hi everyone,

I have been working closely with Gris Cuevas to develop a framework to
increase transparency on how Google Open Source supports community-led
events.  Below you will find a table that identifies different event goals,
community roles, and the type of support Google Open Source can offer in
each case.

If you would like to request support from Google for your meetup, please
follow the meetup support request process
.
Can someone help me put this information, along with the support framework
below, under the Community tab [1] of the Apache Beam website?

We look forward to continuing partnering with our community organizers to
help Beam grow even more! If you have any questions, please let me know.
Support frameworkCommunity Roles

   -

   Project contributor AND community amplifier:
   -

  Contributes code, documentation, project management, etc, to the
  project
  -

  Organizes meetups
  -

  Engages other contributors in becoming organizers
  -

   Project contributor
   -

  Contributes code, documentation, project management, etc, to the
  project
  -

  Organizes meetups
  -

   Company that wants to co-sponsor a meetup
   -

  A company that is an independent entity from Google that expressed
  interest in co-sponsoring a meetup

Framework



Community Goal

Community Role Requesting Support

Support Google Open Source can provide





Raise awareness about project / increase reach of project / maximize
exposure

E.g. Launch a new Meetup series in a new city.

Project contributor AND amplifier


   -

   Up to USD 3,000 a year in swag
   -

   Content
   -

   Speakers

Project contributor

   -

   Up to USD 1,500 a year in swag
   -

   Help to find a meetup sponsor
   -

   Content

A company that wants to co-sponsor a meetup


   -

   Connect to local community members to organize meetup
   -

   Content




Grow project adoption

E.g. create awareness of a new release and help people adopt it.

Project contributor AND amplifier

   -

   Add to leadership network
   -

   Support in finding sponsors

Project contributor

A company that wants to co-sponsor a meetup

   -

   Partner to present use case
   -

   Connect to community member in low-adoption region / city



Grow project contributions

E.g. run a hackathon to contribute to Beam website localization.

Project contributor AND amplifier

   -

   Develop workshop content
   -

   Swag or GCP credits for top contributors

Project contributor

   -

   Develop workshop content

A company that wants to co-sponsor a meetup

   -

   Develop workshop content
   -

   Connect to expert to deliver workshop



Expand professional network for project / Connect project features to other
projects

E.g. Working session at a conference

Project contributor AND amplifier

   -

   Connect to related meetups
   -

   Create a list of potential presenters from other companies

Project contributor

   -

   Connect to related meetups

A company that wants to co-sponsor a meetup

   -

   Connect to local expert for presentations

 --

María

[1] https://beam.apache.org/community/

Re: Please comment on draft comms strategy by Oct 16

[María Cruz]

artifacts
> appear only once with multiple arrows pointing at them (e.g. tech talks).
> Maybe this is on purpose, but just checking.
>

Yes, this is because there are currently 2 live blogs: one on Beam website,
and one on Beam Summit website. On the first proposal
<https://github.com/macruzbar/beam/blob/master/Communication-strategy-DRAFT.md#proposal-1-blog-post-categories-frequency-and-distribution>,
my recommendation is to reduce this to only 1 blog, with different
categories. I hope this can be implemented! =) It will work better towards
bringing new users to Beam events.



Looking forward to your thoughts / comments!

María


>
> Thanks!
> -P.
>
> On Fri, Dec 6, 2019 at 5:12 PM María Cruz  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  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 
>>> wrote:
>>>
>>>> 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 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
>>>>
>>>

Re: Please comment on draft comms strategy by Oct 16

[María Cruz]

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  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 
> wrote:
>
>> 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 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
>>
>


Apache Beam Communications logic model.pdf
Description: Adobe PDF document

Please comment on draft comms strategy by Oct 16

[María Cruz]

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

Re: Introduction + Support in Comms for Beam!

[María Cruz]

Thank you all for the warm welcome!
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!
<https://github.com/macruzbar/beam/blob/master/Communication-strategy-DRAFT.md
>
I will give this a week for comments.

Thank you for your collaboration!

María

On Thu, Oct 3, 2019 at 7:27 AM Cyrus Maden  wrote:

> Welcome, Maria!
>
> On Thu, Oct 3, 2019 at 9:40 AM Ismaël Mejía  wrote:
>
>> Hello and welcome Maria!
>>
>> Great to see you at dev@. Thanks for sharing the link on the comm
>> framework. Now I am curious on what's next and how this will adapt to
>> our community.
>>
>> Ismaël.
>>
>>
>> On Tue, Oct 1, 2019 at 12:15 AM María Cruz  wrote:
>> >
>> > Hi everyone,
>> > my name is María Cruz, I am from Buenos Aires but I live in the Bay
>> Area. I recently became acquainted with Apache Beam project, and I got a
>> chance to meet some of the Beam community at Apache Con North America this
>> past September. I'm testing out a communications framework for Open Source
>> communities. I'm emailing the list now because I'd like to work on a
>> communications strategy for Beam, to make the most of the content you
>> produce during Beam Summits.
>> >
>> > A little bit more about me. I am a communications strategist with 11
>> years of experience in the field, 8 of which are in the non-profit sector.
>> I started working in Open Source in 2013, when I joined Wikimedia, the
>> social movement behind Wikipedia. I now work to support Google Open Source
>> projects, and I also volunteer in the communications team of the Apache
>> Software Foundation, working closely with Sally (for those of you who know
>> her).
>> >
>> > I will be sending the list a proposal in the coming days. Looking
>> forward to hearing from you!
>> >
>> > Best,
>> >
>> > María
>>
>

Introduction + Support in Comms for Beam!

[María Cruz]

Hi everyone,
my name is María Cruz, I am from Buenos Aires but I live in the Bay Area. I
recently became acquainted with Apache Beam project, and I got a chance to
meet some of the Beam community at Apache Con North America this past
September. I'm testing out a communications framework
<https://medium.com/@marianarra_/designing-a-communications-framework-for-community-engagement-e087312f9b83>
for Open Source communities. I'm emailing the list now because I'd like to
work on a communications strategy for Beam, to make the most of the content
you produce during Beam Summits.

A little bit more about me. I am a communications strategist with 11 years
of experience in the field, 8 of which are in the non-profit sector. I
started working in Open Source in 2013, when I joined Wikimedia, the social
movement behind Wikipedia. I now work to support Google Open Source
projects, and I also volunteer in the communications team of the Apache
Software Foundation, working closely with Sally (for those of you who know
her).

I will be sending the list a proposal in the coming days. Looking forward
to hearing from you!

Best,

María