Suggestion: make a decision upstream, then Fedora Workstation will follow the upstream decision?

Upstream has created a microsoft@gnome.org account and a Microsoft 365 client ID that will be used by default. It sounds like some UI changes to the panel and freeze break requests are still required to get things into a good state, but it sounds like this situation is coming under control.

Just for a bit of clarity, the field can just be left empty and the compile-time client ID will be used.

At least one user indicated that their use-case is their employer's tenant/account/whichever, and I have feeling others may want the same. Perhaps a "Login with my organization's <term for account>" button that exposes the "advanced" end of things would do.

I'm not convinced that relying on a zero day update is a great idea here. I suspect that a lot of people want to try out new features immediately after upgrade, and that those upgraded systems will not have received a .1 update yet.

Don't we typically have the .1 release before GA anyway?

Don't we typically have the .1 release before GA anyway?

If we can include GNOME 46.1 in the install media then that would be great indeed.

Hmm, it looks like it's slated for April 20, that's a bit late. Can we backport the needed changes before then? I'd rather not hide the M365 support if we can avoid it.

Hmm, it looks like it's slated for April 20, that's a bit late.

No, I've asked upstream to release a .1 gnome-online-accounts ASAP, not following the GNOME schedule. The GNOME schedule is primarily intended for development releases, not stable releases.

We decline to remove this feature. Instead, we'll wait for any upstream design changes.

If a gnome-online-accounts 40.1 is released very soon, there may still be time to include it in F40 final. There may also be time to backport changes before they are released upstream. But if it's fixed via a post-release update, that's fine too.

For the record, my view is still that we should hide this feature for F40. I'm yet to see a viable UI design upstream, and I don't think that the users will be able to make sense of it without changes. Presenting a new feature in a broken state will leave a lasting impression on users.

It should be removed upstream, then, so Fedora isn't the only distro missing this highly-desired new account type.

It should be removed upstream, then, so Fedora isn't the only distro missing this highly-desired new account type.

GNOME 46.0 is done, though, and it wouldn't make much sense to remove a feature in a GNOME point release.

The feature that people desire is OneDrive support, but it's not being delivered (in any distro) if no one can figure out how to make it work.

I was hoping that upstream would expeditiously create a fixed release. However, this has not happened yet, and there is only one business day left before F40 final freeze. This leaves the feature effectively unusable. There is also no time for further discussion with the Workstation WG before freeze. I'm going to make an executive decision to temporarily disable the feature like Allan requested, to avoid likely mass confusion. We can reenable it via a zero-day update, presuming upstream creates a corrected release before then.

Unfortunately I don't have permission to edit the GNOME 46 update, so I'm going to do the build without using a side tag and we'll just see what happens.

I, however, do have the ability to do so. What do you need?

Thanks for helping with this. We've got it sorted now.