unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Artur Malabarba <bruce.connor.am@gmail.com>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Improving browsing and discoverability in the Packages Menu
Date: Sun, 15 Feb 2015 22:38:13 +0000	[thread overview]
Message-ID: <CAAdUY-KOPrBuKdwwaZ7UPi_WBmfpjw1s8zByLXYf3DB7W4Dyvg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1060 bytes --]

The package menu is fantastic when you know what you're looking for. You
just search for the package name or for a phrase, and you're likely to find
it.

It's not that great when you just want to browse, specially if you have
Melpa and Marmalade configured, simply because the menu is overwhelming. A
few items that stand out to me:

1. The package list is ginormous and growing.
2. There are duplicate entries galore.
3. There's no useful sense of categories. (we have keywords,but see below).
4. Are there other points that people feel can be improved?

I can see myself writing something to improve 2.

Any solution for 3 would also be a solution for 1, but I'm not sure what
that would be.

Also regarding 3: We have keywords but they are not the same thing as
categories.
I'm not saying we should come up with yet another classification, but I'm
saying that keywords need some serious work. It's not obvious to the user
what keywords are available or how to browse them. And they're sort of all
over the place with a lot of overlap.

Cheers to all,
Artur

[-- Attachment #2: Type: text/html, Size: 1250 bytes --]

             reply	other threads:[~2015-02-15 22:38 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-15 22:38 Artur Malabarba [this message]
2015-02-16  2:25 ` Improving browsing and discoverability in the Packages Menu Stefan Monnier
2015-02-18 16:23 ` raman
2015-04-18 11:26   ` Ted Zlatanov
2015-04-18 13:25     ` Artur Malabarba
2015-04-18 13:25     ` Artur Malabarba
2015-04-18 21:11     ` raman
2015-04-18 23:05       ` Ted Zlatanov
2015-04-19  1:20         ` Alexis
2015-04-19  3:16           ` Stefan Monnier
2015-04-19  4:03             ` Alexis
2015-04-19 16:14             ` raman
2015-04-20  1:57               ` Stefan Monnier
2015-04-19 16:12         ` raman
2015-04-20  1:22           ` Ted Zlatanov
2015-04-20  9:02             ` Artur Malabarba
2015-04-20 15:18             ` raman
2015-04-20 15:23               ` Drew Adams
2015-04-21  0:20                 ` raman
2015-04-21  1:07                   ` Drew Adams
2015-04-19  2:59 ` Eric Abrahamsen
2015-04-19 14:58   ` Drew Adams
2015-04-20  8:38     ` Eric Abrahamsen
2015-04-20  9:26       ` Artur Malabarba
2015-04-20 10:17         ` Alexis
2015-04-20 11:30           ` Artur Malabarba
2015-04-20 14:32             ` Drew Adams
2015-04-20 17:32               ` Artur Malabarba
2015-04-20 18:17                 ` Drew Adams
2015-04-20 19:49                   ` Artur Malabarba
2015-04-20 20:30                     ` Drew Adams
2015-04-21  4:05                       ` Tassilo Horn
2015-04-21  5:25                         ` Drew Adams
2015-04-21  6:52                           ` Tassilo Horn
2015-04-21  9:04                             ` Eric Abrahamsen
2015-04-21 15:44                             ` Drew Adams
2015-04-20 14:03           ` Eric Abrahamsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAAdUY-KOPrBuKdwwaZ7UPi_WBmfpjw1s8zByLXYf3DB7W4Dyvg@mail.gmail.com \
    --to=bruce.connor.am@gmail.com \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).