I think it is a great idea -- github has served arrow (and datafusion) very well in my opinion.
Specifically, having to sign up for a JIRA account (which can not be created self-service) adds a small, but real barrier to engagement and contribution. Removing the barrier I think encourages more contributions, especially casual contributions Andrew On Tue, May 28, 2024 at 7:40 PM Rok Mihevc <rok.mih...@gmail.com> wrote: > Hi all, > > I'd like to re-raise the idea of migrating parquet-cpp issues from > Parquet's Jira to Arrow's GitHub issue tracker. Arrow migrated in January > 2023 [1]. The migration was relatively smooth and the experience since > seems to be positive. > > The reasons we would want to migrate parque-cpp issues are: > - Issues of parquet-cpp are effectively already tracked on Github [2] (220 > open, last 20h ago), while Jira [3] is less active (55 open). > - Arrow's release process could be simplified if Jira was not in the > release workflow [4], reducing workload of release manager > > A reason against this would be that split issue tracking of parquet-java > and parquet-cpp doesn't help with feature parity of implementations. > > Migration was already discussed to some degree in the "[C++] Parquet and > Arrow overlap" thread [5], but no clear consensus or vote was reached. If > we can reach an agreement I would proceed and migrate parquet-cpp issues in > one of the coming weekends. > > Additionally, we could migrate other parquet issues with relatively little > additional effort and I'd be willing to do it if there is interest from > the community. > > Rok > > [1] https://github.com/apache/arrow/issues/14546 > [2] > > https://github.com/apache/arrow/issues?q=is%3Aissue+label%3A%22Component%3A+Parquet%22+ > [3] > > https://issues.apache.org/jira/browse/PARQUET-2200?jql=project%20%3D%20PARQUET%20AND%20status%20%3D%20Open%20AND%20component%20%3D%20parquet-cpp%20ORDER%20BY%20created%20DESC%2C%20due%20DESC > [4] > > https://arrow.apache.org/docs/developers/release.html#create-or-update-the-corresponding-maintenance-branch > [5] https://lists.apache.org/thread/jf9wos3t6xxk6xdyx2dof1jlkbpkr56p >
