From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: GNU ELPA package discoverability Date: Wed, 27 May 2020 05:40:32 +0300 Message-ID: <83eer6t80v.fsf@gnu.org> References: <35DBF02E-44D7-41E5-A217-7D6EC84ED221@icloud.com> <4e937898-ae46-710a-cbca-e452a1156fa1@yandex.ru> <2e630dc7-ba1d-e4c9-74b3-4da976db1e82@yandex.ru> <83blmdxus4.fsf@gnu.org> <831rn8vy6o.fsf@gnu.org> <83lflevju7.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="26706"; mail-complaints-to="usenet@ciao.gmane.io" Cc: rms@gnu.org, Emacs-devel@gnu.org To: Tim Cross Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed May 27 04:41:40 2020 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 1jdm0h-0006s9-Tg for ged-emacs-devel@m.gmane-mx.org; Wed, 27 May 2020 04:41:39 +0200 Original-Received: from localhost ([::1]:45294 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jdm0g-0001wl-U7 for ged-emacs-devel@m.gmane-mx.org; Tue, 26 May 2020 22:41:38 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:34094) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jdlzy-0001XK-2u for Emacs-devel@gnu.org; Tue, 26 May 2020 22:40:54 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:57553) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jdlzx-0004Md-QE; Tue, 26 May 2020 22:40:53 -0400 Original-Received: from [176.228.60.248] (port=4360 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jdlzo-0000oZ-Kg; Tue, 26 May 2020 22:40:44 -0400 In-Reply-To: (message from Tim Cross on Wed, 27 May 2020 11:06:37 +1000) 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:251485 Archived-At: > From: Tim Cross > Date: Wed, 27 May 2020 11:06:37 +1000 > Cc: Richard Stallman , Emacs developers > > > That would certainly be a good start. However, is that a maintainable approach. > > That's what we have now. IMO information for contributors should > reflect the present state of affairs. > > Except it isn't. There is nothing in the README about how to obtain write/push rights to the repository or that > it is the same rights as you need to add code to the Emacs repository. Which I agreed should be added. What is your point in reiterating that? The above was in response to a different argument: that describing how to get write access now is in your opinion not TRT, because that might change in the future. Let's keep the argument going forward, not backward or in circles, please. > If and when the situation changes, we will update the information. It > is not useful to worry about issues that didn't yet materialize, and > are anybody's guess when they will. > > I disagree with this approach. All it does is maintain the status quo. It's okay to disagree. Status quo is what needs to be described, because documentation needs to be accurate. > As demonstrated by this thread and others, the current situation is not working. GNU ELPA has relatively few > packages. Because the procedure to get write access is not described? > To make it maintainable, we need to design a solution which minimises the time burden on those > few volunteers prepared to put in the effort. Improvements and change is something which needs to be > driven. Talking about what "we need" to do doesn't get anything done, unfortunately. Frankly, that's my summary of everything you wrote on the subject till now. It helps nothing to lecture what needs to be done when no one is doing it. > I don't know. A proposal was put on the table, but some of the > important stakeholders didn't yet respond to it. > > How long ago? Perhaps that proposal needs to be res erected? Any proposal which is just thrown out into > the ether is rarely going to achieve anything. It usually needs a champion that will drive the proposal until an > eventual resolution (which may be for or against - either are valid and provide a means to move forward). > > Do you have a copy of this proposal and are you able to share it? It's all in the archives, please look there. It wasn't long ago, just a couple of weeks, so it should be no problem to look it up.