The peers of the Reps module discussed this, and whatever mechanism is used to hand out these email addresses, we feel like it falls under our mandate as a need we should be filling - that is to say, not that we want to be the ones to control it, but that it doesn't make sense to create *another* group to handle this. Reps were already created to cover this type of thing.
We want to propose that we do a first wave of giving out these email addresses to Reps, after the program does a review of the current membership. Then we would commit to a timeline to create the process to give the email addresses to volunteers who deserve them but don't fit under the current Reps umbrella. In theory the Reps program also helps non-reps with budget and swag for events, currently the process is to ask a Rep to submit the request for you (basically a vouching process) and I think distributing the email addresses is a pretty similar use case. Obviously we would continue sharing any proposals with Governance just like the original suggestion has done, and of course we could use the ideas already proposed - 2 vouches, renew yearly etc. Does this sound like the right solution? On Tue, Oct 29, 2013 at 1:23 PM, Benjamin Kerensa <[email protected]>wrote: > I wanted to add that I had an opportunity to talk to a few staff from the > Portland office who have been following this and they like the idea. > > One suggested that all staff and contributors should use @mozilla.org > > On Oct 29, 2013 7:05 AM, "Gervase Markham" <[email protected]> wrote: > > > > On 25/10/13 18:30, Monica Chew wrote: > > > I think it's a wonderful idea to give Reps and other contributors > > > email addresses. Can I suggest mozillians.org instead of mozilla.org, > > > though? mozilla.org is not sufficiently distinguishable from > > > mozilla.com to avoid confusing paid staff from not, and Mozillian has > > > the benefit of sounding like a person-descriptor. > > > > I think making the distinction between paid staff and volunteers more > > clear is actively an anti-goal. > > > > When this program happens, I would like to see paid staff who qualify > > for @mozilla.org starting to use that email address as their primary > > Mozilla identity. A few of us already do that. > > > > > 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. > > > > Gerv > > _______________________________________________ > > governance mailing list > > [email protected] > > https://lists.mozilla.org/listinfo/governance > _______________________________________________ > governance mailing list > [email protected] > https://lists.mozilla.org/listinfo/governance > _______________________________________________ governance mailing list [email protected] https://lists.mozilla.org/listinfo/governance
