Re: [Vote] Publishing new website designs

[Griselda Cuevas]

;>> Foundation code of conduct. To learn more see the ASF documentation." I 
>>>>>>> am
>>>>>>> -0 to removing the details. Our bullets highlight specific aspects of 
>>>>>>> the
>>>>>>> code of conduct. Specifically, we split up one of the items into 
>>>>>>> separate
>>>>>>> bullet points, and we did not emphasize "be concise" or "step down
>>>>>>> considerately". I am OK going ahead with this change but want to note 
>>>>>>> that
>>>>>>> this is a content change.
>>>>>>>
>>>>>>> Kenn
>>>>>>>
>>>>>>> On Wed, Feb 10, 2021 at 11:46 AM Robert Bradshaw <
>>>>>>> rober...@google.com> wrote:
>>>>>>>
>>>>>>>> +1 based on some basic browsing around.
>>>>>>>>
>>>>>>>> It would have been nice if the old and new site could have been
>>>>>>>> generated from the same content, to keep the old one around for a bit 
>>>>>>>> (if
>>>>>>>> needed, in that case we might have more confidence nothing was lost), 
>>>>>>>> but
>>>>>>>> probably not worth making and staging a copy.
>>>>>>>>
>>>>>>>> On Tue, Feb 9, 2021 at 12:45 PM Brittany Hermann <
>>>>>>>> herma...@google.com> wrote:
>>>>>>>>
>>>>>>>>> @Ahmet Altay  : Thank you for the suggestions
>>>>>>>>> to the Powered By page! I created two JIRA tickets for each of these.
>>>>>>>>>
>>>>>>>>> On Tue, Feb 9, 2021 at 11:34 AM Brian Hulette 
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> > Optional point: does it make sense to maintain a link to the
>>>>>>>>>> old Website from the new one for some time (in case something
>>>>>>>>>> gets broken in the new version or some information becomes 
>>>>>>>>>> unavailable) ?
>>>>>>>>>>
>>>>>>>>>> We could do this, but I think it would require duplicating all
>>>>>>>>>> the source for the existing website and putting it in a separate 
>>>>>>>>>> directory,
>>>>>>>>>> and the content would slowly get out of date. I'm not sure it would 
>>>>>>>>>> be an
>>>>>>>>>> improvement - we'll have access to the current website in the
>>>>>>>>>> commit history anyway.
>>>>>>>>>>
>>>>>>>>>> Brian
>>>>>>>>>>
>>>>>>>>>> On Mon, Feb 8, 2021 at 4:44 PM Ahmet Altay 
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> +1 - I did a basic review looking around python docs and release
>>>>>>>>>>> guides mostly.
>>>>>>>>>>>
>>>>>>>>>>> One thing I would like to see fixed related to
>>>>>>>>>>> https://beam.apache.org/community/powered-by/
>>>>>>>>>>> - New page is missing existing items from the current list
>>>>>>>>>>> https://beam.apache.org/community/powered-by/. Particularly I
>>>>>>>>>>> could not find TFX and Cloud Dataflow.
>>>>>>>>>>> - And a nice to have for that same page: New page could be
>>>>>>>>>>> simplified. There are a total of 8 powered by items and they are 
>>>>>>>>>>> divided
>>>>>>>>>>> into two groups (1 click) and each group loads 3 items at a time 
>>>>>>>>>>> (another
>>>>>>>>>>> click). I think it would be much more simple to list all 8 
>>>>>>>>>>> references on a
>>>>>>>>>>> single page.
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Feb 8, 2021 at 2:39 PM Griselda Cuevas 
>>>>>>>>>>> wrote:
>>>>>

Re: [Vote] Publishing new website designs

[Griselda Cuevas]

Great suggestion Cham. Noting it as optional.

On Mon, 8 Feb 2021 at 13:51, Chamikara Jayalath 
wrote:

> +1
>
> Thanks. This looks great.
> Optional point: does it make sense to maintain a link to the old Website
> from the new one for some time (in case something gets broken in the new
> version or some information becomes unavailable) ?
>
> Thanks,
> Cham
>
> On Mon, Feb 8, 2021 at 1:09 PM Pablo Estrada  wrote:
>
>> +1
>> I'm taking a superficial look through it as we speak. Thanks everyone for
>> the work : )
>>
>> On Mon, Feb 8, 2021 at 9:32 AM Brian Hulette  wrote:
>>
>>> +1, thank you Gris!
>>>
>>> I just wanted to add a note about my reviews here. I reviewed this
>>> change as a series of PRs that went into the website-revamp branch. My main
>>> focus in reviewing them was ensuring that no content was /unintentionally/
>>> changed.
>>>
>>> Note that some content is intentionally changed and/or moved around as
>>> described in the designs Gris shared. Other content is separated out from
>>> markdown files into yaml files, I believe to aid future translation efforts.
>>>
>>> This makes it pretty tricky to verify the content based on the diff
>>> alone at this point, which is why I want to reassure the community that I
>>> had a particular focus on this in my reviews. I'm not perfect though! so
>>> more people looking over the changed pages will be great.
>>>
>>> Brian
>>>
>>> On Fri, Feb 5, 2021 at 9:13 PM Griselda Cuevas  wrote:
>>>
>>>> Hi Everyone,
>>>>
>>>> The new designs for the Beam website are ready to be published in PR
>>>> #13871 [1], so I'd like to start a vote to merge this PR into the master
>>>> repo. Considering that this PR could get stale very quickly, we're looking
>>>> to follow the 72h voting period starting Monday, if there are minor bugs we
>>>> will file them as Jira tickets so we can address them in the next refresh.
>>>>
>>>> This effort started back in November, when we kicked-off a project to
>>>> redesign a few critical pages of the Beam website, primarily the home page,
>>>> a few of the community sections and the documentation landing page.
>>>>
>>>> Below you can find a summary of the changes and links to the staged
>>>> website for your review.
>>>>
>>>> Thank you,
>>>> G
>>>>
>>>> *What do I need to vote for? *
>>>> To merge PR #13871 [1] into master. This PR has been reviewed by Brian
>>>> H and Gris C (committers). You can see the staged version of the website
>>>> here [2], for mobile versions use the same link in your mobile.
>>>>
>>>> You can see a summary of changed pages in this deck [3]. If you want
>>>> even more background, you can read the requirements document here [4] and
>>>> the design document with copy and wireframes here [5].
>>>>
>>>> *Where can I see how the new designs look?*
>>>> You can see a staged version here [2], for mobile versions use the same
>>>> link in your mobile.
>>>>
>>>> *Why was this redesign made?*
>>>> This redesign was phase II of a long-term effort to make the Apache
>>>> Beam website more effective for users who want to learn about Apache Beam,
>>>> implement it and contribute to the open source project. This phase was
>>>> focused on improving resources for two types of users: 1) those looking to
>>>> understand what Apache Beam is and to make the decision to adopt it and 2)
>>>> those looking to make their first contribution to the OSS project.
>>>>
>>>> *What changes in this redesign?*
>>>> We redesign 8 pages, including the home page, and created 3 new
>>>> sections, see more details here [3].
>>>>
>>>> Links:
>>>> [1] https://github.com/apache/beam/pull/13871
>>>> [2] http://test-beam.surge.sh/
>>>> [3]
>>>> https://docs.google.com/presentation/d/1WcBccS4Bt6ZAEkw-nsud2MjU4H0j_iOkIk5XlPDk8f0/edit#slide=id.p
>>>> [4]
>>>> https://docs.google.com/document/d/1rssE8B6fvwLfyODS6KKp049KryhKn8E-HlHkzM8TWkE/edit
>>>> [5]
>>>> https://docs.google.com/document/d/1DDk8DtYGzuTO7bdu2nqiVEgVnx06lCzZ2idVpwcemFA/edit?resourcekey=0-KGE8dMg8L4j5rcqnQ5SG_g
>>>>
>>>> And lastly, HUGE THANK YOU to the team who contributed to these changes
>>>> (in alphabetical order): Agnieszka Sell, Brian Hulette, Brittany Hermann,
>>>> David Cavazos, Gris Cuevas, Jakub Sadowski,  Kasia Zajac, Kenn Knowles,
>>>> Milka Toikkanen, Nam Bui, Rose Nguyen.
>>>>
>>>>

[Vote] Publishing new website designs

[Griselda Cuevas]

Hi Everyone,

The new designs for the Beam website are ready to be published in PR #13871
[1], so I'd like to start a vote to merge this PR into the master repo.
Considering that this PR could get stale very quickly, we're looking to
follow the 72h voting period starting Monday, if there are minor bugs we
will file them as Jira tickets so we can address them in the next refresh.

This effort started back in November, when we kicked-off a project to
redesign a few critical pages of the Beam website, primarily the home page,
a few of the community sections and the documentation landing page.

Below you can find a summary of the changes and links to the staged website
for your review.

Thank you,
G

*What do I need to vote for? *
To merge PR #13871 [1] into master. This PR has been reviewed by Brian H
and Gris C (committers). You can see the staged version of the website here
[2], for mobile versions use the same link in your mobile.

You can see a summary of changed pages in this deck [3]. If you want even
more background, you can read the requirements document here [4] and the
design document with copy and wireframes here [5].

*Where can I see how the new designs look?*
You can see a staged version here [2], for mobile versions use the same
link in your mobile.

*Why was this redesign made?*
This redesign was phase II of a long-term effort to make the Apache Beam
website more effective for users who want to learn about Apache Beam,
implement it and contribute to the open source project. This phase was
focused on improving resources for two types of users: 1) those looking to
understand what Apache Beam is and to make the decision to adopt it and 2)
those looking to make their first contribution to the OSS project.

*What changes in this redesign?*
We redesign 8 pages, including the home page, and created 3 new sections,
see more details here [3].

Links:
[1] https://github.com/apache/beam/pull/13871
[2] http://test-beam.surge.sh/
[3]
https://docs.google.com/presentation/d/1WcBccS4Bt6ZAEkw-nsud2MjU4H0j_iOkIk5XlPDk8f0/edit#slide=id.p
[4]
https://docs.google.com/document/d/1rssE8B6fvwLfyODS6KKp049KryhKn8E-HlHkzM8TWkE/edit
[5]
https://docs.google.com/document/d/1DDk8DtYGzuTO7bdu2nqiVEgVnx06lCzZ2idVpwcemFA/edit?resourcekey=0-KGE8dMg8L4j5rcqnQ5SG_g

And lastly, HUGE THANK YOU to the team who contributed to these changes (in
alphabetical order): Agnieszka Sell, Brian Hulette, Brittany Hermann, David
Cavazos, Gris Cuevas, Jakub Sadowski,  Kasia Zajac, Kenn Knowles, Milka
Toikkanen, Nam Bui, Rose Nguyen.

Re: [ANNOUNCE] New PMC Member: Chamikara Jayalath

[Griselda Cuevas]

Congratulations Cham!!! Well deserved :)

On Thu, 21 Jan 2021 at 15:23, Connell O'Callaghan 
wrote:

> Well done Cham!!! Thank you for all your contributions to date!!!
>
>
> On Thu, Jan 21, 2021 at 3:18 PM Rui Wang  wrote:
>
>> Congratulations, Cham!
>>
>> -Rui
>>
>> On Thu, Jan 21, 2021 at 3:15 PM Robert Bradshaw 
>> wrote:
>>
>>> Congratulations, Cham!
>>>
>>> On Thu, Jan 21, 2021 at 3:13 PM Brian Hulette 
>>> wrote:
>>>
 Great news, congratulations Cham!

 On Thu, Jan 21, 2021 at 3:08 PM Robin Qiu  wrote:

> Congratulations, Cham!
>
> On Thu, Jan 21, 2021 at 3:05 PM Tyson Hamilton 
> wrote:
>
>> Woo! Congrats Cham!
>>
>> On Thu, Jan 21, 2021 at 3:02 PM Robert Burke 
>> wrote:
>>
>>> Congratulations! That's fantastic news.
>>>
>>> On Thu, Jan 21, 2021, 2:59 PM Reza Rokni  wrote:
>>>
 Congratulations!

 On Fri, Jan 22, 2021 at 6:58 AM Ankur Goenka 
 wrote:

> Congrats Cham!
>
> On Thu, Jan 21, 2021 at 2:57 PM Ahmet Altay 
> wrote:
>
>> Hi all,
>>
>> Please join me and the rest of Beam PMC in welcoming Chamikara
>> Jayalath as our
>> newest PMC member.
>>
>> Cham has been part of the Beam community from its early days and
>> contributed to the project in significant ways, including 
>> contributing new
>> features and improvements especially related Beam IOs, advocating for
>> users, and mentoring new community members.
>>
>> Congratulations Cham! And thanks for being a part of Beam!
>>
>> Ahmet
>>
>

Re: Website is MIT licensed?

[Griselda Cuevas]

Thank you both.

On Thu, 7 Jan 2021 at 16:06, Ahmet Altay  wrote:

> I agree with you. I guess we missed this during the website migration.
>
> https://github.com/apache/beam/pull/13698 is to fix.
>
> On Thu, Jan 7, 2021 at 12:42 PM Kyle Weaver  wrote:
>
>> Hi all,
>>
>> I discovered the Beam website's NPM module purports to be MIT licensed
>> [1]. I don't think we publish the website's NPM package anywhere, but
>> wouldn't the website be Apache 2.0 licensed like everything else?
>>
>> Thanks,
>> Kyle
>>
>> [1]
>> https://github.com/apache/beam/blob/30f9a607509940f78459e4fba847617399780246/website/www/package.json#L6
>>
>

Planning a freeze on website changes to merge new designs

[Griselda Cuevas]

Hi folks,

As you know we've been working on a revamp for the website, and we're
getting ready to commit the work we've done. In order to minimize the risk
of losing changes other contributors make during this period, we'd like to
plan a freeze so we can work on making the revamp commits. A freeze in this
context would mean that we give notice to our dev community to do not make
any PRs or change to the site during this period.

I'd like to propose we have a one-week freeze during the last week of
January or the first week in February.

What do you think?

G

Re: Standarizing the "Runner" concept across website content

[Griselda Cuevas]

Thank you all for this productive conversation!

Interestingly enough, a usability study we ran for Apache Beam (more
details coming soon) pointed out that our documentation and website assume
that the readers will be already familiar with Data Processing basic
concepts such as engines, pipelines, etc. So introducing a glossary and
even rethinking how we add this concepts into our new documentation is a
good practice to have in mind.

In the meantime, I will adopt the suggestion of differentiating between
engine and runner. The first application I made of this is in the copy for
the home page, which you can find as an attached file in this Jira ticket
[1] in case you want to add comments/suggestions.

The home page is the most important page in the website, as it's the one
that explains Beam to the world and markets it's features, so appreciate
feedback there too.

Thanks everyone!

[1]
https://issues.apache.org/jira/browse/BEAM-11346?jql=project%20%3D%20beam%20AND%20assignee%20%3D%20gris%20ORDER%20BY%20priority%20DESC

On Wed, 6 Jan 2021 at 13:33, Kenneth Knowles  wrote:

>
>
> On Wed, Jan 6, 2021 at 12:28 PM Robert Burke  wrote:
>
>> +1 on consolidating and being consistent with our terms.
>>
>> I've always considered them (Runner/Engine) synonymous. From a user
>> perspective, an engine without a runner isn't any good for their beam
>> pipeline. That there's an adapter is an implementation detail in some
>> instances. I do appreciate not using Adapter a term, avoiding confusing
>> descriptions.
>>
>> However, if we make the change and there's a clear glossary of terms
>> somewhere then
>>
>> That puts the lifecycle of a pipeline to be (loosely) something like...
>>
>> A Beam User authors Pipelines by writing DoFns, adding them as
>> PTransforms connected by PCollections into a Pipeline using a Beam SDK. An
>> SDK converts the pipeline into a portable representation, and submit it to
>> the Job Management Service of a Beam Runner. A Beam Runner translates the
>> portable pipeline representation into terms an underlying Engine
>> understands for Execution. The Beam Runner also reverses this translation
>> when the Engine delegates tasks to workers, so that the Beam SDKs can
>> execute the user's DoFns in keeping with the Beam Semantics.
>>
>
> An explicit glossary is a great idea to combine with standardizing
> terminology across the site. I think the important context is that most of
> the engines already existed before Beam and many of them are more
> well-known. In fact, a pretty good way for a user to understand the essence
> of what Beam is about is by taking a look at all the engines for which
> there are Beam runners :-)
>
> Engine: a system/product for doing [big] data processing
> Pipeline: user authors this logic that says what they want to compute (I
> think the fact that it is a DAG of PTransforms is relevant but we can get
> away with omitting it for the high-level view and to avoid introducing the
> term PTransform too early)
> Runner: executes a Beam pipeline on an engine (agree that "adapter" is too
> generic)
>
> I'd say below that level of granularity is getting into things that you
> need to know only after you have started writing pipelines. Possibly you
> need to introduce SDK harness to make clear that Beam pipelines are
> inherently multi-language/multi-runtime, even if the engine isn't (my
> personal opinion is that "UDF server" is the best understood terminology
> for this, and so much better that it is never too late to abandon the
> cryptic term "SDK harness").
>
> Kenn
>
>
>> (Not covered, bundles etc, but you get the idea...)
>>
>> On Wed, Jan 6, 2021, 11:16 AM Robert Bradshaw 
>> wrote:
>>
>>> +1 to keeping the distinction between Runner and Engine as Kenn
>>> described, and cleaning up the site with these in mind (I don't think the
>>> term engine is widely used yet).
>>>
>>> On Wed, Jan 6, 2021 at 11:15 AM Yichi Zhang  wrote:
>>>
>>>> I agree with what kenn said, in most cases I would refer to the term
>>>> runner as the adapter for translating user's pipeline code into a job
>>>> representation and submitting it to the execution engine. Though in some
>>>> cases they may still be used interchangeably such as direct runner?
>>>>
>>>> On Wed, Jan 6, 2021 at 11:02 AM Kenneth Knowles 
>>>> wrote:
>>>>
>>>>> I personally try to always distinguish two concepts: the thing doing
>>>>> the computing (like Spark or Flink), and the adapter for running a Beam
>>>>> pipeline (like SparkRunner or FlinkRunner). I

Re: [Input needed] Capability Matrix Visual Redesign for extended version

[Griselda Cuevas]

Thanks Kenn, this is super helpful.



On Mon, 21 Dec 2020 at 09:57, Kenneth Knowles  wrote:

> For the capability matrix, part of the problem is that the rows don't all
> make that much sense, as we've discussed a couple times.
>
> But assuming we keep the content identical, maybe we could just have the
> collapsed view and make the table selectable where *just* the selected cell
> controls content below? You won't be able to do side-by-side comparisons of
> the full text of things, but you will be able to keep the overview and
> drill in one at a time quickly. Just one idea.
>
> A couple ways to save space without rearchitecting it:
>
>  - Apache Hadoop MapReduce and JStorm can be removed as they are on
> branches, not released.
>  - I think we can also remove rows that are not started or not complete in
> the Beam Model, and remove the Beam Model column.
>  - I think Splittable DoFn really just deserves one row for bounded, one
> for unbounded, and any caveats go in the details.
>  - All the windowing rows can be condensed into "Basic windowing support"
> and "Merging windowing support" and any runner that can only run a couple
> WindowFns can have details in the caveats. At this point any runner that
> doesn't do Windowing by invoking a user's WindowFn simply doesn't really
> support windowing in the model.
>  - "Configurable triggering" can absorb "Event-time triggers",
> "Processing-time triggers", "Count triggers", and "Composite triggers".
> Same. At this point any runner that doesn't support the whole triggering
> language doesn't really support triggers fully.
>
> Kenn
>
> On Mon, Dec 14, 2020 at 7:39 PM Griselda Cuevas  wrote:
>
>> Hi folks, another page that's getting a refresh this time around is the
>> Capability Matrix, which is one of the most critical pages for users as
>> they evaluate the current support for each of the Beam runners.
>>
>> The situation we'd like to get your input on is: How do we optimize the
>> expanded version of the capability matrix, which explains the level of
>> support in each of the functions?
>>
>> Right now the text gets in the way of analyzing the table and makes
>> reading hard. You can see a screenshot in the Beam wiki here [1], the file
>> is titled current_CapMatExt.
>>
>> One of the proposed solutions is that after clicking the link "(click to
>> expand details)", we load a new page that has the corresponding table to
>> the click (what, where, when, how) at the top, and all the content of each
>> runner/function gets displayed at the bottom of the page, the file with the
>> proposed design is also in the Beam wiki here [1] and the file's name is
>> proposed_CapMatExt. This solution isn't perfect either, since we'd need to
>> move too much text under the table and reading isn't much easier.
>>
>> Do you have suggestions/ideas in how to condense the extended version?
>>
>> Share with us your feedback through this week,
>> Thanks!
>> G
>>
>>
>> [1]
>> https://cwiki.apache.org/confluence/display/BEAM/Website+Redesign+Files
>>
>

