Bug 672008 – allow searching by tags

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 672008 - allow searching by tags


Summary:	allow searching by tags


Status:	RESOLVED OBSOLETE

Product:	website
Classification:	Infrastructure
Component:	extensions.gnome.org
Version:	current
Hardware:	Other Linux

Importance:	Normal enhancement
Target Milestone:	---
Assigned To:	Shell extensions maintainer(s)
QA Contact:	Shell extensions maintainer(s)

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2012-03-13 17:14 UTC by Stephen Gallagher
Modified:	2018-09-24 10:22 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Stephen Gallagher 2012-03-13 17:14:00 UTC

I originally posted my concerns to the fedora-devel mailing list[1]. I have some suggestions on how to improve the usability of extensions.gnome.org.

The website should support tags (submittable by the extension writer or requested by users). Tags could be general or specific (e.g. 'notifications' or 'pidgin', resp.). It should then be possible to filter the list of visible extensions by these tags, so if I only want to see extensions having to do with e.g. 'pidgin' and 'audio-notification', I can narrow my search that way.

This should be tied into the search box, but ideally it would also be possible to construct a set of tags (ANDed) to view.


[1]http://lists.fedoraproject.org/pipermail/devel/2012-March/163899.html

Comment 1 Dmitri Naumov 2012-06-02 23:37:54 UTC

Big +1 for this. Described tag system (or even simple categories filter) would significantly improve usability.

Comment 2 GNOME Infrastructure Team 2018-09-24 10:22:00 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/Infrastructure/Websites/issues/73.