From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Artur Malabarba Newsgroups: gmane.emacs.devel Subject: Re: Improving browsing and discoverability in the Packages Menu Date: Mon, 20 Apr 2015 10:26:01 +0100 Message-ID: References: <871tjgj010.fsf@ericabrahamsen.net> <7b3b0d19-01d4-4f97-b85e-19383bee5605@default> <87twwbdwjd.fsf@ericabrahamsen.net> Reply-To: bruce.connor.am@gmail.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11c38750b24f70051424849a X-Trace: ger.gmane.org 1429521980 13597 80.91.229.3 (20 Apr 2015 09:26:20 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 20 Apr 2015 09:26:20 +0000 (UTC) Cc: emacs-devel To: Eric Abrahamsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Apr 20 11:26:19 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Yk7y6-0005SK-AZ for ged-emacs-devel@m.gmane.org; Mon, 20 Apr 2015 11:26:18 +0200 Original-Received: from localhost ([::1]:52526 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yk7y5-0007kl-LM for ged-emacs-devel@m.gmane.org; Mon, 20 Apr 2015 05:26:17 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57400) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yk7xr-0007kY-6e for emacs-devel@gnu.org; Mon, 20 Apr 2015 05:26:04 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Yk7xq-0004pQ-CJ for emacs-devel@gnu.org; Mon, 20 Apr 2015 05:26:03 -0400 Original-Received: from mail-la0-x22c.google.com ([2a00:1450:4010:c03::22c]:32878) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yk7xq-0004pJ-3o for emacs-devel@gnu.org; Mon, 20 Apr 2015 05:26:02 -0400 Original-Received: by layy10 with SMTP id y10so122101245lay.0 for ; Mon, 20 Apr 2015 02:26:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=JqgFGIYoEk5G3iTx50erXe1yJgzlclY+6H3/ZS2Ktg0=; b=03rDciTEk6O0L3XgPlUYKK/1+egT6rB0VihDCgOjaqWyiUDzR7AJiwswcFAuKIU+pj 4WP/JhGPlWGxaF5qqJD2txKA99fzSivNy7uKSq113CrJtuow4gdoYG0ptvFkWShGUmKh YOQPklI6qM0ICEZhFlSstgqAYiWRvq2UxX5vbH/8XyopAnruKoVG0CQbS2QHqTh1oLQz Vw1fAOS4tT0Q8ljPY3F2qJEOEpvZnIHCMw4rxIpq8ryINpFgdt91GhiMaT5xX6wiLFBr rNeyHkgb0rm4hwZn207V3BxrBCPT7YisyoLAz12OHknrMXofEQADXizMPro6LJHwu3zL LO2A== X-Received: by 10.112.200.230 with SMTP id jv6mr14864630lbc.21.1429521961208; Mon, 20 Apr 2015 02:26:01 -0700 (PDT) Original-Received: by 10.25.150.1 with HTTP; Mon, 20 Apr 2015 02:26:01 -0700 (PDT) Original-Received: by 10.25.150.1 with HTTP; Mon, 20 Apr 2015 02:26:01 -0700 (PDT) In-Reply-To: <87twwbdwjd.fsf@ericabrahamsen.net> X-Google-Sender-Auth: ukHT7alpp-oxUH3V_yNDmAWJK6M X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4010:c03::22c X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:185693 Archived-At: --001a11c38750b24f70051424849a Content-Type: text/plain; charset=UTF-8 > On the other hand, I want to be able to search for > packages related to sending email messages from Emacs (for instance), > and know that I'm not missing packages because their author tagged them > as "email" instead of "mail". Agreed. This is precisely why the current state is a mess. > Maybe just expand the canonical list of curated keywords, then let > package authors add their own on top of that? This by itself will take a very long time, if ever, to have any effect. It would have to be coupled with something else. For instance, there could be a compiler warning if the package has unknown keywords. This wouldn't prevent the keyword from working, but it would inform the developer to either change the keyword or ask us to add it in. Is that too much? --001a11c38750b24f70051424849a Content-Type: text/html; charset=UTF-8


> On the other hand, I want to be able to search for
> packages related to sending email messages from Emacs (for instance),
> and know that I'm not missing packages because their author tagged them
> as "email" instead of "mail".

Agreed. This is precisely why the current state is a mess.

> Maybe just expand the canonical list of curated keywords, then let
> package authors add their own on top of that?

This by itself will take a very long time, if ever, to have any effect. It would have to be coupled with something else.
For instance, there could be a compiler warning if the package has unknown keywords. This wouldn't prevent the keyword from working, but it would inform the developer to either change the keyword or ask us to add it in. Is that too much?

--001a11c38750b24f70051424849a--