Re: [Proposal] Requesting PMC approval to start planning for Beam Summits 2019

I'm sorry, but certain things require special care. General organizing discussions can proceed on dev@, excluding this specific one. On Sun, Jan 20, 2019 at 8:43 PM Gris Cuevas wrote: > > > On 2019/01/19 16:58:52, Davor Bonaci wrote: > > I'd say these matters are generally

Re: [Proposal] Requesting PMC approval to start planning for Beam Summits 2019

I'd say these matters are generally private between the organizer(s) and the PMC. This thread should continue on the PMC-private mailing list. On Fri, Jan 18, 2019 at 4:06 PM Ahmet Altay wrote: > Thank you Joana. > > Kenn and PMC members could you comment on what needs to be done to move > this

[ANNOUNCEMENT] New Beam chair: Kenneth Knowles

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

Re: JIRA permissions request

It would be great to spec out "the necessary dashboards, reports, and views", get feedback and agreement, and make it better along the way. AFAIK, requesting this from INFRA should be fine; they can double check what that specific group "all-developers" entails. That said, any tickets filed

Re: [Proposal] Beam Mascot

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

Re: Apache Beam Python Wheels Repository

New repository is not a ticket, it is a self-serve thing. That said, you probably want to develop the proposal a bit further, understanding/educating others about the benefits of what you are proposing, any alternatives, why a repository is needed, why the sample repository has Travis CI when

Re: Community Examples Repository

> > it makes sense to modularize It certainly does, but somebody just had another proposal to move the website into the main repository ;-). That proposal was also good for ~everyone. Fun times... (I have my opinions, of course, but I'm fine with any approach.) On Wed, Aug 1, 2018 at 4:37 PM,

Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2

.) But, it is something that warrants a discussion... On Wed, Jun 20, 2018 at 9:47 AM, Lukasz Cwik wrote: > Davor, please -1 the release if you believe LEGAL-288 applies. > > On Wed, Jun 20, 2018 at 9:37 AM Davor Bonaci wrote: > >> Please take a peek at LEGAL-288 [1], which I lear

Re: [VOTE] Apache Beam, version 2.5.0, release candidate #2

Please take a peek at LEGAL-288 [1], which I learned about recently in the context of another project. Looks like an issue, requiring a new RC, but I didn't have a chance to look closely. Thanks. Davor [1] https://issues.apache.org/jira/browse/LEGAL-288 On Wed, Jun 20, 2018 at 9:17 AM, Pablo

Re: Beam Cookbook?

Hi Austin -- It would be great to see this materialize. I've been pursued by publishers a lot in the last year, so I might be able to facilitate introductions if you need them. You'll probably want to have a few sample draft chapters, however. I'm aware of 3 different groups creating related

Re: [VOTE] Go SDK

Fri, May 25, 2018 at 10:26 AM Davor Bonaci wrote: > >> ETA: weekend. >> >> On Fri, May 25, 2018 at 9:35 AM Henning Rohde wrote: >> >>> RESULT: the vote passed with only +1s! Thanks you all for the kind >>> comments. >>> >>> The

[ANNOUNCEMENT] New committers, May 2018 edition!

Please join me and the rest of Beam PMC in welcoming the following contributors as our newest committers. They have significantly contributed to the project in different ways, and we look forward to many more contributions in the future. * Griselda Cuevas * Pablo Estrada * Jason Kuster

Re: [VOTE] Go SDK

