Hi folks, It's great to see soooo much activity on Apache Polaris right now !
By experience, this high activity can introduce frustration in the community because contributors might be "lost" or have the feeling of missing important changes/proposals. I propose some good practices we could use to improve our collaboration and facilitate team work: 1. GH Issues & PRs should be descriptive and accurate, especially the description should describe a minimum the purpose and the labels should be meaningful (a bug is a breaking change, an improvement is a change on existing, etc). 2. We should avoid duplicating PRs (like creating a new PR and closing another one on the same topic), else we lose the history and comments. 3. All discussions in a PR should be resolved before merging, 4. I propose to wait 2 working days before merging PR to give a chance to contributors to take a look. 5. It's good to take the time for discussion in PR. If you think this discussion needs to move on the dev mailing list (to include the whole community) that's also fine. Regarding 3 and 4, I think I can update the .asf.yaml to enforce that. Thoughts ? Regards JB
