Re: Unable to clone beam site

Make sure to checkout the Website section of the contribution guide that contains all the tips and tricks for working on the website: http://beam.incubator.apache.org/contribute/contribution-guide/#website On Thu, Dec 1, 2016 at 5:51 AM, Sandeep Deshmukh wrote: > Yes,

Re: [DISCUSS] Graduation to a top-level project

+1 You might even say I'm beaming with pride ;-) On Tue, Nov 22, 2016 at 11:58 AM, Kenneth Knowles wrote: > +1 !!! > > I especially love how the diversity of the community has contributed to the > conceptual growth and quality of Beam. I can't wait for more! > > On

Re: Contributing for improvement of the Beam website

And just FYI, there's a section on the website at the end of the contribution guide: http://beam.incubator.apache.org/contribute/contribution-guide/#website On Sat, Oct 29, 2016 at 9:46 AM, Minudika Malshan wrote: > Hi, > > Here is the PR[1] for BEAM-835. > Please review.

Re: [DISCUSS] Merging master -> feature branch

very large > > and > > >> > non-trivial merges later. > > >> > I think that frequent merges for feature-branches should most of the > > time > > >> > be trivial (no conflicts) and a committer should be allowed to > > self-merge

Re: A CI Server for Beam?

Jason recently started documenting the project's testing setup. See http://beam.incubator.apache.org/contribute/testing/ On Sat, Oct 22, 2016 at 11:18 PM, Jean-Baptiste Onofré wrote: > Hi > > We use both Jenkins and Travis. > > Jenkins is on build.apache.org and you can find

Re: [ANNOUNCEMENT] New committers!

Wonderful to see your contributions recognized ;-) On Fri, Oct 21, 2016 at 3:46 PM, Ahmet Altay wrote: > Congratulations to all of you! > > Ahmet > > On Fri, Oct 21, 2016 at 3:35 PM, Ben Chambers > > wrote: > > > Congrats. +3! > > > > On

Re: [REMINDER] Technical discussion on the mailing list

> > At the end of the day, it comes down to two questions: > > 1) Are there technical and project direction discussions happening off > list and not reflected back to the list? > > 2) If yes, are the concrete decisions being made as a result of the off > list discussions? > From an Apache

Re: [PROPOSAL] New Beam website design?

te: > > > Hi all! > > > > I want to revive this thread if I may. Is there any way I can help on the > > website redesign? Additionally, is anyone currently working on the UI/UX > > design? I want to make sure I don't duplicate any work. > > > > Cheers!

Re: FYI: All Runners Tested In Precommit

Awesome! Strong tests are hugely important in a project with so many diverse components. On Thu, Sep 15, 2016 at 12:16 PM, Jason Kuster wrote: > Hi all, > > Just a quick update -- as of yesterday all new PRs now run the WordCount > end-to-end test against every

Re: Proposal: Dynamic PIpelineOptions

+Amit, Aljoscha, Manu Any comments from folks on the Flink, Spark, or Gearpump runners? On Tue, Aug 2, 2016 at 11:10 AM, Robert Bradshaw < rober...@google.com.invalid> wrote: > Being able to "late-bind" parameters like input paths to a > pre-constructed program would be a very useful feature,

[REFLECT] Beam’s Half Birthday!

Hi Beamers! It’s been six months today since Beam was accepted into incubation. It’s thrilling how far we’ve come since then! I’d like to volunteer to put together a post on the Beam blog summarizing our progress since February. Here’s a starting point... What am I missing that we should

Re: [KUDOS] Contributed runner: Gearpump!

Awesome! On Wed, Jul 20, 2016 at 6:42 PM, Manu Zhang wrote: > Thanks Kenn and others for the review and help along the way. Feel free to > ping me on slack if you want to know more about gearpump-runner or > gearpump. > > Thanks everyone :) > Manu Zhang > > > > On Thu,

Re: Beam Interview

Love this, Jesse! And pretty inspired reading the answers so far ;-) On Mon, Jul 11, 2016 at 1:42 PM, Jesse Anderson wrote: > Thanks! > > On Mon, Jul 11, 2016 at 1:02 PM Ismaël Mejía wrote: > > > Great Idea, I just added my answers, English is not my

