From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jean Louis Newsgroups: gmane.emacs.help Subject: Re: NonGNU ELPA (was: Re: Fwd: How do I go about debugging my Elisp code?) Date: Sat, 15 Jan 2022 10:39:29 +0300 Message-ID: References: <87czku1hon.fsf@gnu.org> <87sftpx5ja.fsf_-_@zoho.eu> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="17108"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/2.1.5+104 (cd3a5c8) (2022-01-09) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Sat Jan 15 08:46:23 2022 Return-path: Envelope-to: geh-help-gnu-emacs@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 1n8dlW-0004Dq-NK for geh-help-gnu-emacs@m.gmane-mx.org; Sat, 15 Jan 2022 08:46:22 +0100 Original-Received: from localhost ([::1]:47354 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1n8dlV-0001rX-9k for geh-help-gnu-emacs@m.gmane-mx.org; Sat, 15 Jan 2022 02:46:21 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:60306) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n8diJ-0001AL-14 for help-gnu-emacs@gnu.org; Sat, 15 Jan 2022 02:43:03 -0500 Original-Received: from stw1.rcdrun.com ([217.170.207.13]:34711) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n8diG-0006z9-Rc for help-gnu-emacs@gnu.org; Sat, 15 Jan 2022 02:43:02 -0500 Original-Received: from localhost ([::ffff:41.210.145.184]) (AUTH: PLAIN admin, TLS: TLS1.3,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by stw1.rcdrun.com with ESMTPSA id 000000000005BED3.0000000061E27B02.000067DB; Sat, 15 Jan 2022 00:42:57 -0700 Mail-Followup-To: help-gnu-emacs@gnu.org Content-Disposition: inline In-Reply-To: <87sftpx5ja.fsf_-_@zoho.eu> Received-SPF: pass client-ip=217.170.207.13; envelope-from=bugs@gnu.support; helo=stw1.rcdrun.com X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:135317 Archived-At: * Emanuel Berg via Users list for the GNU Emacs text editor [2022-01-15 02:32]: > Tassilo Horn wrote: > > > But it would still be fine for NonGNU ELPA if it had > > a proper license statement (which is the actual missing > > part). > > What's this NonGNU ELPA I keep hearing about lately? Maybe winter sleep took you too long. NonGNU Emacs Lisp Package Archive is the answer to issues otherwise not handled on MELPA, for example, this repository will include any kind of packages but not steer users to vague licensed packages or proprietary software. More information: https://git.savannah.gnu.org/cgit/emacs/nongnu.git/plain/README.org * Guidance for accepting packages ** We don't ask for copyright assignments to include packages in NonGNU ELPA. ** The Emacs maintainers will decide what packages to put in NonGNU ELPA. ** If an ELisp package follows the rules below, we can add it to NonGNU ELPA if we want to. If the code doesn't follow them, we can change the code to follow them. We may also change the code in NonGNU ELPA for other reasons, technical or not. After all, it is free software. ** For practical reasons, we usually refrain from making local changes to NonGNU ELPA packages, in order to simplify integration of future changes from the upstream version. ** The package's developers don't have an obligation to maintain the NonGNU ELPA version, but we would like to invite them to do that, or to cooperate and coordinate with us in doing that. If you are the developer of a NonGNU ELPA package, or a package that might be added to NonGNU ELPA, and you're interested in maintaining it there, let's discuss it. ** Rules for a package to be acceptable in NonGNU ELPA *** A NonGNU ELPA package must display its copyright notices and license notices clearly on each nontrivial file. The notices do not have to follow the FSF conventions about their presentation. Software files need to carry a free license that is compatible with the GNU GPL version 3-or-later. Which licenses qualify is stated in https://gnu.org/licenses/license-list.html. Manuals need to be under a free license that is compatible with the GNU FDL version 1.4-or-later. Which licenses qualify is stated in https://gnu.org/licenses/license-list.html. All other documentation files, for users (manuals, help files, man pages, and so on), and for developers (program logic, change logs, and so on), can be under a license acceptable for manuals or a license acceptable for software files (see above). We can agree with the package developers to include documentation published under other free licenses. Trivial files of just a few lines don't need to state a copyright or a license. Normally we don't include material other than software or documentation, but we can agree with the developers to include specific material. If the material in question is an educational resource, then it can have a license compatible with GNU FDL version 1.4 or one of the free Creative Commons licenses (CC-BY-SA, CC-BY or CC-0), or another free license at our discretion. If the material is not an educational resource, it can instead be licensed under CC-BY-ND. *** The package need not follow the GNU Coding Standards or the GNU Maintainers Guide, except for a few specific points as stated below. *** The package must follow the rules in https://www.gnu.org/prep/standards/, node References. This means it may not refer users to any nonfree software or nonfree documentation, except as stated there. Leading users to run a program, and suggesting they run it, or depending on it to be installed, are forms of referring users to it. *** Aside from packages obtained from GNU ELPA and NonGNU ELPA, a package may not run code that it has fetched over the internet. In particular, the package may install other packages in GNU ELPA and NonGNU ELPA, but not any other software. We will consider exceptions to that rule, but we will need to consider them carefully, to make sure that the practices are safe for Emacs users, not just in one package but when used in many packages. Each time we approve such an exception, we will say so in comments in the package, with an explanation of our reasoning. *** The package must deliver its full functionality and convenience on a completely free platform based on the GNU operating system (in practice, GNU/Linux), working exclusively with other free software. Otherwise, it would act as an inducement to install nonfree systems or other nonfree software, and that would work against our cause. However, as an exception it is ok for a package to provide, on some non-GNU operating systems, features that the rest of Emacs (plus GNU ELPA and NonGNU ELPA) already supports on GNU. This is a moral issue. See https://www.gnu.org/prep/standards/, node System Portability. The reason for this rule is that at no time, in no way, should a NonGNU ELPA package put users who defend their freedom at a disadvantage compared with those who surrender their freedom. *** The package may communicate with a class of remote services, either using a standard interface or using an ad-hoc interface for each service, or a combination, *provided* that these services' jobs consist of either communication or lookup of published data. The package may not use remote services to do the user's own computational processing. "Your own computational processing" means anything you could _in principle_ do in your own computers by installing and running suitable software, without communicating with any other computers. *** A general Savannah rule about advertisements In general, you may not advertise anything commercial with material in the NonGNU ELPA package or this repository. However, as exceptions, you can point people to commercial support offerings for the package, and you can mention fan items that you sell directly to the users. -- Jean Take action in Free Software Foundation campaigns: https://www.fsf.org/campaigns In support of Richard M. Stallman https://stallmansupport.org/