From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.devel Subject: Re: [RFE] Migration to gitlab Date: Fri, 10 May 2019 19:33:56 +0300 Message-ID: <658fcd11-dfad-2060-c84b-5da938d506b7@yandex.ru> References: <1552789070.5272.1@yandex.ru> <87imwhmmt8.fsf@gmail.com> <87y347g1l3.fsf@iotcl.com> <9ac21e82-8e47-f9b5-f88d-23c0c56946d1@yandex.ru> <87pnpc1lby.fsf@iotcl.com> <83zhoezdqc.fsf@gnu.org> <87imuivfcr.fsf@iotcl.com> <83k1eyfxls.fsf@gnu.org> <3b8e2195-07c0-a240-6164-8d34bcca344f@yandex.ru> <83ftpmfp0y.fsf@gnu.org> <838svefl3p.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="66358"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 Cc: toon@iotcl.com, monnier@iro.umontreal.ca, agrambot@gmail.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri May 10 18:49:41 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hP8iL-000H8e-HU for ged-emacs-devel@m.gmane.org; Fri, 10 May 2019 18:49:41 +0200 Original-Received: from localhost ([127.0.0.1]:46720 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hP8iK-0000B3-E8 for ged-emacs-devel@m.gmane.org; Fri, 10 May 2019 12:49:40 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:44857) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hP8TO-00059N-5a for emacs-devel@gnu.org; Fri, 10 May 2019 12:34:15 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hP8TM-0006Fi-9r for emacs-devel@gnu.org; Fri, 10 May 2019 12:34:14 -0400 Original-Received: from mail-wm1-x32c.google.com ([2a00:1450:4864:20::32c]:51232) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hP8TI-0006Be-Td; Fri, 10 May 2019 12:34:10 -0400 Original-Received: by mail-wm1-x32c.google.com with SMTP id o189so8272836wmb.1; Fri, 10 May 2019 09:34:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=w5R5MxIU1j6/hT4baz5PH/8d6d07dd5uYhrThqUrOnE=; b=bSfJ7W1FSrKGUlNbQi2tImBy9ZOofrE8fWx0YsK1dThf8P3sntqAM81LG/V6K+Gvsd NH2n7QnkoG+e8TQUnB/kRNJ0LD4sv1zVUati6v1MnJLCV53Sa10njYjlBCg7BPjNOkYc SuMDlUF4RrGbG86G+4lTIFpXfEuixUhAW0s2lVLGtvqAfW+IhFAMr8o2ysmtJoqJuDUg GSvBrCmfJxP2dla/EJQq2ILGQA/Q3VwfRSURJTtFi5VNwyYSfOSqCHYc7BBB0QPXJdL7 2IxQBb5vvSs/IdUJwwUN9DrDIjSQGFI8c5fm26d7FO8/VgDsFVwg75IJHD0WYyDVO7Nk ilCg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:cc:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=w5R5MxIU1j6/hT4baz5PH/8d6d07dd5uYhrThqUrOnE=; b=ZBT7++ZV55gZMlREHEiJ4UNjhKpD4CJlPb6XOceOC4TeO6lXQPq0Z92jgSCjwMa9RI kfXhEQIZCZcsczuj8QUBuOSK6Og5MdvYZw4Xpur5SEFasaGWK7/KbFejd47+MtGkFw8l dbxVp/rg1KqcU31OSQUwrhTAcLgYAh/roAHUIX8EhGKvgXNRknC+bWDa2ZnNpTgGn7sM 9A6VxnJy7MaBJWLJ9phjSLF/Wvbgj08Ej/s0lXd20G3Kx9bfVDSue9RDDUTDgLsRHOKr kOz2Nz0e9eE6ZpREJjErap4rICXOQUvbPfsc1ILWPuoT5ZUGv0a9I1tAT0UT8ZA8KtiX LDCw== X-Gm-Message-State: APjAAAV0hPdThleqyQz/cAeyc8ieQdQ5BrXID64GaAPqvhFp+v2KLxp1 Aei+qOb/yQ4/qYSEndO1pRY= X-Google-Smtp-Source: APXvYqzieFWUgxtotCH6r1+xSyRUyiJqlB/1N5GdzHepX78MraPkiahYds2e52unxK94gejuPY5ZUQ== X-Received: by 2002:a1c:7a12:: with SMTP id v18mr7897134wmc.69.1557506041753; Fri, 10 May 2019 09:34:01 -0700 (PDT) Original-Received: from [192.168.0.195] ([109.110.245.170]) by smtp.googlemail.com with ESMTPSA id f6sm7923479wro.12.2019.05.10.09.33.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 10 May 2019 09:34:00 -0700 (PDT) In-Reply-To: <838svefl3p.fsf@gnu.org> Content-Language: en-US X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a00:1450:4864:20::32c X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:236390 Archived-At: On 10.05.2019 17:19, Eli Zaretskii wrote: > Yes, my point was that having to work via a Web browser will need to > switch frequently between it and Emacs. Which is an annoyance, to say > the least. I can believe that, even if I don't really understand it. Anyway, IIRC your current stance on that issue is that we'll need an Emacs-based client anyway, even just for the issues tracker. > It's worse, because debbugs doesn't send me notifications of closing > bugs, except when I close them, or when I was the one who filed the > bug. Hmm. Let's see if it can be configured as well, or we can add that to the list of requirements on the GitLab-CE issue Toon opened. >>> And when a patch is posted, I get another useless notification. >> >> Sorry, you lost me here. Don't you expect to be notified for every >> message in the bug tracker? > > Only once, yes. I don't want notifications about the attributes of > the new bug being set as side effect of accepting it. Same as above. >>> MR reassignments are important to just 2 people: the old and the new >>> assignee, possibly just the latter. I certainly don't want to know >>> about all the reassignments of all the issues. >> >> I don't know if I agree, but hopefully it can be configured this way. > > I hoped someone will explain how. No one did. If you log into EMBA (you might have to register first (*)) and navigate to this page: https://emba.gnu.org/profile/notifications you will see two "notification level" dropdowns, one Global, and one for 'emacs'. I think you can change either. Click on one of them and choose the last item: Custom. You will then be able to choose the events to get notifications for. MR reassignments are in that list. Here's also the same information on the API level: https://docs.gitlab.com/ee/api/notification_settings.html Not sure if that list is exhaustive, or if there are emails we'd want to configure off but cannot. That would, again, be something to ask the GitLab developers for. >> If the email workflow is used, though, you can also do what I've seen >> many people recommend to others who complained about excessive emails >> here (or being Cc'd on discussions they do not want to read, which is >> more of a problem, IMHO): set up email filters. Decent MUAs support that. > > Email filters are the last resort in my book. It would also be in > yours, if you considered a possibility to work via email. But I already do, here. > Once again, if you want to make a change in our workflow, please make > sure the change doesn't raise the bar for the core developers too > much, or else it will be a hard sell. I try. >> Whenever you feel like it, we can go ahead and experiment with the bug >> tracker that's part of the EMBA installation. And see how far we can go >> with email-only workflow, without an Emacs-based client. > > I don't think I understand what such an experiment would mean. Do you > mean we will have to deal with each bug twice? And what would be the > workflow in that case? can someone post some instructions? No, I'm suggesting to use it as a sandbox at first. Post some random issues, close them, reopen them, write some comments, receive comments from others, respond to them over email, etc, and see how well that works, and what the main problems are. To post a new issue, you can navigate to https://emba.gnu.org/emacs/emacs/issues and click "New issue". This also requires registration (at least, for now (**)). (*) I think currently registration is only manual, so we'll need to ask Toon to create an account. (**) IIUC later we can configure it to allow logging in with existing Google/Twitter/etc accounts, and, with some work, even authenticate with Savannah (https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/integration/omniauth.md).