From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Konstantin Kharlamov Newsgroups: gmane.emacs.devel Subject: Re: [RFE] Migration to gitlab Date: Fri, 22 Mar 2019 13:01:58 +0300 Message-ID: <1553248918.28810.1@yandex.ru> References: <1552789070.5272.1@yandex.ru> <1552791707.5272.2@yandex.ru> <1552793646.5272.3@yandex.ru> <1552821396.21432.0@yandex.ru> <83imwhwf4x.fsf@gnu.org> <837ecvux2q.fsf@gnu.org> <9c7cf558-a2d3-951e-d6e1-31b3ad5900cf@yandex.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="194941"; mail-complaints-to="usenet@blaine.gmane.org" Cc: theophilusx@gmail.com, emacs-devel@gnu.org, dgutov@yandex.ru To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Mar 22 11:10:47 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 1h7H8R-000oao-3r for ged-emacs-devel@m.gmane.org; Fri, 22 Mar 2019 11:10:47 +0100 Original-Received: from localhost ([127.0.0.1]:54955 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h7H8Q-0001Cg-3u for ged-emacs-devel@m.gmane.org; Fri, 22 Mar 2019 06:10:46 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:60189) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h7H6x-0007ul-MR for emacs-devel@gnu.org; Fri, 22 Mar 2019 06:09:21 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h7H04-0005k8-0P for emacs-devel@gnu.org; Fri, 22 Mar 2019 06:02:09 -0400 Original-Received: from forward102o.mail.yandex.net ([2a02:6b8:0:1a2d::602]:43223) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1h7H01-0005bg-1x; Fri, 22 Mar 2019 06:02:06 -0400 Original-Received: from mxback12o.mail.yandex.net (mxback12o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::63]) by forward102o.mail.yandex.net (Yandex) with ESMTP id 9D1186682112; Fri, 22 Mar 2019 13:02:00 +0300 (MSK) Original-Received: from smtp4p.mail.yandex.net (smtp4p.mail.yandex.net [2a02:6b8:0:1402::15:6]) by mxback12o.mail.yandex.net (nwsmtp/Yandex) with ESMTP id a7FH2uCMvn-20iSSchJ; Fri, 22 Mar 2019 13:02:00 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1553248920; bh=5iDXz6wCgJ2tx87KY4tOHxGCKZD3jomYE+IUNxwQbOw=; h=In-Reply-To:Cc:To:Subject:From:References:Date:Message-Id; b=m3/8ueNetvyaXqX8ojnIsAWheNHRwZ9vOO/KL6Caqwn8un3AueNM8pHl+l1860TVL FIW6KkefyFhtDJf3zHyRh/Wcp/OSSrJlUqqoKdo7SW+S9eYdXTPjkDcRZrfDKl3YuS umtcO0kW9SRDidbnJvAe8N3qXTGZ7bcYqNe1MQwc= Authentication-Results: mxback12o.mail.yandex.net; dkim=pass header.i=@yandex.ru Original-Received: by smtp4p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id Mngj9P4C7b-1xSGwK9s; Fri, 22 Mar 2019 13:01:59 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) In-Reply-To: <831s32t3fn.fsf@gnu.org> X-Mailer: =?UTF-8?Q?geary=2F=C3=8E=C2=B2=2Dtesting=2Dbran?= =?UTF-8?Q?ch=7Eg4db93c55?= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2a02:6b8:0:1a2d::602 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:234535 Archived-At: On =D0=A1=D1=80, Mar 20, 2019 at 10:23:08, Eli Zaretskii wro= te: >> Date: Wed, 20 Mar 2019 09:56:34 +0300 >> From: Konstantin Kharlamov >> Cc: dgutov@yandex.ru, theophilusx@gmail.com, emacs-devel@gnu.org >>=20 >> > And my point is that we are once again arguing about very much=20 >> minor >> > issues, without doing anything about, nor even touching, the more >> > important ones. E.g., I asked up-thread whether you knew how many >> > people review patches for Emacs; did you follow up on that? This=20 >> is >> > IMO much more important for Emacs development and eventually for=20 >> its >> > future than whether our CI will be from Gitlab or from somewhere=20 >> else, >> > definitely more important than the commit hooks issue. >>=20 >> I didn't reply this point because I don't know what to add. I get=20 >> that >> there's not much people doing review, but it's a pain present in=20 >> most >> projects. Even some Linux kernel subsystems often lacks proper=20 >> review, >> I regularly see articles about that on LWN popping up =E2=80=94 and the >> kernel has thousands of contributors, most of them are paid ones. >=20 > Unlike in many other projects, I consider the situation with patch > review, and more generally with the number of domain experts we have > on board in Emacs, a disaster. FTR, I think one reason that not many people are doing review is the=20 requirement for patches to be sent to bugtracker. Besides being just=20 confusing (obviously, it's a hack to work around lack of patch-tracking=20 system on emacs-devel), this conflicts with the fact, that contributors=20 are more likely to be subscribed to devel list rather than to=20 bugtracker. For example, I'm not subscribed to bugtracker because I don't know=20 Emacs internals to give any useful comment for bugs. But at least for=20 *.c file changes I could help a bit with review if I saw something on=20 ML. If you (not you personally, but Emacs developers) are trying to use=20 mailing list workflow, you might want to copy some parts of it from=20 other projects, such as Mesa drivers. Ignoring for a second the fact=20 that Mesa partially moved to gitlab, for ML part they used =CE=B1)=20 patchwork site to keep track of patches on mesa-devel, and =CE=B2)=20 bugtracker notifications go to mesa-devel ML, so=20 contributors/developers see them. And while on it, a few weeks ago I sent 2 patches to bugtrackers, and I=20 got a notification for each of them. I'm horrified to imagine what I=20 gonna see if I send a series of 20 patches. =