5 ms·
It's an interesting social problem in how you manage those project / library / repository boundaries. On the flipside, though, it's been well documented that am
by WorldMaker 8y ago
It's an interesting social problem in how you manage those project / library / repository boundaries. On the flipside, though, it's been well documented that among many of the major monorepos those boundaries still exist, they just become far more opaque because no one has to track them. You find the weird gatekeepers in the dark that spring out only when you get late in your code review process because you touched "their" file and they got an automated notice from a hidden rules engine in your CI process you didn't even realize existed.
In the polyrepo case those boundaries have to be made explicit (otherwise no one gets anything done) and those owners should be easily visible. You may not like the friction they sometimes bring to the table, but at least it won't be a surprise.
- rgoulter 8y agohttp://wiki.c2.com/?ConwaysLaw http://wiki.c2.com/?ConwaysLaw "Conway's Law" is something like "organisation of code will match the organisation of people". It's a neat description. I think it's more common to merge or split modules and classes than repositories. I wonder if there'd be less tension if repos and teams were 1:1 though.
- freedomben 8y ago> I wonder if there'd be less tension if repos and teams were 1:1 though Anecdotally, yes I think it helps a lot. I was once part of an organization for which each "team" having a repo is the only thing that prevented violence :-)
- matwood 8y agoI've also seen arbitrary separations of repos because 2 people didn't get along and couldn't work together.
- Mxtetris 8y agoCan a monorepo support module- or subdirectory-level ownership controls? Or do teams using a monorepo just do without them? Partially answering my own question: SVN, recommended in a prior comment [0], supports path-based authorization [1]. But what about teams using another version control system? [0] https://news.ycombinator.com/item?id=18810313 https://news.ycombinator.com/item?id=18810313 [1] http://svnbook.red-bean.com/en/1.5/svn-book.html#svn.serverconfig.pathbasedauthz http://svnbook.red-bean.com/en/1.5/svn-book.html#svn.serverc...
- monksy 8y agoSVN allows for you to create mutliple repos within a repo. (That's probably why the path based auth works). Git has the idea of sub-modules, but they're really just filters. (They're in the same repo). So ultimately, you don't have that kind of control.
- icebraining 8y agoGit submodules are not in the same repo, they are a link from one repo to another, and you need to push to both if you make a change to the submodule. Maybe you're thinking of subtrees? I've never used those.
- maktouch 8y agoWith Phabricator, yes, you can setup herald rules that stops a merge from happening if a file has changed in a specific subdir. We use service owners, so when a change spans multiple services, they are all added automatically as blocking reviewers.
- xyzzyz 8y agoPiper, Google’s implementation of monorepo, has that, and it is very important and widely used.
- gusmd 8y agoIf I remember correctly, Gitlab has introduced some sort of ownership control where you can say who owns what directories for things like approving merge requests that affect those directories.
- pulisse 8y agoGithub has this feature[1], which we use extensively in our monorepo. [1] https://help.github.com/articles/about-codeowners/ https://help.github.com/articles/about-codeowners/
- dsumenkovic 8y agoHey, did you mean of assigning approvers based on code owners [1]? You can find more info about Code Owners and syntax at the documentation [2]. [1] https://gitlab.com/gitlab-org/gitlab-ee/issues/1012 https://gitlab.com/gitlab-org/gitlab-ee/issues/1012 [2] https://docs.gitlab.com/ee/user/project/code_owners.html https://docs.gitlab.com/ee/user/project/code_owners.html