[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Improving browsing and discoverability in the Packages Menu

From: Alexis
Subject: Re: Improving browsing and discoverability in the Packages Menu
Date: Mon, 20 Apr 2015 20:17:24 +1000

Artur Malabarba <address@hidden> writes:

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?

Hmm .... i'm not sure how practical that last bit is. For example: should "vcard" be added as an 'official' keyword? (i currently include it in the list of keywords for `org-vcard', the other two being "outline" and "org".) Should i instead replace the "vcard" keyword with "contacts", given that people could plausibly find `org-vcard' via searching package names instead of keywords for the term 'vcard', but currently wouldn't find it were they thinking in terms of "contacts management"? Who would be the person or people making the decision on whether a keyword should be added, modified or removed? Might such a process result in emacs-devel being flooded with interminable ontological bikeshedding?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]