Thank you for the replies. There are further discussions on private@orc mailing list among the members of Apache ORC PMC about the following part.
> No, Transfer [orc-rust](https://github.com/datafusion-contrib/orc-rust) > from [datafusion-contrib](https://github.com/datafusion-contrib) to > [apache](https://github.com/apache) directly, > under the governance of the Apache ORC PMC. Apache ORC PMC members (and ASF members) can join the pre-discussion for the next steps there. Thanks, Dongjoon. On Thu, Oct 31, 2024 at 8:42 PM Xuanwo <xua...@apache.org> wrote: > Hi, Dongjoon > > Thank you very much for your support. Here is our donation plan; please > take a look. > > ## Summary > > Transfer [orc-rust](https://github.com/datafusion-contrib/orc-rust) from > [datafusion-contrib](https://github.com/datafusion-contrib) to [apache]( > https://github.com/apache) directly, under the governance of the Apache > ORC PMC. > > ## Contributor > > All active contributors have agreed to continue contributing to this > project. We are all willing to collaborate on this project under the > governance of the Apache ORC PMC. > > ## License > > - All active contributors have signed the ICLA and CCLA. > - All submitted code is licensed under Apache 2.0. > - All dependencies are compatible with Apache 2.0 and permitted by the ASF. > > We can double-check this part while we are building our first ASF release. > > ## CI > > orc-rust plans to use GitHub Actions as its CI system. Once accepted by > the ORC PMC, all actions not approved by the ASF will be unable to run. We > can address them afterward. > > ## Discussion > > orc-rust plans to use `dev@orc.apache.org` as its main channel. > > ## Release > > orc-rust plans to continue using the current version number. We will make > it very clear that old releases are not approved by the ORC PMC and are > informal ASF releases. > > Once accepted by the ORC PMC, we will alter our release process to meet > the requirements. We will offer ASF release downloads and also have a ` > crates.io` release for user convenience. The crate `orc-rust` will be > transferred to the ORC PMC for control. > > ## Non-blockers > > All code/document changes are not blockers for now. We believe they can be > addressed after being accepted by the ORC PMC. > > Please let me know if any points are still missing. > > On Thu, Oct 31, 2024, at 23:03, Dongjoon Hyun 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. > > -- > Xuanwo > > https://xuanwo.io/
