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: ELPA policy (was: Imports / inclusion of s.el into Emacs) Date: Sat, 09 May 2020 14:11:42 +0300 Message-ID: <83o8qxfjm9.fsf@gnu.org> References: <0c88192c-3c33-46ed-95cb-b4c6928016e3@default> <83zhaij4qn.fsf@gnu.org> <838si1h7m5.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="67374"; mail-complaints-to="usenet@ciao.gmane.io" Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Philippe Vaucher Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat May 09 13:12:23 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 1jXNP4-000HQz-HJ for ged-emacs-devel@m.gmane-mx.org; Sat, 09 May 2020 13:12:22 +0200 Original-Received: from localhost ([::1]:52030 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jXNP3-0004yZ-Gm for ged-emacs-devel@m.gmane-mx.org; Sat, 09 May 2020 07:12:21 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:52114) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jXNOb-0004Yx-5H for emacs-devel@gnu.org; Sat, 09 May 2020 07:11:53 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:50421) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jXNOa-0000Gt-SS; Sat, 09 May 2020 07:11:52 -0400 Original-Received: from [176.228.60.248] (port=2268 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jXNOZ-00085d-RS; Sat, 09 May 2020 07:11:52 -0400 In-Reply-To: (message from Philippe Vaucher on Sat, 9 May 2020 12:42:01 +0200) 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:249399 Archived-At: > From: Philippe Vaucher > Date: Sat, 9 May 2020 12:42:01 +0200 > Cc: Stefan Monnier , > Emacs developers > > > I'd prefer to start from our CONTRIBUTE, since (AFAIU) GNU ELPA is > > supposed to be part of the Emacs project. Commonality of requirements > > is important IMO to make it easier to contribute a package: we could > > then decide relatively easily whether to add the package to core or to > > ELPA. > > Sure, but from a quick look at it CONTRIBUTE lacks a lot of what > https://github.com/melpa/melpa/blob/master/CONTRIBUTING.org#making-your-package-ready-for-inclusion > proposes and would make sense for inclusion in ELPA. I'll copy the > relevant parts of that section here: I think you are missing my point. I didn't mean the details on the level you seem to focus, I meant the deviations from our requirements for code accepted into Emacs. I have comments on your specific points (most of them are in ELPA's README), but I see no reason to start a tangent, because IMO much more important issues are at stake.