From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Konstantin Kharlamov Newsgroups: gmane.emacs.devel Subject: Re: contributing to Emacs Date: Sun, 18 Jun 2023 12:30:13 +0300 Message-ID: <8cc19084ab18d0adb0f2cee4af14aa1b1d914a83.camel@yandex.ru> References: <83v8fnslfz.fsf@gnu.org> <87v8fnh1h2.fsf@web.de> <83mt0zs9rc.fsf@gnu.org> <0a968a4e1b267c0f15dd237e6ea12a709fc06d5e.camel@yandex.ru> <838rcisj7o.fsf@gnu.org> <6537fa5fa5c1fe8437ed99ee0988e35895f5a54b.camel@yandex.ru> <8423a35750d8d8e0437c7708f6b4d0bbdfdb7fe0.camel@yandex.ru> <87o7ldf7ky.fsf@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="29026"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Evolution 3.48.2 Cc: "Alfred M. Szmidt" , eliz@gnu.org, luangruo@yahoo.com, emacs-devel@gnu.org To: "Dr. Arne Babenhauserheide" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Jun 18 11:30:50 2023 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 1qAokE-0007Ps-C6 for ged-emacs-devel@m.gmane-mx.org; Sun, 18 Jun 2023 11:30:50 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qAojo-0000lH-Qt; Sun, 18 Jun 2023 05:30:24 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qAojl-0000kz-Ol for emacs-devel@gnu.org; Sun, 18 Jun 2023 05:30:21 -0400 Original-Received: from forward500b.mail.yandex.net ([178.154.239.144]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qAojj-0002B6-Ax; Sun, 18 Jun 2023 05:30:21 -0400 Original-Received: from mail-nwsmtp-smtp-production-main-46.myt.yp-c.yandex.net (mail-nwsmtp-smtp-production-main-46.myt.yp-c.yandex.net [IPv6:2a02:6b8:c12:3b27:0:640:a9e4:0]) by forward500b.mail.yandex.net (Yandex) with ESMTP id 56BF55EAC7; Sun, 18 Jun 2023 12:30:14 +0300 (MSK) Original-Received: by mail-nwsmtp-smtp-production-main-46.myt.yp-c.yandex.net (smtp/Yandex) with ESMTPSA id DUbmmXVDSSw0-UffxLkfH; Sun, 18 Jun 2023 12:30:14 +0300 X-Yandex-Fwd: 1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1687080614; bh=p1MCEmtDdS/mjoAjvWcacBt+2eHz8cLo9IGeARWAeg8=; h=References:Date:In-Reply-To:Cc:To:From:Subject:Message-ID; b=aunbx9lZexT6hHxwL8nCBURT/TJkaU3P7tCrn6WfOpOok8ONNqvm4FnlJS0MD76Lt Sw1h5R1tvAnfy5mk/zY+ZZXx9vVbRm/0QSYhZrZJRKQUnXXufNyghmoQ5ii/S+5zzx iRFtLUJgSV0IpTGj393C0QIB2dKQBiE8bc/N8Qbo= Authentication-Results: mail-nwsmtp-smtp-production-main-46.myt.yp-c.yandex.net; dkim=pass header.i=@yandex.ru In-Reply-To: <87o7ldf7ky.fsf@web.de> Received-SPF: pass client-ip=178.154.239.144; envelope-from=hi-angel@yandex.ru; helo=forward500b.mail.yandex.net 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:306934 Archived-At: On Sun, 2023-06-18 at 10:59 +0200, Dr. Arne Babenhauserheide wrote: >=20 > Konstantin Kharlamov writes: >=20 > > On Sat, 2023-06-17 at 14:36 -0400, Alfred M. Szmidt wrote: > > open sources projects only requires finding out their upstream URL, >=20 > And usually creating an account, putting SSH keys into it, and so forth = =E2=80=A6 >=20 > > in Emacs case you > > also need to go read HUGE "Sending patches" section. >=20 > This sounds like a writing problem: such a section should be quick to > read. Do you have concrete ideas how to slim this down? >=20 > Maybe with some simple examples how to send the patches. Well=E2=80=A6 Yes. I see that the section "Sending Patches" is actually mix= ed up also with the information about what changes should be contained in it. It is a useful information, but I think it could be great if that was *on the same = page* but *in a separate paragraph*. This would allow a person to immediately kno= w which part is related to just "how to send a patch" and which is about the commit message and stuff like that. I can send the changes if there's any interest. > > And then if that's not enough, from what I've seen maintainers also > > expect you to have read CONTRIBUTE section, which is absolutely large, > > much bigger than "Sending patches". (to be fair, if you are a new > > contributor, you won't know it exists because "Sending patches" has no > > mention of it). >=20 > Same here. I see quite a bit of explanation in the CONTRIBUTE file that > makes that longer than the information a contributor really has to know. Eli said elsewhere that reading this file isn't required, so whatever. The "Sending Patches" section does not refer to it anyway. > > more complicated. You see: these are complete no-brainer in 90% of proj= ects. > > But > > every time I contribute here I have to think about such stuff which is > > completely > > irrelevant to the changes being sent. > > And how do you even get a link where to send new patch revision? I have= two > > dozens > > email notifications coming to my email everyday. So I will have to sear= ch > > through all > > that stuff. >=20 > Can this be improved with changes to debbug emails sent? Or to the > debbug web interface? >=20 > For a github project (to name the elefant in the room) you also have to > know the URL, but there it feels easier. Can we make that easier in the > existing infrastructure? I will need to think about that, but I would guess there should be ways.