search

laysakura / beam

Apache Beam is a unified programming model for Batch and Streaming data processing.
https://beam.apache.org/
Apache License 2.0
5 stars 7 forks source link

How to contribute #1

Closed dahlbaek closed 1 year ago

dahlbaek commented 1 year ago

Coming from https://github.com/apache/beam/issues/21089#issuecomment-1499443923, I noticed that you (@laysakura) welcome contributions! I'm interested in contributing, but wondering how you would prefer to handle contributions.

Do you already have plans regarding the direction/priorities, or should I just go hunting for todos in the code that seem like something I could work on? Would you like an issue created first, or rather not be bothered until (I think) I have something ready for review?

laysakura commented 1 year ago

Hi @dahlbaek ! I'm pretty happy to receive your help.

I created some issues to resolve soon. If you are interested in some of them, please assign them to yourself.

Also, as you already noticed, there are many TODO comments in the rust codebase. I prefer to have issues first and then to create pull request but I don't mind so much if you start from creating a pull request.

dahlbaek commented 1 year ago

Sounds good! I had a brief look at #3, but I don't think I have permission to assign issues 🤔

laysakura commented 1 year ago

I have permission to assign issues 🤔

Oh, sorry. I'll check the permission settings.

laysakura commented 1 year ago

@dahlbaek I sent an invitation to make you as a collaborator of this repository.

laysakura commented 1 year ago

@dahlbaek Thank you so much for the #7 .

Would you be interested in working on any of the existing issues? I am planning to start working on #4 or #6 from Monday (JST). If you have a preference or interest in either of them, please let me know, and I will assign it to you.

dahlbaek commented 1 year ago

Thank you for the opportunity to collaborate!

I would be very interested in #4. However, I should say that I mostly have time available during the weekends, so depending on how much work is needed it might take me some time to prepare a PR. Let me know if you want to move quick on this, in which case it might not be a good idea to assign it to me...

laysakura commented 1 year ago

I think you're the best person to tackle #4 from #7 and https://github.com/laysakura/beam/issues/4#issuecomment-1501012735.

I'm planning to give a presentation about the Beam Rust SDK at Beam Summit 2023, which is happening on June 13th. Of course, I'll make sure to acknowledge your contributions during the presentation! It would be awesome if we could get #4 done by April.

Here's what I'm thinking:

What do you think of this plan?

dahlbaek commented 1 year ago

Sounds great!

brucearctor commented 1 year ago

See you in NY - @laysakura !

laysakura commented 1 year ago

I'm waiting for @sjvanrossum to create issues related to:

I'll also create an issue or a design doc related to:

laysakura commented 1 year ago

@dahlbaek Thank you for your consistent contributions! Would you be interested in continuing with the following task?

https://github.com/laysakura/beam/pull/14#issuecomment-1518941241

My opinion is that we should first aim for putting something together that can run in a distributed manner.

dahlbaek commented 1 year ago

Definitely! I'll have to look around a bit to figure out exactly what's missing and where to start 🤔 feel free to make suggestions if you already have a good feel for it!

laysakura commented 1 year ago

@dahlbaek In my opinion, Rust-specific components are located in two main areas:

  1. API in SDK

  2. Language-specific SDK harness

Although I started with and am continuing to work on 1. (for example, #9), I believe that 2. is more important in determining the types and traits required for distributed runtimes a distributed manner.

Therefore, my suggestion is as follows:

This may be a long journey, but we are happy to help you along the way!

Kelvinyu1117 commented 1 year ago

Hi all, I'm also coming from the same issue on apache/beam and I'm interested in contributing to this project. Which issue is good for me to kickstart?

laysakura commented 1 year ago

@Kelvinyu1117 I appreciate your participance! How about:

laysakura commented 1 year ago

We have created communication channels (Discord and design docs). See the README.

We are waiting for your contribution!

brucearctor commented 1 year ago

Great, @laysakura ! Thanks for keeping this moving, and see you at next beam summit [will make a point to connect in person that time :-) ]

laysakura commented 1 year ago

@brucearctor It definitely was a great memory in my life! I appreciate all the help from community members, including you.

For those who have interests in my talk, I'll quickly share my slides. (I guess the recording will be available about a month later).