[llvm-dev] [cfe-dev] RFC: Switching from Bugzilla to Github Issues

Jacob Lifshay via llvm-dev llvm-dev at lists.llvm.org
Mon Feb 3 09:11:08 PST 2020


On Mon, Feb 3, 2020, 09:00 Michael Kruse <cfe-dev at meinersbur.de> wrote:

> Am Do., 30. Jan. 2020 um 13:29 Uhr schrieb Jacob Lifshay via cfe-dev
> <cfe-dev at lists.llvm.org>:
> >
> > On Thu, Jan 30, 2020, 10:22 Tom Stellard via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
> >>
> >> Hi,
> >>
> >> I want to restart this discussion.  There seemed to be support for this,
> >> but we got held up trying to decide on the appropriate set of tags to
> >> use to classify issues.
> >>
> >> I propose that we move forward with this proposal and disable creation
> of
> >> new bugs in bugzilla on Feb 11, and require all new bugs be filed via
> GitHub
> >> issues from that date forward.
> >>
> >> I think that for choosing the tags to use, we should just take requests
> >> from the community over the next week and add whatever is asked for.
> The main
> >> purpose of adding tags is so we can setup cc lists for bugs, so I think
> this
> >> is a good way to ensure that we have tags people care about.  We can
> always
> >> add more tags later if necessary.
> >>
> >> What does everyone think about this?
> >
> >
> > Before disabling Bugzilla, I think there should be a way for those who
> don't have/want github accounts to create/comment-on bug reports (maybe a
> mailing list with a thread per bug?). Once that's done, I'm all for
> switching to github.
>
> This adds a burden on everyone to observe two locations for bugs. By
> comparison creating a GitHub account is simple. Even creating a
> bugzilla account is more difficult.
>

I think it should be relatively easy to automate using github's APIs.

The issue is not the ease of signing up for github, but that there are some
people who specifically don't have or want GitHub accounts because they
don't want to use proprietary software or were prevented by GitHub's rules
(Iran or similar places, don't know that we would legally be able to post
on GitHub on their behalf though).

I personally don't have either issue, but do know some people with the
former issue who are using LLVM as part of their job.

Jacob
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200203/b01a7529/attachment.html>


More information about the llvm-dev mailing list