From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Philippe Vaucher Newsgroups: gmane.emacs.devel,gmane.emacs.bugs Subject: Re: [RFE] Migration to gitlab Date: Sun, 17 Mar 2019 13:37:42 +0100 Message-ID: References: <1552789070.5272.1@yandex.ru> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000005eb50a0584498bea" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="191707"; mail-complaints-to="usenet@blaine.gmane.org" Cc: bug-gnu-emacs@gnu.org, emacs-devel To: Konstantin Kharlamov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Mar 17 13:54:28 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 1h5VJ5-000nnN-OR for ged-emacs-devel@m.gmane.org; Sun, 17 Mar 2019 13:54:27 +0100 Original-Received: from localhost ([127.0.0.1]:55383 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h5VJ4-0001t9-Q9 for ged-emacs-devel@m.gmane.org; Sun, 17 Mar 2019 08:54:26 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:50083) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h5VIu-0001h1-Ih for emacs-devel@gnu.org; Sun, 17 Mar 2019 08:54:18 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h5V3M-00023M-Gg for emacs-devel@gnu.org; Sun, 17 Mar 2019 08:38:13 -0400 Original-Received: from mail-lj1-x232.google.com ([2a00:1450:4864:20::232]:38564) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1h5V3K-00020N-KZ; Sun, 17 Mar 2019 08:38:11 -0400 Original-Received: by mail-lj1-x232.google.com with SMTP id x13so11597045ljj.5; Sun, 17 Mar 2019 05:38:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+w6IuuZ/SoNavqxnky7pQKc4OqcHzb7O3TU/QrTT1zc=; b=Ik6JzzRlqaS584KXjO3QeiF03Q0m+QTQb3nAo7UBFIFYJaA/AhkVB1td3gZy1SgDhy vbdMldSOzygJi/kl5zTVq3/a85tg+wjsOKjyFRRyppNIF3j/HeHWP6Hv9eS2m/bvFs77 aDB4JWSRZZFLkcp5fc9h/Ay2XiWE/CvcyQQBDkzJrDOsuIA9h35e9m53qDIsFloYOkGk c1v/96+Kr6XR2X4A7f4IoQFmiqqaM6FYnBHMojzWN35RsBxqeumgV9PSD9MZg9yNxaba l1YezRntCVgyAGe6gNGzSsUGAXQF2Co8p1YuINrkwsD85g7x+6zQFfDKr9KKb59Gmg6E xo7A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+w6IuuZ/SoNavqxnky7pQKc4OqcHzb7O3TU/QrTT1zc=; b=T85RVRFsxMzY7PoEE5Gk7kzjkmIHzgtMPDNufQh1oYBrXYvmwRxPDhg8YdlnNJkNJX kzXmBWHmZeWDfeyYd2PWL/Dh0lA37klLeVJwBQi+711nf1YIqJujEEcX+B8UokkyTJ76 xUwkmwTkX0reaqTJjYvR8bhoYSPTpiqdxTan7SOj5p8mMqv6Vh3zgJBCOxxMDFtaY7H7 EHrTdBe286m6HZ82Au4Aqw3V4J8mlYiphZJMeKxtdqBe3TEXG5Gv9G+K47dzJPERvG0c rnNIvHcIVb/Bd7fKnkRpLj9Sa9QaIB26EoKcYNOcJ9YNxawAcw35ZGpMvlIi9q6Uc0dg JGrQ== X-Gm-Message-State: APjAAAWQbLMdBeIBiNLvVVmJFldID577UgGb4H+Vg1LBoV4P9CK8AHG0 wkoutLtQqvte9SRMA6rOWIOT2+ft70TOT0g1oi4= X-Google-Smtp-Source: APXvYqye7op2piwD9Mp/w9dftPNgvqIDPS0xpaEOh9GLb1gR2vaNOUiuL+cnSYnKMpdGSXhJxT9lKX7lDtlI8D42n7U= X-Received: by 2002:a2e:9d53:: with SMTP id y19mr7331459ljj.37.1552826289270; Sun, 17 Mar 2019 05:38:09 -0700 (PDT) In-Reply-To: <1552789070.5272.1@yandex.ru> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a00:1450:4864:20::232 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:234263 gmane.emacs.bugs:156434 Archived-At: --0000000000005eb50a0584498bea Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable > > A lot of open-source projects already migrated to gitlab: all > FreeDesktop projects, all Gnome projects; and KDE are likely to migrate > soon too=C2=B2. Gnome reports: "After switching to GitLab, I noticed almo= st > immediately an increase in contributions from people I hadn=E2=80=99t met > before. I think GitLab really lowered the threshold for people getting > started"=C2=B3. > I agree. I contribute often on github/gitlab, and the process is very simple. In comparison, Emacs has hurdles that requires much more motivation and persistance in order to contribute. I think it boils down to this: on github/gitlab, almost everything is handled by git itself: you propose/test changes by creating/pulling branches on the repository/fork... so you basically only need to use git and click a few buttons in the browser (or use magithub/emacs-gitlab etc). With the Emacs model, you need to go back & forth between emails and git, copying patches, applying them, keeping track of where each changes is, etc. The extra step does not look like much but it is a lot, especially for simple changes. > 4. Impossible to lose "merge request". I've seen in Emacs docs an > advice to send patch series to a bugtracker, because on emacs-devel > they can easily be forgotten. That can't happen so easily with gitlab, > where you have a tab with open merge requests. > Yeah, the maintainer job is easier, no need to remember which topics are the active ones. Searching for existing or past similar issues also feels simpler, but I guess that is just habit. > 5. Discussion on patch series is easier to read. On mailing lists > can > quickly appear a dozen of no longer relevant review mails, that refer > to something that was addressed. In Gitlab the addressed comments can > be marked as such, and get collapsed. > It's also easier to view the current states of the commits, you don't need to search for the latest patch in the list of emails. Now, the Emacs model is similar to the linux kernel dev & the git dev workflow, so obviously "it works fine" and has advantages too, but personally I think those are outweighted by the the disadvantages (or rather than the contribution experience is much nicer with gitlab). Kind regards, Philippe --0000000000005eb50a0584498bea Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
A lot of open-source p= rojects already migrated to gitlab: all
FreeDesktop projects, all Gnome projects; and KDE are likely to migrate soon too=C2=B2. Gnome reports: "After switching to GitLab, I noticed a= lmost
immediately an increase in contributions from people I hadn=E2=80=99t met <= br> before. I think GitLab really lowered the threshold for people getting
started"=C2=B3.

