Thank you xudong, that is a great perspective. A little more backstory is that I am acutely aware of the backup of PRs in need of review in DataFusion, and less so in Arrow. As the contributions grow, we also need to grow our capacity to review them.
We are working in various ways to grow our review capacity and number of committers, but anyone can (and should) feel free to help review. Not only will it help the existing maintainers and other community members, it perhaps will ensure you don't feel blocked waiting on review Thanks again, Andrew On Thu, Mar 3, 2022 at 10:37 PM Wang Xudong <wxd963996...@gmail.com> wrote: > Couldn't agree more with alamb's proposal! > > I started participating in the arrow rust community last year, and at > first, I just contributed code. Later, in order to have a deeper > understanding of the whole codebase and to help new people in the > community, I started to participate in code reviews, sorting out issues. In > this process, not only did I have a deeper understanding of the codebase > but I was able to follow the development of the whole community and not to > get off track. I also learned a lot of new knowledge during the code review > process, which has helped me grow a lot! I'm also proud of helping new > people in the community! > > --- > xudong > > Andrew Lamb <al...@influxdata.com> 于2022年3月4日周五 04:28写道： > > > Hi, > > > > I would like to remind everyone in the Rust community that we not only > > welcome, but encourage community members to help review each other's PRs > in > > addition to contributing code. It is a great way to help the community, > get > > more familiar with Rust, and the Arrow, Parquet, DataFusion and Ballista > > codebases! Of course, it also would help reduce the burden on maintainers > > :) > > > > I also added some notes in the readme files of the arrow-rs [1] and > > datafusion [2] repos to encourage this as well. > > > > [1] https://github.com/apache/arrow-rs/pull/1396 > > [2] https://github.com/apache/arrow-datafusion/pull/1917 > > >
