Hi Shannon, Thanks for considering a contribution to Beam Python SDK. With a direct contribution to Beam SDK, your change will reach larger audience of users, and you will not have to maintain a separate project and keep it up to date with new releases of Beam.
I encourage you to take a look at https://beam.apache.org/contribute/ for general advice on how to get started. To echo some points mentioned in the guide: - If your change is large or it is your first change, it is a good idea to discuss it on the dev@ mailing list - For large changes create a design doc (template, examples) and email it to the dev@ mailing list. Thanks, Valentyn On Wed, Jul 3, 2019 at 3:04 PM Shannon Duncan <[email protected]> wrote: > I have been writing a bunch of utilities for the python SDK such as joins, > selections, composite transforms, etc... > > I am working with my company to see if I can open source the utilities. > Would it be best to post them on a separate PyPi project, or to PR them > into the beam SDK? I assume if they let me open source it they will want > some attribution or something like that. > > Thanks, > Shannon >