Re: [Input Needed] Updating the documentation left navigation (was:Website Revamp update & navigation for documentation page)

[Griselda Cuevas]

Are you referring to things missing in the left navigation or in the right
one?

If things are missing on the left navigation, we will fix in this round, if
there are things missing in the right navigation we won't fix this time
around, the right navigation is automatically created from formatting in
the documentation, displaying headers/sub-headers, and we won't touch the
actual content this time around.

On Mon, 21 Dec 2020 at 09:40, Kenneth Knowles  wrote:

> I like the change. The left nav is inconsistent about things being
> re-collapsed when we return to the page anyhow, and I never really
> understood what part of navigation belonged in which side.
>
> And it seems there are still more levels of subheaders than we can
> display. Is the plan to simply not have those in the nav? (this seems fine
> with me)
>
> Kenn
>
> On Mon, Dec 14, 2020 at 7:30 PM Griselda Cuevas  wrote:
>
>> Hi dev@ community,
>>
>>
>> I wanted to fork this conversation to make it more visible. We'd like to
>> get your feedback on the proposed update for the documentation page in the
>> website.
>>
>>
>> The proposed change is that the left navigation (which is the website
>> main navigation) stays high level and only shows titles, leaving the
>> detailed hierarchy in the right navigation, which appears when you click on
>> a Documentation topic or when you land directly on it.
>>
>>
>> You can see a screenshot of the current and proposed designs in the wiki
>> repo with the other website designs [1]. The names of the files are:
>> current_DocsNav for the current design, and proposed_DocsNav for the
>> proposed design.
>>
>>
>> Please let us know your preference or suggestions through this week.
>>
>>
>> Gris
>>
>>
>> [1]
>> https://cwiki.apache.org/confluence/display/BEAM/Website+Redesign+Files
>>
>

Re: Farewell mail

[Griselda Cuevas]

Thank you Piotr for your contributions.

On Wed, 16 Dec 2020 at 09:16, Ahmet Altay  wrote:

> Thank you Piotr and best wishes!
>
> On Wed, Dec 16, 2020 at 8:46 AM Alexey Romanenko 
> wrote:
>
>> Piotr,
>>
>> Thanks a lot for your contributions, it was very useful and made Beam
>> more stable and finally even better! And it was always interesting to work
>> with you =)
>>
>> I wish you all the best in your next adventure but feel free to get back
>> to Beam and contribute in any way as you can. It is always welcome!
>>
>> Alexey
>>
>> > On 16 Dec 2020, at 17:16, Piotr Szuberski 
>> wrote:
>> >
>> > Hi all,
>> >
>> > This week is the last one I'm working on Beam. It was a pleasure to
>> contribute to this project. I've learned a lot and had really good time
>> with you guys!
>> >
>> > The IT world is quite small so there is no goodbye. See you in the
>> future in the Web and another great projects!
>> >
>> > You can find me at https://github.com/piotr-szuberski
>> >
>> > Piotr
>>
>>

[Input needed] Capability Matrix Visual Redesign for extended version

[Griselda Cuevas]

Hi folks, another page that's getting a refresh this time around is the
Capability Matrix, which is one of the most critical pages for users as
they evaluate the current support for each of the Beam runners.

The situation we'd like to get your input on is: How do we optimize the
expanded version of the capability matrix, which explains the level of
support in each of the functions?

Right now the text gets in the way of analyzing the table and makes reading
hard. You can see a screenshot in the Beam wiki here [1], the file is
titled current_CapMatExt.

One of the proposed solutions is that after clicking the link "(click to
expand details)", we load a new page that has the corresponding table to
the click (what, where, when, how) at the top, and all the content of each
runner/function gets displayed at the bottom of the page, the file with the
proposed design is also in the Beam wiki here [1] and the file's name is
proposed_CapMatExt. This solution isn't perfect either, since we'd need to
move too much text under the table and reading isn't much easier.

Do you have suggestions/ideas in how to condense the extended version?

Share with us your feedback through this week,
Thanks!
G


[1] https://cwiki.apache.org/confluence/display/BEAM/Website+Redesign+Files

[Input Needed] Updating the documentation left navigation (was:Website Revamp update & navigation for documentation page)

[Griselda Cuevas]

Hi dev@ community,


I wanted to fork this conversation to make it more visible. We'd like to
get your feedback on the proposed update for the documentation page in the
website.


The proposed change is that the left navigation (which is the website main
navigation) stays high level and only shows titles, leaving the detailed
hierarchy in the right navigation, which appears when you click on a
Documentation topic or when you land directly on it.


You can see a screenshot of the current and proposed designs in the wiki
repo with the other website designs [1]. The names of the files are:
current_DocsNav for the current design, and proposed_DocsNav for the
proposed design.


Please let us know your preference or suggestions through this week.


Gris


[1] https://cwiki.apache.org/confluence/display/BEAM/Website+Redesign+Files

Re: Website Revamp update & navigation for documentation page

[Griselda Cuevas]

Ack, thanks Ahmet for the suggestion.

I think it's important to bring attention to this discussion separately, so
I am going to for the thread to start one specific about the navigation
design.


On Mon, 14 Dec 2020 at 17:49, Ahmet Altay  wrote:

>
>
> On Mon, Dec 14, 2020 at 4:32 PM Griselda Cuevas  wrote:
>
>> Hi Ahmet, adding response inline.
>>
>> A question about the content. Design adds items for use cases, do we have
>>> existing content that fits into that template?
>>>
>> Yes, the content will be curated from the use cases we got presented at
>> Beam Summits. We are tracking who has given permission to do this in Jira:
>> BEAM-11225 <https://issues.apache.org/jira/browse/BEAM-11225> [1]
>>
>
> Nice!
>
>
>>
>> Re: left navigation on the docs page. The fonts here are more readable to
>>> me and the search feature is great. One question, the current version has
>>> hierarchical and collapsible items on the left navigation. Would that still
>>> be possible. IMO visual grouping, and hiding detailed items makes the
>>> documentation easier to navigate.
>>>
>>
>> This is the point we would like to hear feedback on, the proposal is to
>> remove the full detail in the left navigation and leave the hierarchy view
>> on the right navigation, which appears on the right when you click on a
>> topic. Doing this will allow us to keep the left navigation organized and
>> focused on the high level topics, hoping to make the experience smoother
>> and neater for people and do not overwhelm them with so many
>> topics/subtopics.
>>
>
> Got it. Having a simplified left nav, and a more detailed right nav make
> sense to me.
>
> My _very personal opinion_ is that the left nav is useful, and the right
> nav is usually cluttered and has duplicate information. For example in this
> page (
> https://beam.apache.org/documentation/transforms/python/overview/#element-wise),
> left nav has richer and collapsible information. Right nav has partial
> information. Somewhat of an opposite example in this page (
> https://beam.apache.org/documentation/programming-guide/#triggers). I
> wonder if we can have a single nav menu in a more elegant way?
>
>
>>
>> For context, experienced UX and UI designers are proposing these changes
>> and have optimized for a better discovery and troubleshooting experience,
>> hence the recommendation.
>>
>> [1]
>> https://issues.apache.org/jira/browse/BEAM-11225?jql=project%20%3D%20BEAM%20AND%20text%20~%20%22permission%20use%20cases%22
>>
>>>

Re: Website Revamp update & navigation for documentation page

[Griselda Cuevas]

Hi Ahmet, adding response inline.

A question about the content. Design adds items for use cases, do we have
> existing content that fits into that template?
>
Yes, the content will be curated from the use cases we got presented at
Beam Summits. We are tracking who has given permission to do this in Jira:
BEAM-11225  [1]

Re: left navigation on the docs page. The fonts here are more readable to
> me and the search feature is great. One question, the current version has
> hierarchical and collapsible items on the left navigation. Would that still
> be possible. IMO visual grouping, and hiding detailed items makes the
> documentation easier to navigate.
>

This is the point we would like to hear feedback on, the proposal is to
remove the full detail in the left navigation and leave the hierarchy view
on the right navigation, which appears on the right when you click on a
topic. Doing this will allow us to keep the left navigation organized and
focused on the high level topics, hoping to make the experience smoother
and neater for people and do not overwhelm them with so many
topics/subtopics.

For context, experienced UX and UI designers are proposing these changes
and have optimized for a better discovery and troubleshooting experience,
hence the recommendation.

[1]
https://issues.apache.org/jira/browse/BEAM-11225?jql=project%20%3D%20BEAM%20AND%20text%20~%20%22permission%20use%20cases%22

>

Getting Sprint Management rights on Jira

[Griselda Cuevas]

Hi folks, I'd like to request Sprint management rights on Jira to organize
the Website redesign work around the content creation part.

Could someone in the PMC help me with this?

Re: Add emilymye to JIRA contributers

[Griselda Cuevas]

Hi Emily, did you get access?

On Mon, 7 Dec 2020 at 13:33, Emily Ye  wrote:

> Hi dev@
>
> Just realized I didn't request contributor access to JIRA a while back -
> would someone be able to add me so I can self-assign my issues?
>
> Thank you!
> Emily
>

Re: [Input Needed] Website Designs, share your feedback!

[Griselda Cuevas]

Hi folks, forgot to mention that we continue to work on the design of a few
more pages, one of them is the Powered By, one.

I will continue to add mocks to the wiki folder I shared and ping this
thread with updates.

On Fri, 4 Dec 2020 at 16:21, Griselda Cuevas  wrote:

> Hi Beam community!
>
> New designs for the Beam Website are available and we'd love for you to
> check them out and provide feedback before we move into development. An
> important caveat is that what we have worked on and ironed out is the look
> and feel, plus usability. The content hasn't been revamped yet, so keep
> this in mind when providing feedback.
>
> The pages that we've redesigned are:
>
>- Home Page
>- Overall documentation look and feel
>- Community
>- Community/Contact Us
>- Community/Join Beam community
>- Community/Become a Beam committer
>- Contribution guide
>
> You can see the new designs here [1].
>
> At this point the effort has been around creating the UI and UX for
> optimal navigation considering the use cases outlined in our Public PRD
> [2].
>
> We're looking into productionalize this starting next week, and to produce
> the copy (text) for some of these pages as well. You can follow the work on
> this project in this Jira board [3].
>
> Let us know what you think!
> Gris and the website revamp team
>
> [1]
> https://cwiki.apache.org/confluence/display/BEAM/Website+Redesign+Files
> [2]
> https://docs.google.com/document/d/1rssE8B6fvwLfyODS6KKp049KryhKn8E-HlHkzM8TWkE/edit
> [3] https://issues.apache.org/jira/issues/?filter=12349972
>

[Input Needed] Website Designs, share your feedback!

[Griselda Cuevas]

Hi Beam community!

New designs for the Beam Website are available and we'd love for you to
check them out and provide feedback before we move into development. An
important caveat is that what we have worked on and ironed out is the look
and feel, plus usability. The content hasn't been revamped yet, so keep
this in mind when providing feedback.

The pages that we've redesigned are:

   - Home Page
   - Overall documentation look and feel
   - Community
   - Community/Contact Us
   - Community/Join Beam community
   - Community/Become a Beam committer
   - Contribution guide

You can see the new designs here [1].

At this point the effort has been around creating the UI and UX for optimal
navigation considering the use cases outlined in our Public PRD [2].

We're looking into productionalize this starting next week, and to produce
the copy (text) for some of these pages as well. You can follow the work on
this project in this Jira board [3].

Let us know what you think!
Gris and the website revamp team

[1] https://cwiki.apache.org/confluence/display/BEAM/Website+Redesign+Files
[2]
https://docs.google.com/document/d/1rssE8B6fvwLfyODS6KKp049KryhKn8E-HlHkzM8TWkE/edit
[3] https://issues.apache.org/jira/issues/?filter=12349972

Website Revamp Update – Week 3 & 4

[Griselda Cuevas]

Hi Beam Community!

Sprint 3 and 4 in the website revamp project have concluded and below is a
recap of the work the team has done on it. The working notes can be found
here [1] and the presentations from the past two meetings here [2]. The PRD
has been split in the requirements doc and a Technical Design Doc that
contains discussions on designs and copy, you can find the PRD here [3] and
the TDD here [4].

Lastly, remember you can join the weekly calls if you're interested in
discussing any changes. Let us know in this thread if you'd like to attend,
meetings happen on Wednesdays at 8a.m. Pacific Time.

Sprint 3 and 4 Recap

   - Join the community page: pathway was finalized and copy was added to
   the TDD
   - Contribute page changes: “Get started contributing” and “Become a
   committer” will be moved to the higher level in the page architecture. We
   keep “Committer guide”, “Release guide”, and “Get help” in Commiters.
   - Icons to illustrate the Beam value proposition were finalized, icons
   for (Unified, Portable, extensible, and Value of the community)
   - "Powered by" page will be re-designed to include use cases from Beam
   Summit. BEAM-11225 is tracking permissions and requests to presenters.
   - Beam model illustration: Brainstormed with community members on
   changes needed and key concepts to illustrate
   - Copy for the following pages is needed: Welcome to the Beam Community,
   Contact Us, Beam Community Practices, Become a Commiter, Contribution Guide
   and Documentation Overview. Jiras to be created.

Next Sprint:

   - Finalize details on newly design pages
   - Copy for newly design pages
   - Production will start


[1]
https://docs.google.com/document/d/1CqssBpRt1EjpV0nCBaS9WGaGHt_4stKXbwMz9gYfmwc/edit
[2]
https://docs.google.com/presentation/d/1ay8eKFEi8rz18uUMDqDoBP6gEtYJTo34VZr1EXjqIZM/edit?usp=sharing

[3] https://s.apache.org/beam-site-revamp
[4] https://s.apache.org/beam-website-revamp-tdd

Re: Apache Beam case studies

[Griselda Cuevas]

For context, Polidea wants to develop more like case studies for marketing
collateral rather than UX Research.

@Karolina Rosół   it might be worth also
sending the note to the users@ list.

On Fri, 23 Oct 2020 at 00:57, Karolina Rosół 
wrote:

> Hi,
>
> @Luke thanks a mill for cc'ing Mariann :-) Let's see if there's any
> interest.
>
> Kind regards,
>
> Karolina Rosół
> Polidea  | Head of Cloud & OSS
>
> M: +48 606 630 236 <+48606630236>
> E: karolina.ro...@polidea.com
> [image: Polidea] 
>
> Check out our projects! 
> [image: Github]  [image: Facebook]
>  [image: Twitter]
>  [image: Linkedin]
>  [image: Instagram]
>  [image: Behance]
>  [image: dribbble]
> 
>
>
> On Wed, Oct 21, 2020 at 5:50 PM Luke Cwik  wrote:
>
>> +Mariann Nagy  has been doing things like this for
>> years now and may be interested.
>>
>> On Wed, Oct 21, 2020 at 12:50 AM Karolina Rosół <
>> karolina.ro...@polidea.com> wrote:
>>
>>> Hi folks,
>>>
>>> With some people from Polidea we came up with an idea to carry out
>>> interviews with Apache Beam users to spread the news about the Beam model
>>> and engage more people to use it.
>>>
>>> Ideally, we'd set up an online meeting with interested people and then
>>> do an interview. We'd like to ask questions such as 'how did you find out
>>> about Apache Beam' / 'how do you use Apache Beam in your company/product?'
>>> etc. We'd love to post the whole interview on Polidea and Apache Beam
>>> website.
>>>
>>> If any of you is interested, please let me know in this thread :-)
>>>
>>> Wish you all a happy week and stay safe!
>>>
>>> Karolina Rosół
>>> Polidea  | Head of Cloud & OSS
>>>
>>> M: +48 606 630 236 <+48606630236>
>>> E: karolina.ro...@polidea.com
>>> [image: Polidea] 
>>>
>>> Check out our projects! 
>>> [image: Github]  [image: Facebook]
>>>  [image: Twitter]
>>>  [image: Linkedin]
>>>  [image: Instagram]
>>>  [image: Behance]
>>>  [image: dribbble]
>>> 
>>>
>>

Re: Requesting Jira contributor access for Website revamp project team

[Griselda Cuevas]

Thanks everyone!

On Wed, 21 Oct 2020 at 07:18, Agnieszka Sell 
wrote:

> Hi everyone,
>
> Thank you for your answers! I added issues according to your suggestions
> Kyle :)
>
> @Griselda Cuevas  Timeline is added in the comment
> to the task you created.
>
> Best,
>
> Agnieszka
>
> On Wed, Oct 21, 2020 at 6:35 AM Griselda Cuevas  wrote:
>
>> Thank you Alexey
>>
>> On Fri, 16 Oct 2020 at 09:40, Alexey Romanenko 
>> wrote:
>>
>>> Hi Gris,
>>>
>>> It’s done.
>>>
>>> Regards,
>>> Alexey
>>>
>>> > On 16 Oct 2020, at 16:57, Gris Cuevas  wrote:
>>> >
>>> > Hi folks, could someone in the PMC provide "Contributor" roles to the
>>> following folks who will be working on the website revamp?
>>> >
>>> > Usernames: nam.bui, Milka, AgnieszkaSell, kasiazjc
>>> >
>>>
>>>
>
> --
>
> Agnieszka Sell
> Polidea <https://www.polidea.com/> | Project Manager
>
> M: *+48 504 901 334* <+48504901334>
> E: agnieszka.s...@polidea.com
> [image: Polidea] <https://www.polidea.com/>
>
> Check out our projects! <https://www.polidea.com/our-work>
> [image: Github] <https://github.com/Polidea> [image: Facebook]
> <https://www.facebook.com/Polidea.Software> [image: Twitter]
> <https://twitter.com/polidea> [image: Linkedin]
> <https://www.linkedin.com/company/polidea> [image: Instagram]
> <https://instagram.com/polidea>
>
> Unique Tech
> Check out our projects! <https://www.polidea.com/our-work>
>

Website Revamp Update - Week 1 (and how to get involved)

[Griselda Cuevas]

Hi folks, please find here [1] the updates for week 1 of the website revamp
work. This document will contain notes for every sprint, which will last
one week.

If you want to get involved in this effort here are some resources:

   - The Polidea/Utilo team will be sharing mocks and designs as they are
   available to get feedback from the community, so share your thoughts and
   suggestions!
   - @Agnieszka Sell  will create a public link
   for the weekly review meeting so anyone interesting in joining can come.
   - I created a slack channel [2] if you want to chat about this project
   with the working group

Thanks all,
G

[1]
https://docs.google.com/document/d/1CqssBpRt1EjpV0nCBaS9WGaGHt_4stKXbwMz9gYfmwc/edit
[2] https://join.slack.com/share/zt-i7u8s7vr-g8IYBC8IS3bcUmsCHmYa5Q

Re: Requesting Jira contributor access for Website revamp project team

[Griselda Cuevas]

Thank you Alexey

On Fri, 16 Oct 2020 at 09:40, Alexey Romanenko 
wrote:

> Hi Gris,
>
> It’s done.
>
> Regards,
> Alexey
>
> > On 16 Oct 2020, at 16:57, Gris Cuevas  wrote:
> >
> > Hi folks, could someone in the PMC provide "Contributor" roles to the
> following folks who will be working on the website revamp?
> >
> > Usernames: nam.bui, Milka, AgnieszkaSell, kasiazjc
> >
>
>

Re: Requesting Jira contributor access for Website revamp project team

[Griselda Cuevas]

+1 to Kyle's suggestion.

@Agnieszka Sell  - I went ahead and created
BEAM-11079 . I added the
Public PRD and created the label website-revamp-2020, let's use that to
track work on this project.

Could you add an overview of the timeline as a comment to BEAM-11079
?

On Tue, 20 Oct 2020 at 08:44, Kyle Weaver  wrote:

