Hey folks!
So a bug came up at today's blocker review meeting: https://bugzilla.redhat.com/show_bug.cgi?id=2106868
it takes a minute to parse, but the tl;dr is that right now in Fedora 37, you can't go to https://extensions.gnome.org and install extensions.
We agreed that it doesn't violate any existing release criteria, but to me, this is actually kind of a significant problem. Anecdotally, I get the impression that a lot of our Workstation users do use extensions, and not being able to easily install them on a fresh install would be a big problem for them, and make us look pretty bad.
We have a handful of extensions packaged, though I'm not sure how well they're kept up to date. Aside from those, I don't know of any other really practical way for regular users to install extensions besides https://extensions.gnome.org . Is there one?
Assuming for now that there isn't, I'm gonna propose this as a Final release criterion to see how people feel about it, to come after "Default panel functionality":
#####
=== GNOME extensions ===
On Fedora Workstation, it must be possible to install and remove extensions by visiting https://extensions.gnome.org in the default web browser, after installing the required browser extension.
#####
Do folks think this is important enough to block Final release on? Desktop folks, do you consider it "supportable"?
Thanks!
Might be a better idea to package the third party "extensions manager" application as then you dont even need to visit that page and can eventually have browsers delivered in a flatpak.
On Mon, Sep 12, 2022 at 3:35 PM Adam Williamson adamwill@fedoraproject.org wrote:
Hey folks!
So a bug came up at today's blocker review meeting: https://bugzilla.redhat.com/show_bug.cgi?id=2106868
it takes a minute to parse, but the tl;dr is that right now in Fedora 37, you can't go to https://extensions.gnome.org and install extensions.
We agreed that it doesn't violate any existing release criteria, but to me, this is actually kind of a significant problem. Anecdotally, I get the impression that a lot of our Workstation users do use extensions, and not being able to easily install them on a fresh install would be a big problem for them, and make us look pretty bad.
We have a handful of extensions packaged, though I'm not sure how well they're kept up to date. Aside from those, I don't know of any other really practical way for regular users to install extensions besides https://extensions.gnome.org . Is there one?
Assuming for now that there isn't, I'm gonna propose this as a Final release criterion to see how people feel about it, to come after "Default panel functionality":
#####
=== GNOME extensions ===
On Fedora Workstation, it must be possible to install and remove extensions by visiting https://extensions.gnome.org in the default web browser, after installing the required browser extension.
#####
Do folks think this is important enough to block Final release on? Desktop folks, do you consider it "supportable"?
I think it's important to block the final release on. And as a user, I can't use GNOME without working extensions, so it *must* be supportable by us. So if we can't do it, we should block the release.
On 9/12/22 3:35 PM, Adam Williamson wrote:
We have a handful of extensions packaged, though I'm not sure how well they're kept up to date. Aside from those, I don't know of any other really practical way for regular users to install extensions besides https://extensions.gnome.org . Is there one?
My uers and I need Gnome extensions.
The ones used here are in the Fedora 37 repo, that's where I get them, but there are some that won't run. The Extensions app. says they are not compatable with the current version of Gnome. I've looked into this for the Extension Freon. Freon actually queries the Gnome verion and compares it to the version in a file that comes with the extensiion. I've been able to fix the issue for F36 with:
sudo sed -i 's/40.0/42.2/g' /usr/share/gnome-shell/extensions/freon@UshakovVasilii_Github.yahoo.com/metadata.json
I've been waiting to see what the Gnome version in F37 will be.
This may be the problem with the others that won't run, but I haven't had a chance to look into that yet.
I think the intension of this is to ensure that someone has tested the extension to be sure it works then they put the current Gnome version in the file to enable it to work. Of course this little patch bypasses that assurance.
Have a Great Day!
Pat tablepc
Assuming for now that there isn't, I'm gonna propose this as a Final release criterion to see how people feel about it, to come after "Default panel functionality":
#####
=== GNOME extensions ===
On Fedora Workstation, it must be possible to install and remove extensions by visiting https://extensions.gnome.org in the default web browser, after installing the required browser extension.
#####
Do folks think this is important enough to block Final release on? Desktop folks, do you consider it "supportable"?
Thanks!
We have less than 10% of the extensions available on extensions.gnome.org packaged in Fedora, we can't hope to rely on our packages for extension updates. There are numerous threads on ask.fp.o from people who had trouble with system upgrades because of the problematic extension update mechanism, but at least these issues were solvable. Taking away that mechanism during a system upgrade is going to wreak havoc. I fully agree with Neal on this, we block the release until it gets fixed.
On Mon, Sep 12, 2022 at 3:35 PM Adam Williamson adamwill@fedoraproject.org wrote:
=== GNOME extensions ===
On Fedora Workstation, it must be possible to install and remove extensions by visiting https://extensions.gnome.org in the default web browser, after installing the required browser extension.
#####
Do folks think this is important enough to block Final release on?
Assuming the desktop folks don't say "OMG there's no way we could handle this", then I'm on board with making this a final criterion. This is one of those "we'll get dragged in reviews if it doesn't work" sorts of things.
The wording looks good to me. I'm trying to think of an escape hatch we can give ourselves if it goes particularly sideways at some point, but maybe the "difficult to fix" exception would be good enough.
I would make the criterion a little more generic than that. E.g. we don't want to block Fedora release if https://extensions.gnome.org/ goes down due to a server problem, or if GNOME decides to change the way extension installation works.
On Tue, 2022-09-13 at 09:00 -0500, Michael Catanzaro wrote:
I would make the criterion a little more generic than that. E.g. we don't want to block Fedora release if https://extensions.gnome.org/ goes down due to a server problem, or if GNOME decides to change the way extension installation works.
For the first part, we can add a footnote clarifying that we expect the site to be working. For the second, if that happens, we can just change the criterion. It's only text.
I'm not sure I can write it any more generically without losing all meaning or unexpectedly broadening the scope. For instance if we just say it must be possible to install extensions, what does that *mean*? Is it OK if you can only do it by hacking around with gsettings values manually? Or on the other end of the scale, does it require that *any possible method* of installing extensions works? That just feels too vague to me.
Do you have a suggestion for improved wording?
I believe the Working Group doesn't want to block on shell extensions. We will fix it, though.
On Mon, Sep 12, 2022, at 3:35 PM, Adam Williamson wrote:
Hey folks!
So a bug came up at today's blocker review meeting: https://bugzilla.redhat.com/show_bug.cgi?id=2106868
it takes a minute to parse, but the tl;dr is that right now in Fedora 37, you can't go to https://extensions.gnome.org and install extensions.
We agreed that it doesn't violate any existing release criteria, but to me, this is actually kind of a significant problem. Anecdotally, I get the impression that a lot of our Workstation users do use extensions, and not being able to easily install them on a fresh install would be a big problem for them, and make us look pretty bad.
We have a handful of extensions packaged, though I'm not sure how well they're kept up to date. Aside from those, I don't know of any other really practical way for regular users to install extensions besides https://extensions.gnome.org . Is there one?
Assuming for now that there isn't, I'm gonna propose this as a Final release criterion to see how people feel about it, to come after "Default panel functionality":
#####
=== GNOME extensions ===
On Fedora Workstation, it must be possible to install and remove extensions by visiting https://extensions.gnome.org in the default web browser, after installing the required browser extension.
#####
Do folks think this is important enough to block Final release on? Desktop folks, do you consider it "supportable"?
Discussed at the meeting today, and we definitely want this to work, and appreciate the bug report. We expect we'll be able to get it fixed for release. However, there's reluctance to broaden the scope of the criteria because our influence has limits, including the infrastructure aspects of extensions that we can't control (such as the web site itself). So we'd like to see this covered under existing criterion.
On Tue, 2022-09-13 at 15:42 -0400, Chris Murphy wrote:
Discussed at the meeting today, and we definitely want this to work, and appreciate the bug report. We expect we'll be able to get it fixed for release. However, there's reluctance to broaden the scope of the criteria because our influence has limits, including the infrastructure aspects of extensions that we can't control (such as the web site itself). So we'd like to see this covered under existing criterion.
There is no relevant existing criterion.
desktop@lists.fedoraproject.org