2 ms·
I'm not saying that the ownership should be strict, you should feel free to submit PRs to my repo, and I to yours. I just don't want there to be a no-man's-lan
by __MatrixMan__ 2y ago
I'm not saying that the ownership should be strict, you should feel free to submit PRs to my repo, and I to yours.
I just don't want there to be a no-man's-land. And if there must be an every-mans-land, let it be explicitly so, not some pile of stuff that didn't fit anywhere else.
- jatins 2y ago> you should feel free to submit PRs to my repo, and I to yours Haven't seen it happen in practice. For some reason a separate repo induces more of "not my backyard" feeling that a separate folder
- __MatrixMan__ 2y agoReally? GitHub is packed with commits authored by people besides the maintainers. Have your really not noticed? Or do you just stop looking for a CONTRIBUTING.md when you're at work?
- The_Colonel 2y agoThat's good, but that still produces friction AND reduces the sense of the ownership of the owning team. > I just don't want there to be a no-man's-land. A different model I've seen is that the ownership of the whole system is shared across the trusted senior members (every team has one, but you need to get an approval from an external one). One thing this avoids is the bottleneck on specific teams (only team X can approve the PR, but they're now super busy with their own features).
- __MatrixMan__ 2y agoThats what we're trying to do. I'm not one of those people, but golly they seem overworked.