apache
Tracking issues for improving review process
This issue is used to track how we improve review process to make it not the bottleneck anymore.
Ideas
Adapt review style
From @Xuanwo
Many people mentioned that review is the current bottleneck. That’s also my personal feeling. Some suggested we should engage more people to join reviews and encourage contributors to split PRs into smaller chunks to make them easier to review. Those suggestions are absolutely true and valid.
But I also feel we can adapt our review style somehow. Instead of requiring contributors to address all issues, we can encourage them to create follow-ups (note: these don’t need to be finished by the same person). Some of these follow-ups make great first issues that can help more people join the community.
@Xuanwo Thanks for opening this issue! We’re interested in contributing, but we’re not yet sure which areas on the Rust side are most in need. Could you suggest a high-level direction or point us to a few prioritized or newcomer-friendly issues (e.g., help wanted, good first issue)?
@Xuanwo Thanks for opening this issue! We’re interested in contributing, but we’re not yet sure which areas on the Rust side are most in need. Could you suggest a high-level direction or point us to a few prioritized or newcomer-friendly issues (e.g.,
help wanted,good first issue)?
Thank you for mentioning this. There are many issues that would be good for new contributors, but we haven’t labeled them yet. I’ll go through the issues and add some labels.
Another issue I found is our unit CI is too slow. It takes about an hour, which doesn’t make sense for us. Can we split it up or rethink the test architecture?
Do you have suggestions on this? cc @liurenjie1024, @sdd and @kevinjqliu
@Xuanwo Thanks for opening this issue! We’re interested in contributing, but we’re not yet sure which areas on the Rust side are most in need. Could you suggest a high-level direction or point us to a few prioritized or newcomer-friendly issues (e.g.,
help wanted,good first issue)?Thank you for mentioning this. There are many issues that would be good for new contributors, but we haven’t labeled them yet. I’ll go through the issues and add some labels.
@Xuanwo Very looking forward for this, i'd gladly try something low impact to start out. Regarding the CI we could try adding rust-cache to check job, it saved me a bit of time in one of my projects and shouldn't take long to implement.
