> The lines are admittedly fuzzy, but I'd say Cap'n Proto still mostly belongs to me, not Cloudflare. I meant it more in terms of resources: you seem to be say

> The lines are admittedly fuzzy, but I'd say Cap'n Proto still mostly belongs to me, not Cloudflare. I meant it more in terms of resources: you seem to be saying that you maintain Cap'n Proto as part of your job at Cloudflare. You mention PRs that you have failed to review, I guess Cloudflare did not need them. And as you said, if Cloudflare had needed them, you would probably have been faster doing it yourself. Which also means that opening those PRs was a loss of time for everybody from the beginning on. At least that is more and more how I see open source: - I have to "blindly trust" some projects (e.g. a standard lib, TCP, protobuf) because I couldn't maintain them myself. I try to minimize that and chose those carefully. - I accept to depend on projects that I could easily fork or replace. I can contribute to those, and if the maintainers ignore me I just fork away. - If it's small enough, I'll rewrite it myself (using the open source code for inspiration). Conversely, I behave more and more like this as a maintainer: - I don't hesitate to tell people that I won't take time to review non-trivial PRs - I encourage people to fork if they want something I cannot give them - If people cannot fork and need something I cannot give them, then they are screwed. That's sad, but that's life. I can't burn myself out for them. I use to say "PRs are welcome!" when people asked for new features. I stopped doing that unless I am really sure I will actually review them.