> > Can I ask you to provide me additional ones that will allow me to create
> a new project (Beam website revamp)?
>
> Usually we put all our issues under the BEAM project. Then we organize
> issues by setting their components and labels. I recommend using the
> existing "website" component along with a new label for the website revamp.
> You might already have permissions to create new labels; if not, please let
> us know.
>
> On Mon, Oct 19, 2020 at 11:36 PM Agnieszka Sell <
> agnieszka.s...@polidea.com> wrote:
>
>> Hi folks,
>>
>> Thank you for the Jira permissions for my team! Can I ask you to provide
>> me additional ones that will allow me to create a new project (Beam website
>> revamp)? Now I can create new boards but only for existing projects. My
>> username is Agnieszka Sell.
>>
>> Kind regards,
>>
>> Agnieszka
>>
>> On Fri, Oct 16, 2020 at 6:40 PM Alexey Romanenko <
>> aromanenko@gmail.com> wrote:
>>
>>> Hi Gris,
>>>
>>> It’s done.
>>>
>>> Regards,
>>> Alexey
>>>
>>> > On 16 Oct 2020, at 16:57, Gris Cuevas  wrote:
>>> >
>>> > Hi folks, could someone in the PMC provide "Contributor" roles to the
>>> following folks who will be working on the website revamp?
>>> >
>>> > Usernames: nam.bui, Milka, AgnieszkaSell, kasiazjc
>>> >
>>>
>>>
>>
>> --
>>
>> Agnieszka Sell
>> Polidea  | Project Manager
>>
>> M: *+48 504 901 334* <+48504901334>
>> E: agnieszka.s...@polidea.com
>> [image: Polidea] 
>>
>> Check out our projects! 
>> [image: Github]  [image: Facebook]
>>  [image: Twitter]
>>  [image: Linkedin]
>>  [image: Instagram]
>> 
>>
>> Unique Tech
>> Check out our projects! 
>>
>

Re: [Proposal] Website Revamp project

[Griselda Cuevas]

Thanks Robert.

I have talked to the team who will be working on the redesign, and we are
going to take on the following tasks to make the work more manageable:

1) Work will be managed in Jira by myself and Agnieszka
2) Agnieszka will be sharing weekly updates in the dev@ list, these update
will have calls for feedback so the community can chime in
3) We'll host weekly calls that anyone in the community can join

We hope that #1 and #2 can provide visibility in what to expect on the
review side.


On Mon, 19 Oct 2020 at 10:01, Robert Bradshaw  wrote:

> Welcome. Looking forward to the website improvements.
>
> I would like to call out that it'd be a good idea to have a plan for how
> this can be developed/reviewed incrementally. We were able to get the last
> major website change in, but huge monolithic PRs that change the world are
> difficult to review and integrate, so it'd be good to have a plan upfront
> (learning from or experience last time).
>
> On Fri, Oct 16, 2020 at 1:24 PM Alexey Romanenko 
> wrote:
>
>> Welcome to Beam!
>>
>> Regards,
>> Alexey
>>
>> On 15 Oct 2020, at 16:06, Nam Bui  wrote:
>>
>> Hi everyone,
>>
>> I'm Nam. I used to work on Apache Beam website migration. From now on, I
>> will be responsible for website development. Thus, I will implement new
>> designs and some of the functionalities on our website. Great to be working
>> with you!
>>
>> Best regards,
>> Nam
>>
>>
>>
>> On Thu, Oct 15, 2020 at 8:42 PM Kasia Zając 
>> wrote:
>>
>>> Hi all,
>>>
>>> I am Kasia and I will be responsible for the UX side of things in the
>>> project. I will be preparing the wireframes and also asking you for
>>> feedback later in the process. Happy to join the community at least for a
>>> short amount of time :)
>>>
>>> Have a good day,
>>> Kasia Zając
>>> Product Owner
>>> +48 664 115 440 <+48664115440>
>>> ka...@utilodesign.com
>>> [image: utilo] 
>>>
>>> www.utilodesign.com
>>> [image: Behance]  [image:
>>> dribbble]  [image: Instagram]
>>>  [image: Linkedin]
>>> 
>>>
>>>
>>> On Thu, Oct 15, 2020 at 2:12 PM Agnieszka Sell <
>>> agnieszka.s...@polidea.com> wrote:
>>>
 Hi Everyone,

 I'm Agnieszka Sell, Project Manager in the Beam website revamp project.

 I'm looking forward to getting your feedback on design and development
 progress we'll be sharing with you in upcoming weeks.

 Best,

 Agnieszka

 On Wed, Oct 14, 2020 at 7:06 PM Gris Cuevas  wrote:

> Hi Everyone,
>
> We're ready to start work on the revamp of the website, we'll use the
> PRD shared in this thread previously.
>
> Polidea will be the team working on this revamp and we'll be bringing
> designs and proposals to the community for review as the project
> progresses.
>
> Thank you!
> Gris
>
> On 2020/09/09 18:14:18, Gris Cuevas  wrote:
> > Hi Beam community,
> >
> > In a previous thread [1] I mentioned that I was going to work on
> product requirements document (PRD) for a project to address some of the
> requests and ideas collected by Aizhamal, Rose and David in previous
> efforts.
> >
> > The PRD is ready [2], and I'd like to get your feedback before
> moving forward into implementation. Please add you comments by Sunday
> Septermber 13, 2020.
> >
> > We're looking to start work on this project in around 2 weeks.
> >
> > Thank you!
> > Gris
> >
> > [1]
> https://lists.apache.org/thread.html/r1a4cea1e8b53bef73c49f75df13956024d8d78bc81b36e54ef71f8a9%40%3Cdev.beam.apache.org%3E
> >
> > [2] https://s.apache.org/beam-site-revamp
> >
>


 --
 Agnieszka Sell
 Polidea  | Project Manager
 M: *+48 504 901 334* <+48504901334>
 E: agnieszka.s...@polidea.com
 [image: Polidea] 

 Check out our projects! 
 [image: Github]  [image: Facebook]
  [image: Twitter]
  [image: Linkedin]
  [image: Instagram]
 

 Unique Tech
 Check out our projects! 

>>>
>>

Notification of analysis on publicly available project data

[Griselda Cuevas]

Dear PMC,


I’m contacting you because your project has been selected by the ASF D
committee which is leading a research project to evaluate and understand
the current state of diversity in our community [1]. As part of this
research, we will analyze publicly available data about your project such
as Git logs, Jira boards and mailing lists, to better understand the state
of diversity in Apache projects and to complement the findings we obtained
from the Community Survey that was run this year [2].


This analysis will be performed by Bitegia [3], a vendor specializing in
researching open source projects and foundations. The results will be
published in a report similar to the OpenStack Foundation Analysis
published in 2018 [4].


The analysis will be done only on aggregated data at the project level during
and after processing, ensuring we do not report anything that could
identify a single individual. The data we analyze will be deleted right
after the research is done and won’t be retained by either the researcher
or the ASF.


If you have any concerns or questions, please raise them to the diversity
committee (d...@diversity.apache.org) and/or to the data privacy committee (
priv...@apache.org).


Regards,

Griselda Cuevas

V.P. of Diversity and Inclusion

Apache Software Foundation


[1]
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=127405614

[2] https://youtu.be/4Mr1CRtKqUI

[3] https://bitergia.com/bitergia-analytics/

[4] https://superuser.openstack.org/articles/2018-gender-diversity-report/

Making reporting bugs/feature request easier

[Griselda Cuevas]

Hi folks,

I recently made a few Jira boards [1][2] to help triage and organize Beam's
backlog.


Something that came to my mind is that reporting bugs and feature requests
using Jira might be imposing a high barrier for users who don't have an
account. This process might also make it difficult to ask follow-up
questions to reporters who don't monitor Jira's notifications.


I want to gather consensus on updating the website to give the option to
report bugs and feature requests by sending an email to users@b.a.o and
adding a tag to the subject line ([bug] OR [New Feature])


There are other more sustainable solutions, like looking into using GitHub
issues, but they will have other costs, like migrating current tickets and
systems, pointing them out here in case we want to consider.


Let me know what you think,

G


[1]
https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12335922#

[2]
https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12335923#

[3] https://beam.apache.org/contribute/

[4] https://beam.apache.org/community/contact-us/

Jira Board to track most Beam's tickets

[Griselda Cuevas]

Hi folks,

I made this Jira board [1] to help us have visibility into our project's
tickets.

Right now, the first view shows a filter of the most watched tickets with
key metrics, like the number of watchers, votes, date it was created, time
of last comment and the issue description. The bubble view offers a
correlation between the most watched tickets, the time they've been open
and the number of interactions on it, red means high correlation and a
possible interpretation is that these tickets have a high level of
interest/urgency.

One of the uses I want this board to have is to help us triage issues we
haven't triage yet, so I will add that next.

Do you have any suggestions into what view we should add?
Any questions you'd like to see answers for in the Dashboard?

Thanks!
G

[1]
https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12335849

Usage metrics for Beam

[Griselda Cuevas]

Hi folks - I'm interested in knowing more about Beam's adoption through
user downloads.

Do you know what's the protocol to access Maven and check on Java
downloads?

Also - do you have any other recos on how to measure the project's adoption
evolution?

Thanks!
G

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

[Griselda Cuevas]

Hola Ismael - creo que María te iba a preguntar de los viáticos. Estoy
viendo con Google México lo del patrocinio.

Si lo confirman podemos cubrir tus viáticos si Talend no lo cubre.

También en Octubre 3 y 4 haremos otro evento en GDL y me encantaría si
dieras el workshop de Beam. Es dos días y GDL está increíble.

Podrías en esas fechas?

El evento es ccoss.org

Saludos!

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

[Discuss] Beam Summit 2020 Dates & locations

[Griselda Cuevas]

Hi Beam Community!

I'd like to kick off a thread to discuss potential dates and venues for the
2020 Beam Summits.

I did some research on industry conferences happening in 2020 and
pre-selected a few ranges as follows:

(2 days) NA between mid-May and mid-June
(2 days) EU mid October
(1 day) Asia Mini Summit:  March

I'd like to hear your thoughts on these dates and get consensus on exact
dates as the convo progresses.

For locations these are the options I reviewed:

*NA: *Austin Texas, Berkeley California, Mexico City.
*Europe: *Warsaw, Barcelona, Paris
Asia: Singapore

Let the discussion begin!
G (on behalf of the Beam Summit Steering Committee)

Re: [ANNOUNCE] New committer announcement: Yifan Zou

[Griselda Cuevas]

Congrats Yifan!




On Mon, 22 Apr 2019 at 08:26, Kenneth Knowles  wrote:

> Hi all,
>
> Please join me and the rest of the Beam PMC in welcoming a new committer:
> Yifan Zou.
>
> Yifan has been contributing to Beam since early 2018. He has proposed 70+
> pull requests, adding dependency checking and improving test
> infrastructure. But something the numbers cannot show adequately is the
> huge effort Yifan has put into working with infra and keeping our Jenkins
> executors healthy.
>
> In consideration of Yian's contributions, the Beam PMC trusts Yifan with
> the responsibilities of a Beam committer [1].
>
> Thank you, Yifan, for your contributions.
>
> Kenn
>
> [1] https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-
> committer
>

Re: Hello from Hannah Jiang

[Griselda Cuevas]

Welcome Hannah! - Very excited to see you in the Beam community :)

On Tue, 23 Apr 2019 at 12:59, Hannah Jiang  wrote:

> Hi everyone
>
> I joined Google recently and would work on Python portability part. I am
> happy to be part of the community. Looking forward to working with all of
> you together.
>
> I have a minor request, can admin please give me access to JIRA?
>
> Thanks,
> Hannah
>
>
>

Re: Another New Contributor

[Griselda Cuevas]

Hi Connell - I just found out about Apache Kibble a project made to track
community metrics. I will check this when I come back from vacation and
start checking the progress Beam has had.

Thanks!
G


Gris Cuevas Zambrano

Open Source Strategist

+1 (650) 772-2947

345 Spear Street, San Francisco, 94105




On Sat, 9 Feb 2019 at 14:16, Thomas Weise  wrote:

> Hi Tanay,
>
> Welcome to the project! I just added you as contributor in JIRA.
>
> Thomas
>
> On Sat, Feb 9, 2019 at 11:12 AM Tanay Tummapalli 
> wrote:
>
>> Hey Everyone
>>
>> I am a computer science student from Delhi. I am currently in my senior
>> year at Maharaja Surajmal Institute of Technology, Delhi. I just got done
>> with my internship at SocialCops - an Indian Data Intelligence Startup. I
>> had to build a streaming pipeline there as part of my internship. While
>> studying for it, I read about Apache Beam in the Streaming Systems book
>> written by Tyler Akidau, Reuven Lax and Slava Chernyak.
>>
>> I want to contribute to Open Source this summer as part of Google Summer
>> of Code, or even otherwise. Apache Beam is an exciting project!
>>
>> Can you please add me to Apache Beam JIRA? I want to start contributing.
>> My ASF JIRA username is ttanay.
>>
>> Cheers!
>> Tanay Tummalapalli
>>
>>

Re: 2019 Beam Events

[Griselda Cuevas]

+1 to Pablo's suggestion, if there's interest in "Founding a Meetup group
in a particular city, let's create the Meetup page and start getting sign
ups. Joana will be reaching out with a comprenhexive list of how to get
started and we're hoping to compile a high level calendar of
launches/announcements to feed into your meetup.

G

On Tue, 4 Dec 2018 at 12:04, Daniel Salerno  wrote:

> =)
> What good news!
> Okay, I'll set up the group and try to get interested.
> Thank you
>
>
> Em ter, 4 de dez de 2018 às 17:19, Pablo Estrada 
> escreveu:
>
>> FWIW, for some of these places that have interest (e.g. Brazil, Israel),
>> it's possible to create a group in meetup.com, and start gauging
>> interest, and looking for organizers.
>> Once a group of people with interest exists, it's easier to get interest
>> / sponsorship to bring speakers.
>> So if you are willing to create the group in meetup, Daniel, we can
>> monitor it and try to plan something as it grows : )
>> Best
>> -P.
>>
>> On Tue, Dec 4, 2018 at 10:55 AM Daniel Salerno 
>> wrote:
>>
>>>
>>> It's a shame that there are no events in Brazil ...
>>>
>>> =(
>>>
>>> Em ter, 4 de dez de 2018 às 13:12, OrielResearch Eila Arich-Landkof <
>>> e...@orielresearch.org> escreveu:
>>>
>>>> agree 
>>>>
>>>> On Tue, Dec 4, 2018 at 5:41 AM Chaim Turkel  wrote:
>>>>
>>>>> Israel would be nice to have one
>>>>> chaim
>>>>> On Tue, Dec 4, 2018 at 12:33 AM Griselda Cuevas 
>>>>> wrote:
>>>>> >
>>>>> > Hi Beam Community,
>>>>> >
>>>>> > I started curating industry conferences, meetups and events that are
>>>>> relevant for Beam, this initial list I came up with. I'd love your help
>>>>> adding others that I might have overlooked. Once we're satisfied with the
>>>>> list, let's re-share so we can coordinate proposal submissions, attendance
>>>>> and community meetups there.
>>>>> >
>>>>> >
>>>>> > Cheers,
>>>>> >
>>>>> > G
>>>>> >
>>>>> >
>>>>> >
>>>>>
>>>>> --
>>>>>
>>>>>
>>>>> Loans are funded by
>>>>> FinWise Bank, a Utah-chartered bank located in Sandy,
>>>>> Utah, member FDIC, Equal
>>>>> Opportunity Lender. Merchant Cash Advances are
>>>>> made by Behalf. For more
>>>>> information on ECOA, click here
>>>>> <https://www.behalf.com/legal/ecoa/>. For important information about
>>>>> opening a new
>>>>> account, review Patriot Act procedures here
>>>>> <https://www.behalf.com/legal/patriot/>.
>>>>> Visit Legal
>>>>> <https://www.behalf.com/legal/> to
>>>>> review our comprehensive program terms,
>>>>> conditions, and disclosures.
>>>>>
>>>>
>>>>
>>>> --
>>>> Eila
>>>> www.orielresearch.org
>>>> https://www.meetu <https://www.meetup.com/Deep-Learning-In-Production/>
>>>> p.co <https://www.meetup.com/Deep-Learning-In-Production/>
>>>> m/Deep-Learning-In-Production/
>>>> <https://www.meetup.com/Deep-Learning-In-Production/>
>>>>
>>>>
>>>>

2019 Beam Events

[Griselda Cuevas]

Hi Beam Community,

I started curating industry conferences, meetups and events that are
relevant for Beam, this initial list I came up with
.
*I'd love your help adding others that I might have overlooked.* Once we're
satisfied with the list, let's re-share so we can coordinate proposal
submissions, attendance and community meetups there.


Cheers,

G

Re: Stand at FOSDEM 2019

[Griselda Cuevas]

+1 -- I'm happy to help with the merch, I'll be attending and will help
staff the booth :)

G

On Thu, 29 Nov 2018 at 05:46, Suneel Marthi  wrote:

> +1
>
> On Thu, Nov 29, 2018 at 6:14 AM Matthias Baetens <
> baetensmatth...@gmail.com> wrote:
>
>> Hey Max,
>>
>> Great idea. I'd be very keen to join. I'll look at my calendar over the
>> weekend to see if this would work.
>> Are you going yourself?
>>
>> Cheers,
>> Matthias
>>
>> On Thu, 29 Nov 2018 at 11:06 Maximilian Michels  wrote:
>>
>>> Hi,
>>>
>>> For everyone who might be attending FOSDEM19: What do you think about
>>> taking a slot for Beam at the Apache stand?
>>>
>>> A slot is 2-3 hours. It is a great way to spread the word about Beam. We
>>> wouldn't have to prepare much, just bring some merch.
>>>
>>> There is still plenty of space:
>>> https://cwiki.apache.org/confluence/display/COMDEV/FOSDEM+2019
>>>
>>> Cheers,
>>> Max
>>>
>>> PS: FOSDEM is an open-source conference in Brussels, Feb 2-3, 2019
>>>
>> --
>>
>>
>

Agenda for the Beam Summit London 2018

[Griselda Cuevas]

Hi Beam Community,

We have finalized the agenda for the Beam Summit London 2018, it's here:
https://www.linkedin.com/feed/update/urn:li:activity:6450125487321735168/


We had a great amount of talk proposals, thank you so much to everyone who
submitted one! We also sold out the event, so we're very excited to see the
community growing.


See you around,

Gris on behalf of the Organizing Committee

Re: [ANNOUNCEMENT] New Beam chair: Kenneth Knowles

[Griselda Cuevas]

Thank you so much Davor for all the work you put into the project since its
inception.
Congrats Kenn on becoming the new Chair!

On Thu, 20 Sep 2018 at 12:54, Neelesh Salian 
wrote:

> Congratulation Kenn!
> Thank you for your continued leadership , Davor.
>
> On Wed, Sep 19, 2018 at 12:54 PM Davor Bonaci  wrote:
>
>> Hi everyone --
>> It is with great pleasure that I announce that at today's meeting of the
>> Foundation's Board of Directors, the Board has appointed Kenneth Knowles as
>> the second chair of the Apache Beam project.
>>
>> Kenn has served on the PMC since its inception, and is very active and
>> effective in growing the community. His exemplary posts have been cited in
>> other projects. I'm super happy to have Kenn accepted the nomination, and
>> I'm confident that he'll serve with distinction.
>>
>> As for myself, I'm not going anywhere. I'm still around and will be as
>> active as I have recently been. Thrilled to be able to pass the baton to
>> such a key member of this community and to have less administrative work to
>> do ;-).
>>
>> Please join me in welcoming Kenn to his new role, and I ask that you
>> support him as much as possible. As always, please let me know if you have
>> any questions.
>>
>> Davor
>>
>
>
> --
> Regards,
> Neelesh S. Salian
>
>

Re: Apache Beam Newsletter - September 2018

[Griselda Cuevas]

Thank you so much for helping us put this together Rose!

And thanks everyone who contributed, is so good to see how our
contributions grow and how much more events we're representing Beam at!




On Mon, 10 Sep 2018 at 19:56, Rose Nguyen  wrote:

