From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: GNU ELPA package discoverability Date: Sat, 23 May 2020 23:53:00 -0400 Message-ID: References: <35DBF02E-44D7-41E5-A217-7D6EC84ED221@icloud.com> <4e937898-ae46-710a-cbca-e452a1156fa1@yandex.ru> <2e630dc7-ba1d-e4c9-74b3-4da976db1e82@yandex.ru> Reply-To: rms@gnu.org Content-Type: text/plain; charset=Utf-8 Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="61228"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Emacs-devel@gnu.org To: Tim Cross Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun May 24 05:53:44 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 1jchhn-000FoX-Ao for ged-emacs-devel@m.gmane-mx.org; Sun, 24 May 2020 05:53:43 +0200 Original-Received: from localhost ([::1]:41958 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jchhm-0002Nt-C5 for ged-emacs-devel@m.gmane-mx.org; Sat, 23 May 2020 23:53:42 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:60210) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jchh9-0001U7-3P for Emacs-devel@gnu.org; Sat, 23 May 2020 23:53:03 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:54524) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jchh8-0001Oj-PE; Sat, 23 May 2020 23:53:02 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.82) (envelope-from ) id 1jchh6-0000La-W0; Sat, 23 May 2020 23:53:01 -0400 In-Reply-To: (message from Tim Cross on Sat, 23 May 2020 10:29:59 +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:251299 Archived-At: [[[ To any NSA and FBI agents reading my email: please consider ]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > You mention 'within the limits of our basic goals'. I don't think this has > been clearly defined The goal of the GNU Project is to develop the entirely-free operating system GNU and rid the world of nonfree software. It is a very ambitious goal, but we will push as far as we can, and we will not give up. > Something which will need to > be considered at this point is available maintenance resources. For > example, at a high level, having a stable and reliable archive of elisp > packages which are guaranteed to be GPL compliant and do not reference, > link-to or encourage the use of non-free software, but does not require > assignment of copyright to the FSF may be a worthy goal. However, if the > resources are not available to maintain such an archive and or > adding/updating code in the archive becomes a slow process because > approvals take too long (because there are insufficient resources), it > simply won't work. Since we will put less effort into checking and maintaining these packages than into GNU ELPA packages, we can surely handle more packages in it. How many more? It isn't useful to worry about. If this is the right approach, we will try it and see how many. > Document process workflow, the steps a developer needs to follow in order > to get their code into the appropriate place and how to manage bugs, Our usual approach is to try things, develop a practice that works, then write it down. Too much advance planning is a pain, and often it turns out not to be useful. Once we have real experience we can make a better plan. What we do need to write down are the criteria that would make a package acceptable for each repositor. We need that stated clearly so that we make consistent decisions. > developer should be confident [perse] now know[s] what is the appropriate > location for [per] code When would that question arise? In what scenario? -- Dr Richard Stallman Chief GNUisance of the GNU Project (https://gnu.org) Founder, Free Software Foundation (https://fsf.org) Internet Hall-of-Famer (https://internethalloffame.org)