There's already talk from participants of the XMPP event cancelling their travels due to COVID19 concerns. I'm honestly also not sure myself if it's a good idea to travel to airports and train stations in a place like Berlin at that time, considering the development in recent weeks and days.
Seeing as some of us already don't have time, how about we eye something in June on Sicily (Hacker House) for the first 2019 hack days? Sambuca should be pretty safe, and there are cheap non-stop flights from many places during the summer season.
So why are they a "Person" in the first place? They're not people, so shouldn't they be something else?
Are we going to have issues like this for every software we're running? If not, isn't it a bit superfluous?
This change is not explained in the commit messages. The package is removed, but I don't see a replacement.
Why do we have to filter anything? We agreed that every user should have a wiki account, no matter what (and that we may want to do the same with other accounts, like e.g. personal Gitea accounts).
I think the emails should be sent out before the switch, and they should contain the date and time for when their password stops working, no?
As stated on chat, I think the way you frame this issue is not addressing the underlying problems.
- Why is there a config in production that hasn't been approved beforehand via a PR?
- Why is the firewall rule necessary, but not the rest? Why can the firewall rule be merged/changed, but not the rest? Why wouldn't there be a separate PR for that in the first place?
I have disabled registrations just now (by downloading, editing, and re-uploading the app.ini config, and deleting and re-creating the deployment).
The inactive accounts are still there.