>
> [image: Beam.png]
>
> September 2018 | Newsletter
>
>
> What’s been done
>
>
> CI improvement (by: Etienne Chauchot)
>
>-
>
>For each new commit on master Nexmark suite is run in both batch and
>streaming mode in Spark, Flink, Cloud Dataflow (thanks to Andrew) and
>dashboards graphs are produced to track functional and performance
>regressions.
>
>
> Elasticsearch IO Supports Version 6 (by: Dat Tran)
>
>-
>
>Elasticsearch IO now supports version 6.x in addition to version 2.x
>and 5.x.
>-
>
>See the merged PR
>
>for more details.
>
>
> KuduIO Added (by: Tim Robertson)
>
>-
>
>Apache Beam master now has KuduIO that will be released with Beam
>2.7.0.
>-
>
>See BEAM-2661  for
>more details.
>
>
>
> What we’re working on...
>
>
> Flink Portable Runner (by: Ankur Goenka, Maximilian Michels, Thomas
> Weise, Ryan Williams)
>
>-
>
>Support for streaming side inputs merged
>
>-
>
>Portable Compatibility Matrix tests pass in streaming mode
>
>-
>
>Many more ValidatesRunner tests pass (ValidatesRunner is a
>comprehensive suite for Beam test pipelines)
>-
>
>Python Pipelines can be tested without bringing up a JobServer first
>(it is started in a container)
>-
>
>Experimental support for executing the SDK harnesses in a process
>instead of a Docker container
>-
>
>Bug fixes to Beam discovered during working on the portability
>
> State and Timer Support in Python SDK (by: Charles Chen, Robert Bradshaw)
>
>-
>
>This change adds the reference DirectRunner implementation of the
>Python User State and Timers API. With this change, a user can execute
>DoFns with state and timers on the DirectRunner.
>-
>
>See the design doc
> and PR
> for more details..
>
>
> New IO - HadoopOutputFormatIO (by: Alexey Romanenko)
>
>-
>
>Adding support of MapReduce OutputFormat.
>-
>
>See BEAM-5310  for
>more details.
>
>
> High-level Java 8 DSL (by: David Moravek, Vaclav Plajt, Marek Simunek)
>
>-
>
>Adding high-level Java 8 DSL based on Euphoria API
> project
>-
>
>See BEAM-3900  for
>more details.
>
> Performance improvements for HDFS file writing operations (by: Tim
> Robertson)
>
>-
>
>Autocreate directories when doing an HDFS rename
>-
>
>See PR  for more details
>
>
> Recognition of non-code contributions (by: Gris Cuevas)
>
>-
>
>Got consensus about recognizing non-code contributions
>-
>
>See
>
> 
>discussion for more details
>-
>
>Planned launch date: Beam Summit London (October 2nd)
>
>
> Weekly Community Updates (by: Gris Cuevas)
>
>-
>
>Some of the project’s subcomponents run weekly updates in the mailing
>list, we’ll be consolidating best practices to share a weekly community
>update with all project related must knows in a shell
>
>
>
> What’s planned
>
>
> Beam Cookbook (by: Austin Bennett, David Cavazos, Gris Cuevas, Andrea
> Foegler, Rose Nguyen, Connell O'Callaghan, and you!)
>
>-
>
>We are creating a cookbook for common data science tasks in Beam and
>have started brainstorming
>-
>
>We want to have a hackathon after the London Summit to generate
>content from the community
>-
>
>There will be a session at the summit to gather more ideas and input.
>Watch the dev and users mailing list for a call for contributions soon!.
>
>
> Beam 2.7.0 release (by: Charles Chen)
>
> Beam Mascot (by: Gris Cuevas & Community!)
>
>-
>
>We got approval to launch a contest to create a new Apache Beam mascot
>-
>
>See
>
>discussion for more details, if you’re interested in driving this, reach
>out in the thread!
>-
>
>Planned launch date: Last week of September
>
>
>
> New Members
>
>
> New Contributors
>
>-
>
>Đạt Trần, Ho Chi Minh City, Vietnam
>-
>
>   See BEAM-5107
>   
>   for more details on “Support ES-6.x for ElasticsearchIO”
>   -
>
>Ravi Pathak, Copenhagen, Denmark
>-
>
>   Using Beam for indexing 

Re: [ANNOUNCE] Apache Beam 2.6.0 released!

[Griselda Cuevas]

Thanks Pablo!





On Thu, 9 Aug 2018 at 15:24, Ismaël Mejía  wrote:

> Two really interesting features in 2.6.0 not mentioned in the announcement
> email:
>
>
> - Bounded SplittableDoFn support is available now in all runners (SDF is
> the new IO connector API).
>
> - HBaseIO was updated to be the first IO supporting Bounded SDF (using
> readAll).
>
>
>
>
> On Fri, Aug 10, 2018 at 12:14 AM Connell O'Callaghan 
> wrote:
>
>> Pablo and all involved thank you for working to get this release
>> completed!!!
>>
>> On Thu, Aug 9, 2018 at 3:06 PM Pablo Estrada  wrote:
>>
>>> Of course, I messed that link up again. The release notes should be here:
>>>
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527=12343392
>>>
>>> On Thu, Aug 9, 2018 at 10:11 AM Pablo Estrada 
>>> wrote:
>>>
 As was pointed out to me by Ryan Williams, the link I posted with the
 release notes is not right. Here is a link with Beam 2.6.0 release notes
 for those interested:

 https://issues.apache.org/jira/projects/BEAM/versions/12343392

 On Thu, Aug 9, 2018 at 9:41 AM Alexey Romanenko <
 aromanenko@gmail.com> wrote:

> Great news!
> Thanks to Pablo for driving this and to all contributors of this
> release!
>
>
> On 9 Aug 2018, at 00:48, Pablo Estrada  wrote:
>
> The Apache Beam team is pleased to announce the release of 2.6.0
> version!
>
> Apache Beam is an open source unified programming model to define and
> execute data processing pipelines, including ETL, batch and stream
> (continuous) processing. See https://beam.apache.org
>
> You can download the release here:
>
> https://beam.apache.org/get-started/downloads/
>
> This release includes the following major new features & improvements,
> among others:
> - Improvements for internal Context Management in Python SDK
> - A number of improvements to the Portability Framework
> - A Universal Local Runner has been added to Beam. This runner runs in
> a single machine using portability, and containerized SDK harnesses.
> - Increased the coverage of ErrorProne analysis of the codebase.
> - Updates to various dependency versions
> - Updates to stability, performance, and documentation.
> - SQL - improvements: support exists operator, implemented sum()
> aggregations, fixes to CASE expression, support for date comparison,
> support LIMIT on Unbounded Data
> - Provide automatic schema registration for POJOs
>
> You can take a look at the Release Notes for more details:
>
> *https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12343392=12319527
> *
>
> Thanks to everyone who participated in this release, and we hope
> you'll have a good time using Beam 2.6.0.
> --
> Pablo Estrada, on behalf of The Apache Beam team
> --
> Got feedback? go/pabloem-feedback
> 
>
>
> --
 Got feedback? go/pabloem-feedback
 

>>> --
>>> Got feedback? go/pabloem-feedback
>>> 
>>>
>>

Re: [Proposal] Track non-code contributions in Jira

[Griselda Cuevas]

Thanks all for the votes and comments.

re:Jira - I hear and understand all questions about Jira not being the
absolute best option, however I think the positive points are strong enough
to still use is as primary option.

re: Taxonomy - The Project Management I refer to in #1 are more tasks like,
clean-up Stale Jira tickets or ensure releases are on time. Therefore I
would leave it as a separate option.

Thanks all for your valuable comments, I'll proceed to implement this.

G




On Fri, 24 Aug 2018 at 12:09, Hadar Hod  wrote:

> +1
>
> On Fri, Aug 24, 2018 at 11:50 AM Henning Rohde  wrote:
>
>> +1
>>
>> On Fri, Aug 24, 2018 at 11:44 AM Rose Nguyen  wrote:
>>
>>> +1 Great idea
>>>
>>> On Fri, Aug 24, 2018 at 10:01 AM Mikhail Gryzykhin 
>>> wrote:
>>>
>>>> +1. Idea sounds great.
>>>>
>>>> --Mikhail
>>>>
>>>> Have feedback <http://go/migryz-feedback>?
>>>>
>>>>
>>>> On Fri, Aug 24, 2018 at 7:19 AM Maximilian Michels 
>>>> wrote:
>>>>
>>>>> +1 Code is just one part of a successful open-source project. As long
>>>>> as
>>>>> the tasks are properly labelled and actionable, I think it works to
>>>>> put
>>>>> them into JIRA.
>>>>>
>>>>> On 24.08.18 15:09, Matthias Baetens wrote:
>>>>> >
>>>>> > I fully agree and think it is a great idea.
>>>>> >
>>>>> > I think that, next to visibility and keeping track of everything
>>>>> that is
>>>>> > going on in the community, the other goal would be documenting best
>>>>> > practices for future use.
>>>>> >
>>>>> > I am also not sure, though, if JIRA is the best place to do so, as
>>>>> > Austin raised.
>>>>> > Introducing (yet) another tool on the other hand, might also not be
>>>>> > ideal. Has anyone else experience with this from other Apache
>>>>> projects?
>>>>> >
>>>>> > On Fri, 24 Aug 2018 at 06:04 Austin Bennett <
>>>>> whatwouldausti...@gmail.com
>>>>> > <mailto:whatwouldausti...@gmail.com>> wrote:
>>>>> >
>>>>> > Certainly tracking and managing these are important -- though, is
>>>>> > Jira the best tool for these things?
>>>>> >
>>>>> > I do see it useful to put in Jira tickets in for my director to
>>>>> have
>>>>> > conversations on specific topics with people, for consensus
>>>>> > building, etc etc.  So, I have seen it work even for non-coding
>>>>> tasks.
>>>>> >
>>>>> > It seems like much of #s 2-6 mentioned requires project
>>>>> management
>>>>> > applied to those specific domains and is applicable elsewhere,
>>>>> > wondering what constitutes "pure" project management in #1 (as it
>>>>> > applies here)...?  In that light I'm just getting picky about
>>>>> > taxonomy :-)
>>>>> >
>>>>> >
>>>>> >
>>>>> >
>>>>> >
>>>>> > On Thu, Aug 23, 2018 at 3:10 PM Alan Myrvold <
>>>>> amyrv...@google.com
>>>>> > <mailto:amyrv...@google.com>> wrote:
>>>>> >
>>>>> > I like the idea of recognizing non-code contributions. These
>>>>> > other efforts have been very helpful.
>>>>> >
>>>>> > On Thu, Aug 23, 2018 at 3:07 PM Griselda Cuevas <
>>>>> g...@google.com
>>>>> > <mailto:g...@google.com>> wrote:
>>>>> >
>>>>> > Hi Beam Community,
>>>>> >
>>>>> > I'd like to start tracking non-code contributions for
>>>>> Beam,
>>>>> > specially around these six categories:
>>>>> > 1) Project Management
>>>>> > 2) Community Management
>>>>> > 3) Advocacy
>>>>> > 4) Events & Meetups
>>>>> > 5) Documentation
>>>>> > 6) Training
>>>>> >
>>>>> > The proposal would be to create six boards in Jira, one
>>>>> per
>>>>> > proposed category, and as part of this initiative also
>>>>> clean
>>>>> > the already existing "Project Management" component, i.e.
>>>>> > making sure all issues there are still relevant.
>>>>> >
>>>>> > After this, I'd also create a landing page in the website
>>>>> > that talks about all types of contributions to the
>>>>> project.
>>>>> >
>>>>> > The reason for doing this is mainly to give visibility to
>>>>> > some of the great work our community does beyond code
>>>>> pushes
>>>>> > in Github. Initiatives around Beam are starting to spark
>>>>> > around the world, and it'd be great to become an Apache
>>>>> > project recognized for our outstanding community
>>>>> recognition.
>>>>> >
>>>>> > What are your thoughts?
>>>>> > G
>>>>> >
>>>>> > Gris
>>>>> >
>>>>> > --
>>>>>
>>>>> --
>>>>> Max
>>>>>
>>>>
>>>
>>> --
>>>
>>>
>>> Rose Thi Nguyen
>>>
>>>   Technical Writer
>>>
>>> (281) 683-6900
>>>
>>

[Perk] Sharing the love for Flink Forward

[Griselda Cuevas]

Hi Beam Community!

As you know, Apache Beam is a big supporter of Apache Flink - pun intended
;) - and because Google Cloud is a proud sponsor of Flink Forward we have
10 passes for members of our Apache Beam community to attend the event in
Berlin this Sept. 3rd & 4th for free.

If you're interested in one of the passes please reach out to me
(gris[at]apache[dot]org), the only requisite is obviously that you love the
Flink+Beam combo.

Happy Friday!
G

Re: [PROPOSAL] Prepare Beam 2.7.0 release

[Griselda Cuevas]

+1 Thanks for volunteering and keeping us in schedule!




On Thu, 23 Aug 2018 at 11:58, Udi Meiri  wrote:

> +1
>
> On Mon, Aug 20, 2018 at 3:33 PM Boyuan Zhang  wrote:
>
>> +1
>> Thanks for volunteering, Charles!
>>
>> On Mon, Aug 20, 2018 at 3:22 PM Rafael Fernandez 
>> wrote:
>>
>>> +1, thanks for volunteering, Charles!
>>>
>>> On Mon, Aug 20, 2018 at 12:09 PM Charles Chen  wrote:
>>>
 Thank you Andrew for pointing out my mistake.  We should follow the
 calendar and aim to cut on 8/29, not 9/7 as I incorrectly wrote earlier.

 On Mon, Aug 20, 2018 at 12:02 PM Andrew Pilloud 
 wrote:

> +1 Thanks for volunteering! The calendar I have puts the cut date at
> August 29th, which looks to be 6 weeks from when 2.6.0 was cut. Do I have
> the wrong calendar?
>
> See:
> https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com=America%2FLos_Angeles
>
> Andrew
>
> On Mon, Aug 20, 2018 at 11:43 AM Connell O'Callaghan <
> conne...@google.com> wrote:
>
>> +1 Charles thank you for taking this up and helping us maintain this
>> schedule.
>>
>> On Mon, Aug 20, 2018 at 11:29 AM Charles Chen  wrote:
>>
>>> Hey everyone,
>>>
>>> Our release calendar indicates that the process for the 2.7.0 Beam
>>> release should start on September 7.
>>>
>>> I volunteer to perform this release and propose the following
>>> schedule:
>>>
>>>- We start triaging issues in JIRA this week.
>>>- I will cut the initial 2.7.0 release branch on September 7.
>>>- After September 7, any blockers will need to be manually
>>>cherry-picked into the release branch.
>>>- After tests pass and blockers are fully addressed, I will move
>>>on and perform other release tasks.
>>>
>>> What do you think?
>>>
>>> Best,
>>> Charles
>>>
>>

Re: [Proposal] Beam Mascot

[Griselda Cuevas]

Very well, I'll kick this off!

On Thu, 23 Aug 2018 at 16:24, Davor Bonaci  wrote:

> I'd like to get input from the PMC on how this should be pursued (people
>>> at the foundation who need to be involved, permissions needed, etc.), could
>>> you advice?
>>>
>>
> Please proceed as you see fit. Nothing is needed, no restrictions.
>
> NB: the moment vote passes (and/or the mascot is contributed to the
> website), its usage by third parties requires written approval (in most
> cases).
>
> Thanks for asking.
>
>>

[Proposal] Track non-code contributions in Jira

[Griselda Cuevas]

Hi Beam Community,

I'd like to start tracking non-code contributions for Beam, specially
around these six categories:
1) Project Management
2) Community Management
3) Advocacy
4) Events & Meetups
5) Documentation
6) Training

The proposal would be to create six boards in Jira, one per proposed
category, and as part of this initiative also clean the already existing
"Project Management" component, i.e. making sure all issues there are still
relevant.

After this, I'd also create a landing page in the website that talks about
all types of contributions to the project.

The reason for doing this is mainly to give visibility to some of the great
work our community does beyond code pushes in Github. Initiatives around
Beam are starting to spark around the world, and it'd be great to become an
Apache project recognized for our outstanding community recognition.

What are your thoughts?
G

Gris

[Proposal] Beam Mascot

[Griselda Cuevas]

Hi Folks,

I'm interested in launching a community contest to design a mascot for
Apache Beam. I'd like to get input from the PMC on how this should be
pursued (people at the foundation who need to be involved, permissions
needed, etc.), could you advice?

Here's a point-by-point description of the contest as I envision it:

   - Send call for participation with a few guidelines (around brand for
   Beam)
   - Open the contest submissions for 2 weeks
   - Send proposed designs to the mailing list for votes
   - Open votes to select the winner for 72h
   - The design that wins will be announced at the Beam Summit and the
   creator will get a symbolic prize as well as recognition at the Summit


Thanks,
G

[Event] Open Source Challenge Mexico

[Griselda Cuevas]

Hi Beam Community,

The First Open Source Challenge Mexico is taking place today in IBM
Guadalajara Campus. The purpose of this event was to give Mexican Engineers
the opportunity to contribute to Open Source Projects. The two projects
that were the focus of this event were Blue Xolo and Apache Beam.

*We have had 8 engineers contributing to 5 Jira issues so far. *This has
been a great experience for the community and for the folks participating
in the challenge. Arianne Navarro, the organizer of this event, will share
with us more data and impact metrics after the competition ends, in the
mean time, here are some pictures of this great session [1].

I hope you enjoy!
G


P.S. If you'd be interested in hosting a Beam Hackathon, reach out via this
thread or the beam-events-meetups Slack channel [2].

[1]
https://drive.google.com/drive/folders/1RXgCbkXuduzWd4WDIfbhyr0ktzP0iLVk?usp=sharing

[2]
https://the-asf.slack.com/messages/CA8D5DPHQ/convo/CA8D5DPHQ-1534357996.000100/

Re: Apache Beam Newsletter - August 2018

[Griselda Cuevas]

Thanks for compiling and sending Rose!


On Fri, 10 Aug 2018 at 13:09, Pablo Estrada  wrote:

> Thank you for compiling this Rose! Interesting stories and news.
> -P.
>
> On Fri, Aug 10, 2018 at 12:37 PM Rose Nguyen  wrote:
>
>> [image: Beam.png]
>>
>> August 2018 | Newsletter
>>
>> What’s been done
>>
>> [image: Tick - done]
>>
>> Apache Beam 2.6.0 Release
>>
>>-
>>
>>The Apache Beam team is pleased to announce the release of 2.6.0
>>version! This is the second release under the new build system, and
>>the process has kept improving.
>>-
>>
>>You can download the release here
>> and read the release
>>notes
>>
>> 
>>for more details.
>>
>>
>> Beam Summit London 2018 (by: Matthias Baetens, Gris Cuevas, Viktor Kotai)
>>
>>-
>>
>>Approval from the Apache Software Foundation is underway. We are
>>currently finding a venue and sponsors. We’ll send the call for
>>participation soon to curate the agenda.
>>-
>>
>>If you’re interested in participating in the organization of the
>>event, reach out to the organizers.
>>-
>>
>>Dates TBD be we are considering the first or last days of October.
>>
>>
>> Support for Bounded SDF in all runners (by: Eugene Kirpichov)
>>
>>-
>>
>>Beam introduced recently a new type of DoFn called SplittableDoFn
>> (SDF)
>>to enable richer modularity in its IO connectors.
>>-
>>
>>Support for SDF in bounded (batch) connectors was added for all
>>runners.
>>
>> Apache Kudu IO (by: Tim Robertson)
>>
>>-
>>
>>A new IO connector for the Apache Kudu
>> data
>>store was added recently.
>>-
>>
>>See BEAM-2661 for more details on it.
>>
>>
>> IO improvements (by: Ismaël Mejía)
>>
>>-
>>
>>HBaseIO added a new transform based on SDF called readAll.
>>-
>>
>>See BEAM-4020 for more details on it.
>>
>>
>>
>> What we’re working on...
>>
>> Interactive Runner for Beam (by: Harsh Vardhan, Sindy Li, Chamikara
>> Jayalath, Anand Iyer, Robert Bradshaw)
>>
>>-
>>
>>Notebook-based interactive processing of Beam pipelines.
>>-
>>
>>This is now ready to try out in Jupyter Notebook for BeamPython
>>pipelines over DirectRunner!
>>-
>>
>>See the design doc  for more
>>details and watch a demo here
>>.
>>-
>>
>>Thoughts, comments and discussions welcome :)
>>
>>
>> Python 3 Support (by, in alphabetical order: Ahmet Altay,  Robert
>> Bradshaw, Charles Chen, Matthias Feys, Holden Karau, Sergei Lebedev, Robbe
>> Sneyders, Valentyn Tymofieiev)
>>
>>-
>>
>>Major progress has been made on making Beam Python codebase
>>Python3-compatible through futurization.
>>-
>>
>>Read for more details in the proposal
>>.
>>
>>
>> New IO connectors (by: John Rudolf Lewis, Jacob Marble)
>>
>>-
>>
>>Amazon Simple Queue Service (SQS) is in review.
>>-
>>
>>Amazon Redshift is in progress.
>>
>> Portable Runners (by: Ankur Goenka, Eugene Kirpichov, Ben Sidhom, Axel
>> Magnuson, Thomas Weise, Ryan Williams , Robert Bradshaw, Daniel Oliveira,
>> Holden Karau)
>>
>>-
>>
>>Good progress on Portable Flink Runner and many of the
>>ValidatesRunner tests are passing now.
>>-
>>
>>Portable Flink Runner can now execute batch WordCount in Java, Python
>>and Go.
>>-
>>
>>Many enhancements and bug fixes in Portable Reference Runner.
>>-
>>
>>See Jira https://issues.apache.org/jira/browse/BEAM-2889 for more
>>details on  progress.
>>
>> Dependencies (by: Yifan Zou, Chamikara Jayalath)
>>
>>-
>>
>>We added a dependencies guide for Beam and tooling to automatically
>>create JIRAs for significantly outdated dependencies. We are working on
>>upgrading existing dependencies.
>>-
>>
>>See the Beam dependencies guide
>> for more details.
>>
>>
>>
>>
>> New Members
>>
>> New Contributors
>>
>>-
>>
>>Rose Nguyen, Seattle, WA, USA
>>-
>>
>>   Beam docs contributor
>>   -
>>
>>   Working to improve docs usability
>>   -
>>
>>Connell O'Callaghan, Seattle, WA, USA
>>-
>>
>>   Interested in growing the community
>>   -
>>
>>   Helping with community triages and managing issues
>>
>>
>>
>>
>> Talks & Meetups
>>
>> Stream Processing Meetup@LinkedIn  7/19/18
>>
>>-
>>
>>Xinyu Liu gave a talk on building a Samza Runner for Beam
>>-
>>
>>“Beam meet up, Samza!” and see it here
>>.
>>
>>
>> Large Scale Landuse Classification of Satellite 

