Robert, the docs <https://help.github.com/articles/about-codeowners/> say: "The people you choose as code owners must have write permissions for the repository," but I want to ignore that for now and see what happens. :)
Also, I'm not sure how the auto-assignment works. Does it round-robin? Will it assign more than one reviewer? We'll see how it goes. Feel free to add components as you see fit. Most of what I've done is guesswork. On Tue, Jul 10, 2018 at 11:13 AM Ahmet Altay <al...@google.com> wrote: > +1 > > I added my name and a few others names that frequently do reviews in some > areas. > > On Tue, Jul 10, 2018 at 10:23 AM, Jean-Baptiste Onofré <j...@nanthrax.net> > wrote: > >> +1 >> >> I added my name on some components ;) >> >> Thanks ! >> Regards >> JB >> >> On 10/07/2018 02:06, Udi Meiri wrote: >> > Hi everyone, >> > >> > I'm proposing to add auto-reviewer-assignment using Github's CODEOWNERS >> > mechanism. >> > Initial version is here: _ >> https://github.com/apache/beam/pull/5909/files_ >> > >> > I need help from the community in determining owners for each component. >> > Feel free to directly edit the PR (if you have permission) or add a >> comment. >> > >> > >> > Background >> > The idea is to: >> > 1. Document good review candidates for each component. >> > 2. Help choose reviewers using the auto-assignment mechanism. The >> > suggestion is in no way binding. >> > >> > >> >> -- >> Jean-Baptiste Onofré >> jbono...@apache.org >> http://blog.nanthrax.net >> Talend - http://www.talend.com >> > >
smime.p7s
Description: S/MIME Cryptographic Signature
