Thanks Kou for raising this. I am supportive of this change. I would say it might be interesting to have a policy on when and how new implementations are added to the main repository. We might want to have new language implementations start directly on a new repository or have them on apache/arrow-experiments [1] until they are mature enough to move to their own repository. This is inline with some previously attempted PRs to for example add support for the D programming language [2].
Regards, Raúl [1] https://github.com/apache/arrow-experiments/ [2] https://github.com/apache/arrow/issues/44515 El vie, 16 may 2025 a las 10:49, Sutou Kouhei (<k...@clear-code.com>) escribió: > 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, > -- > kou >
