From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: [RFE] Migration to gitlab Date: Sun, 17 Mar 2019 20:05:18 +0200 Message-ID: <83imwhwf4x.fsf@gnu.org> References: <1552789070.5272.1@yandex.ru> <1552791707.5272.2@yandex.ru> <1552793646.5272.3@yandex.ru> <1552821396.21432.0@yandex.ru> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="108650"; mail-complaints-to="usenet@blaine.gmane.org" Cc: theophilusx@gmail.com, emacs-devel@gnu.org To: Konstantin Kharlamov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Mar 17 19:06:18 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 1h5aAr-000S9P-Vt for ged-emacs-devel@m.gmane.org; Sun, 17 Mar 2019 19:06:18 +0100 Original-Received: from localhost ([127.0.0.1]:58497 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h5aAq-0003J0-PK for ged-emacs-devel@m.gmane.org; Sun, 17 Mar 2019 14:06:16 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:53044) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h5aAF-0003IO-Tf for emacs-devel@gnu.org; Sun, 17 Mar 2019 14:05:41 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:50422) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h5aAE-0005vh-Ax; Sun, 17 Mar 2019 14:05:38 -0400 Original-Received: from [176.228.60.248] (port=2968 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1h5aA6-0007Ua-V6; Sun, 17 Mar 2019 14:05:32 -0400 In-reply-to: <1552821396.21432.0@yandex.ru> (message from Konstantin Kharlamov on Sun, 17 Mar 2019 14:16:36 +0300) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] 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:234287 Archived-At: > Date: Sun, 17 Mar 2019 14:16:36 +0300 > From: Konstantin Kharlamov > Cc: emacs-devel > > savannah.gnu.org looks like a news site Are you sure you are looking at the right page? You should be looking here: https://savannah.gnu.org/projects/emacs > > One thing I think you have possibly overlooked or glossed over is the > > copyright requirements for contributions to GNU Emacs. I suspect this > > is one of the reasons Emacs is not developed in a similar fashion to > > other projects which are based on the use of pull requests etc. > > I've just read a bit about that. I might be missing some nuances of the > process, but right now I don't see how using merge requests vs emails > could interfere. It doesn't interfere, but it slows down the process for new contributors, so doing this stuff quickly is no longer an attainable goal. > If an arbitrary newcomer out there would consider "Hmm, I have used > Emacs and Visual Studio Code, where do I want to contribute"; they > easily gonna stop half-way through figuring out how to send a patch, > and not gonna contribute to Emacs. Sending patches via email is only one requirement. There are other requirements peculiar to Emacs, which will not go away if we switch to another patch submitting system. Some of these requirements, each and every one of them flagged at some point as an obstacle for newcomers: . code submissions should include documentation . commit log messages should be formatted in a certain way . bug numbers should be referenced in log messages . US English conventions in writing comments and documentation (spelling, two spaces between sentences, etc.) . we require copyright assignments for accepting changesets larger than about 15 original source lines . we have peculiar rules regarding the branch were certain changes should be pushed (affects the branch against which contributors should prepare patches) . very elaborate coding and documenting conventions (their description takes around 900 lines in the ELisp manual) So as you see, being a contributor to Emacs is not easy and takes some getting used to. Plenty of reasons for arbitrary newcomers not to be bothered, whether or not we use Gitlab. Contributing to Emacs needs a lot of motivation regardless. We shouldn't forget that when we discuss individual issues.