Re: [VOTE] Community Examples Repository

[Griselda Cuevas]

I'd vote for 2.

Giving independence to an example repository and creating the right
infrastructure to maintain them will give visibility to the efforts our
users are creating to solve their uses cases with Beam. I also want to make
the process of sharing common work more easily.

Re:The examples that will remain in core, I agree that it's crucial to keep
some examples for testing.


On Wed, 8 Aug 2018 at 11:44, Lukasz Cwik  wrote:

> I would vote for 3.
>
> My reasoning is that Java has a good mechanism to get a starter/example
> project going by using the the maven archetypes already. Our quickstart
> guide for Apache Beam for the Java SDK already covers generating the
> examples archetype.
> We could point users to the starter project at the end of the java
> quickstart.
>
> If python/go have a similar mechanism that is commonly used, I would go
> with those over creating a separate repo for examples and adding the
> maintenance burden involved.
>
>
>
> On Wed, Aug 8, 2018 at 11:01 AM Rui Wang  wrote:
>
>> 2 - examples that rely on experimental API can still stay in where they
>> are because such examples could be changed.
>>
>> -Rui
>>
>> On Wed, Aug 8, 2018 at 10:52 AM Charles Chen  wrote:
>>
>>> 3 - We benefit from increased test coverage by having examples together
>>> with the rest of the code.  As Robert mentions in the doc, hosting the Beam
>>> examples in the main repository is the best way to keep the examples
>>> visible, tested and maintained.  Given that we recently moved to a single
>>> repository for the website since that previously caused a lot of pain, it
>>> makes sense to be consistent here.
>>>
>>> On Wed, Aug 8, 2018 at 10:27 AM Ahmet Altay  wrote:
>>>
 2 - Similar to Huygaa, I see value in keeping a core set of examples
 tested and maintained against head. At the same time I understand the value
 of a growing set of community grown examples that are targeted against a
 pre-defined versions of Beam and not necessarily updated at every release.

 On Wed, Aug 8, 2018 at 10:22 AM, Huygaa Batsaikhan 
 wrote:

> 2 - I like the idea of having a separate repo where we can have more
> freedom to check in examples. However, we benefit from having immediate
> core examples in Beam for testing purposes.
>
> On Wed, Aug 8, 2018 at 9:38 AM David Cavazos 
> wrote:
>
>> Hi everyone!
>>
>> We discussed several options as well as some of the implications of
>> each option. Please vote for your favorite option, feel free to back it 
>> up
>> with any reasons that make you feel that way.
>>
>> 1) Move *all* samples to a *new *examples* repository*
>> 2) Move *some* samples to a *new *examples* repository*
>> 3) Leave samples where they are
>>
>> Some implications to creating a new repository:
>> - Every example would be independent from every other example, so
>> tests can be run in parallel
>> - Examples would now show how to use Beam *externally*
>> - The examples repository would need a testing infrastructure
>> - Decoupling makes examples easier to test on different versions
>> - Easier to copy-paste an existing example and start from there,
>> almost like a template
>> - Smaller size for the core Beam library
>> - Two different repositories to maintain
>> - Versioning could mirror Beam's current version
>>
>> Link to proposal
>> 
>>
>

Re: Hello Beam Community!!!

[Griselda Cuevas]

Welcome!

On Fri, Aug 3, 2018, 9:44 PM Jean-Baptiste Onofré  wrote:

> Welcome aboard !
>
> Regards
> JB
>
> On 04/08/2018 04:39, Connell O'Callaghan wrote:
> > Hi All
> >
> > My name is Connell. I am relatively new to Beam (and Google where I work
> > as a technical PM). My philosophy is very much oriented around how can I
> > serve the team. Hence, I am extremely interested to learn how I can help
> > continue the great work of this community. One particular area I am
> > curious about is how this community triages and manages issues. I will
> > do some self study on this. But I would be very interested to engage
> > with others interested in this general topic. Please let me know if you
> > wish to connect on this or other topics!!!
> >
> > Thank you in advance!!!
> >
> > - Connell
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: Beam Docs Contributor

[Griselda Cuevas]

Welcome Rose, very glad to have you in the community :)



On Fri, 27 Jul 2018 at 16:29, Ahmet Altay  wrote:

> Welcome Rose! Looking forward to your contributions.
>
> On Fri, Jul 27, 2018 at 4:08 PM, Rose Nguyen  wrote:
>
>> Hi all:
>>
>> I'm Rose! I've worked on Cloud Dataflow documentation and now I'm
>> starting a project to refresh the Beam docs and improve the onboarding
>> experience. We're planning on splitting up the programming guide into
>> multiple pages, making the docs more accessible for new users. I've got
>> lots of ideas for doc improvements, some of which are motivated by the UX
>> research, and am excited to share them with you all and work on them.
>>
>> I look forward to interacting with everybody in the community. I welcome
>> comments, thoughts, feedback, etc.
>> --
>>
>>
>> Rose Thi Nguyen
>>
>>   Technical Writer
>>
>> (281) 683-6900
>>
>
>

[Call for Volunteers] Apache Beam Summit Europe 2018

[Griselda Cuevas]

*Hi Beam Community: If you’d like to sponsor/help organize the Europe
Apache Beam Summit Europe 2018, please reach out to gris [at] apache [dot]
org with your contact info and what areas would you like to help with.
We’ll be hosting a kick-off meeting with the organizing committee the last
week of July. Cheers, G*

[Events] Save the Date, Apache Beam Summit Europe 2018

[Griselda Cuevas]

*Hi Beam Community, We are happy to announce that the Apache Beam Summit
Europe will be hosted in London on October 1st & 2nd. Please mark your
calendars and keep an eye open for the call for speakers and the
registration announcement.If you have questions or suggestions, please let
us know. Gris on behalf of the Summit Organizers*

Re: FYI on Slack Channels

[Griselda Cuevas]

This is awesome, thanks Rafael!




On Tue, 26 Jun 2018 at 13:46, Scott Wegner  wrote:

> This is great, thanks Rafael!
>
> On Tue, Jun 26, 2018 at 6:45 AM Rafael Fernandez 
> wrote:
>
>> Ah! Didn't know -- thanks Romain!
>>
>> Done for all channels I could find. Also, here is a list of channels:
>>
>> #beam
>> #beam-events-meetups
>> #beam-go
>> #beam-java
>> #beam-portability
>> #beam-python
>> #beam-sql
>> #beam-testing
>>
>>
>> On Tue, Jun 26, 2018 at 1:18 AM Romain Manni-Bucau 
>> wrote:
>>
>>> +1 sounds very good
>>>
>>> side note: any channel must invite @asfarchivebot, I did it for the ones
>>> before "etc" but if you add others please ensure it is done
>>>
>>> Romain Manni-Bucau
>>> @rmannibucau  |  Blog
>>>  | Old Blog
>>>  | Github
>>>  | LinkedIn
>>>  | Book
>>> 
>>>
>>>
>>> Le mar. 26 juin 2018 à 01:05, Lukasz Cwik  a écrit :
>>>
 +u...@beam.apache.org 

 On Mon, Jun 25, 2018 at 4:04 PM Rafael Fernandez 
 wrote:

> Hello!
>
> I took the liberty to create area-specific channels (such as
> #beam-java, #beam-python, #beam-go, etc.) As our project and community
> grows, I am seeing more and more "organic" interest groups forming -- this
> may help us chat more online. If they don't, we can delete later.
>
> Any thoughts? (I am having second thoughts... #beam-go should probably
> be #beam-burrow ;p )
>
> Cheers,
> r
>

Re: Going on leave for a bit

[Griselda Cuevas]

Enjoy the time off Kenn!


On Tue, 26 Jun 2018 at 12:14, Kai Jiang  wrote:

> Congrats! Enjoy your family time.
>
> Best,
> Kai
>
> On Tue, Jun 26, 2018, 09:11 Alan Myrvold  wrote:
>
>> Congrats, Kenn and have a great break.
>>
>> On Tue, Jun 26, 2018 at 9:10 AM Alexey Romanenko <
>> aromanenko@gmail.com> wrote:
>>
>>> Best wishes to you and your family, Kenneth!
>>>
>>> Alexey
>>>
>>> On 26 Jun 2018, at 15:45, Rafael Fernandez  wrote:
>>>
>>> Have a great time, Kenn!
>>>
>>> On Tue, Jun 26, 2018 at 5:49 AM Ismaël Mejía  wrote:
>>>
 Enjoy your family time.

 Best wishes,
 Ismael


 On Tue, Jun 26, 2018 at 12:13 PM Pei HE  wrote:

> (A late) Congrats for the newborn!
> --
> Pei
>
> On Tue, Jun 26, 2018 at 1:42 PM, Kenneth Knowles 
> wrote:
> > Hi friends,
> >
> > I think I did not mention on dev@ at the time, but my child #2
> arrived March
> > 14 (Pi day!) and I took some weeks off. Starting ~July 4 I will be
> taking a
> > more significant absence, until ~October 1, trying my best to be
> totally
> > offline.
> >
> > JFYI so that you know why JIRAs and PRs are not being addressed. I
> am also
> > unassigning my JIRAs so that I am not holding any mutexes, and I
> will close
> > PRs so they don't get stale.
> >
> > Any questions or pressing issues, I will be online this week and a
> little
> > bit next week.
> >
> > Kenn
>

>>>

Celebrating Pride... in the Apache Beam Logo

[Griselda Cuevas]

Someone in my team edited some Open-Source-Projects' logos to celebrate
pride and Apache Beam was included!


I'm attaching what she did... sprinkling some fun in the mailing list,
because it's Friday!

Apache Beam June Newsletter

[Griselda Cuevas]

Hi Beam Community!

Here

[1]
is the June Edition of our Apache Beam Newsletter. This edition was curated
by our community of contributors, committers and PMCs. Generally, it
contains the work done in the previous month (May in this case) and what's
planned for the future.

We hope to provide visibility to what's going on in the community, so if
you have questions, feel free to ask in this thread.

Cheers,
Gris

[1]
https://docs.google.com/document/d/1BwRhOu-uDd3SLB_Om_Beke5RoGKos4hj7Ljh7zM2YIo/edit?ts=5b17fb92#

Re: [FYI] New Apache Beam Swag Store!

[Griselda Cuevas]

Thanks All!

To close the loop on the suggestions, I'll order more t-shirts in black so
we have some options.

G

On Wed, 13 Jun 2018 at 08:39, Ismaël Mejía  wrote:

> Great ! Thanks Gris and Matthias for putting this in place.
> Hope to get that hoodie soon. As a suggestion, more colors too, and
> eventually a t-shirt just with the big B logo.
> On Mon, Jun 11, 2018 at 6:50 PM Mikhail Gryzykhin 
> wrote:
> >
> > That's nice!
> >
> > More colors are appreciated :)
> >
> > --Mikhail
> >
> >
> > On Sun, Jun 10, 2018 at 8:20 PM Kenneth Knowles  wrote:
> >>
> >> Sweet! Agree with Raghu :-)
> >>
> >> Kenn
> >>
> >> On Sun, Jun 10, 2018 at 6:06 AM Matthias Baetens <
> baetensmatth...@gmail.com> wrote:
> >>>
> >>> Great news, big thanks for all the work, Gris! Looking forward to
> people wearing this around the globe ;)
> >>>
> >>> On Sat, 9 Jun 2018 at 01:28 Ankur Goenka  wrote:
> >>>>
> >>>> Awesome!
> >>>>
> >>>>
> >>>> On Fri, Jun 8, 2018 at 4:24 PM Pablo Estrada 
> wrote:
> >>>>>
> >>>>> Nice : D
> >>>>>
> >>>>> On Fri, Jun 8, 2018, 3:43 PM Raghu Angadi 
> wrote:
> >>>>>>
> >>>>>> Woo-hoo! This is terrific.
> >>>>>>
> >>>>>> If we are increasing color choices I would like black or
> charcoal... Beam logo would really pop on a dark background.
> >>>>>>
> >>>>>> On Fri, Jun 8, 2018 at 3:32 PM Griselda Cuevas 
> wrote:
> >>>>>>>
> >>>>>>> Hi Beam Community,
> >>>>>>>
> >>>>>>> I just want to share with you the exciting news about our brand
> new Apache Beam Swag Store!
> >>>>>>>
> >>>>>>> You can find it here: https://store-beam.myshopify.com/
> >>>>>>>
> >>>>>>> How does it work?
> >>>>>>>
> >>>>>>> You can just select the items you want and check-out. Our Vendor
> ships to anywhere in the world and normally can have swag to be delivered
> within 1 week. Each company or user will need to pay for their own swag.
> >>>>>>> If you are hosting an event or representing Beam at one, reach out
> to me or the beam-events-meetups slack channel, I'll be happy to review
> your event and see if we can sponsor the swag. We'll have codes for this
> occasions thanks to Google, who has sponsored an initial inventory.
> >>>>>>>
> >>>>>>> If you have feedback, ideas on new swag, questions or suggestions,
> reach out to me and/or Matthias Baetens.
> >>>>>>>
> >>>>>>> Happy Friday!
> >>>>>>> G
> >>>>>>>
> >>>>>>>
> >>>>> --
> >>>>> Got feedback? go/pabloem-feedback
> <https://goto.google.com/pabloem-feedback>
> >>>
> >>> --
> >>>
>

[Call for Speakers] Deep Learning in Production Meetup, Boston Area on June 26th

[Griselda Cuevas]

Hi Beam Community,


Eila Arich-Landkof (from OrielResearch) and I are co-hosting the next
edition of the Deep Learning in Production Meetup
 on June 26th at the
Google Office in Cambridge, Massachusetts.


*We are looking for speakers who would like to share their Beam use case.*


We are expecting an audience of 150 people, so this is a great visibility
opportunity and also a fantastic way to network and get to meet people from
the Beam community.


If you are in the Area, come join us!


Cheers,

Eila & Gris

Re: [DISCUSS] Use Confluence wiki for non-user-facing stuff

[Griselda Cuevas]

Hi Everyone,


(a) should we do it? -- I like the idea of having a wiki, yes. Mainly to
differentiate the documentation we cater to users and the one we cater to
contributors. For things like user examples, and more demo-y content, I'd
suggest we still host it in the Website.

(b) what should go there? -- The ultimate purpose of the wiki should be to
host everything needed to a) get started (with official documentation) and
b) how to get the most out of Beam (here is where I see things like what
Robert suggested could fit, tips, tricks and other cool things created by
and for our contributors.)

(c) what should not go there? -- Any demos, examples or showcases. I think
that material should be either embedded or linked (listed) in the website.

Tu summarize, I'd like to see the wiki to be a knowledge collection for*
people who contribute* to the project and the website the collection of
information that allows *someone to make the decision to use Beam* (or join
the community).

When we are ready to vote on the creation of a wiki, I'd like to propose
that the first thing we document there is the Beam Improvement plan along
side with a concrete "Get Started Contributing to Beam" cheatsheet.

WDYT?


On Tue, 12 Jun 2018 at 09:34, Alexey Romanenko 
wrote:

> +1 for having Wiki for devs and users.
>
> Even though editing interface is not so native and obvious (comparing to
> Google docs), but, at least, it will be already put in one place and should
> be much more easy to search and discover.
>
> The only my concern about Wiki (based on using it in other different
> projects) that, in course of time, the information becomes outdated and
> weak structured which makes this not so valuable and even deceptive.
>
> WBR,
> Alexey
>
> On 12 Jun 2018, at 18:01, Robert Bradshaw  wrote:
>
> On Mon, Jun 11, 2018 at 2:40 PM Kenneth Knowles  wrote:
>
>> OK, yea, that all makes sense to me. Like this?
>>
>>  - site/documentation: writing just for users
>>  - site/contribute: basic stuff as-is, writing for users to entice them,
>> links to the next...
>>  - wiki/contributors: contributors writing just for each other
>>
>> And you also have
>>
>>  - wiki/users: users writing for users
>>
>> That's interesting.
>>
>
> Yep. We don't have to start wiki/users right away, but it could be useful
> down the line.
>
>
>
>> On Mon, Jun 11, 2018 at 2:30 PM Robert Bradshaw 
>> wrote:
>>
>>> On Fri, Jun 8, 2018 at 2:18 PM Kenneth Knowles  wrote:
>>>
>>>
 I disagree strongly here - I don't think the wiki will have appropriate
 polish for users. Even if carefully polished I don't think the presentation
 style is right, and it is not flexible. Power users will find it, of 
 course.

