From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: =?utf-8?Q?=C3=93scar_Fuentes?= Newsgroups: gmane.emacs.help Subject: Re: What is the policy for moving a feature into core or not? Date: Sat, 14 Dec 2019 15:05:38 +0100 Message-ID: <87woaz9f4d.fsf@telefonica.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="237145"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: "help-gnu-emacs@gnu.org" To: ndame Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sat Dec 14 22:13:22 2019 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1igEj4-000zby-E3 for geh-help-gnu-emacs@m.gmane.org; Sat, 14 Dec 2019 22:13:22 +0100 Original-Received: from localhost ([::1]:33068 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1igEj3-0005pD-70 for geh-help-gnu-emacs@m.gmane.org; Sat, 14 Dec 2019 16:13:21 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:56066) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1igEir-0005mo-9z for help-gnu-emacs@gnu.org; Sat, 14 Dec 2019 16:13:10 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1igEiq-0005mk-2h for help-gnu-emacs@gnu.org; Sat, 14 Dec 2019 16:13:09 -0500 Original-Received: from relayout03.e.movistar.es ([86.109.101.203]:21963 helo=relayout03-redir.e.movistar.es) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1igEip-0005ab-Rt for help-gnu-emacs@gnu.org; Sat, 14 Dec 2019 16:13:08 -0500 Original-Received: from sky (132.red-79-151-140.dynamicip.rima-tde.net [79.151.140.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: 981711563@telefonica.net) by relayout03.e.movistar.es (Postfix) with ESMTPSA id 47Zq7R5MCszMlW4; Sat, 14 Dec 2019 15:05:39 +0100 (CET) In-Reply-To: (ndame's message of "Tue, 30 Jul 2019 06:20:34 +0000 (GMT)") X-CTCH-Score: 0.000 X-CTCH-ScoreCust: 0.000 X-TnetOut-Country: IP: 79.151.140.132 | Country: ES X-TnetOut-Information: AntiSPAM and AntiVIRUS on relayout03 X-TnetOut-MsgID: 47Zq7R5MCszMlW4.A4616 X-TnetOut-SpamCheck: no es spam, Unknown X-TnetOut-From: ofv@wanadoo.es X-TnetOut-Watermark: 1576937141.06565@qyatJtlAGJFF5821zokngg X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 86.109.101.203 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.23 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.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:122047 Archived-At: ndame writes: > Let's take the kill ring. It's a central piece of emacs, yet I don't see = any keyboard > based solution built in to browse and search the kill ring. M-y is extrem= ely basic. There is > a menu, but it's mouse based, inefficient. > > There are external packages, of course, but I wonder if there should be a= builtin way to > navigate and search the kill ring from the keyboard. By builtin I mean a = package available > from at least elpa. Elpa has undo-tree. > Is there a current policy which governs what features are integrated into= the core (elpa)=C2=A0 > and what features are left to outside developers? Elpa is not core. Anyone can contribute a package to Elpa as long as it meets certain quality and legal requirements. It is relatively easy and painless. Contributions to core Emacs must meet much more strict quality and usability requirements. Typically, long discussions ensue even for apparently trivial details. BTW, I'm not an Emacs maintainer. This is what I learnt after years of observing the community.