That sounds great Brian, thanks! On Tue, Dec 14, 2021 at 8:28 PM Brian Hulette <bhule...@google.com> wrote:
> Hi Matt, > > See https://beam.apache.org/contribute/become-a-committer/#process which > discusses the process for becoming a committer. Basically: make > contributions to Beam (including code contributions, contributing to > mailing list discussions, etc...). The PMC will take note of these > contributions and eventually invite you to become a committer. I'm not a > PMC member, but I'd imagine your willingness to maintain the Neo4j IO in > the future is certainly a positive signal for such a consideration! > > Note that we do take code reviews from non-committers into account (e.g. a > committer is free to self-merge their contribution if it has a review from > a non-committer). So my suggestion for Neo4jIO maintenance would be for you > to take a first pass on any relevant code reviews, and/or triage bug > reports and feature requests. When you do need a committer to merge a PR > you've reviewed feel free to ping myself or another committer. It will > likely go fast since you've already taken a look. > > Brian > > On Tue, Dec 14, 2021 at 11:09 AM Matt Casters <matt.cast...@neo4j.com> > wrote: > >> Hi Beams! >> >> In the light of the ongoing work with the Neo4jIO connector (see pr 15916 >> [1]) I think it's a good idea to become a committer to Apache Beam. In this >> case I guess it means that I'd like to commit to following up the new >> connector with future bug reports and feature requests. >> Is there any specific procedure I should follow? >> >> Thanks in advance! >> >> Kind regards, >> >> Matt >> >> [1] https://github.com/apache/beam/pull/15916 >> -- >> Neo4j Chief Solutions Architect >> *✉ *matt.cast...@neo4j.com / mcast...@apache.org >> >> >> >> >> -- Neo4j Chief Solutions Architect *✉ *matt.cast...@neo4j.com
