Basically, the PR looks good to me, but I would want @manno 's opinion as well. Also, I strongly dislike the term "stakeholder" for multiple reasons. Maybe ON_SITE or ON_VENUE would be a more neutral descriptor for that group?

Thanks erdgeist.

Re ON SITE: they're not necessarily on site. I see the assistant role used in two ways: (1) the speaker has a secretary which needs to get all relevant emails and is in charge of the speaker's travel arrangements and so forth. (2) a mentor capacity, someone who helps the speakers make sure their slides are attractive, well written, etc. She needs access to all files, and needs to know if the event was moved/rescheduled etc.

I am adding a commit adding i18n to the settings -> notification page (it was part English before), and also removed the usage of 'stakeholder' externally. Instead I use "people". So 'stakeholder' is used in code only.

I wonder, if the term "subscriber" properly transports the meaning. If you look at why we build this list in the first place, is to ensure everyone who needs to be notified about state changes of the event … actually is notified. This is what a subscription is. So I think, this term might be used instead of steakholder ;)

In other contexts the term "watchers" is used, like in ticket systems.

I thought "watchers" to be confusing is the sense that people come to a conference in order to watch the actual event.

So I changed all "stakeholders" to "subscribers" - internally the term was not used.

I kept the external wording "send to 2 people" and did not use "2 subscribers" becuase I think it's clearer.