[clangd-dev] [llvm-dev] Subprojects, GitHub, and the Monorepo

Duncan P. N. Exon Smith via clangd-dev clangd-dev at lists.llvm.org
Sat Oct 20 18:39:18 PDT 2018

> On Oct 20, 2018, at 18:12, Sam McCall via clangd-dev <clangd-dev at lists.llvm.org> wrote:
> On Sun, Oct 21, 2018 at 12:16 AM James Y Knight <jyknight at google.com <mailto:jyknight at google.com>> wrote:
> I think these issues you raise are all basically fixable, without fragmenting the community.
> # Bugtracker
> 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!)
> This is a necessary improvement, but not a sufficient one:
>  - our users still won't know how to use bugzilla
>  - bolted-on github account support is second-class (e.g. cc lists are still email addresses, @mentions don't work)
>  - bugzilla's UI is atrocious (hard to summarize; happy to go into this if there's real disagreement)
>  - it's not feasible to run an instance per subproject, so e.g. subprojects have no ability to define their own labels/keywords

> (Current LLVM developers *also* know the LLVM equivalents, but that's a small group).

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.

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.
- clang
- clangd
- (whatever else)
- llvm
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/clangd-dev/attachments/20181020/92157188/attachment.html>

More information about the clangd-dev mailing list