Re: Scala DSL

+Rafal & Andrew again I am leaning DSL for two reasons: (1) scio uses the existing java execution environment (and won't have a language-specific fn harness of its own), and (2) it changes the abstractions that users interact with. I recently saw a scio repl demo from Reuven -- there's some

Re: [NOTICE] Change on Filter

Release notes for each release are being tracked in JIRA. For example: https://issues.apache.org/jira/browse/BEAM/fixforversion/12335764/ Davor is planning to send a follow up email about how we use this process. And as we redo the website layout, we should figure out how to surface this

Re: [thread fork] Apache Beam & Google Cloud Dataflow

With my Google employee hat on, I'd like to soften that claim a little ;-) Currently, the Beam SDK runs again Google Cloud Dataflow. But since Beam isn't itself ready for prime time yet, Google doesn't officially provide support for running Beam on Cloud Dataflow right now, and Google Cloud

Re: [PROPOSAL] New Beam website design?

T ? > > Regards > JB > > > On 06/17/2016 12:21 AM, Frances Perry wrote: > >> Good point, JB -- let's redo the page layout as well. >> >> I started with your proposal and tweaked it a bit to add in more details >> and divide things a bit more accord

Re: [DISCUSS] Developing new components -- branches, maturity, and committers

en we say feature branch, are we talking about a branch in the main >>>> >>> repo? >>> >>>> I would propose that feature branches live in the repos of the >>>> committers >>>> who are working on a feature. >>>>

[DISCUSS] Developing new components -- branches, maturity, and committers

Hi Beamers -- I’m thrilled by the recent energy and activity on writing new Beam runners! But that also means it’s probably time for us to figure out how, as a community, we want to support this process. ;-) Back near the beginning, we had a thread [1] discussing that feature branches are the

Re: (Virtual) Beam Developers Meetup - 5/4 @ 8am PDT

kat...@innerzeal.com> wrote: > In my experience, G+Hangouts has a limitation of 10 attendees which is > lame. You could explore zoom or some free conferencing service. > > Thanks! > > On Fri, Apr 29, 2016 at 9:49 PM Frances Perry <f...@google.com.invalid> > wrote: > >

Re: getting started?

Here's the Beam jira: https://issues.apache.org/jira/browse/BEAM If you want to dig into examples to learn the Beam model, I'd suggest starting with these walkthroughs: https://cloud.google.com/dataflow/examples/wordcount-example https://cloud.google.com/dataflow/examples/gaming-example

Re: [PROPOSAL] New sdk languages

+Neville and Rafal for their take ;-) Excited to see this out. Multiple community driven SDKs are right in line with our goals for Beam. On Thu, Mar 24, 2016 at 3:04 PM, Ismaël Mejía wrote: > Addendum: actually the semantic model support is not so far away as I said >

Re: [PROPOSAL] Create new Jira IO component

The original plan was that IOs would just be in the library extensions (e.g. sdk-java-extensions). It'd fine to subdivide that further if needed, but maybe we should wait until it gets a bit bigger? Dan, what do you think, as component owner? On Mon, Mar 21, 2016 at 2:33 AM, Jean-Baptiste Onofré

Draft Contribution Guide

Hi Beamers! We've started a draft for the Beam contribution guide. Please take a look and provide feedback. Once things settle, we'll get this moved over on to the Beam website. Frances

Re: Optimization of logical plan

(I'm not familiar with the details of Catalyst itself.) The existing runners (Cloud Dataflow, Spark, Flink) all do optimizations of their own, though it's quite likely there's a set of optimizations that are conceptually shared. For example, something like ParDo fusion is pretty basic to

Re: Apache Storm Runner for Beam?

As we set up the JIRA, I've created a placeholder issue to track interest in a Storm runner: https://issues.apache.org/jira/browse/BEAM-9 On Wed, Feb 10, 2016 at 9:36 PM, Jean-Baptiste Onofré wrote: > Hi Taylor, > > In a first time, I would say in Beam (as we do for the other