First-time contributor: how to get started with delta-rs? #3463
-
Hello, I'm really interested in contributing to delta-rs, but this would be my very first time contributing to an open source project. I’ve been learning Rust for about a year and a half and would consider myself still early in the journey. I’m really motivated to get involved and contribute, ideally starting with small tasks so I can gradually understand the structure and internals of the project. I noticed there aren’t any good first issue tags available at the moment. Would it be a good idea to start by picking up some of the // TODO: comments in the codebase and try to implement them? Or would you recommend another approach for someone completely new to open source? Thanks a lot in advance for your help and guidance! |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
Hey @pauldouane, First, awesome you want to get involved! I personally find a great place to start is to add more tests or examples :). These can usually get merged quite quickly and give you a good idea of some APIs. Looking at TODO statements if also a way to go, but these may often require some context. If you find one you like where you might need some I'd suggest opening an issue, where I'd be happy to help sketch an approach. Should you encounter hurdles in the dev setup o.a. it might also be an option to improve dev ergonomics via docs or improved scripts. Good callout though the the Good first Issues, I'll see that I find some time to tag or add a few. |
Beta Was this translation helpful? Give feedback.
-
Also, joining the slack channel (link in Readme) is a good way to interact with the contributors. |
Beta Was this translation helpful? Give feedback.
Hey @pauldouane,
First, awesome you want to get involved!
I personally find a great place to start is to add more tests or examples :). These can usually get merged quite quickly and give you a good idea of some APIs.
Looking at TODO statements if also a way to go, but these may often require some context. If you find one you like where you might need some I'd suggest opening an issue, where I'd be happy to help sketch an approach.
Should you encounter hurdles in the dev setup o.a. it might also be an option to improve dev ergonomics via docs or improved scripts.
Good callout though the the Good first Issues, I'll see that I find some time to tag or add a few.