[GitHub] [arrow-julia] quinnj commented on issue #342: Need to improve code review/release process and reduce developer productivity friction

[GitBox <gi...@apache.org>]

quinnj commented on issue #342:
URL: https://github.com/apache/arrow-julia/issues/342#issuecomment-1273401122

   > If the approval for pull request is meaningless for us, we can disable the "require 1 approval before merging a pull request" feature by removing https://github.com/apache/arrow-julia/blob/main/.asf.yaml#L41-L43 . It's just added because the original repository has the configuration.
   > 
   > >
   
   Yeah, it would probably be best to disable this for now. I think it's a nice feature on larger codebases, but for Arrow.jl, I think it's just too small at the moment.
   
   
   
   > Are you interested in joining Apache Arrow PMC? If you're an Apache Arrow PMC member, we'll get 2 `+1` (from you and me) soon. We just need one more `+1` for a new release. If one more Apache Arrow PMC members from Apache Arrow Julia community in the future, we'll get 3+ `+1` soon.
   
   Yes, this would also be helpful.
   
   > Could you provide a text to use the discussion for each person?
   
   @jrevels has been a solid contributor by reporting issues, making pull requests, and bringing up larger design discussion for the project as he works on the key data integration of arrow data at Beacon Biosignals.
   
   @omus is a solid contributor that helped a lot in the process of registering the ArrowTypes.jl subpackage and working out CI wrinkles so Arrow.jl and ArrowTypes.jl worked together nicely. He has also contributed to larger package design discussions in meaningful ways.
   
   @ericphanson has been super helpful reporting issues, making fixes, and helping triage issues as they come in to the repo. 
   
   @nickrobinson251 has started helping triage issues and has shown interest in working on finishing the C data interface for the Julia implementation. He is strong in design discussions and would help being able to provide fixes for issues as they come in.
   
   @bkamins is a strong contributor across the JuliaData ecosystem. He's a leading member of larger, coordinating projects that affect lots of packages and is the primary DataFrames.jl maintainer. It would be helpful to include him as a committer to help review inter-package PRs in the Arrow.jl repo (like for the recent efforts to coordinate Julia-side metadata for tables).
   
   @baumgold has made a number of large, meaningful pull requests to the project, in addition to helping triage issues and do code reviews on outstanding pull requests.


-- 
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-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org