I agree. I contrib= ute often on github/gitlab, and the process is very simple. In comparison, = Emacs has hurdles that requires much more motivation and persistance in ord= er to contribute.

I think it boils down to this: o= n github/gitlab, almost everything is handled by git itself: you propose/te= st changes by creating/pulling branches on the repository/fork... so you ba= sically only need to use git and click a few buttons in the browser (or use= magithub/emacs-gitlab etc). With the Emacs model, you need to go back &= ; forth between emails and git, copying patches, applying them, keeping tra= ck of where each changes is, etc. The extra step does not look like much bu= t it is a lot, especially for simple changes.

=C2= =A0
=C2=A0 =C2=A0 =C2=A0 =C2=A0 4. Impossible to lose "merge request"= . I've seen in Emacs docs an
advice to send patch series to a bugtracker, because on emacs-devel
they can easily be forgotten. That can't happen so easily with gitlab, =
where you have a tab with open merge requests.

Yeah, the maintainer job is easier, no need to remember which topic= s are the active ones. Searching for existing or past similar issues also f= eels simpler, but I guess that is just habit.

=C2= =A0
=C2=A0 =C2=A0 =C2=A0 =C2=A0 5. Discussion on patch series is easier to read= . On mailing lists can
quickly appear a dozen of no longer relevant review mails, that refer
to something that was addressed. In Gitlab the addressed comments can
be marked as such, and get collapsed.

I= t's also easier to view the current states of the commits, you don'= t need to search for the latest patch in the list of emails.

=
Now, the Emacs model is similar to the linux kernel dev & th= e git dev workflow, so obviously "it works fine" and has advantag= es too, but personally I think those are outweighted by the the disadvantag= es (or rather than the contribution experience is much nicer with gitlab).<= /div>

Kind regards,
Philippe
=
--0000000000005eb50a0584498bea--