Re: Greetings! (and regarding the invitation to Apache Nemo Slack)

Thanks! I've confirmed that it works well :) 2018. 2. 23. 오후 10:07에 "Joo Yeon Kim" 님이 작성: Hi all. I just setup a Slack workspace for Apache Nemo and sent out an invitation link to dev@. However, it seems like the invitation link only works for a single invite. (It will tell

Re: Hello, I'm Jae Hyeon Park, accepted to GSoC.

Oh, and I’ll also send you the appropriate invitations for our slack channel, etc. so that you can get familiar with the development tools! :) > On 24 Apr 2018, at 4:51 PM, 송원욱 <wsong0...@gmail.com> wrote: > > Welcome aboard JaeHyeon! > > I’m looking forward to mentor

Blog posted on our website!

Hi all! I'm writing to notify the community about the blog that just have been set up on our website! http://nemo.apache.org/blog/2018/03/20/nemo-blog-published/ Feel free to write about our project and you can post new articles on the website through the

Contributing Guideline and Code of Conduct

Hi again, I'm here to notify the community that a PR for including contribution guideline and code of conduct have been opened. https://github.com/apache/incubator-nemo/pull/10 As this establishes a policy for our project, it seems necessary to ask the community for advices and agreement.

CI for incubator-nemo

Now that we have our codebase migrated to apache, we should start setting up CI (probably Jenkins or Travis, or both) for our master branch. Can we set them up or should we open a ticket in INFRA? Moreover, to ensure the use of CI, we can set up a few things on GitHub. We can set our master

Re: New GitBox for website

:00 Byung-Gon Chun <bgc...@gmail.com>: > Hi Wonook, > > I just created https://gitbox.apache.org/repos/asf/incubator-nemo- > website.git > > Cheers, > Gon > > > On Sun, Mar 4, 2018 at 1:40 PM, 송원욱 <won...@apache.org> wrote: > > > Hi > > > &

Re: CI for incubator-nemo

/display/INFRA/Jenkins > > https://ci.apache.org/ > > > > Taegeon has experience on setting up CIs in Apache. > > > > It would be great to set up both Jenkins and Travis for fault tolerance. > :) > > > > Thanks. > > -Gon > > > > > >

Re: CI for incubator-nemo

this? Our repository already has .travis.yml file set up. Wonook 2018-03-04 21:46 GMT+09:00 Byung-Gon Chun <bgc...@gmail.com>: > Thanks! > > > > On Sun, Mar 4, 2018 at 9:43 PM, 송원욱 <won...@apache.org> wrote: > > > I've set up Jenkins CI. You can see them und

Re: New GitBox for website

ou take a look? > > Thanks. > -Gon > > On Sun, Mar 4, 2018 at 4:41 PM, 송원욱 <won...@apache.org> wrote: > > > Lovely! I just migrated our website code to the repository. You can > follow > > the status via > > https://issues.apache.org/jira/projects/INF

Re: Handling nemo-website PR

It’s been handled :) Thanks for the notification! Wonook > On 12 Nov 2018, at 11:17 AM, Jangho Seo wrote: > > Hi all. > > We have a pending PR [1] on github.com:apache/incubator-nemo-website > repository. > Wonook, can you handle this PR? > > [1]

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

Hi all, It's nice to hear that the first release is coming up pretty soon with the progress that we are making! With the first release and the current development for supporting stream processing, I think it's time for us to consider sending a request to the *Apache Beam* community to include the

Re: [GSoC Mentors] GSoC 2019 Org applications now open

Looking at the threads, it seems like we have a few ideas as below: supporting Apache Arrow Supporting a history server. Supporting more application DSLs Any other ideas would be welcome to be suggested on this thread. Wonook 2019년 1월 16일 (수) 오후 2:53, 송원욱 님이 작성: > It looks like GSoC 2

Re: Release 0.1 (automatically in progress)

I've got this handled  Wonook 2019년 1월 8일 (화) 오전 7:09, Byung-Gon Chun 님이 작성: > Thanks for the suggestion, Davor and Max! > > Posting a blog and creating a Twitter account all sound great. > Nemoers, any volunteers? > > Cheers, > Gon > > > On Tue, Jan 8, 2019 at 1:01 AM Maximilian Michels

Nemo twitter account created!

Hi, Now that we have our first release handled, in order to communicate with the users better, I've created a twitter account for announcing the events and blog posts related to Apache Nemo. I haven't posted much yet, but here is what I've posted so far: https://twitter.com/ApacheNemo. If there

Fwd: [GSoC Mentors] GSoC 2019 Org applications now open

It looks like GSoC 2019 is coming on the way. We’ve had a successful year last summer, with two GSoC students contributing to our project. If we are to receive students this year as well, I think it’s a good time to start brainstorming. How do you all think? > Begin forwarded message: > >

Re: Nemo twitter account created!

