> > I should also point out that in the future, it may become very > > important to be able to distinguish official email from Mozilla as a > > project, versus someone who is affiliated with Mozilla (as paid staff > > or not). > > Email always comes from a person, it never comes from an organization > (at least, I hope Mozilla will never even attempt to be that > impersonal!). I do not think there will be a problem distinguishing > summit announcements from e.g. IETF contributions (which are always > individual), even if both come from @mozilla.org email addresses.
We have at least one product that requires email verification flow (Persona) and there's also a payments API (https://wiki.mozilla.org/Apps/ID_and_Payments, https://wiki.mozilla.org/WebAPI/WebPayment). The email verification flow already involves mail that is from a service, not from a person. I could imagine that the payments API might involve email that's similar. That's not being impersonal -- that's using the communication model that everyone already understands from things like Paypal and bank email notifications. Besides that issue, I still don't think that foo.com and foo.org addresses still make sense simultaneously for any protocol, including mail. Otherwise, many domains wouldn't redirect from one to the other (including ours), and resolv.conf wouldn't support search directives. We shouldn't try to create a distinction artificially and expect people to understand it. Thanks, Monica _______________________________________________ governance mailing list [email protected] https://lists.mozilla.org/listinfo/governance
