From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: [nongnu] main 74116339a8 2/3: * elpa-packages (anzu): New package Date: Sun, 16 Jan 2022 18:47:34 -0500 Message-ID: References: <164145738158.2838.5769558384331859964@vcs2.savannah.gnu.org> <20220106082302.0A19CC0DA1E@vcs2.savannah.gnu.org> <87k0fdmbat.fsf@posteo.net> <87tueh3s2x.fsf@posteo.net> <87mtjvd10u.fsf@posteo.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="30094"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: Philip Kaludercic , emacs-devel@gnu.org To: Stefan Kangas Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Jan 17 00:48:45 2022 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 1n9FGO-0007eb-Ic for ged-emacs-devel@m.gmane-mx.org; Mon, 17 Jan 2022 00:48:44 +0100 Original-Received: from localhost ([::1]:33284 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1n9FGM-0002Qz-Lm for ged-emacs-devel@m.gmane-mx.org; Sun, 16 Jan 2022 18:48:42 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:39218) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n9FFN-0001kZ-TK for emacs-devel@gnu.org; Sun, 16 Jan 2022 18:47:41 -0500 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:50649) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n9FFL-0006lN-I8 for emacs-devel@gnu.org; Sun, 16 Jan 2022 18:47:41 -0500 Original-Received: from pmg2.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 1795680297; Sun, 16 Jan 2022 18:47:37 -0500 (EST) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 858B6802FF; Sun, 16 Jan 2022 18:47:35 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1642376855; bh=/42wuyzWthBw+D4TXXtd3EyJjgtmQf/2hww0/RGrpJw=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=hWsTwD1WMADE31wE+Q4AzmQGOa/7OyRu+mHUs2hMVBojjEnCyIjYl14MRS9J0fmpU EqV150MUEQfslP9IdbeSvq9iO2y/1kTUoErbPT2jJuLxpGQL+5VeNJcWYrgbOLE/+2 SQ9hx6e2SkgYFNaNV1/+J210iRRQFDKlxPCODhorIOw5vp4NSPrAWDTzrucZCogx8j pt0vVKeOWGxN9QbBM9uS0kogWLTJbgRYsYIw7XNXzGd9fXHBiAb3SZl7HHcnuD0Y6y SB9WDP+mBngjYJA3a3d8kIDpM5AaH05RYgC6cJWRmChiRWkPDmKWx2rcurq1dr9uUy ZgoQbG514h76A== Original-Received: from ceviche (unknown [216.154.30.173]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 464E01204E9; Sun, 16 Jan 2022 18:47:35 -0500 (EST) In-Reply-To: (Stefan Kangas's message of "Sun, 16 Jan 2022 14:32:47 -0800") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, 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.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" Xref: news.gmane.io gmane.emacs.devel:284852 Archived-At: >>> I am not against any efforts in this direction, of course, and I would >>> welcome any kind of initiative to do "community outreach" here. >> What do you mean by this? > I think it would be beneficial to think of ways to encourage people to > consider sending patches to Emacs or packages instead of writing up yet > another package. This could be in the form of posts on Reddit, IRC, > blogs, etc. I think in many cases it's illusory to expect this because it's easier for the users to write their own package custom-tailored to their specific case (oftentimes without realizing to what extent it's custom tailored) than to try and understand the generic code which has to take into account many more cases that they've never even dreamed of. But we should at least aim to make it so those users find it natural to send us a bug report showing describing the problem they encountered and the way they fixed it in their package. And also make sure that we then followup on it, to try and integrate a fix or the features, encouraging him to take part in it, without necessarily forcing him to do the work. > Personally, I would just do it. The new defaults are arguably just > better in those cases; no one will benefit from not having NonGNU ELPA > or trying to connect to an almost dead IRC network. Actually for `package-archives` I was thinking of doing it in `gnu-elpa-keyring-update`. Stefan