>>>
>>> I wasn't imagining a wiki as a platform for developers to author
>>> documentation, rather a place for users to author content for other users
>>> (tips and tricks, handy PTransforms, etc.) at a much lower bar than
>>> expecting users to go in and update our documentation. I agree with the
>>> goal of not (further) fragmenting our documentation.
>>>
>>> As for mixing contributor vs. user information on the same site, I think
>>> it's valuable to have some integration and treat the two as a continuum
>>> (after all, our (direct) users are already developers) and consider it an
>>> asset to have a "contribute" heading right in the main site. (Perhaps, if
>>> it's confusing, we could move it all the way to the right.) I don't think
>>> we'll be doing ourselves a favor by blinding copying all the existing docs
>>> to a wiki. That being said I think it makes sense to start playing with
>>> using a wiki, and see how much value that adds on top of what we already
>>> have.
>>>
>>>


> On Fri, Jun 8, 2018 at 12:05 PM Thomas Weise  wrote:
>
>> +1 most of the contributor material could live on Wiki and there it
>> will be easier to maintain (perhaps the lower bar for updates will lead 
>> to
>> more information and increased maintenance). Contribution policy related
>> material should remain on the website and go through proper
>> review/versioning.
>>
>>
>> On Fri, Jun 8, 2018 at 11:44 AM, Udi Meiri  wrote:
>>
>>> (a) Yes.
>>> (b) I'm interested in putting documentation for contributors there.
>>> (test triage guide, precommit and postcommit guidelines, processes, 
>>> etc.)
>>> It'd be faster than having to go through the motions of a github
>>> pull request and a review process.
>>> (c) Anything that goes to a wide audience, such as SDK users. That
>>> would need review.
>>>
>>> Also, have you looked at https://wiki.apache.org/general/ ? (not
>>> sure if that's Confluence)
>>>
>>>
>>> On Fri, Jun 8, 2018 at 10:07 AM Andrew Pilloud 
>>> wrote:
>>>
 +1 It would be really nice to have a lightweight place to share
 that is more searchable then random Google docs.

 Andrew

 On Fri, 

[FYI] New Apache Beam Swag Store!

[Griselda Cuevas]

Hi Beam Community,

I just want to share with you the exciting news about our brand new Apache
Beam Swag Store!

You can find it here: https://store-beam.myshopify.com/

*How does it work?*

   - You can just select the items you want and check-out. Our Vendor ships
   to anywhere in the world and normally can have swag to be delivered within
   1 week. Each company or user will need to pay for their own swag.
   - If you are hosting an event or representing Beam at one, reach out to
   me or the beam-events-meetups slack channel, I'll be happy to review your
   event and see if we can sponsor the swag. We'll have codes for this
   occasions thanks to Google, who has sponsored an initial inventory.

If you have feedback, ideas on new swag, questions or suggestions, reach
out to me and/or Matthias Baetens.

Happy Friday!
G

Re: [Proposal] Apache Beam's Public Project Roadmap

[Griselda Cuevas]

;>> initiatives (ongoing and future) in an easy to consume format, but also
>>>>>> think that "roadmap" sounds a bit too corporate...
>>>>>>
>>>>>> Other projects, including Flink, Kafka and Spark have the concept of
>>>>>> "Improvement Proposal" that could serve this purpose, so maybe it is time
>>>>>> for "BIP"?
>>>>>>
>>>>>> There could then be an overview/list style page that shows
>>>>>> in-progress and proposed items that gives the visitor an idea where the
>>>>>> project is headed.
>>>>>>
>>>>>> Also, can we consider confluence for this? It is ASF hosted but
>>>>>> easier to maintain than beam-site.
>>>>>>
>>>>>> Thanks,
>>>>>> Thomas
>>>>>>
>>>>>>
>>>>>> On Thu, Jun 7, 2018 at 4:59 AM, Kenneth Knowles 
>>>>>> wrote:
>>>>>>
>>>>>>> OK, I have one note: what about longer-term "roadmap", in quotes
>>>>>>> because that just means it is "ideas for the future". Like the Spark 
>>>>>>> runner
>>>>>>> could have a written roadmap that includes lots of TODOs that extend far
>>>>>>> into the future. It gives a menu of things to think about when filling 
>>>>>>> this
>>>>>>> out each quarter. Users and contributors could potentially comment / 
>>>>>>> upvote.
>>>>>>>
>>>>>>> I think this is probably a separate thing than what you have here -
>>>>>>> it could just be a public gdoc with no particular structure, or JIRA 
>>>>>>> tags
>>>>>>> bundled into some kind of report - but what do you think?
>>>>>>>
>>>>>>> Kenn
>>>>>>>
>>>>>>> On Wed, Jun 6, 2018 at 8:37 PM Kenneth Knowles 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> This is great. I'm really excited to build a community process for
>>>>>>>> this.
>>>>>>>>
>>>>>>>> Kenn
>>>>>>>>
>>>>>>>> On Wed, Jun 6, 2018 at 5:05 PM Griselda Cuevas 
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi Beam Community,
>>>>>>>>>
>>>>>>>>> I'd like to propose the creation of a Public Project Roadmap. Here
>>>>>>>>> are the details as well as some artifacts I started already.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ---_---
>>>>>>>>>
>>>>>>>>> *Proposal *
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> *What?*
>>>>>>>>>
>>>>>>>>> Create a simple spreadsheet-based project roadmap to generate an
>>>>>>>>> overview of all the efforts driven by different members of the 
>>>>>>>>> community. I
>>>>>>>>> propose doing something like this tracker I put together
>>>>>>>>> <https://docs.google.com/spreadsheets/d/1W6xvPmGyG8Nd9R7wkwgwRJvZdyLoBg6F3NCrPafbKmk/edit#gid=0>
>>>>>>>>>  [1].
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> *Why?*
>>>>>>>>>
>>>>>>>>> *The ultimate purpose of this roadmap is to create a tool and
>>>>>>>>> method to make our project more transparent and efficient. It will 
>>>>>>>>> help us
>>>>>>>>> map dependencies, identify collaboration areas and communicate future
>>>>>>>>> releases to users more clearly. *
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> *How?*
>>>>>>>>>
>>>>>>>>> We could update the current status of the roadmap every three
>>>>>>>>> months (quarter), following these guidelines and timeline
>>>>>>>>> <https://docs.google.com/document/d/1jzASbp_5GrZdsF5YXau-MPh_v0jW6egJwL_Pyac5zeE/edit#heading=h.6dyyhz5krl9v>
>>>>>>>>>  [2].
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Thanks!
>>>>>>>>> G
>>>>>>>>>
>>>>>>>>> [1]
>>>>>>>>> https://docs.google.com/spreadsheets/d/1W6xvPmGyG8Nd9R7wkwgwRJvZdyLoBg6F3NCrPafbKmk/edit#gid=0
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> [2]
>>>>>>>>> https://docs.google.com/document/d/1jzASbp_5GrZdsF5YXau-MPh_v0jW6egJwL_Pyac5zeE/edit#heading=h.6dyyhz5krl9v
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>
>>>>
>>

[Proposal] Apache Beam's Public Project Roadmap

[Griselda Cuevas]

Hi Beam Community,

I'd like to propose the creation of a Public Project Roadmap. Here are the
details as well as some artifacts I started already.

---_---

*Proposal *


*What?*

Create a simple spreadsheet-based project roadmap to generate an overview
of all the efforts driven by different members of the community. I propose
doing something like this tracker I put together

 [1].


*Why?*

*The ultimate purpose of this roadmap is to create a tool and method to
make our project more transparent and efficient. It will help us map
dependencies, identify collaboration areas and communicate future releases
to users more clearly. *


*How?*

We could update the current status of the roadmap every three months
(quarter), following these guidelines and timeline

 [2].


Thanks!
G

[1]
https://docs.google.com/spreadsheets/d/1W6xvPmGyG8Nd9R7wkwgwRJvZdyLoBg6F3NCrPafbKmk/edit#gid=0


[2]
https://docs.google.com/document/d/1jzASbp_5GrZdsF5YXau-MPh_v0jW6egJwL_Pyac5zeE/edit#heading=h.6dyyhz5krl9v

Re: [Call for items] Beam June Newsletter

[Griselda Cuevas]

Great question Scott!

Yes, this is a monthly Newsletter and the June Edition should cover the
things that happened in May.

On Wed, 6 Jun 2018 at 08:05, Scott Wegner  wrote:

> Thanks for putting this together, Gris. I'm not familiar with the format:
> what time period this newsletter should cover? Is this a monthly newsletter
> and the June edition covers news from May?
>
> On Tue, Jun 5, 2018 at 4:47 PM Griselda Cuevas  wrote:
>
>> Hi Everyone,
>>
>> Just a reminder to add items to the June Newsletter, the idea behind it
>> is to summarize community efforts in the project to get others identify
>> similar actions, opportunities to collaborate and ask questions. Folks in
>> the mailing list have found these newsletters useful in the past, so let's
>> keep the tradition going :)
>>
>> I'll extend the deadline until 6/7 11:59 p.m. PST. If you have questions
>> let me know.
>>
>> Thanks!
>> G
>>
>> On Fri, 1 Jun 2018 at 12:19, Griselda Cuevas  wrote:
>>
>>> Hi Everyone,
>>>
>>> Here's
>>> <https://docs.google.com/document/d/1BwRhOu-uDd3SLB_Om_Beke5RoGKos4hj7Ljh7zM2YIo/edit>
>>> [1] the template for the June Beam Newsletter.
>>>
>>> *Add the updates you want to share with the community by 6/5 11:59 p.m.*
>>> *Pacific Time.*
>>>
>>> I'll edit and send the final version through the users mailing list on
>>> 6/7.
>>>
>>> Thank you!
>>> Gris
>>>
>>> [1]
>>> https://docs.google.com/document/d/1BwRhOu-uDd3SLB_Om_Beke5RoGKos4hj7Ljh7zM2YIo/edit
>>>
>>

Re: [Call for items] Beam June Newsletter

[Griselda Cuevas]

Hi Everyone,

Just a reminder to add items to the June Newsletter, the idea behind it is
to summarize community efforts in the project to get others identify
similar actions, opportunities to collaborate and ask questions. Folks in
the mailing list have found these newsletters useful in the past, so let's
keep the tradition going :)

I'll extend the deadline until 6/7 11:59 p.m. PST. If you have questions
let me know.

Thanks!
G

On Fri, 1 Jun 2018 at 12:19, Griselda Cuevas  wrote:

> Hi Everyone,
>
> Here's
> <https://docs.google.com/document/d/1BwRhOu-uDd3SLB_Om_Beke5RoGKos4hj7Ljh7zM2YIo/edit>
> [1] the template for the June Beam Newsletter.
>
> *Add the updates you want to share with the community by 6/5 11:59 p.m.*
> *Pacific Time.*
>
> I'll edit and send the final version through the users mailing list on 6/7.
>
> Thank you!
> Gris
>
> [1]
> https://docs.google.com/document/d/1BwRhOu-uDd3SLB_Om_Beke5RoGKos4hj7Ljh7zM2YIo/edit
>

Re: Initial contributor experience

[Griselda Cuevas]

+user@ in case someone has had similar experiences.

Thanks for documenting this Austin & Pablo!

If any other folks would like to participate in improving the "First
contribution experience" for Beam let us know in this thread.

On Tue, 5 Jun 2018 at 13:40, Austin Bennett 
wrote:

> Had been meaning to get setup to contribute for a bit - so walked through
> with Pablo, to try to point out assumptions, lacking docs, etc.
>
> Write-up found-->
>
>
> https://docs.google.com/document/d/1hq-s3L676LkMTftvhv0eCkdwrRnZmCRiLdaQBWLHWWA/edit
>

Re: [VOTE] Code Review Process

[Griselda Cuevas]

+1

On Mon, 4 Jun 2018 at 12:30, Robert Burke  wrote:

> +1
>
> On Mon, Jun 4, 2018, 9:01 AM Raghu Angadi  wrote:
>
>> +1
>>
>> On Fri, Jun 1, 2018 at 10:25 AM Thomas Groh  wrote:
>>
>>> As we seem to largely have consensus in "Reducing Committer Load for
>>> Code Reviews"[1], this is a vote to change the Beam policy on Code Reviews
>>> to require that
>>>
>>> (1) At least one committer is involved with the code review, as either a
>>> reviewer or as the author
>>> (2) A contributor has approved the change
>>>
>>> prior to merging any change.
>>>
>>> This changes our policy from its current requirement that at least one
>>> committer *who is not the author* has approved the change prior to merging.
>>> We believe that changing this process will improve code review throughput,
>>> reduce committer load, and engage more of the community in the code review
>>> process.
>>>
>>> Please vote:
>>> [ ] +1: Accept the above proposal to change the Beam code review/merge
>>> policy
>>> [ ] -1: Leave the Code Review policy unchanged
>>>
>>> Thanks,
>>>
>>> Thomas
>>>
>>> [1]
>>> https://lists.apache.org/thread.html/7c1fde3884fbefacc252b6d4b434f9a9c2cf024f381654aa3e47df18@%3Cdev.beam.apache.org%3E
>>>
>>

[Call for items] Beam June Newsletter

[Griselda Cuevas]

Hi Everyone,

Here's

[1] the template for the June Beam Newsletter.

*Add the updates you want to share with the community by 6/5 11:59 p.m.*
*Pacific Time.*

I'll edit and send the final version through the users mailing list on 6/7.

Thank you!
Gris

[1]
https://docs.google.com/document/d/1BwRhOu-uDd3SLB_Om_Beke5RoGKos4hj7Ljh7zM2YIo/edit

Re: The full list of proposals / prototype documents

[Griselda Cuevas]

Hi Everyone,


@Alexey, I think this is a great idea, I'd like to understand more of the
motivation behind having all the designs doc under a single page. In my
opinion it could become a challenge to maintain a page, so knowing what you
want to accomplish could help us think of alternative solutions?

On Wed, 23 May 2018 at 14:08, Daniel Oliveira 
wrote:

> +1 to web site page (not Google Doc).
>
> Definitely agree that a common entry point would be excellent. I don't
> like the idea of the Google Doc so much because it's not very good for
> having changes reviewed and keeping track of who added what, unlike Github.
> Adding an entry to the list in the website would require reviews and leave
> behind a commit history, which I think is important for an
> authoritative source like this.
>
> PS: I also have a doc I proposed that I didn't see in the lists:
> https://s.apache.org/beam-runner-api-combine-model
>
> On Wed, May 23, 2018 at 12:52 PM Lukasz Cwik  wrote:
>
>> +1, Thanks for picking this up Alexey
>>
>> On Wed, May 23, 2018 at 10:41 AM Huygaa Batsaikhan 
>> wrote:
>>
>>> +1. That is great, Alexey. Robin and I are working on documenting some
>>> missing pieces of Java SDK. We will let you know when we create polished
>>> documents.
>>>
>>> On Wed, May 23, 2018 at 9:28 AM Ismaël Mejía  wrote:
>>>
 +1 and thanks for volunteering for this Alexey.
 We really need to make this more accesible.
 On Wed, May 23, 2018 at 6:00 PM Alexey Romanenko <
 aromanenko@gmail.com>
 wrote:

 > Joseph, Eugene - thank you very much for the links!

 > All, regarding one common entry point for all design documents. Could
 we
 just have a dedicated page on Beam web site with a list of links to
 every
 proposed document? Every entry (optionally) might contain, in addition,
 short abstract and list of author(s). In this case, it would be easily
 searchable and available for those who are interested in this.

 > In the same time, using a Google doc for writing/discussing the
 documents
 seems more than reasonable since it’s quite native and easy to use. I
 only
 propose to have a common entry point to fall of them.

 > If this idea looks feasible, I’d propose myself to collect the links
 to
 already created documents, create such page and update this list in the
 future.

 > WBR,
 > Alexey

 > On 22 May 2018, at 21:34, Eugene Kirpichov 
 wrote:

 > Making it easier to manage indeed would be good. Could someone from
 PMC
 please add the following documents of mine to it?

 > SDF related documents:
 > http://s.apache.org/splittable-do-fn
 > http://s.apache.org/sdf-via-source
 > http://s.apache.org/textio-sdf
 > http://s.apache.org/beam-watch-transform
 > http://s.apache.org/beam-breaking-fusion

 > Non SDF related:
 > http://s.apache.org/context-fn
 > http://s.apache.org/fileio-write

 > A suggestion: maybe we can establish a convention to send design
 document
 proposals to dev+desi...@beam.apache.org? Does the Apache mailing list
 management software support this kind of stuff? Then they'd be quite
 easy
 to find and filter.

 > On Tue, May 22, 2018 at 10:57 AM Kenneth Knowles 
 wrote:

 >> It is owned by the Beam PMC collectively. Any PMC member can add
 things
 to it. Ideas for making it easy to manage are welcome.

 >> Probably easier to have a markdown file somewhere with a list of
 docs so
 we can issue and review PRs. Not sure the web site is the right place
 for
 it - we have a history of porting docs to markdown but really that is
 high
 overhead and users/community probably don't gain from it so much. Some
 have
 suggested a wiki.

 >> Kenn

 >> On Tue, May 22, 2018 at 10:22 AM Scott Wegner 
 wrote:

 >>> Thanks for the links. Any details on that Google drive folder? Who
 maintains it? Is it possible for any contributor to add their design
 doc?

 >>> On Mon, May 21, 2018 at 8:15 AM Joseph PENG <
 josephtengp...@gmail.com>
 wrote:

  Alexey,

  I do not know where you can find all design docs, but I know a blog
 that has collected some of the major design docs. Hope it helps.

  https://wtanaka.com/beam/design-doc

 
 https://drive.google.com/drive/folders/0B-IhJZh9Ab52OFBVZHpsNjc4eXc

  On Mon, May 21, 2018 at 9:28 AM Alexey Romanenko <
 aromanenko@gmail.com> wrote:

 > Hi all,

 > Is it possible to obtain somewhere a list of all proposals /
 prototype documents that have been published as a technical / design
 documents for new features? I 

Getting Ready for the Apache Community Summit @ San Francisco, CA

[Griselda Cuevas]

Hi Everyone,

As you might remember from this thread [1] we're hosting the first Apache
Beam Community Summit in San Francisco tomorrow.

I've prepared a notes document [2] so that people can read after the
sessions. Additionally, folks who cannot attend can add questions starting
now so we can address them during or after the summit.

I'll report back with a summary after the event. Thanks to everyone who is
coming!

Gris Cuevas

[1] https://lists.apache.org/list.html?u...@beam.apache.org:lte=2M:summit
[2]
https://docs.google.com/document/d/1B4EU8jjZy9TnlRiZWW9hSCqegbmOh8boIgjkAyOfnCk/edit#

Re: Presentations about Apche Beam

[Griselda Cuevas]

Ciao Davide,

Just checking if you'd like to share the presentations with the community?

Have a great weekend!

>
> On Wed, Feb 14, 2018, 10:26 PM Davide Russo 
> wrote:
>
>> Dear Beam Community,
>>
>>
>>
>> My name is David and i’m a studet of University of Molise, Italy. I’m
>> studing “Security of Software System” and during this degree I’m attending
>> the course of “Complex Software Architecture and Styes”; for the exam I
>> have to analyse an Apache complex system. I selected to analyse Apache Beam
>> for many reason. I’m writing you because for this project I produced 3
>> presentations about Beam that I would to submit you to add them on Beam
>> website as presentation material. They derived in part form the existing
>> presentation so if you think that these presentations are good and well
>> done it could be cool if you add them on the Beam website. If you are
>> interested let me know that I’ll send you as soon as possible my work.
>>
>>
>>
>> Best Regards.
>>
>> DR
>>
>

Re: [YouTube channel] Add video: Apache Beam meetup London 2: use case in finance + IO in Beam and Splittable DoFns

[Griselda Cuevas]

+1 to the proposal

@Matthias could you share more about the dynamics in how people in the
community would be able to add videos and who would be owning the curation
of the channel?

G



On 21 February 2018 at 09:08, Matthias Baetens  wrote:

> Hi Gaurav,
>
> Thanks for pointing that out. The channel can be found here
> .
> No videos there yet though, waiting for approval to publish the first one!
>
> Cheers,
> Matthias
>
> On Wed, Feb 21, 2018 at 12:55 AM, Gaurav Thakur 
> wrote:
>
>> How can people get access to the channel?
>>
>> Thanks, Gaurav
>>
>> On Wed, Feb 21, 2018 at 1:34 PM, Matthias Baetens <
>> matthias.baet...@datatonic.com> wrote:
>>
>>> Hi all,
>>>
>>> This is a proposal to launch the Apache Beam YouTube channel and at the
>>> same time add the first video to the channel.
>>>
>>> We would like to use the channel to centralize all videos / recordings
>>> related to Apache Beam and make it a community driven channel, so people
>>> have a one stop shop for learnings about Beam.
>>>
>>> The first video would be the recording of the second Beam meetup in
>>> London:
>>> Apache Beam meetup London 2: use case in finance + IO in Beam and
>>> Splittable DoFns. The video can be seen on the channel if you have login
>>> details (it is currently set to private).
>>>
>>> Please let me know if there are any questions or comments!
>>>
>>> Best regards,
>>> Matthias
>>>
>>
>>
>
>
> --
>
>
> *Matthias Baetens*
>
>
> *datatonic | data power unleashed*
>
> office +44 203 668 3680 <+44%2020%203668%203680>  |  mobile +44 74 918
> 20646
>
> Level24 | 1 Canada Square | Canary Wharf | E14 5AB London
> 
>
>
> We've been announced
> 
>  as
> one of the top global Google Cloud Machine Learning partners.
>

[Event] OSCON Call For Proposals Deadline is 1/30

[Griselda Cuevas]

Hi Beam Community,

I just wanted to send a reminder that OSCON's CFP deadline is this 1/30. I
have added a reminder in our brand new events calendar.

You can find more information about the event in their website
. To submit a proposal you
can use this link.


If you're submitting something related to Beam, let us know in this thread.

Enjoy the weekend!
G

Re: [Proposal] Apache Beam Event's Calendar

[Griselda Cuevas]

Ok, so given that the proposal seem to have traction I'll proceed as
follows:


   1. I'll give all PMC members owner rights to the calendar, so they can
   edit and add events.
   2. I'll share the calendar with the dev@ and user@ lists
   3. I'll investigate how to add the calendar to the Website

Proposed dynamic to add events to the calendar:

   - Anyone can announce an event in the mailing list
   - Anyone with editing rights in the calendar can add a new event

[For people with Calendar editing rights only] How to add an event to the
calendar:

   - I'll suggest we use [tags] to classify events in this calendar:
   [Deadline] -- Use this tag for reminders on deadlines for CFPs,
   Registrations, etc.
   [USA] -- Use this tag for events in the USA
   [Europe] -- Use this tag for events in Europe
   [APAC] -- Use this tag for events in APAC
   - We should add speakers, participants or content directly in the
   calendar space for details

Cheers,
G

On 25 January 2018 at 01:35, Ismaël Mejía <ieme...@gmail.com> wrote:

> +1
>
> I think it makes sense to separate it the calendar in two, one for the
> CFPs more interesting for dev@ and one for confirmed events where
> there will be presentations on Beam that concerns more the users
> (user@). It also probably makes sense to include this one in the
> website too.
>
>
>
>
> On Thu, Jan 25, 2018 at 9:46 AM, Etienne Chauchot <echauc...@apache.org>
> wrote:
> > +1, great initiative!
> >
> >
> > Le 25/01/2018 à 01:05, Griselda Cuevas a écrit :
> >
> > Hi Beam Community,
> >
> > I've created this public calendar to curate events that the Apache Beam
> > community will attend or is organizing, as well as industry events we
> should
> > keep in the radar. With this calendar, I want to:
> >
> > Give visibility to the community on what conferences we want to
> participate
> > in
> > What events is our community organizing
> >
> >
> > My proposal: Share the calendar with the entire dev@ & users@ mailing
> list
> > and give access as admins to the few folks I know are organizing events
> to
> > help curate our events.
> >
> > If we get enough votes I'll share the calendar publicly and I'll give
> access
> > to the other folks.
> >
> > Thanks,
> > G
> >
> >
>

Re: [Proposal] Apache Beam Event's Calendar

[Griselda Cuevas]

@Lukasz - Yes we can add that info as we know who is participating.

@Reuven, When I add the user@ and dev@ lists to the calendar, the invites
will alert the mailing list, it'd be an automated way to share this
information, not a substitution.



On 24 January 2018 at 16:36, Reuven Lax <re...@google.com> wrote:

> I think the calendar is a great idea for collecting events. However events
> ideally will still be announced to the dev list, the calendar shouldn't be
> a substitute for that.
>
> Reuven
>
> On Wed, Jan 24, 2018 at 4:05 PM, Griselda Cuevas <g...@google.com> wrote:
>
>> Hi Beam Community,
>>
>> I've created this public calendar
>> <https://calendar.google.com/calendar/embed?src=r24up18ne2ddgl0t93flk0hsj8%40group.calendar.google.com=America%2FLos_Angeles>
>>  to
>> curate events that the Apache Beam community will attend or is organizing,
>> as well as industry events we should keep in the radar. With this calendar,
>> I want to:
>>
>>
>>1. Give visibility to the community on what conferences we want to
>>participate in
>>2. What events is our community organizing
>>
>>
>> My proposal: Share the calendar with the entire dev@ & users@ mailing
>> list and give access as admins to the few folks I know are organizing
>> events to help curate our events.
>>
>> If we get enough votes I'll share the calendar publicly and I'll give
>> access to the other folks.
>>
>> Thanks,
>> G
>>
>
>

[DISCUSS] State of the project: Community growth

[Griselda Cuevas]

*Hi Everyone, Thanks Davor for starting the discussion around the state of
the Apache Beam in 2017[1]. In this fork of that conversation, I’d like to
continue the dialogue around how should we grow our community in alignment
to the project's vision, goals & values.Here are some areas and prompts to
guide the conversation. If there are other ideas related to community
growth missing here, please add them in this thread as well. 1. New users:
How could the community help potential and new users learn about Beam? How
can we support questions from users better?2. New contributors: What are
our contributions Best Practices and how can we share them with new
members? How could the community help new contributors ramp up faster in
our Project’s dev environment? How could we empower new developers to
contribute to Beam’s core features? 3. Community engagement: What type of
activities and efforts would you like to see to increase our community
engagement?4. Events: What events should we attend? What events should we
sponsor? How could we support community led events better?5. Brand
building: What efforts do you think we should do to build our brand? What
use cases, ideas, talks, etc. should we collaborate on to give the project
more visibility?If there’s interest, I’d also be happy to host a virtual
meeting for anyone who’d prefer that avenue of discussion and will make
sure that any new ideas or details are brought back to the discussion
threads after that. Express interest in a virtual meeting in this thread so
I can coordinate.Thanks, and let’s make this an exciting community!Gris
Cuevas[1]https://lists.apache.org/thread.html/f750f288af8dab3f468b869bf5a3f473094f4764db419567f33805d0@%3Cdev.beam.apache.org%3E
*

Re: Happy new year

[Griselda Cuevas]

Happy New Year everyone!

@JB, congrats on your achievements.

It's exciting to see all the great accomplishments Beam had in 2017, I'm
excited to see where we go in 2018!



On 2 January 2018 at 12:42, Tyler Akidau  wrote:

> +1 all around. 2017 was excellent, and we're in a great position for 2018
> to be even better. Looking forward to it. :-)
>
> On Tue, Jan 2, 2018 at 10:34 AM Kenneth Knowles  wrote:
>
>> Happy new year! Very excited for 2018's possibilities. And nice work, JB.
>>
>> Kenn
>>
>> On Tue, Jan 2, 2018 at 6:42 AM, Ismaël Mejía  wrote:
>>
>>> Happy new year everyone !
>>>
>>> Agree 100% with Davor. 2017 was a good year for the project and it is
>>> worth to thank everyone who helped to make the project better.
>>> Now is the time to work to have a great project in 2018 too !
>>>
>>> Best wishes to all (and kudos to JB too for the top 5) !
>>>
>>> Ismaël
>>>
>>>
>>>
>>> On Mon, Jan 1, 2018 at 9:29 PM, David Sabater Dinter
>>>  wrote:
>>> > Happy New year all!
>>> >
>>> > On Mon, 1 Jan 2018 at 19:43, Davor Bonaci  wrote:
>>> >>
>>> >> Hi everyone --
>>> >> As we begin the new year, I wanted to send the best wishes in 2018 to
>>> >> everyone in the Beam community -- users, contributors and observers
>>> alike!
>>> >>
>>> >> There's so much to be proud of in 2017; including graduation to a
>>> >> top-level project and the availability of the first stable release.
>>> Thanks
>>> >> to everyone for making this possible!
>>> >>
>>> >> Finally, I'd also like to pass along some fun facts compiled by others
>>> >> [1]. Beam mailing lists had the 9th highest volume among all user@
>>> +dev@
>>> >> lists. Our very own, Jean-Baptiste Onofre, has once again finished in
>>> the
>>> >> top 5 committers across all projects in the Apache Software
>>> Foundation. This
>>> >> year, JB finished as #3, with 2,142 commits, among 6,504 committers.
>>> >> Congrats JB!
>>> >>
>>> >> Happy New Year -- and I hope to see you out and about in the next few
>>> >> months!
>>> >>
>>> >> Davor
>>> >>
>>> >> [1] https://blogs.apache.org/foundation/entry/apache-in-2017-by-the
>>> >>
>>> >> On Mon, Jan 1, 2018 at 8:41 AM, Jesse Anderson <
>>> je...@bigdatainstitute.io>
>>> >> wrote:
>>> >>>
>>> >>> Happy New Year!
>>> >>>
>>> >>>
>>> >>> On Sun, Dec 31, 2017, 11:09 PM Jean-Baptiste Onofré >> >
>>> >>> wrote:
>>> 
>>>  Hi beamers,
>>> 
>>>  I wish you a great and happy new year !
>>> 
>>>  Regards
>>>  JB
>>>  --
>>>  Jean-Baptiste Onofré
>>>  jbono...@apache.org
>>>  http://blog.nanthrax.net
>>>  Talend - http://www.talend.com
>>> >>
>>> >>
>>> >
>>>
>>
>>

Re: Report to the Board, December 2017 edition

[Griselda Cuevas]

LGTM thanks for sharing.



On 12 December 2017 at 20:54, Jean-Baptiste Onofré  wrote:

> It looks good to me.
>
> Thanks !
> Regards
> JB
>
>
> On 12/13/2017 05:51 AM, Davor Bonaci wrote:
>
>> We are expected to submit a project report to the ASF Board of Directors
>> ahead of its next meeting. The report is due on Wednesday, 12/13.
>>
>> If interested, please take a look at the draft [1], and comment or
>> contribute content, as appropriate. I'll submit the report sometime in the
>> next 24 hours.
>>
>> Thanks!
>>
>> Davor
>>
>> [1] https://docs.google.com/document/d/17AFM3iLXH8YyUc7FiYZS5YFI
>> OHymFWbbEJ5Ea2ySnkA/
>>
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: A personal update

[Griselda Cuevas]

Welcome back!


On 12 December 2017 at 22:47, Ahmet Altay  wrote:

> Welcome back! Looking forward to your contributions.
>
> Ahmet
>
> On Tue, Dec 12, 2017 at 10:05 PM, Jesse Anderson <
> je...@bigdatainstitute.io> wrote:
>
>> Congrats!
>>
>> On Wed, Dec 13, 2017, 5:54 AM Jean-Baptiste Onofré 
>> wrote:
>>
>>> Hi Davor,
>>>
>>> welcome back !!
>>>
>>> It's really great to see you back active in the Beam community. We
>>> really need you !
>>>
>>> I'm so happy !
>>>
>>> Regards
>>> JB
>>>
>>> On 12/13/2017 05:51 AM, Davor Bonaci wrote:
>>> > My dear friends,
>>> > As many of you have noticed, I’ve been visibly absent from the project
>>> for a
>>> > little while. During this time, a great number of you kept reaching
>>> out, and for
>>> > that I’m deeply humbled and grateful to each and every one of you.
>>> >
>>> > I needed some time for personal reflection, which led to a transition
>>> in my
>>> > professional life. As things have settled, I’m happy to again be
>>> working among
>>> > all of you, as we propel this project forward. I plan to be active in
>>> the
>>> > future, but perhaps not quite full-time as I was before.
>>> >
>>> > In the near term, I’m working on getting the report to the Board
>>> completed, as
>>> > well as framing the discussion about the project state and vision going
>>> > forwards. Additionally, I’ll make sure that we foster healthy
>>> community culture
>>> > and operate in the Apache Way.
>>> >
>>> > For those who are curious, I’m happy to say that I’m starting a
>>> company building
>>> > products related to Beam, along with several other members of this
>>> community and
>>> > authors of this technology. I’ll share more on this next year, but
>>> until then if
>>> > you have a data processing problem or an Apache Beam question, I’d
>>> love to hear
>>> > from you ;-).
>>> >
>>> > Thanks -- and so happy to be back!
>>> >
>>> > Davor
>>>
>>> --
>>> Jean-Baptiste Onofré
>>> jbono...@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>
>

Apache Beam Workshop in Guadalajara Mexico

[Griselda Cuevas]

Hi Everyone,

I wanted to share with you that on December 2nd, Wizeline Academy [1] will
host an Apache Beam workshop in Guadalajara Mexico. The objective of this
workshop is to identify adoption barriers and improvement opportunities for
the project through the observation and documentation of the experience of
new Beam users. We hope that the findings of this workshop can provide
supportive information to shape the direction of our project, specially now
that we have started conversation about next releases.

If you are in the area and are interested in joining us, please sign up
[2]. If you're interested in running similar efforts reach out to me and
I'll be happy to share resources and connect with you. I'll report back
with findings after the workshop.

Cheers,
Gris

[1] https://academy.wizeline.com/about/
[2] https://academy.wizeline.com/apache-beam/

Re: New Contributor

[Griselda Cuevas]

Welcome guys!

On 14 November 2017 at 13:11, Jesse Anderson 
wrote:

> Welcome!
>
> On Tue, Nov 14, 2017, 10:03 PM Ben Sidhom 
> wrote:
>
> > Hey all,
> >
> > My name is Ben Sidhom. I'm an engineer at Google working on open source
> > data processing on top of GCP. I hope to contribute to the runner
> > portability effort along with Axel.
> >
> >
> > On 2017-11-14 11:38, Axel Magnuson  wrote:
> > > Hello All,>
> > >
> > > My name is Axel Magnuson and I intend to start contributing to the
> Beam>
> > > project.>
> > >
> > > I work as a Software Engineer at Google, with a background in Spark
> and>
> > > Hadoop.  I am hoping to make myself useful in particular around
> > portability>
> > > efforts and the open source engine runners.>
> > >
> > > Best,>
> > > Axel>
> > >
> > > -- >
> > > Axel Magnuson | Software Engineer | axelm...@google.com |   1 (425)
> > 893-4624>
> > >
> >
> --
> Thanks,
>
> Jesse
>

Re: [Proposal] Apache Beam Swag Store

[Griselda Cuevas]

Excellent - we're getting approval from the trademark@ folks. I'll update
the thread when I have news.



On 5 November 2017 at 14:04, Ted Yu <yuzhih...@gmail.com> wrote:

> +1
>  Original message From: Jacob Marble <jmar...@kochava.com>
> Date: 11/5/17  1:50 PM  (GMT-08:00) To: dev@beam.apache.org Subject: Re:
> [Proposal] Apache Beam Swag Store
> I think this is a great idea, ready to order mine. :)
>
> Jacob
>
> On Sat, Oct 28, 2017 at 11:19 AM, Jean-Baptiste Onofré <j...@nanthrax.net>
> wrote:
>
> > It sounds good. Please let us know trademark update.
> >
> > Thanks
> > Regards
> > JB
> >
> > On Oct 28, 2017, 20:15, at 20:15, Griselda Cuevas
> <g...@google.com.INVALID>
> > wrote:
> > >Thanks for the feedback all, I'll send this idea to the trademark@
> > >folks
> > >and wait for validation. Once we have it I'll look into building the
> > >store
> > >possibly embedded in the website.
> > >
> > >Enjoy the weekend.
> > >G
> > >
> > >5
> > >
> > >
> > >
> > >On 27 October 2017 at 11:53, Tyler Akidau <taki...@google.com.invalid>
> > >wrote:
> > >
> > >> One additional note: for the logos w/ the name below them, would be
> > >nice to
> > >> not have quite so much whitespace between the logo and the name.
> > >Otherwise,
> > >> trademark validation aside, this looks great.
> > >>
> > >> On Fri, Oct 27, 2017 at 10:15 AM Griselda Cuevas
> > ><g...@google.com.invalid>
> > >> wrote:
> > >>
> > >> > Hi Dan - thanks for bringing this up to my attention. I haven't
> > >raised
> > >> this
> > >> > up to the tradema...@apache.org people. Can I just reach out to
> > >them to
> > >> > get
> > >> > the proposal or should one of the PMCs do this?
> > >> >
> > >> >
> > >> >
> > >> > Gris Cuevas Zambrano
> > >> >
> > >> > g...@google.com
> > >> >
> > >> > Open Source Strategy
> > >> >
> > >> > 345 Spear Street, San Francisco, 94105
> > >> > <https://maps.google.com/?q=345+Spear+Street,+San+Francisco,
> > >> +94105=gmail=g>
> > >> >
> > >> >
> > >> >
> > >> > On 26 October 2017 at 18:30, Daniel Kulp <dk...@apache.org> wrote:
> > >> >
> > >> > >
> > >> > > Have you run this through tradema...@apache.org yet?
> > >> > >
> > >> > > I bring this up for two reasons:
> > >> > >
> > >> > > 1) We would need to make sure the appearance and such of the logo
> > >is
> > >> > > “correct”
> > >> > >
> > >> > > 2).A few years ago, Apache did have a partnership with a company
> > >that
> > >> > > would produce various swag things and then donate a portion back
> > >to
> > >> > > Apache.   I don’t know what the state of that agreement is and
> > >whether
> > >> > that
> > >> > > would restrict going to another vendor or something.
> > >> > >
> > >> > > Dan
> > >> > >
> > >> > >
> > >> > > > On Oct 25, 2017, at 8:51 AM, Griselda Cuevas
> > ><g...@google.com.INVALID
> > >> >
> > >> > > wrote:
> > >> > > >
> > >> > > > Hi Everyone,
> > >> > > >
> > >> > > > I'd like to propose the creation of an online swag store for
> > >Apache
> > >> > Beam
> > >> > > where anyone could order swag from a wide selection and get it
> > >deliver
> > >> to
> > >> > > their home or office. I got in touch with a provider who could
> > >include
> > >> > this
> > >> > > service as part of an order I'm placing to send swag for the
> > >Meetups
> > >> > we're
> > >> > > organizing this year. What do you think?
> > >> > > >
> > >> > > > I'd also like to get your feedback on the swag I'm requesting
> > >(you
> > >> can
> > >> > > see it in the pdf I attached), what do you think of the colors,
> > >design,
> > >> > > etc.?
> > >> > > >
> > >> > > > Lastly, I'll be ordering swag for Meetup organized this year so
> > >if
> > >> > > you're hosting one or speaking at one get in touch with me to
> > >send
> > >> some!
> > >> > > >
> > >> > > > Cheers,
> > >> > > > G
> > >> > >
> > >> > > --
> > >> > > Daniel Kulp
> > >> > > dk...@apache.org - http://dankulp.com/blog
> > >> > > Talend Community Coder - http://coders.talend.com
> > >> > >
> > >> > >
> > >> >
> > >>
> >
>

Re: [Proposal] Apache Beam Swag Store

[Griselda Cuevas]

Thanks for the feedback all, I'll send this idea to the trademark@ folks
and wait for validation. Once we have it I'll look into building the store
possibly embedded in the website.

Enjoy the weekend.
G

5



On 27 October 2017 at 11:53, Tyler Akidau <taki...@google.com.invalid>
wrote:

> One additional note: for the logos w/ the name below them, would be nice to
> not have quite so much whitespace between the logo and the name. Otherwise,
> trademark validation aside, this looks great.
>
> On Fri, Oct 27, 2017 at 10:15 AM Griselda Cuevas <g...@google.com.invalid>
> wrote:
>
> > Hi Dan - thanks for bringing this up to my attention. I haven't raised
> this
> > up to the tradema...@apache.org people. Can I just reach out to them to
> > get
> > the proposal or should one of the PMCs do this?
> >
> >
> >
> > Gris Cuevas Zambrano
> >
> > g...@google.com
> >
> > Open Source Strategy
> >
> > 345 Spear Street, San Francisco, 94105
> > <https://maps.google.com/?q=345+Spear+Street,+San+Francisco,
> +94105=gmail=g>
> >
> >
> >
> > On 26 October 2017 at 18:30, Daniel Kulp <dk...@apache.org> wrote:
> >
> > >
> > > Have you run this through tradema...@apache.org yet?
> > >
> > > I bring this up for two reasons:
> > >
> > > 1) We would need to make sure the appearance and such of the logo is
> > > “correct”
> > >
> > > 2).A few years ago, Apache did have a partnership with a company that
> > > would produce various swag things and then donate a portion back to
> > > Apache.   I don’t know what the state of that agreement is and whether
> > that
> > > would restrict going to another vendor or something.
> > >
> > > Dan
> > >
> > >
> > > > On Oct 25, 2017, at 8:51 AM, Griselda Cuevas <g...@google.com.INVALID
> >
> > > wrote:
> > > >
> > > > Hi Everyone,
> > > >
> > > > I'd like to propose the creation of an online swag store for Apache
> > Beam
> > > where anyone could order swag from a wide selection and get it deliver
> to
> > > their home or office. I got in touch with a provider who could include
> > this
> > > service as part of an order I'm placing to send swag for the Meetups
> > we're
> > > organizing this year. What do you think?
> > > >
> > > > I'd also like to get your feedback on the swag I'm requesting (you
> can
> > > see it in the pdf I attached), what do you think of the colors, design,
> > > etc.?
> > > >
> > > > Lastly, I'll be ordering swag for Meetup organized this year so if
> > > you're hosting one or speaking at one get in touch with me to send
> some!
> > > >
> > > > Cheers,
> > > > G
> > >
> > > --
> > > Daniel Kulp
> > > dk...@apache.org - http://dankulp.com/blog
> > > Talend Community Coder - http://coders.talend.com
> > >
> > >
> >
>

Re: [Proposal] Apache Beam Swag Store

[Griselda Cuevas]

Hi Dan - thanks for bringing this up to my attention. I haven't raised this
up to the tradema...@apache.org people. Can I just reach out to them to get
the proposal or should one of the PMCs do this?



Gris Cuevas Zambrano

g...@google.com

Open Source Strategy

345 Spear Street, San Francisco, 94105



On 26 October 2017 at 18:30, Daniel Kulp <dk...@apache.org> wrote:

