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

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.

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

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.

Michael

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>

On Monday, February 3, 2020, Jacob Lifshay <programmerjake at gmail.com>
wrote:
>
> ---------- Forwarded message ---------
> From: Jacob Lifshay <programmerjake at gmail.com>
> Date: Mon, Feb 3, 2020, 09:11
> Subject: Re: [cfe-dev] [llvm-dev] RFC: Switching from Bugzilla to Github
> Issues
> To: Michael Kruse <cfe-dev at meinersbur.de>
> Cc: Tom Stellard <tstellar at redhat.com>, llvm-dev <llvm-dev at
lists.llvm.org>,
> LLDB Dev <lldb-dev at lists.llvm.org>, cfe-dev <cfe-dev at
lists.llvm.org>
>
>
> 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.
>
>
please don't.

as jacob says that will be yet another project that libre ethical
developers plus individuals who have not received authorisation and are
under explicit instructions never to register on social platforms plus
iranian and other developers will be prevented and prohibited from
interacting with llvm at a basic and fundamental level: bugreporting.

plus: do not be offended, i am deliberately raising the "thorny"
perspective if you know what i mean (because almost without a doubt noone
else will).

consider this: what kind of message does it send to developers wishing to
contribute to a project if the admins are so... "incompetent" (strong
word,
you know what i mean) that they cannot self-host their own infrastructure,
independent of corporate and other control?

the way i see it: as maintainers of high profile mission critical
infrastructure for the entire planet's software we have a duty and a
responsibility to be fully independent and impartial, with no corporate
sponsors or services that may be pulled at any time and blackmail
effectively deployed with zero warning.

what happens if the US decides that *yet another* country is to be added to
their Trade and Sanctions War?

you really want to place the bugtracker and hosting at the mercy and
political whim of not just a corporation but of one of the most
irresponsible governments of the 21st century?

moo?

:)

food for thought.

l.



-- 
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20200203/81811745/attachment.html>