Eric Christopher (@echristo) is listed as the code owner for Clang debug info. I asked him if he wanted to pass on the mantle to David Blaikie (@dblaikie), and David said he was willing to take that on. Other notable contributors to debug info are @pogo59 , @JDevlieghere , and @adrian.prantl .
Are folks in agreement that David is the right owner for debug info in clang? I have spoken to several community members, and people tell me that they really appreciate his helpful and thorough code review.
I’m 100% in support of @dblaikie becoming a code owner for debug info. But for clarity, does @echristo want to remain a code owner as well? Having multiple code owners is something we’re doing these days in Clang and there’s a lot of benefits to that model, so that might be a good option if David and Eric are comfortable with such an arrangement. (Not trying to pressure anyone, it’s also totally fine if we continue to have a solo owner here.)
I’m supportive of Dave becoming the new code owner. Unless there’s objection to having multiple code owners [1], I would like to nominate @adrian.prantl to complement to Dave on the Apple side of things (e.g. Objective-C, gmodules, etc). Adrian wrote most of that code anyway and like Dave has been an active reviewer.
[1] I personally really like this idea. I was inspired by @AaronBallman’s work in this space for clang and started working on a RFC to bring that model to LLDB (whose code owners are horribly outdated). I hope to publish that soon.
@rnk is there a reason this is only for Clang debug info, and not LLVM debug info also? Because of the way the project is split up, code ownership is maintained separately, but it makes more sense to have the owners be the same for both projects.
Unless there’s objection to having multiple code owners [1], I would like to nominate @adrian.prantl to complement to Dave on the Apple side of things (e.g. Objective-C, gmodules, etc). Adrian wrote most of that code anyway and like Dave has been an active reviewer.
I’m 100% in support of @dblaikie becoming a code owner for debug info. But for clarity, does @echristo want to remain a code owner as well? Having multiple code owners is something we’re doing these days in Clang and there’s a lot of benefits to that model, so that might be a good option if David and Eric are comfortable with such an arrangement. (Not trying to pressure anyone, it’s also totally fine if we continue to have a solo owner here.)
