> INFRA tickets are required before migration. Perhaps this is different for existing repositories, but just a note that it may also be possible by editing .asf.yaml (e.g. [1])
[1] https://github.com/apache/arrow-nanoarrow/blob/81711045e8bb4ded1cb3b5a6fa354b35f18aa4e7/.asf.yaml#L24-L25 On Wed, May 29, 2024 at 10:39 PM Gang Wu <ust...@gmail.com> wrote: > > Just want to mention that these apache/parquet-* Github repositories > have not yet enabled issues and INFRA tickets are required before > migration. > > Best, > Gang > > On Thu, May 30, 2024 at 1:55 AM Micah Kornfield <emkornfi...@gmail.com> > wrote: > > > SGTM +1 > > > > On Wed, May 29, 2024 at 10:50 AM Rok Mihevc <rok.mih...@gmail.com> wrote: > > > > > On Wed, May 29, 2024 at 4:39 PM Fokko Driesprong <fo...@apache.org> > > wrote: > > > > > > > Hey Rok, > > > > > > > > Thanks for bringing this up. I'm also very much in favor of Github. > > Once > > > > we've migrated cpp, I think migrating the other repositories is a great > > > > idea. Let me know if I can help! > > > > > > > > > Perfect! A question I think we want to answer is where to move which > > > issues. My mapping by component would be: > > > > > > jira/parquet-avro --> github/parquet-java > > > jira/parquet-cascading --> github/parquet-java > > > jira/parquet-cli --> github/parquet-java > > > jira/parquet-cpp --> github/arrow > > > jira/parquet-format --> github//parquet-format > > > jira/parquet-hadoop --> github//parquet-java > > > jira/parquet-mr --> github/parquet-java > > > jira/parquet-pig --> github/parquet-java > > > jira/parquet-protobuf --> github/parquet-java > > > jira/parquet-site --> github/parquet-site > > > jira/parquet-testing --> github/parquet-testing > > > jira/parquet-thrift --> github/parquet-java > > > > > > Would this be ok for everyone? > > > > > > Rok > > > > >