>
> Have you run this through tradema...@apache.org yet?
>
> I bring this up for two reasons:
>
> 1) We would need to make sure the appearance and such of the logo is
> “correct”
>
> 2).A few years ago, Apache did have a partnership with a company that
> would produce various swag things and then donate a portion back to
> Apache.   I don’t know what the state of that agreement is and whether that
> would restrict going to another vendor or something.
>
> Dan
>
>
> > On Oct 25, 2017, at 8:51 AM, Griselda Cuevas <g...@google.com.INVALID>
> wrote:
> >
> > Hi Everyone,
> >
> > I'd like to propose the creation of an online swag store for Apache Beam
> where anyone could order swag from a wide selection and get it deliver to
> their home or office. I got in touch with a provider who could include this
> service as part of an order I'm placing to send swag for the Meetups we're
> organizing this year. What do you think?
> >
> > I'd also like to get your feedback on the swag I'm requesting (you can
> see it in the pdf I attached), what do you think of the colors, design,
> etc.?
> >
> > Lastly, I'll be ordering swag for Meetup organized this year so if
> you're hosting one or speaking at one get in touch with me to send some!
> >
> > Cheers,
> > G
>
> --
> Daniel Kulp
> dk...@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
>

Re: [Proposal] Sharing Neville's post and upcoming meetups in the Twitter handle

[Griselda Cuevas]

Hi folks, could you help us to tweet the second part of Neville's blogpost?

Here's a suggested tweet:
2nd part of @sinisa_lyh's post is out! Read how @Spotify developed Scio, a
high level Scala API 4 the Beam Java SDK. https://goo.gl/kyjr4n

Thx!



On 20 October 2017 at 13:08, Griselda Cuevas <g...@google.com> wrote:

> Hi everyone - What do you think about sharing Neville's blogpost[1] about
> the road to Scio on the Apache Beam Twitter account?, I think it'd be good
> to share some content since the last time we were active as 9/27.
>
> Also - could you help promote some of the upcoming Meetups? I made the
> following tweets:
>
> 11/1 - San Francisco Cloud Mafia
> Tweet:
> Come join the SF Cloud Mafia to learn about stream & batch processing with
> #ApacheBeam on Nov. 1st. https://www.meetup.com/Sa
> n-Francisco-Cloud-Mafia/events/244180581/
>
> 11/22 - StockholmApache Beam Meetup
> Tweet:
> Stockholm is ready for its first #ApacheBeam meetup on Nov. 22nd. Join if
> you're around! https://www.meetup.com/Apache-Beam-Stockholm/
>
> [1] https://labs.spotify.com/2017/10/16/big-data-processing-
> at-spotify-the-road-to-scio-part-1/
>
> Thanks!
> G
>

Re: [Proposal] Apache Beam Swag Store

[Griselda Cuevas]

Hi everyone - pinging the thread to see what do you folks think about the
store idea and the initial designs for t-shirts, hoodies and stickers.

On 25 October 2017 at 09:02, Griselda Cuevas <g...@google.com> wrote:

> Ok, I just discovered I can't attach a file :s
>
> Here is the link:
> https://drive.google.com/file/d/0B-QOa4cFPVznZWlsVFgxMXVwNnM
> /view?usp=sharing
>
>
>
> On 25 October 2017 at 08:57, Lukasz Cwik <lc...@google.com.invalid> wrote:
>
>> I don't see any attachments to the e-mail.
>>
>> On Wed, Oct 25, 2017 at 8:51 AM, Griselda Cuevas <g...@google.com.invalid
>> >
>> wrote:
>>
>> > Hi Everyone,
>> >
>> > I'd like to propose the creation of an online swag store for Apache Beam
>> > where anyone could order swag from a wide selection and get it deliver
>> to
>> > their home or office. I got in touch with a provider who could include
>> this
>> > service as part of an order I'm placing to send swag for the Meetups
>> we're
>> > organizing this year. What do you think?
>> >
>> > I'd also like to get your feedback on the swag I'm requesting (you can
>> see
>> > it in the pdf I attached), what do you think of the colors, design,
>> etc.?
>> >
>> > Lastly, I'll be ordering swag for Meetup organized this year so if
>> you're
>> > hosting one or speaking at one get in touch with me to send some!
>> >
>> > Cheers,
>> > G
>> >
>>
>
>

Re: UnconsumedReads

[Griselda Cuevas]

Hi Chaim - could you elaborate a little more on how you're using or want to
use the UnconsumedReads so we can help?



Gris Cuevas Zambrano

g...@google.com

Open Source Strategy

345 Spear Street, San Francisco, 94105



On 17 October 2017 at 06:03, Chaim Turkel  wrote:

> what is the purpose of this phase?
>
> chaim
>

Re: [Proposal] Apache Beam Swag Store

[Griselda Cuevas]

Ok, I just discovered I can't attach a file :s

Here is the link:
https://drive.google.com/file/d/0B-QOa4cFPVznZWlsVFgxMXVwNnM/
view?usp=sharing



On 25 October 2017 at 08:57, Lukasz Cwik <lc...@google.com.invalid> wrote:

> I don't see any attachments to the e-mail.
>
> On Wed, Oct 25, 2017 at 8:51 AM, Griselda Cuevas <g...@google.com.invalid>
> wrote:
>
> > Hi Everyone,
> >
> > I'd like to propose the creation of an online swag store for Apache Beam
> > where anyone could order swag from a wide selection and get it deliver to
> > their home or office. I got in touch with a provider who could include
> this
> > service as part of an order I'm placing to send swag for the Meetups
> we're
> > organizing this year. What do you think?
> >
> > I'd also like to get your feedback on the swag I'm requesting (you can
> see
> > it in the pdf I attached), what do you think of the colors, design, etc.?
> >
> > Lastly, I'll be ordering swag for Meetup organized this year so if you're
> > hosting one or speaking at one get in touch with me to send some!
> >
> > Cheers,
> > G
> >
>

[Proposal] Apache Beam Swag Store

[Griselda Cuevas]

Hi Everyone,

I'd like to propose the creation of an online swag store for Apache Beam
where anyone could order swag from a wide selection and get it deliver to
their home or office. I got in touch with a provider who could include this
service as part of an order I'm placing to send swag for the Meetups we're
organizing this year. What do you think?

I'd also like to get your feedback on the swag I'm requesting (you can see
it in the pdf I attached), what do you think of the colors, design, etc.?

Lastly, I'll be ordering swag for Meetup organized this year so if you're
hosting one or speaking at one get in touch with me to send some!

Cheers,
G

Re: [Proposal] Sharing Neville's post and upcoming meetups in the Twitter handle

[Griselda Cuevas]

@Ahmet - thanks for sharing part 1 of Neville's post and the one about the
SF Cloud Mafia Meetup. We can tweet about part 2 maybe tomorrow or Weds and
about the Stockholm meetup closer to the date.

@Ismael - re:Swag, I'm thinking of creating a swag store for Apache Beam -
I'll send a separate thread with the proposal. The idea is that we create
an online store for people to order swag for their events, they could pick
from a wide selection offered by a vendor. I got us an initial budget of
USD$2k and I was planning to give codes to Meetup founders and folks
speaking at conferences this year, once we run out of this budget people
can get their own swag or we can collaborate on a joint fund to get the
store going. I'll submit a new thread with details and the vendor proposal.

G

On 23 October 2017 at 07:56, Etienne Chauchot <echauc...@gmail.com> wrote:

> Hi,
>
> +1 to share Neville's blogpost.
>
> Etienne
>
>
>
> Le 20/10/2017 à 22:08, Griselda Cuevas a écrit :
>
>> Hi everyone - What do you think about sharing Neville's blogpost[1] about
>> the road to Scio on the Apache Beam Twitter account?, I think it'd be good
>> to share some content since the last time we were active as 9/27.
>>
>> Also - could you help promote some of the upcoming Meetups? I made the
>> following tweets:
>>
>> 11/1 - San Francisco Cloud Mafia
>> Tweet:
>> Come join the SF Cloud Mafia to learn about stream & batch processing with
>> #ApacheBeam on Nov. 1st. https://www.meetup.com/San-
>> Francisco-Cloud-Mafia/events/244180581/
>>
>> 11/22 - StockholmApache Beam Meetup
>> Tweet:
>> Stockholm is ready for its first #ApacheBeam meetup on Nov. 22nd. Join if
>> you're around! https://www.meetup.com/Apache-Beam-Stockholm/
>>
>> [1] https://labs.spotify.com/2017/10/16/big-data-processing-at-
>> spotify-the-road-to-scio-part-1/
>>
>> Thanks!
>> G
>>
>>
>

[Proposal] Sharing Neville's post and upcoming meetups in the Twitter handle

[Griselda Cuevas]

Hi everyone - What do you think about sharing Neville's blogpost[1] about
the road to Scio on the Apache Beam Twitter account?, I think it'd be good
to share some content since the last time we were active as 9/27.

Also - could you help promote some of the upcoming Meetups? I made the
following tweets:

11/1 - San Francisco Cloud Mafia
Tweet:
Come join the SF Cloud Mafia to learn about stream & batch processing with
#ApacheBeam on Nov. 1st. https://www.meetup.com/San-
Francisco-Cloud-Mafia/events/244180581/

11/22 - StockholmApache Beam Meetup
Tweet:
Stockholm is ready for its first #ApacheBeam meetup on Nov. 22nd. Join if
you're around! https://www.meetup.com/Apache-Beam-Stockholm/

[1] https://labs.spotify.com/2017/10/16/big-data-processing-at-
spotify-the-road-to-scio-part-1/

Thanks!
G

Re: New contributor

[Griselda Cuevas]

Welcome Vilhem!


Gris Cuevas Zambrano

g...@google.com

Open Source Strategy

345 Spear Street, San Francisco, 94105



On 17 October 2017 at 13:54, Kenneth Knowles  wrote:

> Welcome!
>
> There are many contributor-oriented docs on the website - even if you've
> read some of them, there are probably more :-)
>
> And in case it didn't jump out, there's a label "starter" [1] that we try
> to tag JIRAs with if they might be gentle intros to the code.
>
> Kenn
>
> https://issues.apache.org/jira/issues/?jql=project%20%
> 3D%20BEAM%20AND%20labels%20%3D%20starter
>
> On Tue, Oct 17, 2017 at 1:18 PM, Vilhelm von Ehrenheim <
> vonehrenh...@gmail.com> wrote:
>
> > Hi everyone!
> > My name is Vilhelm von Ehrenheim and I would like to start contributing
> to
> > Beam.
> > I work as a Data Engineer at EQT in Stockholm and we are actively using
> > Beam on Dataflow for our processing tasks. That aside, I am also the host
> > of the Apache Beam Stockholm Meetup and would love to start being more
> > involved in the project.
> >
> > My ASF id is `while`.
> >
> > Regards,
> > Vilhelm von Ehrenheim
> >
>

[Proposal] Beam Newsletter

[Griselda Cuevas]

Hi Beam Community,

I have a proposal to start sending *monthly newsletters* to our dev and
user mailing lists. The idea is to summarize what's happening in the
project and keep everyone informed of what's happening, specially new
members, people interested in specific initiatives/efforts and help
visualize the progress in concrete milestones.

This is what I propose:

1. I'll send an email to the dev & user mailing list with a "Call for
updates" with a link to a Google doc like this

so people can add their updates.
2. I'll edit it to get it ready to share
3. I'll send an email with highlights and the link to the finalized Google
doc

I propose to do this monthly.

What do you guys think?

Gris

[Event] Strata Data Conference - New York 2017

[Griselda Cuevas]

Hi Beam Community,

Apache Beam will be featured at Strata Data Conference New York next week
[1].

Scheduled events:

** Realizing the promise of portability with Apache Beam*
Speaker: Reuven Lax
11:20am–12:00pm Thursday, September 28, 2017

** Foundations of streaming SQL; or, How I learned to love stream and table
theory*
Speaker: Tyler Akidau
1:15pm–1:55pm Thursday, September 28, 2017

** Apache Beam Dinner @ OBAO Hell's Kitchen*
If you'd like to attend please RSVP[2], space in New York restaurants is
limited and we want to make sure we can acomodate everyone :)

Everyone is welcome to this events - users and contributors, feel free to
use code Google20 to get 20% off any pass for the conference.

I hope to see a good part of our community there!

Gris

[1] https://conferences.oreilly.com/strata/strata-ny
[2] https://www.eventbrite.com/e/beam-dinner-strata-tickets-37851664347

Re: New contributor

[Griselda Cuevas]

Welcome!

On Sep 13, 2017 4:43 PM, "Lukasz Cwik"  wrote:

> Welcome.
>
> On Wed, Sep 13, 2017 at 4:30 PM, Reuven Lax 
> wrote:
>
> > Welcome Daniel!
> >
> > Reuven
> >
> > On Wed, Sep 13, 2017 at 4:27 PM, Jesse Anderson <
> je...@bigdatainstitute.io
> > >
> > wrote:
> >
> > > Welcome!
> > >
> > > On Wed, Sep 13, 2017 at 2:24 PM Daniel Oliveira
> > >  wrote:
> > >
> > > > Hi everyone,
> > > >
> > > > My name's Daniel Oliveira. I work at Google and I'd like to start
> > > > contributing to this project so I wanted to introduce myself.
> > > >
> > > > I've already read through the contribution guide and I'm excited to
> > start
> > > > making contributions soon!
> > > >
> > > > Thank you,
> > > > Daniel Oliveira
> > > >
> > > --
> > > Thanks,
> > >
> > > Jesse
> > >
> >
>

Re: new guy

[Griselda Cuevas]

Welcome Joey!

On 31 August 2017 at 07:43, Aviem Zur  wrote:

> Welcome JB #2!
>
> Glad to have you on board.
>
> On Tue, Aug 29, 2017 at 5:38 PM Joey Baruch  wrote:
>
> > my jira username is joeyfezster
> >
> > thanks
> >
> > On Tue, Aug 29, 2017 at 4:12 PM Jean-Baptiste Onofré 
> > wrote:
> >
> > > Welcome !
> > >
> > > What's your apache id ?
> > >
> > > Regards
> > > JB
> > >
> > > On 08/29/2017 02:57 PM, Joey Baruch wrote:
> > > > Hey everyone,
> > > >
> > > > Apache Beam looks like a pretty exciting new project, and I'd love to
> > > > contribute to it.
> > > > I'm a relatively fresh developer, but i'm looking learn by doing.
> > > >
> > > > Would appreciate to be added as a contributor on jira.
> > > >
> > > > Thanks!
> > > > Joey
> > > >
> > >
> > > --
> > > Jean-Baptiste Onofré
> > > jbono...@apache.org
> > > http://blog.nanthrax.net
> > > Talend - http://www.talend.com
> > >
> >
>

Re: [DISCUSS] Capability Matrix revamp

[Griselda Cuevas]

Hi, I'd also like to ask if versioning as proposed in BEAM-166 <
https://issues.apache.org/jira/browse/BEAM-166> is still relevant? If it
is, would this be something we want to add to this proposal?

G

On 21 August 2017 at 08:31, Tyler Akidau  wrote:

> Is there any way we could add quantitative runner metrics to this as well?
> Like by having some benchmarks that process X amount of data, and then
> detailing in the matrix latency, throughput, and (where possible) cost,
> etc, numbers for each of the given runners? Semantic support is one thing,
> but there are other differences between runners that aren't captured by
> just checking feature boxes. I'd be curious if anyone has other ideas in
> this vein as well. The benchmark idea might not be the best way to go about
> it.
>
> -Tyler
>
> On Sun, Aug 20, 2017 at 9:43 AM Jesse Anderson 
> wrote:
>
> > It'd be awesome to see these updated. I'd add two more:
> >
> >1. A plain English summary of the runner's support in Beam. People who
> >are new to Beam won't understand the in-depth coverage and need a
> > general
> >idea of how it is supported.
> >2. The production readiness of the runner. Does the maintainer think
> >this runner is production ready?
> >
> >
> >
> > On Sun, Aug 20, 2017 at 8:03 AM Kenneth Knowles 
> > wrote:
> >
> > > Hi all,
> > >
> > > I want to revamp
> > > https://beam.apache.org/documentation/runners/capability-matrix/
> > >
> > > When Beam first started, we didn't work on feature branches for the
> core
> > > runners, and they had a lot more gaps compared to what goes on `master`
> > > today, so this tracked our progress in a way that was easy for users to
> > > read. Now it is still our best/only comparison page for users, but I
> > think
> > > we could improve its usefulness.
> > >
> > > For the benefit of the thread, let me inline all the capabilities fully
> > > here:
> > >
> > > 
> > >
> > > "What is being computed?"
> > >  - ParDo
> > >  - GroupByKey
> > >  - Flatten
> > >  - Combine
> > >  - Composite Transforms
> > >  - Side Inputs
> > >  - Source API
> > >  - Splittable DoFn
> > >  - Metrics
> > >  - Stateful Processing
> > >
> > > "Where in event time?"
> > >  - Global windows
> > >  - Fixed windows
> > >  - Sliding windows
> > >  - Session windows
> > >  - Custom windows
> > >  - Custom merging windows
> > >  - Timestamp control
> > >
> > > "When in processing time?"
> > >  - Configurable triggering
> > >  - Event-time triggers
> > >  - Processing-time triggers
> > >  - Count triggers
> > >  - [Meta]data driven triggers
> > >  - Composite triggers
> > >  - Allowed lateness
> > >  - Timers
> > >
> > > "How do refinements relate?"
> > >  - Discarding
> > >  - Accumulating
> > >  - Accumulating & Retracting
> > >
> > > 
> > >
> > > Here are some issues I'd like to improve:
> > >
> > >  - Rows that are impossible to not support (ParDo)
> > >  - Rows where "support" doesn't really make sense (Composite
> transforms)
> > >  - Rows are actually the same model feature (non-merging windowfns)
> > >  - Rows that represent optimizations (Combine)
> > >  - Rows in the wrong place (Timers)
> > >  - Rows have not been designed ([Meta]Data driven triggers)
> > >  - Rows with names that appear no where else (Timestamp control)
> > >  - No place to compare non-model differences between runners
> > >
> > > I'm still pondering how to improve this, but I thought I'd send the
> > notion
> > > out for discussion. Some imperfect ideas I've had:
> > >
> > > 1. Lump all the basic stuff (ParDo, GroupByKey, Read, Window) into one
> > row
> > > 2. Make sections as users see them, like "ParDo" / "side Inputs" not
> > > "What?" / "side inputs"
> > > 3. Add rows for non-model things, like portability framework support,
> > > metrics backends, etc
> > > 4. Drop rows that are not informative, like Composite transforms, or
> not
> > > designed
> > > 5. Reorganize the windowing section to be just support for merging /
> > > non-merging windowing.
> > > 6. Switch to a more distinct color scheme than the solid vs faded
> colors
> > > currently used.
> > > 7. Find a web design to get short descriptions into the foreground to
> > make
> > > it easier to grok.
> > >
> > > These are just a few thoughts, and not necessarily compatible with each
> > > other. What do you think?
> > >
> > > Kenn
> > >
> > --
> > Thanks,
> >
> > Jesse
> >
>

Re: contrib package for beam?

[Griselda Cuevas]

I like the idea -- This seems like a thing I can help with to get familiar
with the project. Who could help me make a list of available things?

On 16 August 2017 at 12:02, Jesse Anderson 
wrote:

> I've had this discussion before. I'd love to see one so that there's a
> consistent home for things that don't belong in the API.
>
> On Wed, Aug 16, 2017, 2:55 PM Pablo Estrada 
> wrote:
>
> > Hi all,
> > What would be an appropriate medium for contributions such as utility
> > Pipelines or PTransforms? Perhaps it's different for each kind of
> > contribution (sources/sinks, PTransforms, or utility pipelines).
> >
> > The question comes from an active user on Stack Overflow[1], and it seems
> > pertinent. What's standard practice in other projects to keep this sort
> of
> > contributions shared and available? Perhaps keep a list with links in our
> > readme, or the beam site, or something else?
> >
> > Best
> > -P.
> >
> > 1 -
> >
> > https://stackoverflow.com/questions/45603814/any-
> contrib-package-for-apache-beam-where-i-can-commit-a-dataflow-pipeline
> >
> --
> Thanks,
>
> Jesse
>

Hello from a newbie to the data world living in the city by the bay!

[Griselda Cuevas]

Hi Beam community,

I’m Griselda (Gris) Cuevas and I’m very excited to join the community, I’m
looking forward to learning awesome things from you and to getting the
chance to collaborate on great initiatives.

I’m currently working at Google and I’m studying a masters in operations
research and data science at UC Berkeley. I’m interested in Natural
Language Processing, Information Retrieval and Online Communities. Some
other fun topics I love are juggling, camping and -just getting into it-
 listening to podcasts, so if you ever want to discuss and talk about any
of these topics, here I am!

Another reason why I’m here is because I want to help this project grow and
thrive. This means that you’ll see me contributing to the project, reaching
out to ask questions as I get familiar with our community, and I also
helping evangelize Apache Beam by organizing meetups, hangouts, etc.

I say bye for now, I’ll see you around,

Cheers,

G