From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: Oleh Krehel <ohwoeowho@gmail.com>,
Artur Malabarba <bruce.connor.am@gmail.com>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: Adding a few more finder keywords
Date: Tue, 09 Jun 2015 13:39:51 +0900 [thread overview]
Message-ID: <873821xzon.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <jwvr3pludlz.fsf-monnier+emacs@gnu.org>
Stefan Monnier writes:
> We could decide that the specific keywords are unwanted, tho.
An "unwanted" keyword doesn't exist though. Somebody wanted it or it
wasn't in Keywords: in the first place. And although every human is
unique, very few humans are so unique that they'll choose a keyword
that nobody else would use to look up packages.
So I think what you mean by "unwanted" is mostly "redundant (because a
synonym)". It seems to me that
1. There *should* be a list of "recommended keywords" which package
maintainers can easily access for reference when choosing keywords
to specify for their packages and users can refer to get an idea
of the keywords maintainers are likely to use.
2. There *should* be a database of synonyms of recommended keywords
for use by maintainers to discover recommended keywords, and for
*finder* to use in user searches for keywords. Finder should
probably divide its report into exact matches for the user's
keyword and matches discovered via synonyms.
The schema for this database is unclear to me. Should there be a
"similarity" measure to indicate how synonymous two keywords are?
(Probably a YAGNI.) Should the primary key of the database be
restricted to recommended keywords, or perhaps just be the most
frequently used of a synonym group? (See point 3 below.)
3. There should be a tool to walk the libraries producing a Pareto
distribution of keywords. Those at the top of the distribution
would be excellent candidates for the "recommended" list (but
beware, it's quite possible that two popular keywords could be
synonyms!). Those at the bottom would be candidates for addition
to the database of synonyms and replacement with a recommended
keyword.
Probably this tool only needs to be run at release time, and the
distribution database could be included in etc.
There's no need to be fascist about keyword maintenance and
pruning low-frequency keywords that have synonyms, either. There
is quite some incentive for maintainers to use user-discoverable
(ie, recommended) keywords, if you provide the tools so that they
can find them easily.
next prev parent reply other threads:[~2015-06-09 4:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-25 16:59 Adding a few more finder keywords Artur Malabarba
2015-04-25 18:51 ` Drew Adams
2015-04-25 19:23 ` Artur Malabarba
2015-06-08 14:56 ` Oleh Krehel
2015-06-08 15:37 ` Drew Adams
2015-06-08 15:43 ` Oleh Krehel
2015-06-08 16:20 ` Drew Adams
2015-06-08 16:15 ` Artur Malabarba
2015-06-08 16:19 ` Artur Malabarba
2015-06-08 16:27 ` Drew Adams
2015-06-08 20:59 ` Stefan Monnier
2015-06-09 4:39 ` Stephen J. Turnbull [this message]
2015-06-09 6:52 ` Oleh Krehel
2015-06-09 8:02 ` Artur Malabarba
2015-06-09 8:54 ` Oleh Krehel
2015-06-09 14:22 ` Drew Adams
2015-06-09 14:47 ` Oleh Krehel
2015-06-09 16:05 ` Drew Adams
2015-06-09 16:47 ` Oleh Krehel
2015-06-09 17:19 ` Drew Adams
2015-06-09 16:08 ` Stephen J. Turnbull
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=873821xzon.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=bruce.connor.am@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
--cc=ohwoeowho@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.