Hi Dongjoon, I think the voting content is pretty clear. We are voting for the following actions: 1. Create an apache/orc-rust GitHub repository which is governed by Apache ORC PMC. 2. Open a PR against apache/orc-rust to move all the files from datafusion-contrib/orc-rust.
I mentioned that the created repo is governed by Apache ORC PMC, meaning that the ORC PMC could determine whether to fix all issues on README, release cadence, CI and so on before or after merging. It is obvious that these issues cannot be fixed now without actually opening the PR. I initialized the previous discussion thread to give a chance for the ORC community to take a look at the datafusion-contrib/orc-rust codebase to provide the context. As the discussion received promising feedbacks, this vote is mainly for giving a green light to proceed. The authors of the rust implementation have done a good job on their side and now are waiting for us to proceed. For those specific questions mentioned above, I think the original authors might have better answers than me so I will let them chime in. But overall I don't think those are required for this vote. We anyway need a final vote on accepting the donation after everything looks good. Best, Gang On Thu, Oct 31, 2024 at 11:05 PM Dongjoon Hyun <dongjoon.h...@gmail.com> wrote: > To Gang and all. > > I'd like to give +1 in the context of the proposed title, "Create > apache/orc-rust repository". > > However, I feel we need to clarify that the following is incorrect and not > a scope of this vote > because the migration PR will be reviewed and revised in the Apache ORC way > anyway. > > > Specifically, the datafusion-contrib/orc-rust repository will be moved to > > apache/orc-rust and governed by Apache ORC PMC. > > Although I understand you want to provide more transparent migration > technically, > they (BEFORE and AFTER) could be differently technically. For example, > > - We are not going to change README? > - What about the version number? > - Do we need to continue the version number with 0.5.1? or a new scheme? > - What about the CIs on a new repository? > - All github action plugins are verified by the ASF infra team? > - What about the release process and distribution channel change? (Crate + > ASF Download) > > For me, the above sentence (`Specifically, ... moved to ... ORC PMC`) is an > overclaim > (and just an aspiration) which we didn't agree with anything yet. > > So, as a member of Apache ORC PMC, I'm -1 for the specific promise of the > vote content. > > Best Regards, > Dongjoon. >
