Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionMatthias Clasen
2015-04-02 12:26:28 UTC
We should include a small number of "popular" extensions ("top five") in the extensions package so people can use them in a supported way. The ones that I have seen suggested are:
- topicons
- dash-to-dock
- frippery-icons
- weather
(In reply to Matthias Clasen from comment #0)
> We should include a small number of "popular" extensions ("top five") in the
> extensions package so people can use them in a supported way.
I'd like to keep the (upstream) gnome-shell-extensions module about
(1) classic mode
(2) stuff that is useful to GNOME, but not general enough to be built-in
(screenshot-window-sizer to resize windows for AppData screenshots)
(3) possibly UI experiments we consider for core, but want to evaluate first
(no precedents here)
There is currently also
(0) random stuff that was written before extensions.gnome.org was created
but I'm very wary of adding anything else in that category (however there have been several removals there over the last couple of releases). Not least because there's a good chance that an extension will be worse off, because the original authors stops feeling responsible, and all I do is quickly check for obvious breakages before doing a release ...
Of course packaging extensions downstream (like the background-logo one) is something else entirely, no objections there from my side ...
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2015-2216.html
We should include a small number of "popular" extensions ("top five") in the extensions package so people can use them in a supported way. The ones that I have seen suggested are: - topicons - dash-to-dock - frippery-icons - weather