I think another thing that got mentioned on the call that might be worth adding to the agenda for the next meeting was something Jorge said along the lines of:
"The original Rust Arrow implementation was modeled after the C++ implementation. As it matures, it seems like we are heading more towards the API style in the Rust standard library" This seems to be happening organically, but I wonder if it is a good thing to make explicit. Andrew On Wed, Jan 27, 2021 at 1:01 PM Benjamin Blodgett < benjaminblodg...@gmail.com> wrote: > Looks like I put this on my calendar wrong, but really glad this is > happening, will be there next call! > > We are doing a lot in rust and arrow this year and super excited you got > this started Andy! > > On Wed, Jan 27, 2021 at 9:58 AM Rémi Dettai <rdet...@gmail.com> wrote: > > > thanks Andy!! > > > > Le mer. 27 janv. 2021 à 18:41, Andy Grove <andygrov...@gmail.com> a > écrit > > : > > > > > Attendees > > > > > > - > > > > > > Mahmut Bulut > > > - > > > > > > Remi Dettai > > > - > > > > > > Andy Grove > > > - > > > > > > Fernando Herrera > > > - > > > > > > Jorn Horstmann > > > - > > > > > > Andrew Lamb > > > - > > > > > > Jorge Leitao > > > - > > > > > > Mike Seddon > > > > > > Topics Discussed > > > > > > - > > > > > > Release process > > > - > > > > > > There is an email thread "[Proposal] Modify release process to > vote > > > only on source release" that we should participate in > > > - > > > > > > Backwards Compatibility / API Guarantees > > > - > > > > > > We had a discussion about this but no decisions made. We will > > discuss > > > again next time. > > > - > > > > > > Serializing DataFusion query plans > > > - > > > > > > Other projects have needs around serializing query plans so that > > they > > > can be sent between networked processes. Ballista has an > > > implementation > > > already based on protobuf and we discussed the merits of donating > > > this to > > > Arrow. Another approach would be to use a Rust-native approach > > > such as the > > > serde or Cap'n Proto crate, which would have much lower > > > development effort > > > at the cost of only supporting Rust. > > > - > > > > > > PR approval process / policy > > > - > > > > > > We discussed some ideas around formalizing the process around PR > > > reviews, such as how many approvals needed (and by whom) and > > > this may vary > > > across crates. Discussed using github PR templates to suggest to > > > contributors who they should ping on PRs. Also discussed idea of > > > using > > > CODEOWNERS file. > > > - > > > > > > Blog Post for 3.0.0 Release > > > - > > > > > > There is a Google doc where we are drafting the blog post for > this > > > release: > > > > > > > > > https://docs.google.com/document/d/1HfdmVE9iQcYlWyfk68BN2PcIjAAhRFpuPLsZW6ffy3Y/edit?usp=sharing > > > > > >
