At a prior employer, we managed our default reviewers via YAML files in each directory of the repository. I am looking to do something similar at my current company and I'm not sure where to start.
Below is my recollection of the steps: There was an initial round of requesting that people register ownership of/interest in the various files in the repo via a web tool; as I recall, a user would log in and they were initially presented with a page that showed all of the files and directories at the root of the repo. To the right of each of these they could select yes/no for each(or something like that, memory a bit hazy). They could click on a directory name, whereupon they would be presented with a list of files/directories where they could take the same actions. Eventually(with some prodding) all of the files had been claimed. The collected data was processed down into YAML files, something like .reviewers.yaml, one per directory. Some were empty, but were intended as placeholders in case they were needed. The data was somehow parsed and entered into the "Default Reviewers" in ReviewBoard. For ongoing maintenance of the information, developers were expected to update the YAML files. For example, if I added a new file, I was expected to add an entry to the YAML indicating I should be a reviewer. There was some cron or other backend process that would periodically scan the YAML files and update Default Reviewers in RB. Does this ring a bell with anyone? Can anyone offer pointers to some pieces that I can leverage to implement a similar solution? -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups "reviewboard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
