<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">Alex Lorenz and Jan Korous are maintaining libclang (clang-c) from the Apple side these days; I suggest asking them for reviews.</div><div><br class=""><blockquote type="cite" class=""><div class="">On 2019 Dec 2, at 10:02, Arthur Peters via cfe-dev <<a href="mailto:cfe-dev@lists.llvm.org" class="">cfe-dev@lists.llvm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" class="">
<div text="#000000" bgcolor="#FFFFFF" class=""><p class="">One possibility would be to have me be an unofficial owner for a
while and have someone with commit access act as an intermediary
and sanity check until it's appropriate for me to be the official
owner. Regardless of how we slice this, there will be a need for a
few people who are willing to review my changes (I'm happy to
round-robin to spread the work) even though they are not
interested my pet module. Eventually small changes will not need
review, but larger changes still will, so the need for reviewers
will not totally go away.<br class="">
</p><p class="">-Arthur<br class="">
</p>
<div class="moz-cite-prefix">On 12/2/19 10:26 AM, David Blaikie
wrote:<br class="">
</div>
<blockquote type="cite" cite="mid:CAENS6EvJsTCz26eYaqu0Attssip_vr6rFNG60Hg_8YhK4Dp2Rw@mail.gmail.com" class="">
<meta http-equiv="content-type" content="text/html; charset=UTF-8" class="">
<div dir="ltr" class="">Richard Smith (as code owner of Clang) is probably
the decider here (cc'd) - and, yeah, it's a bit awkward having
an owner who hasn't previously had commit access etc - but that
seems to me to be the nature of finding owners for abandoned
components like this. So I'm leaning towards "yeah, this seems
reasonable" (but might require some of us folks who don't have
much involvement to at least review a few of your patches to
check we're generally on the same page with regards to design,
etc).</div>
<br class="">
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, Nov 26, 2019 at 3:47
PM Arthur Peters via cfe-dev <<a href="mailto:cfe-dev@lists.llvm.org" moz-do-not-send="true" class="">cfe-dev@lists.llvm.org</a>>
wrote:<br class="">
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" class=""><p class="">Hello all,</p><p class="">I have a couple of revisions to the clang-c API (the C
interface in libclang) and to the Python wrapper of it
(cindex). But I have not been able to find a maintainer
who could review these changes.</p><p class="">Are there current maintainers for these components?</p><p class="">If there is not, I may be willing to take on at least the
Python component given that I have found it very useful
and expect to continue using it. Would this be useful to
the community? (I don't yet have commit access or
anything, so I know it would be a process.)<br class="">
</p><p class="">-Arthur<br class="">
</p><p class="">PS: The existing revisions which need review are: <a href="https://reviews.llvm.org/D70358" target="_blank" moz-do-not-send="true" class="">D70358: Add
Cursor.get_reference_name_range to clang python binding</a>
<a href="https://reviews.llvm.org/D10833" target="_blank" moz-do-not-send="true" class="">https://reviews.llvm.org/D10833</a>
, and <a href="https://reviews.llvm.org/D10833" target="_blank" moz-do-not-send="true" class="">D10833: Retrieve
BinaryOperator::getOpcode and
BinaryOperator::getOpcodeStr via libclang and its python
interface</a> <a href="https://reviews.llvm.org/D70358" target="_blank" moz-do-not-send="true" class="">https://reviews.llvm.org/D70358</a>
(which I commandeered and updated). I also have several
other changes locally that I would like to push once I get
a hang for the process. The are all extensions and bug
fixes for clang-c and cindex.<br class="">
</p>
</div>
_______________________________________________<br class="">
cfe-dev mailing list<br class="">
<a href="mailto:cfe-dev@lists.llvm.org" target="_blank" moz-do-not-send="true" class="">cfe-dev@lists.llvm.org</a><br class="">
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" rel="noreferrer" target="_blank" moz-do-not-send="true" class="">https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a><br class="">
</blockquote>
</div>
</blockquote>
</div>
_______________________________________________<br class="">cfe-dev mailing list<br class=""><a href="mailto:cfe-dev@lists.llvm.org" class="">cfe-dev@lists.llvm.org</a><br class="">https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev<br class=""></div></blockquote></div><br class=""></body></html>