This was fixed back then but I forgot to close the task.

So is there more to do here, or can this be resolved?

Patched on the servers.

As long as it's in read-only mode it doesn't really matter, login wouldn't work either way. I only encountered this because I took the site out of read-only mode to fix T296602: Space (Discourse) theme broken but couldn't log in as an admin (later I found out that I'm not an admin at all :) and that admins have an emergency login method via /u/admin-login which would work around this).

I have disabled the theme compoennts and the UI, even if simpler, seems to be fully functional again.

I can look into this later as well. I think it is a matter of removing the custom components.

Thank you for looking into this. I see the developer has responded already. We seem to be in an impasse, where either we... remove Wikimedia login and leave Discourse in pure read-only mode, or if someone has Discourse plans in mind, we talk to the developer to work on a fix. I'm sure there are other possibilities, but these two are logical.

Upstream task is paviliondev/discourse-wikimedia-auth#4.

The error refers to user_name_suggester.rb line 7, which takes one argument, but the documentation mentions a second and discourse-wikimedia-auth indeed uses two, so probably a recent change.

https://discuss-space.wmflabs.org/about lists @elappen-WMF, @Ckoerner and @Qgil as admins. Given the lack of activity on this Phab ticket for 14 months and on the Space thread for 11 months, I'm going to realistically set the task status to declined. The admins are very welcome to reopen if they plan to take actions (though I'd personally would like to see an overall strategy first, given our highly impressive communication venue fragmentation).

I am surprised that you could log in at all.

Thanks! Because users can also change the frequency of email summaries in their preferences, I think leaving it at one eek is good.

In T248841#6011720, @bd808 wrote:

The Discourse instance in question actually was created in the discourse Cloud VPS project, so @Samwilson, @Tgr, @Qgil, and the other admins in that project need to evaluate this request and determine if they are willing to take on another co-maintainer or make data dumps available to recreate the instance in another project with more narrow scope.

Ah, glad you found a way, and thanks for the quick update! :)

In T250187#6056553, @Aklapper wrote:

@Mardetanha: No I am not sure, I only said that I am surprised. :)
I only know that the Space project has been archived in Phabricator by Quim, so I do not know where bugs should get reported - maybe in Space itself, as it is about Space?

@Mardetanha: No I am not sure, I only said that I am surprised. :)
I only know that the Space project has been archived in Phabricator by Quim, so I do not know where bugs should get reported - maybe in Space itself, as it is about Space?

Space is discontinued, so I am surprised that you could log in at all.

Space is discontinued, so I am surprised that you could log in at all.

I had suppressed the mailing lists from showing up in the digest but missed Education. That list is now also suppressed. Frequency of digests is default once per week, but maybe we should set it to less frequent.

Elena had looked into this.

Hi, see https://discuss-space.wmflabs.org/t/responding-to-questions-about-a-future-discuss-space-owned-by-volunteers/3367

Presumably the Cloud VPS TOU covers that?

And to be clear, these questions preclude but don't avoid the points made by @bd808 above. They are relevant regardless of where Discuss Space is hosted and how it is maintained.

Just a quick note now to say that we will need to do some homework in order to have answers about a couple of important questions that at least I don't know the answer right now:

A change in project admins is outside the scope of the Cloud-VPS (Project-requests) process. The Toolforge-standards-committee exists to handle this sort of thing in the Toolforge project, but only for abandoned tools. We don't have any similar system for Cloud-VPS projects today.

I'm boldly declining this task based on the assumption that the new community blog will have native WordPress comments and therefore this problem, if it exists at all, will be completely different.

Well, investigating this isn't important now. As we close down Discourse we'll not need to fix this problem! We'll be using WordPress comments in the new blog.

The task with the developer is still open, months later. I don't think it's a priority for them at the moment. As we transition to a new community blog from Space I think this feature is rather low priority. Perhaps we can revisit in the future, but for now declining.