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, 20 May 2020 17:23:06 +0300 Message-ID: <83k1167kj9.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> Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="32891"; 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 20 16:30:05 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 1jbPjR-0008PK-SS for ged-emacs-devel@m.gmane-mx.org; Wed, 20 May 2020 16:30:05 +0200 Original-Received: from localhost ([::1]:38216 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jbPjQ-00014K-UK for ged-emacs-devel@m.gmane-mx.org; Wed, 20 May 2020 10:30:04 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58338) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jbPcx-0007Bp-Cn for Emacs-devel@gnu.org; Wed, 20 May 2020 10:23:23 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:50172) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jbPcx-0006Ka-0c; Wed, 20 May 2020 10:23:23 -0400 Original-Received: from [176.228.60.248] (port=2061 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jbPcf-000133-CD; Wed, 20 May 2020 10:23:06 -0400 In-Reply-To: (message from Tim Cross on Wed, 20 May 2020 10:28:42 +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:251053 Archived-At: > From: Tim Cross > Date: Wed, 20 May 2020 10:28:42 +1000 > Cc: Emacs developers > > I think the following might help > > - Define the rationale and objectives that underpins ELPA. Forget about historical context and focus on > current context. > > - Define what should be and what should not be included in ELPA. This should be based on objective criteria > > - Define an ELPA custodian responsible for deciding whether a package should or should not be > added/removed from ELPA. This custodian should be able to appoint a team of people who can assist. > There will probably need to be some appeal process as well, but I'd keep it simple to begin with. > > - Ensure the custodian is supported and is seen as the 'official voice'. Any ideas, concerns or need for > clarification re: policy etc should first be discussed with the ELPA custodian (they may delegate some of the > work, but announcements, decisions etc should come from them). Note that this does not mean they are the > decision maker or benevolent dictator - they are just the spokesperson and what they say can be take as the > official position. > > - Develop guidelines on when a package or library should be included in core Emacs i.e. is in the Emacs > source code distribution and when it should be in ELPA. > > - Decide if we really need the ability to have some sort of category or split i.e the 'blessed' and 'neutral' > packages (I'm not convinced this is a good idea). Sounds like a good plan, thanks.