From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jim Porter Newsgroups: gmane.emacs.devel Subject: Re: Gitlab Migration Date: Thu, 26 Aug 2021 11:42:08 -0700 Message-ID: References: <87h7fcnmq0.fsf@posteo.net> <87o89kw0hl.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="29804"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Daniel Fleischer , emacs-devel@gnu.org To: Lars Ingebrigtsen , Philip Kaludercic Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Aug 26 20:43:38 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mJKLh-0007Z5-NB for ged-emacs-devel@m.gmane-mx.org; Thu, 26 Aug 2021 20:43:37 +0200 Original-Received: from localhost ([::1]:49706 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mJKLg-0006yO-Ix for ged-emacs-devel@m.gmane-mx.org; Thu, 26 Aug 2021 14:43:36 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37158) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mJKKP-0006Gc-3z for emacs-devel@gnu.org; Thu, 26 Aug 2021 14:42:17 -0400 Original-Received: from mail-pj1-x102b.google.com ([2607:f8b0:4864:20::102b]:39529) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1mJKKM-0007Fi-S8 for emacs-devel@gnu.org; Thu, 26 Aug 2021 14:42:16 -0400 Original-Received: by mail-pj1-x102b.google.com with SMTP id oc2-20020a17090b1c0200b00179e56772d6so7212209pjb.4 for ; Thu, 26 Aug 2021 11:42:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=eO6YvShTN9+2LOkc3s1mQLhnAitt5NRRMMbP72WG2Ys=; b=aUSVGK2cmgyXAi76iD5V9tsatN73cB+t1MUBWEaCGpLwppkiny0FxAgsm0HiAW2Oz4 X08QKTg+2uk9P5+XAGWy7ZlHaIBuEr1QZGM/y4UnG8HfI/1HA0Lb3eM+TywglZ+SSfv9 QFei49mFtQeQIT4HnUmZe8VJ7HY2wLjKB4zidzu3BpUUXQ1OuAv+m0+oBoSV1K0qqjLU iuW6ndLp9Q9zQQgQKZ8Pb0fTrtaZ/ssnrP3mPhF2bYjgLoYJXhFlgWY3D9QyI9KMtyJs dMMmyHsX/OXsoG6DYwecH+6oxF6t3HobhZ6zVRlyqlLXUo/Vb788osmxF5sS907jwHcP iqrQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=eO6YvShTN9+2LOkc3s1mQLhnAitt5NRRMMbP72WG2Ys=; b=i2vTTVHBRpEJj7NZG+hayOglSC3c+20KPj+xrKcQ+vMB/MpHS7wmSnp8mCOO3DcRDZ mxeAEEWbaTKeGU7ZJmTPJfI3WeuCVmgTy9va5kKUPr62ZUwOEZEXfgURFhSakSfmX7/o LrIuaMGVnNfkMJA33aKfMRA5Pl7Ni80f11aSbE6kjc2SkVEE0X0YYS8Fde+4/E4qDfQc K+tb6le3xFGx8bDrWd7wxWq+d2AYJrmHsBXoyJLtlpOeo1iMB3QfKnxLqQSPVoRJgiIw iZuEhB5JkmSgCDZfopHFEDG074n0g6pCphyZjUMpEf1mwm0N2WCaseKNhroQZeSD3tsj dBGQ== X-Gm-Message-State: AOAM533O1oaUGn9eUo3BYlTek/68gk43sJ+jslRtbs4QmV4lHwLyr2xN 85h4dEWEyIikTgYpq4jvgiXxOoxVp6I= X-Google-Smtp-Source: ABdhPJxQuc2YeCJKUIbFTDTeMWm5vvzqSr9t2ktGZUhENN74/BrlqRbT8OjnaQn/hhLwqWBWtIWp8Q== X-Received: by 2002:a17:90a:d3d0:: with SMTP id d16mr18474771pjw.103.1630003331140; Thu, 26 Aug 2021 11:42:11 -0700 (PDT) Original-Received: from [192.168.1.2] (cpe-76-168-148-233.socal.res.rr.com. [76.168.148.233]) by smtp.googlemail.com with ESMTPSA id f137sm3670748pfa.160.2021.08.26.11.42.10 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 26 Aug 2021 11:42:10 -0700 (PDT) In-Reply-To: <87o89kw0hl.fsf@gnus.org> Content-Language: en-US Received-SPF: pass client-ip=2607:f8b0:4864:20::102b; envelope-from=jporterbugs@gmail.com; helo=mail-pj1-x102b.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:273063 Archived-At: On 8/26/2021 10:59 AM, Lars Ingebrigtsen wrote: > It seems like it should be easier to just send a patch, but feedback > we're getting shows that it's not for a number of developers. Many > don't use mail at all for development, and all they're used to is the > GitLab/Hub way of doing it. I'm pretty new contributing to Emacs, and so I can definitely understand the feeling of intimidation about using a mailing list-based workflow for contributions. However, once I actually tried it, it turned out to be very similar as a contributor (I don't know if I'd want to *maintain* a project using a mailing list workflow, but that's not my job, so it's not a problem for me). One issue, however, is that the documentation for sending patches[1], while very thorough, doesn't make things easy to understand for someone familiar with a pull request workflow. While all the advice in the documentation is useful, a lot of it is stuff that anyone who's sent a PR before (hopefully) already knows, such as, "Don’t mix together changes made for different reasons. Send them individually." After resolving to read the documentation thoroughly, I realized I only really needed a few short bits of advice: 1) The bug tracker is at https://debbugs.gnu.org 2) To submit a patch: a) Clone the Emacs git repo b) Make a branch and add some commits (as usual for the PR workflow) c) Run `git format-patch master` d) Compose an email to bug-gnu-emacs@ with the files in (c) attached 3) Commit messages have a special format (but you can just imitate what you see in prior commits) Almost everything else is either common advice for contributing to any project, or something maintainers can address after a patch is submitted (e.g. copyright assignment). While I don't think the existing documentation should be removed, having a "quick-start intro" for people already familiar with the PR workflow would probably go a long way towards making new contributors feel less intimidated. If the above sounds reasonable, I can work on a patch to the docs once my copyright paperwork is updated (or someone else can update them instead; I don't have a preference). It might even be helpful to add a "Contributing" section to the main Emacs homepage[2] with a short version of what's already in the full documentation. - Jim [1] https://www.gnu.org/software/emacs/manual/html_node/emacs/Sending-Patches.html [2] https://www.gnu.org/software/emacs/