By the way, the release note for 0.1 is on the way. Whenever it's ready, I'll post an update on twitter.  Wonook 2019년 1월 16일 (수) 오후 2:56, 송원욱 님이 작성: > Hi, > > Now that we have our first release handled, in order to communicate with > the users better, I've created a twi

Re: Nemo twitter account created!

I'll ask the INFRA about the issue. Thanks for the suggestion! Wonook 2019년 1월 17일 (목) 오전 11:17, Davor Bonaci 님이 작성: > > > > Whenever it's ready, I'll post an update on twitter. > > > What about Twitter account credentials, associated information to recover > the password, security questions,

JIRA permissions?

Hi all, I've been experiencing this for quite a while now, but it doesn't look like I have the permissions to assign issues to users (even to myself), and to close or resolve issues. Would there be anyone who would have the access or who can grant the access to the committers for such JIRA

Re: JIRA permissions?

I've filed an issue: https://issues.apache.org/jira/browse/INFRA-17684 Wonook 2019년 1월 18일 (금) 오후 4:21, Byung-Gon Chun 님이 작성: > Yes. Please do so. > I don't have permissions, either. > > Thanks. > -Gon > > On Fri, Jan 18, 2019 at 4:17 PM 송원욱 wrote: > > > Hi all,

Re: JIRA permissions?

This issue is resolved. I've granted everyone with access to JIRA issues with appropriate rights. If I've missed someone out, please let me know on the thread. Thanks! Wonook 2019년 1월 18일 (금) 오후 4:30, 송원욱 님이 작성: > I've filed an issue: https://issues.apache.org/jira/browse/INFRA-17684 >

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

+1 Build success on JDK 1.8 and Mac OS 10.14.1 (Mojave). Wonook 2018년 12월 12일 (수) 오전 6:11, Byung-Gon Chun 님이 작성: > Mentors, could you take a look? > > Thanks! > -Gon > > > On Tue, Dec 11, 2018 at 5:58 PM Byung-Gon Chun wrote: > > > +1 (binding) > > > > I checked the signature and digests. > >

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

> On 11/15/18 7:29 PM, Byung-Gon Chun wrote: > > Sounds good! > > > > On Thu, Nov 15, 2018 at 6:09 PM Joo Yeon Kim wrote: > > > >> This sounds great to me :) +1 > >> > >> On Tue, Nov 13, 2018 at 1:13 PM 송원욱 wrote: > >> > >>>

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

+1 for source-only as well Wonook 2018년 12월 6일 (목) 오후 1:54, Jangho Seo 님이 작성: > +1 for releasing source-only. > > Best, > Jangho > > On 12/5/18 6:17 PM, Byung-Gon Chun wrote: > > +1 for releasing only source code > > > > On Wed, Dec 5, 2018 at 6:01 PM Taegeon Um wrote: > > > >> Thanks Joo

Re: Release Note 0.1

m-2.6.0.html > > I'd like to suggest to make the description of features be concise and add > JIRA issue numbers. > For credits, you can list up all the contributors alphabetically (by first > name). You don't need to describe who did what in details. > > Thanks. > -Gon > &

Re: Release Note 0.1

it's best > to call out individual contribution from SNU (in the blog post). > After all, we'd like to attract more developers from other institutions. > > -Gon > > > On Fri, Feb 1, 2019 at 2:55 PM 송원욱 wrote: > > > Since it’s an initial note, what I’ve had in my min

Release Note 0.1

Hi all, I've been working on a first draft of our 0.1 release note. I should have shared this earlier, but if anyone wants to take a look, please do so! It's our first release note, with a lot of work included, so I'm guessing that it would be quite lengthy with all the explanations. I was

Re: Nemo twitter account created!

The subversion repo has been set up for the PPMCs, but I'm afraid I don't have the permissions to make changes there. Would there be any volunteers that I could pass on the credentials, so that it can be shared among the PPMCs? Wonook 2019년 1월 18일 (금) 오후 3:59, 송원욱 님이 작성: > I'll ask the IN

