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: Mon, 25 May 2020 18:20:15 +0300 Message-ID: <831rn8vy6o.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> Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="67597"; 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 Mon May 25 17:22:34 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 1jdEvy-000HTw-6m for ged-emacs-devel@m.gmane-mx.org; Mon, 25 May 2020 17:22:34 +0200 Original-Received: from localhost ([::1]:36868 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jdEvx-00069i-9w for ged-emacs-devel@m.gmane-mx.org; Mon, 25 May 2020 11:22:33 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:56002) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jdEtl-00051w-JZ for Emacs-devel@gnu.org; Mon, 25 May 2020 11:20:17 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:50932) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jdEtl-00022d-8m; Mon, 25 May 2020 11:20:17 -0400 Original-Received: from [176.228.60.248] (port=4840 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jdEtY-0006s5-9h; Mon, 25 May 2020 11:20:08 -0400 In-Reply-To: (message from Tim Cross on Mon, 25 May 2020 10:21:47 +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:251370 Archived-At: > From: Tim Cross > Date: Mon, 25 May 2020 10:21:47 +1000 > Cc: Richard Stallman , Emacs developers > > Aren't these questions answered in ELPA's README? > > No it doesn't. It does answer some of them, but not others (and is probably not > the right place to answer some of them). > > The ELPA README is certainly a start with respect to basic workflow. Information > which it lacks that a new developer may want to know or which needs > clarification includes > > - Who can get push permission to the ELPA git repository? > - How do you request push permission? > - The README is a little weak on process when you don't have push permission > - The instructions re: email to emacs-devel for package developers who do not > have push permission does not indicate how to provide the package > sources/updates. It says that someone will push it for you, but if you > don't have push permission to the git repo, how do you get your code in there > to begin with? So basically what's missing is the write access issue. That should be a single sentence: we don't have ELPA write access, only access to the entire Emacs repository, so they need to request membership in the Emacs project. > Questions about what can/should go into ELPA, what should be included in Emacs > core and what cannot go into ELPA are not addressed at all (the README is > probably not the right place for this information) It's quite expected that this is not described, because we are still arguing about that.