qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alistair Francis <alistair23@gmail.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: John Snow <jsnow@redhat.com>,
	"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: Migrating to the gitlab issue tracker
Date: Thu, 29 Oct 2020 09:49:58 -0700	[thread overview]
Message-ID: <CAKmqyKOY+5WcxUg3Rvq2t3vYWOHrHQdhcv8PkiqZX2zVMdqJ3Q@mail.gmail.com> (raw)
In-Reply-To: <20201029174114.47e2b351.cohuck@redhat.com>

On Thu, Oct 29, 2020 at 9:41 AM Cornelia Huck <cohuck@redhat.com> wrote:
>
> On Thu, 29 Oct 2020 12:01:27 -0400
> John Snow <jsnow@redhat.com> wrote:
>
> > If you're in the CC list, it's because you are listed in MAINTAINERS.
>
> <cleared the cc: list except for qemu-devel :)>
>
> >
> > Paolo's QEMU keynote this morning mentioned the possible use of the
> > Gitlab issue tracker instead of using Launchpad.
> >
> > I'm quite fond of the gitlab issue tracker, I think it works quite well
> > and it has pretty good and uncomplicated API access to it in order to
> > customize your workflow if you'd really like to.
> >
> > In experimenting with my mirror on gitlab though, I was unable to find a
> > way to configure it to send issue tracker notifications to the email
> > list. A move to gitlab would likely mean, then:
> >
> > 1. The cessation of (automatic) issue tracker mails to the list
> > 2. The loss of the ability to update the issue tracker by replying to
> > said emails
> > 3. Anyone listed in MAINTAINERS would be expected to have a gitlab
> > account in order to interact with the issue tracker.
>
> The gitlab issue tracker is almost certainly is an improvement over
> launchpad (and I do have a gitlab account); but not being able to
> interact via email is at least annoying. I expect that not only
> maintainers will want to interact with bug reports?
>
> >
> > However, once you have a gitlab account, you DO gain the ability to
> > receive emails for issues; possibly only those tagged with labels that
> > you cared about -- giving a nice filtering mechanism to receive only
> > bugs you care about.
> >
> > Gitlab also does support individual accounts updating issues using a
> > generated personalized email address, so if the email workflow is
> > crucial to you, it is still available.
>
> You mean that I can update via email, provided it's an address
> associated with my account?
>
> >
> > I'm for it, or at least for beginning a pilot program where we
> > experiment with the idea for interested parties. I wanted to send up a
> > trial balloon to see how we were feeling about this.

I'm not sure if you want Acks, but it sounds good to me.

Alistair

> >
> > --js
>
>


  reply	other threads:[~2020-10-29 17:03 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-29 16:01 Migrating to the gitlab issue tracker John Snow
2020-10-29 16:30 ` Daniel P. Berrangé
2020-10-29 16:41 ` Cornelia Huck
2020-10-29 16:49   ` Alistair Francis [this message]
2020-10-29 17:12     ` John Snow
2020-10-29 17:36       ` Kashyap Chamarthy
2020-10-29 19:55       ` Thomas Huth
2020-10-29 20:27         ` John Snow
2020-10-30  9:23           ` Daniel P. Berrangé
2020-10-30 10:03             ` Peter Maydell
2020-10-30 10:10               ` Daniel P. Berrangé
2020-10-30 10:57                 ` Peter Maydell
2020-11-05  0:06                   ` John Snow
2020-11-05  6:14                     ` Thomas Huth
2020-11-05  9:54                       ` Daniel P. Berrangé
2020-11-05 15:44                       ` John Snow
2020-11-05 15:50                         ` Daniel P. Berrangé
2020-11-08  9:00                           ` Thomas Huth
2020-11-08 11:58                             ` Peter Maydell
2020-11-09  8:04                               ` Thomas Huth
2020-11-09 10:10                               ` Daniel P. Berrangé
2020-11-09 10:14                                 ` Peter Maydell
2021-01-21 10:57                     ` Thomas Huth
2021-01-21 16:20                       ` John Snow
2020-10-30 10:26           ` Alex Bennée
2020-10-30 12:53             ` John Snow
2020-11-08  8:57               ` Thomas Huth
2020-10-29 18:04   ` John Snow
2020-10-29 20:33     ` Cornelia Huck
2020-10-30  9:16 ` Stefan Hajnoczi
2020-10-30 15:39   ` John Snow
2020-11-02 13:57   ` Laszlo Ersek
2020-11-02 14:26     ` Daniel P. Berrangé
2020-11-02 14:42       ` Eric Blake
2020-11-04 17:10         ` Laszlo Ersek
2020-11-04 17:03       ` Laszlo Ersek
2020-11-04 17:19         ` Daniel P. Berrangé
2020-11-06 15:37           ` Laszlo Ersek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAKmqyKOY+5WcxUg3Rvq2t3vYWOHrHQdhcv8PkiqZX2zVMdqJ3Q@mail.gmail.com \
    --to=alistair23@gmail.com \
    --cc=cohuck@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).