Fwd: [ACTION REQ'D] Your session Running Apache Beam programs on Apache Nemo has been accepted!

Hi all, I'm happy to share that I have submitted a session about Apache Nemo for the Beam Summit occurring in Berlin in June, and has been accepted & confirmed. I'll be introducing Nemo, and explaining how it is used with Apache Beam programs (since it's Beam Summit), along with a short demo.

Back from Berlin Beam Summit 2019

Hi! I got back from the Beam Summit Europe 2019 that happened last week in Berlin, and I had lots of interesting conversations and feedbacks from the people that I've met there. I thought I would share some of them with the dev list. By the way you can check out the talk on youtube

Re: Release v0.2 Feature List

Thanks, Sanha for volunteering! I have a few PRs that are waiting to be reviewed, and I think it would be nice to handle them before the 0.2 release Below are the list of PRs waiting to be reviewed. I'll try to indicate reviewers for each of them, as otherwise I think that they probably will be

Re: Release v0.2 Feature List

>> Joo Yeon >> >> 2019년 9월 19일 (목) 오전 10:02, Byung-Gon Chun 님이 작성: >> >>> Wonook, any update? >>> Sanha, if things go well, we can start the process soon. >>> >>> Have you gotten any write up about release management from Joo Yeon?

Re: [VOTE] Release Apache Nemo (Incubating) 0.2 (rc3)

+1 for me  I’ve confirmed on my iMac Catalina with jdk 11. Thanks! > On 12 Feb 2020, at 1:09 AM, Sanha Lee wrote: > > There was a minor fix for packaging. > > Now the release hash is: > https://github.com/apache/incubator-nemo/commit/65332d47bca8f7f8d424d9c199bd0be43ba032da > > Thanks, >

Re: Download page issue

Hi, I'll fix the problem during today. Thanks! 2020년 3월 4일 (수) 오전 11:08, Byung-Gon Chun 님이 작성: > Nemoers, > > Justin pointed out that the Nemo download page has the following issue. > > Nemo (http://nemo.incubator.apache.org/pages/downloads/) > Links to signatures and hashes are missing > >

Re: Please welcome our new committer: Haeyoon Cho

Congrats Haeyoon! > On Feb 27, 2020, at 7:20 PM, Haeyoon Cho wrote: > > Hi, > > Thank you for the warm welcome. > I am so glad to be a part of the community! > > Looking forward to contribute to the project :) > > Best, > Haeyoon > > > 2020년 2월 27일 (목) 오후 6:02, Byung-Gon Chun 님이 작성: > >>

Re: [VOTE] Release Apache Nemo (Incubating) 0.2-rc5

+1 Thanks! Wonook 2020년 3월 2일 (월) 오후 12:42, Gyewon Lee 님이 작성: > +1 > > I checked RC5 on my Macbook Pro (Mac OS X 10.15.3) > > - 'mvn clean install' passes with Oracle JDK 1.8.0_221 > - sha512sum > > Best, > Gyewon > > 2020년 2월 29일 (토) 오후 10:53, Jangho Seo 님이 작성: > > > +1 > > > > I checked RC5

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

;>>>> (including 11). >>>>>>> >>>>>>> Markus, can you perhaps try again with the following commands >>> starting >>>>>>> from a clean slate? >>>>>>> These commands seem to work on my laptop with the late

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

succeed (`mvn -TC1 ...`). >>> Maybe there is a dependency not captured in the build files? Maven has >>> a tendency to satisfy these dependencies out of the local maven >>> repository. However, I have no prior version of Nemo on my machine... >>> >&

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

+1 `mvn clean install` ran successfully on Mac OS with Java 11 Thanks for the work Sanha! Wonook > On Feb 7, 2020, at 8:35 PM, Sanha Lee wrote: > > Hello Nemo PPMC. > > I packed our new release candidate which supports Java 11. > > Please refer to the information below to vote on this

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

It succeeds with Java 8 on my Mac as well, but fails with JDK 11. I’ll see what’s required to support JDK 11 and we could measure if it would be doable before the release. > On Jan 22, 2020, at 10:41 AM, Markus Weimer wrote: > > Hi, > > I have tried to compile Nemo, and hit an error: > >

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

EMO-437>. +1 in the meanwhile :) > On Jan 22, 2020, at 9:57 PM, 송원욱 wrote: > > It succeeds with Java 8 on my Mac as well, but fails with JDK 11. I’ll see > what’s required to support JDK 11 and we could measure if it would be doable > before the release. > >> On Jan

Re: [MENTORS] https://www.apache.org/dist/ has been deprecated

I found a couple of links using the deprecated address. I’ve fixed and pushed the changes, it should be fine now :) > On Mar 12, 2020, at 2:41 PM, Byung-Gon Chun wrote: > > Nemoers, > > Could you check the Nemo download page? > > Thanks! > -Gon > > > -- Forwarded message -

Re: GSoC 2020: We have Hwarim and Dongjoo for GSoC projects on Nemo

Welcome aboard Hwarim and Dongjoo! > On 7 May 2020, at 2:11 PM, Jeongyoon Eo wrote: > > To Nemo devs, > > I'm happy to inform you that we have two student participants accepted for > GSoC 2020. > Hwarim will work on dynamic task sizing with Wonook and Gyewon as mentors > and Dongjoo on

Moving to Java 11?

Hi Nemoers, As the release for 0.2 has been completed, I thought that it would be nice to move our project to use Java 11 from our future releases, as there are a number of new features in Java 11 that we could be using in our codebase: (blog post pointing out the new features

Re: Time for a new release?

Hi, I agree, since quite a lot of changes and improvements have been made since our last release. I think I could find the time to be the release manager for this release  Thanks > On 26 Oct 2020, at 3:28 PM, Byung-Gon Chun wrote: > > Hi Nemoers, > > We haven't created a release for a

Re: Nemo and the Apache Maturity Model

Hi, sorry for checking in late! As far as I could check for CO50, the criteria is clearly documented on the code of conduct, and the instructions are also given for how to contribute and commit to the project, on our GitHub.