From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.6 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id F2327C4363A for ; Thu, 29 Oct 2020 17:13:34 +0000 (UTC) Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 5250620759 for ; Thu, 29 Oct 2020 17:13:34 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="E4Yj1FT5" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 5250620759 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([::1]:44120 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kYBUT-000742-4R for qemu-devel@archiver.kernel.org; Thu, 29 Oct 2020 13:13:33 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:35996) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kYBTU-0006Vq-0u for qemu-devel@nongnu.org; Thu, 29 Oct 2020 13:12:32 -0400 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:20728) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.90_1) (envelope-from ) id 1kYBTS-0002po-BB for qemu-devel@nongnu.org; Thu, 29 Oct 2020 13:12:31 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1603991548; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=BICz9Hx9h7U2mkAjZ+q4kODhFfSnaEEV3ceg7+0Ja2E=; b=E4Yj1FT5WBSpIPSXANXH7V5mmZI53GJusp3OtGF2pckTeTRmxjCf4JKMiLfk+ueJYCml6z Q415GM7wZYhFOoXnq2IAyhZZmy/EOAEBwu8tkwFnixCPAHp0oyQU/ll3SwJerDcEH12FwR 8+FU7dBXL6766FnWI/Y/v5WN+6imBN0= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-9-9Iy1BBY8NpC1kdeFTAiHQw-1; Thu, 29 Oct 2020 13:12:24 -0400 X-MC-Unique: 9Iy1BBY8NpC1kdeFTAiHQw-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 79658185A0C3; Thu, 29 Oct 2020 17:12:23 +0000 (UTC) Received: from [10.10.118.238] (ovpn-118-238.rdu2.redhat.com [10.10.118.238]) by smtp.corp.redhat.com (Postfix) with ESMTP id AF8535B4AB; Thu, 29 Oct 2020 17:12:22 +0000 (UTC) Subject: Re: Migrating to the gitlab issue tracker To: Alistair Francis , Cornelia Huck References: <20201029174114.47e2b351.cohuck@redhat.com> From: John Snow Message-ID: <3713093e-bf3b-bf23-a8d0-70fe429032ba@redhat.com> Date: Thu, 29 Oct 2020 13:12:22 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.3.1 MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=jsnow@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Received-SPF: pass client-ip=216.205.24.124; envelope-from=jsnow@redhat.com; helo=us-smtp-delivery-124.mimecast.com X-detected-operating-system: by eggs.gnu.org: First seen = 2020/10/29 00:47:54 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] [fuzzy] X-Spam_score_int: -23 X-Spam_score: -2.4 X-Spam_bar: -- X-Spam_report: (-2.4 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.261, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: "qemu-devel@nongnu.org Developers" Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" On 10/29/20 12:49 PM, Alistair Francis wrote: > On Thu, Oct 29, 2020 at 9:41 AM Cornelia Huck wrote: >> >> On Thu, 29 Oct 2020 12:01:27 -0400 >> John Snow wrote: >> >>> If you're in the CC list, it's because you are listed in MAINTAINERS. >> >> >> >>> >>> 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 > Mostly I was looking for any hard objections over the idea of issues not necessarily being sent to the list anymore, if there were any. I want to hear from Thomas Huth too, but maybe we can work out a pilot migration and give it a test-run and find more concrete objections that way. --js