liurenjie1024 commented on issue #1797:
URL: https://github.com/apache/iceberg-rust/issues/1797#issuecomment-3468183790

   Thanks @alamb for raising this. As one of the authors and maintainers, it's 
very glad to see  so much interest in this project. I absolutely agree with you 
that we should reduce the need of forks and grow this community. This is  why 
we(me, @Xuanwo , @JanKaul ) started this project in apache repo rather than 
maintaining our own forks, we believe this will unit contributors around the 
world to bring iceberg to rust ecosystem.
   
   > To the existing maintainers:
   > 
   > 1. What would help you the most maintaining / moving this crate forward? 
How can we help?
   
   As a maintainer, I would say currently what we need at most is reviewers. 
You can see that there are a lot of pending prs waiting for review. Also, after 
doing a lot of reviews, I also have some suggestions for contributors:
   
   1. Split your prs into small ones. Smaller prs is typically easier to 
review, which means it would be easier to got merged. This helps us to move 
fast. As a guideline, prs should be less than 500 addtions(excluding 
Cargo.lock).
   2. Add description to your pr. This helps maintainers to understand your use 
case and motivation.
   3. For large features which can't fit into one pr, it's better to have a 
draft pr to do a prototype, and after the community reached consensus in the 
direction, we could split the larger one into smaller ones. Ideally, for 
complex features, we should have a design doc to describe the overall design, 
which helps reviewers to understand the pr.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to