<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=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Oct 20, 2018, at 18:12, Sam McCall via clangd-dev <<a href="mailto:clangd-dev@lists.llvm.org" class="">clangd-dev@lists.llvm.org</a>> wrote:</div><div class=""><div dir="ltr" class=""><div class="gmail_quote"><div dir="ltr" class=""><br class=""></div><div dir="ltr" class="">On Sun, Oct 21, 2018 at 12:16 AM James Y Knight <<a href="mailto:jyknight@google.com" class="">jyknight@google.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class=""><div dir="ltr" class="">I think these issues you raise are all basically fixable, without fragmenting the community.<br class=""></div><div dir="ltr" class=""><div class=""><br class="m_-254088590852149228gmail-Apple-interchange-newline"></div><div class=""><div class=""># Bugtracker</div><div class=""><br class=""></div><div class="">Yes, everyone has a github account -- but I think everyone could also use bugzilla easily enough, if we add a "Login with github" button. I would like someone to volunteer to work on getting bugzilla patched with that functionality. (Someone, please volunteer!)</div></div></div></div></blockquote><div class="">This is a necessary improvement, but not a sufficient one:</div><div class=""> - our users still won't know how to use bugzilla</div><div class=""> - bolted-on github account support is second-class (e.g. cc lists are still email addresses, @mentions don't work)</div><div class=""> - bugzilla's UI is atrocious (hard to summarize; happy to go into this if there's real disagreement)</div><div class=""> - it's not feasible to run an instance per subproject, so e.g. subprojects have no ability to define their own labels/keywords</div></div></div></div></blockquote><br class=""></div><div>also:</div><div><div class=""><blockquote type="cite" class="">(Current LLVM developers *also* know the LLVM equivalents, but that's a small group).</blockquote></div><div class=""><br class=""></div></div><div>I don't think anyone likes or wants to use or administer Bugzilla. It's just what we have right now and we don't as a community have bandwidth to figure out what to do until we've made the repository move. When we have bandwidth, we should just fix this across the project. Probably after we move the repo; possibly with GitHub issues, but I think it should be the same across the project.</div><div><br class=""></div><div>I can see how having a completely separate bug tracker could help a little, but I'm skeptical there are major benefits over putting each tool that has a distinct userbase at the top-level.</div><div>- clang</div><div>- clangd</div><div>- (whatever else)</div><div>- llvm</div><div> </div></body></html>