Some mentoring changes

Nemo PPMC, I'd like to step down from the role of a formal IPMC mentor to the project. There are several reasons for my decision: (i) lack of time, (ii) sufficient mentor coverage with four other mentors available, (iii) the project seems to have entered a steady state, reducing the need for

Re: Nemo podling report draft

Signed off. Comments: Lots of good work on community building and outreach -- kudos for that. Please keep up the good work, and results will follow. Obviously, in-project activity lower than before, but that is less important anyways. Graduation: one or two releases more, and evidence of

Re: Back from Berlin Beam Summit 2019

Would love to meet if you are in the area. Scheduling wise, I’ll be landing at SEA around 6 pm on the 15th, so 16th and onwards would be better. Evening on the 15th can work, but it is pushing it. Davor On Mon, Jul 1, 2019 at 8:40 AM 송원욱 wrote: > Hi! > > I got back from the Beam Summit Europe

Re: June 2019 podling report draft

Signed off. There were only two commits since the beginning of Q2, and none since 4/14. This is obviously worrisome from growth perspective, and I'd love to see the community discuss the state of the project. On Sun, Jun 2, 2019 at 1:14 AM Byung-Gon Chun wrote: > Hi all, > > I've added a

Re: March 2019 podling report

community? > It seems like it is a good starting point to present Nemo at developer > conferences such as ApacheCon and Beam Summit. > I'd love to hear your thoughts. > > Thanks. > -Gon > > > On Sun, Mar 3, 2019 at 8:22 AM Davor Bonaci wrote: > > > Signed off. >

Re: March 2019 podling report

Signed off. Overall impression: good progress; nothing to add. Focus on community building needed going forward. On Sat, Mar 2, 2019 at 2:23 AM Byung-Gon Chun wrote: > Hi all, > > I added a (draft) report to https://wiki.apache.org/incubator/March2019. > I am very happy with the progress. > >

Re: Nemo twitter account created!

> > Whenever it's ready, I'll post an update on twitter. What about Twitter account credentials, associated information to recover the password, security questions, etc.? It would be best to request a PPMC-private space from Infra in the Subversion repository (git doesn't have access control) to

Re: Release 0.1 (automatically in progress)

Congrats to everyone on the big milestone! Tip: I'd love to see some promotional activity around the release to grow the community. A blog post, social media, friendly endorsements from others, etc. would be great. (There are some limitations for incubating projects -- please don't issue formal

Re: [VOTE] Release Apache Nemo (Incubating) 0.1-rc2

I’d defer back to you; technically you can choose to either way. Think about this: Is it better for community growth to push the release out, or to delay a bit so that an experience on the Windows platform is improved? The answer probably depends on what portion of the community do you expect to

Re: [VOTE] Release Apache Nemo (Incubating) 0.1-rc2

+1 (binding), but please look into Markus' feedback. Non-blocking comments: - Please add instruction header to the KEYS file (see example in Beam) - Examples parent module should go too? Great work. On Thu, Dec 13, 2018 at 6:27 PM Markus Weimer wrote: > I tried to build on Ubuntu 18.04 to

Re: December 2018 podling report

Signed off. On Sun, Dec 2, 2018 at 10:18 PM Byung-Gon Chun wrote: > Hi all, > > I added a (draft) report to https://wiki.apache.org/incubator/December2018 > . > Again we have made awesome progress. :) > > If you have any suggestion to make changes, please let us know. > > Cheers, > Gon > > -- >

Re: [VOTE] Release Apache Nemo (Incubating) 0.1

+1 (binding) Great job! Things to improve, none of which I consider release-blocking: - Missing Apache header in a few files, mostly XML and like files. It would be great to make all that part of checkstyle. - Examples produce shaded artifact, which bundles parts of Beam, Spark. This bundling

Re: Sending a pull request to Apache Beam for the Nemo Runner?

I think the first decision you have to make is around the governance of the runner. It can live in the Beam project (and be governed by the Beam PMC), or in the Nemo project (and be governed by the Nemo PPMC). Both are viable paths, and different folks have chosen different paths. On the

Re: Release v0.1 Timeline

mailing list. > Let us all work productively, but without too much pressure :) > > Best, > Joo Yeon > > > > 2018년 8월 15일 (수) 오후 12:48, Davor Bonaci 님이 작성: > > > With my Beam lenses, there's no meaningful difference between 2.5.0 and > > 2.6.0 (relevant in this c

Re: Release v0.1 Timeline

With my Beam lenses, there's no meaningful difference between 2.5.0 and 2.6.0 (relevant in this context). Upgrade should be easy as well. Anything goes. A comment was made earlier that the first release will be finalized between 8/21 and 8/31. This would be *awesome*, but sounds like a bit

Re: May 2018 podling report

Signed off. On Sun, Apr 29, 2018 at 10:49 PM, Byung-Gon Chun wrote: > Thanks, JB! > > -Gon > > On Mon, Apr 30, 2018 at 2:28 PM, Jean-Baptiste Onofré > wrote: > > > Hi, > > > > It looks good to me, I just signed it off. > > > > Thanks ! > > > > Regards > >

Re: New Nemo blog posts!

Nice posts. FYI only, you may be interested in [1], which was published a few days earlier. Keep doing the good work! Davor [1] https://cloud.google.com/blog/big-data/2018/03/joining-a nd-shuffling-very-large-datasets-using-cloud-dataflow On Fri, Mar 23, 2018 at 12:04 AM, John Yang