Hi, Good point! I agree with the concerns. But the concerns are still valid even if we keep swift/ in apache/arrow... Because the current implementation is difficult to use by users. (Users can't use Swift Package Manager to use the Swift implementation.)
Let's see what happens by repository split. Some active contributors may be appeared or the current lack of activity may be kept. Thanks, -- kou In <cah4123bguyktcnfj5mt3jww-mph-q-gzaorwmhj1-rjnbev...@mail.gmail.com> "Re: [DICSUSS] Split Swift to separated repository" on Mon, 19 May 2025 13:53:44 -0400, Matt Topol <zotthewiz...@gmail.com> wrote: > +1. I am supportive of this, though I still have concerns given the > current lack of representation, activity and support for the swift > impl. Just worried about it falling by the wayside. > > That aside, thanks for the work on this Kou! > > --Matt > > On Mon, May 19, 2025 at 1:47 PM Ruoxi Sun <zanmato1...@gmail.com> wrote: >> >> +1. Thank you kou for driving this! >> >> *Regards,* >> *Rossi SUN* >> >> >> On Mon, May 19, 2025 at 9:17 AM Antoine Pitrou <anto...@python.org> wrote: >> >> > >> > +1, I am supportive of this change as well. >> > >> > Regards >> > >> > Antoine. >> > >> > >> > Le 16/05/2025 à 10:48, Sutou Kouhei a écrit : >> > > Hi, >> > > >> > > This is a similar discussion to the "[DISCUSS] Split Go >> > > release process" thread[1], the "[DISCUSS] Split Java >> > > release process" thread[2], the "[DISCUSS] Split R release >> > > process" thread[3], the "[DISCUSS] Split C# release process" >> > > thread[4] and the "[DISCUSS] Split JS release process" >> > > thread[5]: >> > > >> > > [1] https://lists.apache.org/thread/fstyfvzczntt9mpnd4f0b39lzb8cxlyf >> > > [2] https://lists.apache.org/thread/b99wp2f3rjhy09sx7jqvrfqjkqn9lnyy >> > > [3] https://lists.apache.org/thread/6xl7zzf9y71dpjv5dvmn3fcm7rppggzx >> > > [4] https://lists.apache.org/thread/xbtq1ndjnljyo9jpm4ozblq9wx7hrc7y >> > > [5] https://lists.apache.org/thread/qpjt8ypmw1h8j1445kmn8s7wqml0cwoy >> > > >> > > But this discussion focuses on only repository split >> > > (splitting the swift/ directory in apache/arrow to >> > > apache/arrow-swift) because we haven't released our Swift >> > > packages yet. Our source archive includes the swift/ >> > > directory but it can't be used as a Swift package. Because a >> > > Swift package requires: >> > > >> > > * A Git repository >> > > * Must have "Package.swift" at the top-level of the Git >> > > repository >> > > >> > > See also the Swift Package Manager (SwiftPM) documentation: >> > > https://www.swift.org/documentation/package-manager/ >> > > >> > > >> > > We can add Package.swift to the top-level of apache/arrow >> > > but it may not be desired. We need to create a separated >> > > repository for Swift so that we release a Swift package. >> > > >> > > >> > > Concerns: >> > > * We haven't any PMC members nor committers who focus on >> > > Swift yet >> > > * I can keep helping the Swift implementation but more >> > > helps are better >> > > * ... >> > > >> > > >> > > What do you think about this? >> > > >> > > >> > > Thanks, >> > >> >