ETA: weekend. On Fri, May 25, 2018 at 9:35 AM Henning Rohde wrote: > RESULT: the vote passed with only +1s! Thanks you all for the kind > comments. > > The only pending item is the IP clearance form (draft: > https://web.tresorit.com/l#nUkKlgi3cBYxYAOyhCMXIw >

Re: Missing copyright notices for shaded packages

> > jars generated off of current master contain no LICENSE, NOTICE, or other > metadata > We should fix this. This may be an issue. suggested approach of overapproximating >> > The purpose of quoted sentence above ("A part of...") is to qualify when a particular portion applies. It contains

Re: [VOTE] Go SDK

gt; On Tue, May 22, 2018 at 3:14 PM Robert Bradshaw <rober...@google.com> > wrote: > >> On Tue, May 22, 2018 at 2:42 PM Davor Bonaci <da...@apache.org> wrote: >> >> >>* Robert mentioned that "SGA should have probably already been >> file

Re: Missing copyright notices for shaded packages

t notice, this list of conditions and the following disclaimer in > the documentation and/or other materials provided with the distribution. > > (4) any proposed fix > > NOTICE file in the jar. > > I am not a lawyer, this is not legal advice. > > On Tue, May 22, 2018 at 2

Re: Missing copyright notices for shaded packages

Thanks for the report! Could you please comment more as to: (1) what artifacts are impacted and where are they distributed, (2) the external dependency being distributed, (3) license and/or term not adhered to, and (4) any proposed fix? Any such information would be helpful in triaging the

Re: [VOTE] Go SDK

> > * Robert mentioned that "SGA should have probably already been filed" > in the previous thread. I got the impression that nothing further was > needed. I'll follow up. > Please just follow: http://incubator.apache.org/ip-clearance/. Simple. Quick. Perhaps relevant: I saw some golang

Re: [VOTE] Go SDK

+1 (binding), with the following caveats: * [before closing the vote] Completion of IP clearance process, as we've been requested. It is easier to do it than having to argue why it is not necessary. * [at any time, possibly later] Figuring out the release mechanics. Great work; across the board!

Re: Graal instead of docker?

This thread is extremely valuable. It poses hard questions. It strengthens good arguments. It teaches a way of thinking. It gives feedback. I want to thank Romain in particular for driving it, and everyone who has participated thus far. That being said, the exchange has crossed the line on behalf

Re: Apache Beam - jenkins question

nkins to access the credentials UI; once the >> credential is created in Jenkins it should be able to be set as an >> environment variable through the Jenkins job configuration (groovy files in >> $BEAM_ROOT/.test-infra/jenkins). Hope this helps. >> >> Jason >>

Fwd: Apache Beam - jenkins question

Hi Kamil -- Thanks for reaching out. This is a great question for the dev@ mailing list. You may want to share a little bit more why you need, how long, frequency of updates to the secret, etc. for the community to be aware how things work. Hopefully others on the mailing list can help you by

Re: [PROPOSAL] JIRA notification recipient changes

An INFRA ticket is needed. (As long as the report is automatically a watcher, the change is a strict improvement. If not, it's a strict degradation.) On Tue, Apr 17, 2018 at 1:55 PM, Kenneth Knowles wrote: > Hi all, > > Currently, every touch on a JIRA causes four

Re: Board report - March '18

net> > wrote: > >> +1 >> >> It looks good to me. >> >> Thanks ! >> >> Regards >> JB >> Le 15 mars 2018, à 08:40, Davor Bonaci <da...@apache.org> a écrit: >>> >>> Thanks JB for starting the report. >>> >>> I

Re: Board report - March '18

Thanks JB for starting the report. If interested, please take a look at the complete draft [1], and comment or contribute content, as appropriate. I'll submit the report sometime in the next 24 hours. Thanks! Davor [1]

Re: slack @the-asf?

Go for it! Thanks Romain! On Wed, Mar 14, 2018 at 1:35 AM, Romain Manni-Bucau wrote: > Hi guys, > > What do you think to migrate to the standard asf slack? I would make it a > bit more easy to find beam channel IMHO and it would stay consistent with > others. It also

Re: The Go SDK got accidentally merged - options to deal with the pain

I support leaving things as they stand now -- thanks for finding a good way out of an uncomfortable situation. That said, two things need to happen: (1) SGA needs to be filed asap, per Board feedback in the last report, and (2) releases cannot contain any code from the Go SDK before formally

Re: Euphoria Java 8 DSL - proposal

So, it's on track but it takes a little more time than expected. >> >> Regards >> JB >> >> On 02/19/2018 05:40 AM, Davor Bonaci wrote: >> > I may have missed things, but any update on the progress of this >> donation? >> > >&

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

(That's not the question for Matthias, it is for the PMC. Thankfully, JB volunteered to help formalize things.) On Fri, Feb 23, 2018 at 7:56 AM, Kenneth Knowles wrote: > +1 to the proposal, and same question as Gris. > > On Wed, Feb 21, 2018 at 9:17 AM, Griselda Cuevas

Re: Euphoria Java 8 DSL - proposal

sense after the last method he used >> (eg.: in >> ReduceByKey, we know that after >> keyBy either reduceBy method should >> come). >> It is >> implemented as a series of >>

Fwd: Google Summer of Code 2018 is coming

This is a great way to grow the community. If you are interested in mentoring students contributing to Beam, please apply! -- Forwarded message -- From: Ulrich Stärk Date: Sun, Jan 21, 2018 at 1:22 PM Subject: Google Summer of Code 2018 is coming To:

[DISCUSS] State of the project

Hi everyone -- Apache Beam was established as a top-level project a year ago (on December 21, to be exact). This first anniversary is a great opportunity for us to look back at the past year, celebrate its successes, learn from any mistakes we have made, and plan for the next 1+ years. I’d like

Re: Happy new year

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.

Re: Euphoria Java 8 DSL - proposal

Hi David, As JB noted, merging of these two projects is a great idea. If fact, some of us have had those discussions in the past. Legally, nothing particular is strictly necessary as the code seem to already be Apache 2.0 licensed. We don't, however, want to be perceived as making hostile forks,

Re: Report to the Board, December 2017 edition

, 2017 at 1:58 PM, Griselda Cuevas <g...@google.com> wrote: >> >>> LGTM thanks for sharing. >>> >>> >>> >>> On 12 December 2017 at 20:54, Jean-Baptiste Onofré <j...@nanthrax.net> >>> wrote: >>> >>>> It

Report to the Board, December 2017 edition

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.

A personal update

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

DataWorks Summit Sydney 2017

Apache Beam will be featured at the DataWorks Summit / Hadoop Summit next week in Sydney, Australia [1]. Scheduled events: * Realizing the promise of portable data processing with Apache Beam [2] Time: Thursday, 9/21, 3:10 pm Speaker: Davor Bonaci * Birds-of-a-feather: IoT, Streaming

Re: Report to the Board, September 2017 edition

Thanks everyone for a super quick turnaround! (The report is now submitted.) On Wed, Sep 13, 2017 at 10:45 AM, Davor Bonaci <da...@apache.org> 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 Wed

Report to the Board, September 2017 edition

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, 9/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.

[ANNOUNCEMENT] New PMC members, August 2017 edition!

Please join me and the rest of Beam PMC in welcoming the following committers as our newest PMC members. They have significantly contributed to the project in different ways, and we look forward to many more contributions in the future. * Ahmet Altay Beyond significant work to drive the Python

[ANNOUNCEMENT] New committers, August 2017 edition!

Please join me and the rest of Beam PMC in welcoming the following contributors as our newest committers. They have significantly contributed to the project in different ways, and we look forward to many more contributions in the future. * Reuven Lax Reuven has been with the project since the

Re: MergeBot is here!

This is fantastic! Thank you Jason, and special thanks to the Infrastructure team for supporting us every step of the way. On Fri, Jul 7, 2017 at 1:21 PM, Jason Kuster wrote: > Hi Beam Community, > > Early on in the project, we had a number of discussions about

Re: [DISCUSS] Apache Beam 2.1.0 release next week ?

+1 On Thu, Jun 22, 2017 at 5:42 AM, Etienne Chauchot wrote: > Besides, there are some minor fixes/enhancements that lack in spark > > For info, bellow are the ones raised by nexmark test suite: > > https://issues.apache.org/jira/browse/BEAM-2499 > >

Fwd: [Report] Eagle - June 2017

>From this month's Eagle report: "Community is working on Alert engine based Apache Beam, led by YHD.com. https://github.com/1haodian/eagle/tree/alertenginebeam; This could be an opportunity for someone in the Beam project to reach out, and help out with the cross-project integration. Any

Re: Reduced Availability from 17.6. - 24.6

To tag along on the same thread, I'm out through the Independence Day holiday. Back on 7/5. On Fri, Jun 16, 2017 at 10:03 PM, Aljoscha Krettek wrote: > Hi, > > I’ll be on vacation next week, just in case anyone is wondering why I’m > not responding. :-) > > Best, > Aljoscha

Re: Report to the Board, June 2017 edition

Thanks everyone; the report is now submitted. On Tue, Jun 13, 2017 at 7:47 AM, Davor Bonaci <da...@apache.org> 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, 6/14. > > If inter

Re: DataWorks Summit San Jose 2017

, Davor Bonaci <da...@apache.org> wrote: > Apache Beam will be featured at the DataWorks Summit / Hadoop Summit next > week in San Jose, CA [1]. > > Scheduled events: > * Realizing the promise of portable data processing with Apache Beam [2] > Time: Wednesday, 6/14, 11:

Report to the Board, June 2017 edition

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, 6/14. If interested, please take a look at the draft [1], and comment or contribute content, as appropriate. I'll submit the report sometime on Wednesday. Thanks!

DataWorks Summit San Jose 2017

Apache Beam will be featured at the DataWorks Summit / Hadoop Summit next week in San Jose, CA [1]. Scheduled events: * Realizing the promise of portable data processing with Apache Beam [2] Time: Wednesday, 6/14, 11:30 am Speaker: Davor Bonaci * Stateful processing of massive out-of-order

Re: Python SDK: BigTableIO

(JIRA role added; reassigned.) On Thu, Jun 1, 2017 at 10:05 AM, Chamikara Jayalath wrote: > Thanks. I added some comments to the doc. > > Davor should be able to assign this JIRA to you. Also, Solomon who > implemented the Java BigTable connector might have more input

Re: New doc: Beam Runner Guide

Great work! Once comments are resolved in the document, can we move this to the Contribute section of the website? I think that would make it much more discoverable to everyone. On Mon, May 22, 2017 at 1:33 AM, Aljoscha Krettek wrote: > Cool, I’ll give this a read once I’m

Re: Streaming Data Pipeline Support in Python

As a project, we don't have an official time-based roadmap. So far, the project went through the "standard" cycle: getting accepted into incubation, code donation, first release, graduation, and the first stable release last week. Going forward, I'll be looking into discussing and formalizing

Re: [Road map][R SDK]

> > Is there an "official" roadmap for 2017? > We don't have an official time-based roadmap. So far, the project went through the "standard" cycle: getting accepted into incubation, code donation, first release, graduation, and the first stable release last week. Going forward, I'll be looking

Re: Apache: Big Data North America 2017 conference

What an incredible conference this year. It was nice to meet many of you -- thanks everyone! On Wed, May 17, 2017 at 6:00 PM, Davor Bonaci <da...@apache.org> wrote: > Just a remainder that the Birds of a Feather sessions begins in 30 minutes > in the Windsor room. > > Aft

Re: Apache: Big Data North America 2017 conference

-of-a-Feather room, and figure out the logistics.) On Mon, May 15, 2017 at 10:10 AM, Davor Bonaci <da...@apache.org> wrote: > If you'd like to meet at the conference, I know many of us will be in the > Balmoral room immediately after the keynote finishes on Wednesday, around > 9:45 am or

First stable release completed!

The first stable release is now complete! Release artifacts are available through various repositories, including dist.apache.org, Maven Central, and PyPI. The website is updated, and announcements are published. Apache Software Foundation press release:

Re: Website homepage visual refresh

I think it is great too -- since it is an obvious improvement, let's merge and iterate! On Tue, May 16, 2017 at 6:06 AM, Jean-Baptiste Onofré wrote: > Hi Jeremy, > > great job ! I like the new look'n feel. > > Thanks ! > Regards > JB > > > On 05/16/2017 07:44 AM, Jeremy

[RESULT] [VOTE] First stable release: release candidate #4

I'm happy to announce that we have unanimously approved this release. There are 14 approving votes, 6 of which are binding: * Ahmet Altay * Davor Bonaci * Robert Bradshaw * Lukasz Cwik * María García Herrero * Thomas Groh * Dan Halperin * Pei He * Chamikara Jayalath * Aljoscha Krettek * Jason

Re: [VOTE] First stable release: release candidate #4

t; > > > >>> cause some tests to be skipped (but no failure). However, I > > don't > > > > > > >>> think it's worth cutting another release candidate for. > > > > > > >>> > > > > > > >>> Everything else is l

Re: First stable release: release candidate #3

This RC is now obsolete -- see RC #4 information with a formal vote in a separate thread [1]. Davor [1] https://lists.apache.org/thread.html/8cf5d7583111f7d67bd21918eb35a29823572ad9ebc1d6df9656bc79@%3Cdev.beam.apache.org%3E On Fri, May 12, 2017 at 12:57 AM, Davor Bonaci <da...@apache.org>

[VOTE] First stable release: release candidate #4

Hi everyone -- After going through several release candidates, setting and validating acceptance criteria, running a hackathon, and polishing the release, now is the time to vote! Please review and vote on the release candidate #4 for the version 2.0.0, as follows: [ ] +1, Approve the release [ ]

Re: First stable release: release candidate #2

This RC is now obsolete -- see RC #3 information in a separate thread [1]. Davor [1] https://lists.apache.org/thread.html/25493fded77367299ad185c308d658eeb10e4f03be725154b0e5b08d@%3Cdev.beam.apache.org%3E On Wed, May 10, 2017 at 10:28 PM, Davor Bonaci <da...@apache.org> wrote: > Th

First stable release: release candidate #3

The release candidate #3 for the version 2.0.0 has been built. I think this candidate could be it -- we have cleared the entire list of blocking changes [8]! I'd like to ask everyone to give this candidate a try -- this is the last opportunity we have to fix any critical issues if the final

Apache Beam Meetup in Bay Area

. Location: Hortonworks HQ 5470 Great America Parkway, Santa Clara, CA, USA Agenda: 6:00 pm: Doors open 6:00 pm - 6:15 pm: Networking, Pizza and Drinks 6:15 pm - 6:30 pm: Introduction & Apache Beam release 2.0.0 - Rafael Coss and Davor Bonaci 6:30 pm - 7:15 pm: Using Apache Beam for Batch, Strea

Re: First stable release: release candidate #1

This RC is now obsolete -- see RC #2 information in a separate thread [1]. Davor [1] https://lists.apache.org/thread.html/f4f13f8b4768d0597e7f0c60a0b4d4358c4b8cbc4af86f17f58a1a4d@%3Cdev.beam.apache.org%3E On Mon, May 8, 2017 at 1:59 PM, Davor Bonaci <da...@apache.org> wrote: > Th

First stable release: release candidate #2

The release candidate #2 for the version 2.0.0 has been built. I believe this is a pretty good candidate for release -- we have (basically) cleared the entire list of blocking changes [8]! I'd like to ask everyone to give this candidate a try -- this is the last opportunity we have to fix any

Re: Apache: Big Data North America 2017 conference

I think we'll plan as we go -- watch for updates here. Thursday would be the most likely day. On Tue, May 9, 2017 at 10:31 AM, Ashish <paliwalash...@gmail.com> wrote: > I will be there. > > Any hack hour planned yet or we plan on the go. > > On Mon, May 8, 2017 at 11:20

Re: Apache: Big Data North America 2017 conference

Just a remainder that this is happening next week -- I hope to see many of your there! On Mon, Apr 24, 2017 at 7:18 AM, Aljoscha Krettek <aljos...@apache.org> wrote: > I’ll also be there. Looking forward to meeting all of you! > > Best, > Aljoscha > > On 24. Apr 2017, at

Re: Congratulations Davor!

t; > > >>>>> On May 4, 2017, at 7:08 AM, Amit Sela < > > > > > > > > amitsel...@gmail.com > > > > > > > > > > > > > > > > > > > > >> > wrote: > > > > > >

First stable release: release candidate #1

The release candidate #1 for the version 2.0.0 has been built. The complete staging area is available for review, which includes: * JIRA release notes [1], * the official Apache source release to be deployed to dist.apache.org [2], which is signed with the key with fingerprint 8F0D334F [3], * all

First stable release: Acceptance criteria

Based on the process previously discussed [1], I've seeded the acceptance criteria document [2]. Please consider contributing to this effort by: * proposing additional acceptance criteria, and/or * supporting criteria proposed by others, and/or * validating a criteria. Please note that

Re: Process for getting the first stable release out

is would reduce the > need for manual (and error-prone) cherry-picking. > > On Fri, May 5, 2017 at 5:21 PM, Davor Bonaci <da...@apache.org> wrote: > > The release branch is now created [1]. Anything for the first stable > > release should go into master as usual, and then get c

Re: Process for getting the first stable release out

ww.quora.com/Why-do-you-have-to-throw-out-the-first-pancake> > > will > > be not ready to serve customers. > > > > On Fri, May 5, 2017 at 11:40 AM, Kenneth Knowles <k...@google.com.invalid > > > > wrote: > > > > > On Thu, May 4, 2017 at 12:07 PM

Re: First stable release: version designation?

gt; > > > 2.0.0. > > > > > > > > > > > > On Thu, May 4, 2017 at 12:25 PM, Lukasz Cwik > > > <lc...@google.com.invalid > > > > > > > > > > > wrote: > > > > > > > > > > > > &g

Re: Seeking help for running bash script in Maven

I don't believe this has anything to do with Maven. Maven isn't passing any arguments to the script, or anything similar. Script's location is figured out here: HERE="$(dirname $0)" and then used to like this: ARCHETYPE_ROOT="${HERE}/src/main/resources/archetype-resources" mkdir -p

Re: First stable release: version designation?

I slightly prefer1.0.0 for the *first* stable release, but fine > with > > > > 2.0.0. > > > > > > > > > > On Thu, May 4, 2017 at 12:25 PM, Lukasz Cwik > > <lc...@google.com.invalid > > > > > > > > > wrote: > > >

Re: Slack Invites

Off-topic: The most annoying thing (to me) is that Slack's auto-detection of self-invite bots is very sensitive to frequent invites of just one member. When this activates, we get blocked from inviting more people and we have to contact Slack support to unblock further invites. They resolve it

Re: First stable release: version designation?

release process to make sure what is released is > > indeed stable. > > > > Normally people would have higher expectation on 2.0 release compared to > > 1.0 release. > > > > On Mon, Mar 6, 2017 at 6:34 PM, Davor Bonaci <da...@apache.org> wrote: > > > > > It

Process for getting the first stable release out

We've been working on the first stable release for a while now -- we've been tracking blocking issues [1], resolved many of them, organized a hackathon [2], and improved testing coverage in various areas. I think we are nearly done -- there are a few more blocking issues left in JIRA, and

Re: Community hackathon

! Davor On Wed, Apr 26, 2017 at 2:02 PM, Davor Bonaci <da...@apache.org> wrote: > The outage is still ongoing, unfortunately... I think we should make one > more (and final) delay. > > New (final) start time: 11 PM Pacific, and we start regardless of the > outage. > > On We

Re: Community hackathon

The outage is still ongoing, unfortunately... I think we should make one more (and final) delay. New (final) start time: 11 PM Pacific, and we start regardless of the outage. On Wed, Apr 26, 2017 at 10:04 AM, Davor Bonaci <da...@apache.org> wrote: > *** DELAYED START *** > > Unf

Re: Community hackathon

gt; > > > > On Apr 24, 2017 12:51 AM, "Jean-Baptiste Onofré" <j...@nanthrax.net> > > wrote: > > > > > > > That's a wonderful idea ! > > > > > > > > I think the easiest way to organize this event is using the Slack > > > chan

Community hackathon

We've been working as a community towards the first stable release for a while now, and I think we made a ton of progress across the board over the last few weeks. We could try to organize a community-wide hackathon to identify and fix those last few issues, as well as to get a better sense of

Re: Hanging Jenkins builds.

Intermittent hanging exist for several days, maybe up to a week. I think it correlates with updates/restarts/reconfiguration/etc. of the Jenkins instance on the infrastructure side. Terminating the build and restarting did work around the problem a few times. On Sat, Apr 22, 2017 at 9:42 AM, Ted

Re: [PROPOSAL] Remove KeyedCombineFn

+1 -- this is a good simplification. On Fri, Apr 21, 2017 at 10:24 AM, Kenneth Knowles wrote: > Hi all, > > I propose that we remove KeyedCombineFn before the first stable release. > > I don't think it adds enough value for the complexity it adds to e.g. >

Re: Build failed in Jenkins: beam_SeedJob #214

Not so simple, unfortunately [1]. Ideas welcome ;-) Davor [1] https://github.com/jenkinsci/job-dsl-plugin/wiki/Migration#migrating-to-160 On Tue, Apr 18, 2017 at 9:57 AM, Ted Yu wrote: > I wonder if we should adopt the suggestion here (involving evaluate): >

Re: Build failed in Jenkins: beam_SeedJob #209

Something has changed on the infrastructure side; looking... On Sun, Apr 16, 2017 at 11:02 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > -- > [...truncated 263.39

Re: JStorm runner

Also, JIRA component created [1], with Pei as component lead. Davor [1] https://issues.apache.org/jira/browse/BEAM/component/12332477/?selectedTab=com.atlassian.jira.jira-projects-plugin:component-summary-panel On Thu, Apr 6, 2017 at 7:55 PM, Kenneth Knowles wrote: >

Re: Apache Storm/JStorm Runner(s) for Apache Beam

This is a great discussion; thanks everyone. >From my perspective, the functionality to execute pipelines on both Storm and JStorm is very welcome and a big step forward for Beam. I'm not an expert on the Storm/JStorm differences, but one vs. two runners discussion sounds more like a packaging /

[ANNOUNCEMENT] New committers, March 2017 edition!

Please join me and the rest of Beam PMC in welcoming the following contributors as our newest committers. They have significantly contributed to the project in different ways, and we look forward to many more contributions in the future. * Chamikara Jayalath Chamikara has been contributing to

Re: Apache Beam (virtual) contributor meeting @ Tue Mar 7, 2017

2017 at 3:20 AM, Davor Bonaci <da...@apache.org> wrote: > > > Link: https://hangouts.google.com/hangouts/_/google.com/beam-dev-mtg > > > > I'll try to be available on Slack shortly before the meeting, just in > case > > someone has trouble connecting. > &g

Re: [VOTE] Release 0.6.0, release candidate #2

+1 (binding) Contingent on adding NOTICE and LICENSE files into "apache-beam-0.6.0-python.zip", just as they are present in the "apache-beam-0.6.0-source-release.zip". On Tue, Mar 14, 2017 at 10:02 AM, Aljoscha Krettek wrote: > +1 (binding) > > - verified release signature

Re: [PROPOSAL] Add 2.0.0 version in Jira

I added "First stable release" in JIRA as a version identifier a while back, to avoid any prejudice what that version might be called. I think it makes sense to resolve (newly fixed) issues against that version. Once we finalize the name of that release, we can easily rename it to either "1.0.0"

Re: Add GitHub topics to Beam repository

We certainly cannot do this ourselves, but it is within the realm of possibility that Apache Infra can assign tags to our GitHub repositories. Looking at the tags that already exist, perhaps we could go with: * apache-beam * big-data * data-processing * data-analysis * data-science *

Re: Report to the Board, March 2017 edition

The report is now submitted; thanks for the comments and improvements! On Tue, Mar 7, 2017 at 6:14 PM, Davor Bonaci <da...@apache.org> 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 We

Report to the Board, March 2017 edition

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, 3/8. This is the third is the series of three consecutive monthly reports required for new projects. If interested, please take a look at the draft [1], and comment

Re: found a typographical error in the Beam documentation.

apache_beam_doc_ko>. If you are > interested, it would be a great honor for me. > > Thanks for the quick answer :) > > > 켜짐 2017년 3월 7일 에서 오후 11:50:58, Davor Bonaci (da...@apache.org) 작성됨: > > Indeed -- there's a typo on that page. > > Would you be willing to subm

Re: found a typographical error in the Beam documentation.

Indeed -- there's a typo on that page. Would you be willing to submit a pull request to our website repository [1] correcting this? Thanks! Davor [1] https://github.com/apache/beam-site On Tue, Mar 7, 2017 at 12:28 AM, 성준영 wrote: > In Beam Documentation - Programming

Fwd: Google Summer of Code 2017 Mentor Registration

There was a previous discussion and planning around Beam's involvement with the Summer of Code 2017 -- here's more information on how to get started and formally register as a mentor. Davor -- Forwarded message -- From: Ulrich Stärk Date: Mon, Mar 6, 2017 at

  1   2   >