For what it is worth, from my perspective the use of a separate repository for arrow-rs has been very beneficial for the Rust project -- it helps focus the conversations, tickets, and contributor PR experience.
That being said, it does require non trivial additional overhead, both 1. initially with setup and cross language integration test as mentioned elsewhere on this thread, though you could use what we did in arrow-rs as a model, 2. ongoing with a separate release process (e.g. voting threads, etc) So I am +1 on the idea as long as there is sufficient maintainer capacity to run the separate repo. Andrew On Wed, Oct 11, 2023 at 1:16 PM Alva Bandy <aba...@live.com> wrote: > Hi Kou, > > Totally makes sense. Great idea! > > Thank you, > Alva Bandy > > > On Oct 10, 2023, at 10:26 PM, Sutou Kouhei <k...@clear-code.com> wrote: > > > > Hi, > > > > I'm OK with this if we can keep following the Apache Way: > > > > * https://www.apache.org/theapacheway/ > > * https://theapacheway.com/ > > > > > > Can we discuss how to develop with separated arrow-swift > > repository after we re-read the above documentations? > > > > FYI: Here are discussions for arrow-rs and arrow-julia: > > > > * [DISCUSS] [Rust] Move Rust components to new repos and process > > https://lists.apache.org/thread/w3dr1vlt9115r3x9m7bprmo4zpnog483 > > * [DISCUSS][Julia] How to restart at apache/arrow-julia? > > https://lists.apache.org/thread/9hy387r8hvfrtnqdvgyszj3mf53mdr96 > > * Future of the Julia arrow implementation > > https://github.com/apache/arrow-julia/issues/284 > > > > > > Thanks, > > -- > > kou > > > > In > > < > mn2pr02mb5789a434a52b040c204d363eb2...@mn2pr02mb5789.namprd02.prod.outlook.com > > > > "[DISCUSS][Swift] repo for swift similar to arrow-rs" on Mon, 9 Oct > 2023 20:26:53 +0000, > > Alva Bandy <aba...@live.com> wrote: > > > >> Hi, > >> > >> I would like to request a repo for Arrow Swift (similar to arrow-rs). > Swift arrow is currently fully Swift and doesn't leverage the C++ > libraries. One of the goals of Arrow Swift was to provide a fully Swift > impl and splitting them now would help ensure that Swift Arrow stays on > this path. > >> > >> Also, the Swift Package Manager uses a git repo url to pull down a > package. This can lead to a large download since the entire arrow repo > will be pulled down just to include Arrow Swift. It would be great to make > this change before registering Swift Arrow with a Swift registry (such as > Swift Package Registry). > >> > >> Please let me know if this is possible and if so, what would be the > process going forward. > >> > >> Thank you, > >> Alva Bandy > >
