Yes, That’s a pain point. It should rather default to the developer_emails as defined in app.yml because the dev/sysadmin is far more interested in pushing the update than website support (which could be a non-tech team altogether)
Maybe the answer here is to change the
new version emails admin setting from a toggle to a comma separated list of email addresses, defaulting to the first site admin who sets up the site in the first place.
That said, do we have rule of three? I have not heard this request from anyone else. The official contact is supposed to reach someone about important issues relating to the forum, and can forward the email to the person in charge of doing updates.
There is a strong chance people might be unaware of the existence of this feature.
Let’s see… by default, Discourse checks for version updates. Also by default, if a new version is available an email is sent to the
In the setup wizard, they are prompted to fill the
I guess it is true that people might not make it that far at first setup and may never return to complete that admin setting. We could be doing more to make sure Discourse nudges people so they do complete it, to make sure they are reachable for critical notifications and on their about page for urgent matters.
It’s also true that for self-hosters, an email address for the person setting up the site is provided during setup in
app.yml, and so a smoother experience might indeed be to send the email to the email address in
app.yml, as suggested above.
Or another idea would be to change the admin setting to specify a group to notify, default admin? That would be noisy or people stepping on each other’s toes on sites with many admins but we could add a note to the admin getting started guide to change the group in that case.