domoritz edited a comment on issue #284: URL: https://github.com/apache/arrow-julia/issues/284#issuecomment-1042480283
Just adding two cents from the Arrow JS perspective. We are also a small developer group (3 contributors) working on Arrow in bursts and in no way full time. Overall, I'd say that being part of Apache adds some overhead but also gives us a lot more legitimacy and support. For example, there are awesome folks doing releases (including announcement blog posts), maintenance of the CI, and benchmarking. For a long time, I had no commit access to the main repo but sending pull requests worked fine. The other committers often didn't even merge the PRs but we had committers who don't work on JS jump in and merge approved PRs. Now I can also merge commits but for me it didn't make a huge difference in the day-to-day development. Maybe there is a way to fast-track where people who committed significantly to the Julia Arrow package get considered for a committer role right away without nomination. To reduce the overhead for releases, could the Julia release process be folded into the releases for https://github.com/apache/arrow? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: github-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
