Thanks for kicking off this process Yifan-- I'll add my name to some dependencies I'm familiar with.
Do you expect this to be a one-time process, or will we maintain the owners over time? If we will maintain this list, it would be easier to keep it up-to-date if it was closer to the code. i.e. perhaps each dependency registration in the Gradle BeamModulePlugin [1] should include a list of owners. [1] https://github.com/apache/beam/blob/master/buildSrc/src/main/groovy/org/apache/beam/gradle/BeamModulePlugin.groovy#L325 On Wed, Jun 27, 2018 at 8:52 AM Yifan Zou <[email protected]> wrote: > Hi all, > > We now have the automated detections for Beam dependency updates and > sending a weekly report to dev mailing list. In order to address the > updates in time, we want to find owners for all dependencies of Beam, and > finally, Jira bugs will be automatically created and assigned to the owners > if actions need to be taken. We also welcome non-owners to upgrade > dependency packages, but only owners will receive the Jira tickets. > > Please review the spreadsheet Beam SDK Dependency Ownership > <https://docs.google.com/spreadsheets/d/12NN3vPqFTBQtXBc0fg4sFIb9c_mgst0IDePB_0Ui8kE/edit?ts=5b32bec1#gid=0> > and > sign off if you are familiar with any Beam dependencies and willing to > take in charge of them. It is definitely fine that a single package have > multiple owners. The more owners we have, the more helps we will get to > keep Beam dependencies in a healthy state. > > Thank you :) > > Regards. > Yifan > > > https://docs.google.com/spreadsheets/d/12NN3vPqFTBQtXBc0fg4sFIb9c_mgst0IDePB_0Ui8kE/edit?ts=5b32bec1#gid=0 >
