The Owners[1] tool in phabricator is a good way to take inventory of the code owned by each team or individual. I encourage everyone to create packages for the repos you care about (or even subdirectories within said repos, since packages can be scoped to sub-directory trees)

Packages are used for code auditing purposes (that is, post-commit review when a change bypasses pre-commit review) and also can be referenced in custom herald rules which notify you about specific changes.

[1] https://phabricator.wikimedia.org/owners/

On Wed, Jul 13, 2016 at 3:45 PM, Kevin Smith <ksmith@wikimedia.org> wrote:
Adam pointed out that Reading has something similar:
https://www.mediawiki.org/wiki/Reading/Component_responsibility

It includes service level agreements for code review, but even without that it seems like a nice inventory of components/projects that they consider to be within their scope.



Kevin Smith
Agile Coach, Wikimedia Foundation


On Wed, Jul 13, 2016 at 1:33 PM, Kevin Smith <ksmith@wikimedia.org> wrote:
Another team at the foundation has published a list of code repositories they manage and/or monitor, along with norms for reviewing code[1]. Should Discovery create something similar?

[1] https://www.mediawiki.org/wiki/Wikimedia_Language_engineering/Code_review_statement_of_intent

Kevin Smith
Agile Coach, Wikimedia Foundation



_______________________________________________
discovery mailing list
discovery@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/discovery