Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Proposal for Creating an "Emeritus" Status
77 views
Skip to first unread message
Mitchell Baker
Nov 7, 2012, 10:05:52 AM11/7/12
to mozilla-g...@lists.mozilla.org
Over the years we've identified a few specific roles at Mozilla. These
are described in the Roles and Responsibilities document
(http://www.mozilla.org/about/roles.html). I'd like to update this
document in general to reflect the Mozilla project today. That's a task
that will take some work and you'll see from me about this in the coming
months.
For now, I'm proposing we add a new role or status. I'd like to be able
to recognize people who have built something at Mozilla and then passed
on their authority. This will give us a way to describe people after
it is no longer accurate to say "I'm the module owner" or community
leader or other activities. I'm thinking we'd attach a year to it.
So someone would be something like "[Name of module or similar activity]
Module Owner Emeritus, 2012.", The year would be the date the person
passed on their leadership to someone else. I'm inclined start with the
present, and work our way backwards in time.
We cold make an Emeritus Roll, where we list people, including a link to
the materials that show *how* and when they passed on their authority.
This would allow others to learn, and allow us to point to the ones that
seem the best learning examples as reference material.
Thoughts?
Mitchell
are described in the Roles and Responsibilities document
(http://www.mozilla.org/about/roles.html). I'd like to update this
document in general to reflect the Mozilla project today. That's a task
that will take some work and you'll see from me about this in the coming
months.
For now, I'm proposing we add a new role or status. I'd like to be able
to recognize people who have built something at Mozilla and then passed
on their authority. This will give us a way to describe people after
it is no longer accurate to say "I'm the module owner" or community
leader or other activities. I'm thinking we'd attach a year to it.
So someone would be something like "[Name of module or similar activity]
Module Owner Emeritus, 2012.", The year would be the date the person
passed on their leadership to someone else. I'm inclined start with the
present, and work our way backwards in time.
We cold make an Emeritus Roll, where we list people, including a link to
the materials that show *how* and when they passed on their authority.
This would allow others to learn, and allow us to point to the ones that
seem the best learning examples as reference material.
Thoughts?
Mitchell
Axel Hecht
Nov 7, 2012, 10:38:23 AM11/7/12
to mozilla-g...@lists.mozilla.org
and passing something along (XSLT peerhood).
Axel
Majken Connor
Nov 7, 2012, 11:44:17 AM11/7/12
to Axel Hecht, mozilla-g...@lists.mozilla.org
This is a great idea.
Mitchell, a little while ago on the Mozillians list I proposed we create a
historical wiki inspired by similar ideas. One part to remember great
contributors that new people wouldn't get a chance to hear about otherwise,
the other to remember cultural things like "cookies are delicious
delicacies" or old projects.
The idea was well received. Deb Richardson has mozillapedia.x domains
(Sorry don't recall which tlds). I've been slowly hacking away at a demo
instance on my hosting, http://mozillapedia.steelgryphon.com - those of us
working on it all have higher priority projects so it's not impressive yet.
If you're interested I can give a more detailed update on where things are.
Having pages for these emeritus contributors would be the perfect content
to get it going and I think the wiki would be a great place to expose the
community to these emeritus contributors.
-Majken
On Wed, Nov 7, 2012 at 10:38 AM, Axel Hecht <ax...@pike.org> wrote:
> On 07.11.12 16:05, Mitchell Baker wrote:
>
> governance mailing list
> gover...@lists.mozilla.org
> https://lists.mozilla.org/**listinfo/governance<https://lists.mozilla.org/listinfo/governance>
>
Mitchell, a little while ago on the Mozillians list I proposed we create a
historical wiki inspired by similar ideas. One part to remember great
contributors that new people wouldn't get a chance to hear about otherwise,
the other to remember cultural things like "cookies are delicious
delicacies" or old projects.
The idea was well received. Deb Richardson has mozillapedia.x domains
(Sorry don't recall which tlds). I've been slowly hacking away at a demo
instance on my hosting, http://mozillapedia.steelgryphon.com - those of us
working on it all have higher priority projects so it's not impressive yet.
If you're interested I can give a more detailed update on where things are.
Having pages for these emeritus contributors would be the perfect content
to get it going and I think the wiki would be a great place to expose the
community to these emeritus contributors.
-Majken
On Wed, Nov 7, 2012 at 10:38 AM, Axel Hecht <ax...@pike.org> wrote:
> On 07.11.12 16:05, Mitchell Baker wrote:
>
>> Over the years we've identified a few specific roles at Mozilla. These
>> are described in the Roles and Responsibilities document
>> (http://www.mozilla.org/about/**roles.html<http://www.mozilla.org/about/roles.html>).
>> are described in the Roles and Responsibilities document
>> I'd like to update this
>> document in general to reflect the Mozilla project today. That's a task
>> that will take some work and you'll see from me about this in the coming
>> months.
>>
>> For now, I'm proposing we add a new role or status. I'd like to be able
>> to recognize people who have built something at Mozilla and then passed
>> on their authority. This will give us a way to describe people after
>> it is no longer accurate to say "I'm the module owner" or community
>> leader or other activities. I'm thinking we'd attach a year to it. So
>> someone would be something like "[Name of module or similar activity]
>> Module Owner Emeritus, 2012.", The year would be the date the person
>> passed on their leadership to someone else. I'm inclined start with the
>> present, and work our way backwards in time.
>>
>> We cold make an Emeritus Roll, where we list people, including a link to
>> the materials that show *how* and when they passed on their authority.
>> This would allow others to learn, and allow us to point to the ones that
>> seem the best learning examples as reference material.
>>
>> Thoughts?
>>
>> Mitchell
>>
>
>> document in general to reflect the Mozilla project today. That's a task
>> that will take some work and you'll see from me about this in the coming
>> months.
>>
>> For now, I'm proposing we add a new role or status. I'd like to be able
>> to recognize people who have built something at Mozilla and then passed
>> on their authority. This will give us a way to describe people after
>> it is no longer accurate to say "I'm the module owner" or community
>> leader or other activities. I'm thinking we'd attach a year to it. So
>> someone would be something like "[Name of module or similar activity]
>> Module Owner Emeritus, 2012.", The year would be the date the person
>> passed on their leadership to someone else. I'm inclined start with the
>> present, and work our way backwards in time.
>>
>> We cold make an Emeritus Roll, where we list people, including a link to
>> the materials that show *how* and when they passed on their authority.
>> This would allow others to learn, and allow us to point to the ones that
>> seem the best learning examples as reference material.
>>
>> Thoughts?
>>
>> Mitchell
>>
>
> I like the idea, from both sides of having taken something (RDF owner),
> and passing something along (XSLT peerhood).
>
> Axel
>
> ______________________________**_________________
> and passing something along (XSLT peerhood).
>
> Axel
>
> governance mailing list
> gover...@lists.mozilla.org
> https://lists.mozilla.org/**listinfo/governance<https://lists.mozilla.org/listinfo/governance>
>
David Ascher
Nov 7, 2012, 12:01:55 PM11/7/12
to Majken Connor, Axel Hecht, mozilla-g...@lists.mozilla.org
Mitchell et al. --
I think that transferring responsibilities is a key part of the contributor lifecycle, and we should definitely encourage it. In any system of reward or recognition, however, we should be thoughtful about the outcomes we want "socially encouraged," and make sure that the system is more likely to lead to the outcomes we want.
In particular, I think we should not just 'fix deadwood', but encourage thoughtful succession planning: in my mind, the ideal contributor looks to the health of the area that they're involved with (I'll likely use the word 'module' to describe that concept more loosely than the existing module definition implies). As part of that long term view, the module owner, IMO, would seek out potential successors early, train them while they're still active, and transition ownership while they'r still involved. (As part of that long term view they also would look at contributor pipeline, internal integrity (things like architecture docs, code docs, wiki health, etc., but that's a bit off topic.)
We should also try to make it so that contribution to the project as a whole is more heavily valued than the bragging rights of a particular role. A module owner whose time is stretched by too many commitments should be incentivized to find a replacement, not to keep holding on to a 'title'.
Speaking of titles: I have a bit of a concern that the word emeritus has negative brand connotations depending on the background of the people involved -- it would be good to find out whether the 'labels' we use have the positive association we intend for them to have.
--david
I think that transferring responsibilities is a key part of the contributor lifecycle, and we should definitely encourage it. In any system of reward or recognition, however, we should be thoughtful about the outcomes we want "socially encouraged," and make sure that the system is more likely to lead to the outcomes we want.
In particular, I think we should not just 'fix deadwood', but encourage thoughtful succession planning: in my mind, the ideal contributor looks to the health of the area that they're involved with (I'll likely use the word 'module' to describe that concept more loosely than the existing module definition implies). As part of that long term view, the module owner, IMO, would seek out potential successors early, train them while they're still active, and transition ownership while they'r still involved. (As part of that long term view they also would look at contributor pipeline, internal integrity (things like architecture docs, code docs, wiki health, etc., but that's a bit off topic.)
We should also try to make it so that contribution to the project as a whole is more heavily valued than the bragging rights of a particular role. A module owner whose time is stretched by too many commitments should be incentivized to find a replacement, not to keep holding on to a 'title'.
Speaking of titles: I have a bit of a concern that the word emeritus has negative brand connotations depending on the background of the people involved -- it would be good to find out whether the 'labels' we use have the positive association we intend for them to have.
--david
Lawrence Mandel
Nov 7, 2012, 1:30:16 PM11/7/12
to Mitchell Baker, mozilla-g...@lists.mozilla.org
I think this is a great idea that has some precedent in the open source community. Here's a link to the Eclipse committer emeritus page.
http://www.eclipse.org/projects/committers-emeritus.php
Lawrence
----- Original Message -----
> Over the years we've identified a few specific roles at Mozilla.
> These
> are described in the Roles and Responsibilities document
> (http://www.mozilla.org/about/roles.html). I'd like to update this
> _______________________________________________
> governance mailing list
> gover...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/governance
>
http://www.eclipse.org/projects/committers-emeritus.php
Lawrence
----- Original Message -----
> Over the years we've identified a few specific roles at Mozilla.
> These
> are described in the Roles and Responsibilities document
> governance mailing list
> gover...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/governance
>
Mitchell Baker
Nov 7, 2012, 1:50:22 PM11/7/12
to Lawrence Mandel, mozilla-g...@lists.mozilla.org
Wow, this is a great tip. Thanks! I'm temped to adopt it ver batim.
It's great. and I like the idea of open source projects using standard
techniques and practices.
many thanks!
mitchell
It's great. and I like the idea of open source projects using standard
techniques and practices.
many thanks!
mitchell
Mitchell Baker
Nov 7, 2012, 2:24:22 PM11/7/12
to mozilla-g...@lists.mozilla.org
Ah, on looking closer I see that the Eclipse Emeritus status in Ecplise
is not for everyone who passes on leadership. For that they have
Alumni. Hmm, our case will be a bit different. In our case someone
could stop being a module owner but still be very active in our
community and thus not necessarily an alumni. We hope that passing on
authority allows a bunch of people to do new things within mozilla.
Ugh, that means we might be using the same words to mean different
things .... worth considering if Emeritus is the right word . . . .
though I'm reasonably sure alumni isn't quite it.
mitchell
is not for everyone who passes on leadership. For that they have
Alumni. Hmm, our case will be a bit different. In our case someone
could stop being a module owner but still be very active in our
community and thus not necessarily an alumni. We hope that passing on
authority allows a bunch of people to do new things within mozilla.
Ugh, that means we might be using the same words to mean different
things .... worth considering if Emeritus is the right word . . . .
though I'm reasonably sure alumni isn't quite it.
mitchell
Alina Mierlus
Nov 7, 2012, 3:25:35 PM11/7/12
to Mitchell Baker, mozilla-g...@lists.mozilla.org
Hi all,
I like the idea, especially the one with creating a knowledge base of
best practices from those who already passed on their leadership roles.
Sometimes it is not so easy in certain areas (I see for example from
my experience, and I know closely others where is more difficult) to
simply pass on your role. Finding the right person or the right group of
people can take a lot of time. And a knowledge base could help define
some good practices.
But I'm not sure about the term Emeritus. In Wikipedia it is defined as:
"It is also commonly used in business and nonprofit organizations to
denote perpetual status of the founder of an organization or individuals
who moved the organization to new heights as a former key member on the
board of directors (e.g., chairman emeritus; director emeritus;
president of the board emeritus)." - http://en.wikipedia.org/wiki/Emeritus
Emeritus basically means retired (which it is not something that fits
with the dynamic and complex nature of an ecosystem as Mozilla).
Maybe thinking about expanding something like the badges concept?
Scouts may be a good model to study for example. Or community centers or
student organizations?
For those who come at the Mozilla Festival, there is going to be a
session which tries to find some answers to "open governance" questions:
http://mozillafestival.org/schedule/sessions/open-governance-methods-from-open-communities-adapted-to-projects-and-innovation/
(probably interesting to learn from others).
Just my first thoughts.
-Alina
> Ah, on looking closer I see that the Eclipse Emeritus status in Ecplise
> is not for everyone who passes on leadership. For that they have
> Alumni. Hmm, our case will be a bit different. In our case someone
> could stop being a module owner but still be very active in our
> community and thus not necessarily an alumni. We hope that passing on
> authority allows a bunch of people to do new things within mozilla.
>
> Ugh, that means we might be using the same words to mean different
> things .... worth considering if Emeritus is the right word . . . .
> though I'm reasonably sure alumni isn't quite it.
>
> mitchell
>
> On 11/7/12 7:50 PM, Mitchell Baker wrote:
--
Alina Mierlus
@alina_mierlus
I like the idea, especially the one with creating a knowledge base of
best practices from those who already passed on their leadership roles.
Sometimes it is not so easy in certain areas (I see for example from
my experience, and I know closely others where is more difficult) to
simply pass on your role. Finding the right person or the right group of
people can take a lot of time. And a knowledge base could help define
some good practices.
But I'm not sure about the term Emeritus. In Wikipedia it is defined as:
"It is also commonly used in business and nonprofit organizations to
denote perpetual status of the founder of an organization or individuals
who moved the organization to new heights as a former key member on the
board of directors (e.g., chairman emeritus; director emeritus;
president of the board emeritus)." - http://en.wikipedia.org/wiki/Emeritus
Emeritus basically means retired (which it is not something that fits
with the dynamic and complex nature of an ecosystem as Mozilla).
Maybe thinking about expanding something like the badges concept?
Scouts may be a good model to study for example. Or community centers or
student organizations?
For those who come at the Mozilla Festival, there is going to be a
session which tries to find some answers to "open governance" questions:
http://mozillafestival.org/schedule/sessions/open-governance-methods-from-open-communities-adapted-to-projects-and-innovation/
(probably interesting to learn from others).
Just my first thoughts.
-Alina
> Ah, on looking closer I see that the Eclipse Emeritus status in Ecplise
> is not for everyone who passes on leadership. For that they have
> Alumni. Hmm, our case will be a bit different. In our case someone
> could stop being a module owner but still be very active in our
> community and thus not necessarily an alumni. We hope that passing on
> authority allows a bunch of people to do new things within mozilla.
>
> Ugh, that means we might be using the same words to mean different
> things .... worth considering if Emeritus is the right word . . . .
> though I'm reasonably sure alumni isn't quite it.
>
> mitchell
>
> On 11/7/12 7:50 PM, Mitchell Baker wrote:
Alina Mierlus
@alina_mierlus
Jason Duell
Nov 9, 2012, 1:58:10 AM11/9/12
to gover...@lists.mozilla.org
On 11/07/2012 10:50 AM, Mitchell Baker wrote:
> Wow, this is a great tip. Thanks! I'm temped to adopt it verbatim.
The idea is good, and so is most of the language (I like "emeritus").
> Wow, this is a great tip. Thanks! I'm temped to adopt it verbatim.
Re: verbatim: I don't know that we'd want to tie becoming emeritus to
giving up commit status. In particular, I can imagine some of our less
active module owners being willing to give up that title/role in
exchange for emeritus status, but not necessarily at the cost of no
longer being able to review patches or land them, etc.
Jason
Mitchell Baker
Nov 19, 2012, 11:50:57 PM11/19/12
to mozilla-g...@lists.mozilla.org
I've found there are two different ideas that I may have confused.
So, theres a Revised Proposal below!
One idea is a way of identifying someone who was a module owner /
community leader but no longer is. That's a factual matter.
The other idea is a way of honoring a subset of people who have made
extraordinary contributions. The "emeritus" title seems to suggest this
to a number of people. And the Eclipse project uses "ereritus" for this
latter category and "former committers" for the first category.
My first goal is to create the first category. Factual. The "honored,
specially nominated or identified subset of contirubors" may be a good
group to create as well. In any case, i think we need a way to identify
"Former Module Owners" and "Former Community Leaders" factually.
I don't want to have a setting where passing on authority means no
organizational status unless people agree you're particularly special.
That feels like a very divisive path to me.
So, I've got a REVISED proposal.
1. We make an offical "Former" status. It's quite factual; everyone
who passes on a module or analagous leadership role can use this, and we
can maintain a list, etc. We implement this first. I'm very open to
words other than "Former" but haven't been able to think of a great one
myself.
How about we use "emeritus" instead of "former" here (anyone who's been
a module owner/peer/CEO/board member, etc surely merits such a fancy
title :) and then come up with something else for category #2, which may
or may not imply past tense.
2. We look at creating a group of specially honored contributors. We'll
want to decide if those are only those who are no longer active, or
include people who are still active but we want to recognize. I haven't
thought this through, so don't have crisp ideas on this myself yet.
We can see who seems obvious to honor and when, and decide based on some
experience. Or we could make a theory and test it.
I can drive item 1. If you've got a particular interest in Item 2, and
actually some time to think about it, please let me know and we can do
some brainstorming.
Daniel Glazman
Nov 20, 2012, 3:20:04 AM11/20/12
to gover...@lists.mozilla.org
On 20/11/12 05:50, Mitchell Baker wrote:
>
> I've found there are two different ideas that I may have confused.
> So, theres a Revised Proposal below!
>
> One idea is a way of identifying someone who was a module owner /
> community leader but no longer is. That's a factual matter.
>
> The other idea is a way of honoring a subset of people who have made
> extraordinary contributions. The "emeritus" title seems to suggest this
> to a number of people. And the Eclipse project uses "ereritus" for this
> latter category and "former committers" for the first category.
If I like the concept, I don't really like the word "emeritus". Sounds
>
> I've found there are two different ideas that I may have confused.
> So, theres a Revised Proposal below!
>
> One idea is a way of identifying someone who was a module owner /
> community leader but no longer is. That's a factual matter.
>
> The other idea is a way of honoring a subset of people who have made
> extraordinary contributions. The "emeritus" title seems to suggest this
> to a number of people. And the Eclipse project uses "ereritus" for this
> latter category and "former committers" for the first category.
a bit too academic to me and because of that a bit too distant from
our "culture". We already have a concept that we use in my opinion
too lightly : "Friend of the Tree"... I really _like_ that name and
I think it's almost perfectly representing what you outlined in your
message. You could derive that into "Friend of the Tree", "Best Friend
of the Tree", etc. Because of the wording, it can easily be represented
through icons, and many trees make a forest, and and and :-)
Just my personal opinion here.
</Daniel>
Pascal Finette | Mozilla
Nov 20, 2012, 10:06:01 AM11/20/12
to gover...@lists.mozilla.org
Hi Daniel et al.,
If I like the concept, I don't really like the word "emeritus". Sounds
> a bit too academic to me and because of that a bit too distant from
> our "culture". We already have a concept that we use in my opinion
> too lightly : "Friend of the Tree"... I really _like_ that name and
> I think it's almost perfectly representing what you outlined in your
> message. You could derive that into "Friend of the Tree", "Best Friend
> of the Tree", etc. Because of the wording, it can easily be represented
> through icons, and many trees make a forest, and and and :-)
>
The challenge with "Friends of the Tree" is that we are using it for
something very different at the moment - every week in the project meeting
we are calling out people who went above and beyond what is normally
expected of them and call them a "Friend of the Tree" (here for example:
https://wiki.mozilla.org/WeeklyUpdates/2012-11-12#Friends_of_the_Tree).
Personally I also think you want a title which carries gravitas - the
people who we want to celebrate with this title have done extraordinary
things for the project, so it would be awesome if we find a title which
reflects this.
Emeritus sounds a bit academic to my ears as well. On the other side - it's
the best I can come up with too. :)
Warmly,
P
If I like the concept, I don't really like the word "emeritus". Sounds
> a bit too academic to me and because of that a bit too distant from
> our "culture". We already have a concept that we use in my opinion
> too lightly : "Friend of the Tree"... I really _like_ that name and
> I think it's almost perfectly representing what you outlined in your
> message. You could derive that into "Friend of the Tree", "Best Friend
> of the Tree", etc. Because of the wording, it can easily be represented
> through icons, and many trees make a forest, and and and :-)
>
something very different at the moment - every week in the project meeting
we are calling out people who went above and beyond what is normally
expected of them and call them a "Friend of the Tree" (here for example:
https://wiki.mozilla.org/WeeklyUpdates/2012-11-12#Friends_of_the_Tree).
Personally I also think you want a title which carries gravitas - the
people who we want to celebrate with this title have done extraordinary
things for the project, so it would be awesome if we find a title which
reflects this.
Emeritus sounds a bit academic to my ears as well. On the other side - it's
the best I can come up with too. :)
Warmly,
P
Mitchell Baker
Nov 28, 2012, 3:23:24 AM11/28/12
to mozilla-g...@lists.mozilla.org
There seems to be discomfort with the word emeritus.
So I'll start with the *very* factual Former Module Owners group.
Also, at MozCamp Asia last week I gave a special recognition to Channy
Yun, for his decade plus work in Korea, combined with the careful way he
identified, mentored and passed on his role as community leader to
another member. I'll try to get a video clip of this -- probably not
more than a few minutes, so easy to watch -- so anyone interested can
see it. That way we can see if it's a good basis for a program of the
type described in item 2 below.
mitchell
So I'll start with the *very* factual Former Module Owners group.
Also, at MozCamp Asia last week I gave a special recognition to Channy
Yun, for his decade plus work in Korea, combined with the careful way he
identified, mentored and passed on his role as community leader to
another member. I'll try to get a video clip of this -- probably not
more than a few minutes, so easy to watch -- so anyone interested can
see it. That way we can see if it's a good basis for a program of the
type described in item 2 below.
mitchell
Pascal Finette | Mozilla
Dec 8, 2012, 1:05:39 PM12/8/12
to mozilla-g...@lists.mozilla.org
Here is the video from MozCamp Mitchell referenced in her email:
https://www.youtube.com/watch?v=xfs53QypXOQ
On Wed, Nov 28, 2012 at 12:23 AM, Mitchell Baker <mitc...@mozilla.com>wrote:
> There seems to be discomfort with the word emeritus.
>
> So I'll start with the *very* factual Former Module Owners group.
>
> Also, at MozCamp Asia last week I gave a special recognition to Channy
> Yun, for his decade plus work in Korea, combined with the careful way he
> identified, mentored and passed on his role as community leader to another
> member. I'll try to get a video clip of this -- probably not more than a
> few minutes, so easy to watch -- so anyone interested can see it. That way
> we can see if it's a good basis for a program of the type described in item
> 2 below.
>
> mitchell
>
>
>>>>> http://www.eclipse.org/**projects/committers-emeritus.**php<http://www.eclipse.org/projects/committers-emeritus.php>
>>>>>> ______________________________**_________________
>>>>>> governance mailing list
>>>>>> gover...@lists.mozilla.org
>>>>>> https://lists.mozilla.org/**listinfo/governance<https://lists.mozilla.org/listinfo/governance>
>>>>>>
>>>>>>
>>>> ______________________________**_________________
>>>> governance mailing list
>>>> gover...@lists.mozilla.org
>>>> https://lists.mozilla.org/**listinfo/governance<https://lists.mozilla.org/listinfo/governance>
>>>>
>>>
>>>
>>
> ______________________________**_________________
> governance mailing list
> gover...@lists.mozilla.org
> https://lists.mozilla.org/**listinfo/governance<https://lists.mozilla.org/listinfo/governance>
>
--
*Join the fight against e-mail overload:*
– Focus on *your* priorities; I'll understand if you don't reply.
– Sorry if I don't reply; I'm trying to focus, too.
– If it's urgent, reach me by Twitter or SMS.
https://www.youtube.com/watch?v=xfs53QypXOQ
On Wed, Nov 28, 2012 at 12:23 AM, Mitchell Baker <mitc...@mozilla.com>wrote:
> There seems to be discomfort with the word emeritus.
>
> So I'll start with the *very* factual Former Module Owners group.
>
> Also, at MozCamp Asia last week I gave a special recognition to Channy
> Yun, for his decade plus work in Korea, combined with the careful way he
> identified, mentored and passed on his role as community leader to another
> member. I'll try to get a video clip of this -- probably not more than a
> few minutes, so easy to watch -- so anyone interested can see it. That way
> we can see if it's a good basis for a program of the type described in item
> 2 below.
>
> mitchell
>
>
>>>>>
>>>>> Lawrence
>>>>>
>>>>> ----- Original Message -----
>>>>>
>>>>>> Over the years we've identified a few specific roles at Mozilla.
>>>>>> These
>>>>>> are described in the Roles and Responsibilities document
>>>>>> (http://www.mozilla.org/about/**roles.html<http://www.mozilla.org/about/roles.html>).
>>>>> Lawrence
>>>>>
>>>>> ----- Original Message -----
>>>>>
>>>>>> Over the years we've identified a few specific roles at Mozilla.
>>>>>> These
>>>>>> are described in the Roles and Responsibilities document
>>>>>> governance mailing list
>>>>>> gover...@lists.mozilla.org
>>>>>> https://lists.mozilla.org/**listinfo/governance<https://lists.mozilla.org/listinfo/governance>
>>>>>>
>>>>>>
>>>> ______________________________**_________________
>>>> governance mailing list
>>>> gover...@lists.mozilla.org
>>>> https://lists.mozilla.org/**listinfo/governance<https://lists.mozilla.org/listinfo/governance>
>>>>
>>>
>>>
>>
> ______________________________**_________________
> governance mailing list
> gover...@lists.mozilla.org
> https://lists.mozilla.org/**listinfo/governance<https://lists.mozilla.org/listinfo/governance>
>
--
*Join the fight against e-mail overload:*
– Focus on *your* priorities; I'll understand if you don't reply.
– Sorry if I don't reply; I'm trying to focus, too.
– If it's urgent, reach me by Twitter or SMS.
tni...@mozilla.com
Dec 17, 2012, 12:09:34 PM12/17/12
to mozilla-g...@lists.mozilla.org, mozilla-g...@lists.mozilla.org
On Monday, November 19, 2012 8:48:23 PM UTC-8, Mitchell Baker wrote:
> I've found there are two different ideas that I may have confused.
I agree that splitting this into 2 different things is the way to go.
> I've found there are two different ideas that I may have confused.
> So, theres a Revised Proposal below!
>
>
>
> One idea is a way of identifying someone who was a module owner /
>
> community leader but no longer is. That's a factual matter.
>
>
>
> The other idea is a way of honoring a subset of people who have made
>
> extraordinary contributions. The "emeritus" title seems to suggest this
>
> to a number of people. And the Eclipse project uses "ereritus" for this
>
> latter category and "former committers" for the first category.
Just my 2cts,
--Tristan
tni...@mozilla.com
Dec 17, 2012, 12:09:34 PM12/17/12
to mozilla.g...@googlegroups.com, mozilla-g...@lists.mozilla.org
On Monday, November 19, 2012 8:48:23 PM UTC-8, Mitchell Baker wrote:
> I've found there are two different ideas that I may have confused.
I agree that splitting this into 2 different things is the way to go.
> So, theres a Revised Proposal below!
>
>
>
> One idea is a way of identifying someone who was a module owner /
>
> community leader but no longer is. That's a factual matter.
>
>
>
> The other idea is a way of honoring a subset of people who have made
>
> extraordinary contributions. The "emeritus" title seems to suggest this
>
> to a number of people. And the Eclipse project uses "ereritus" for this
>
> latter category and "former committers" for the first category.
>
>
>
> One idea is a way of identifying someone who was a module owner /
>
> community leader but no longer is. That's a factual matter.
>
>
>
> The other idea is a way of honoring a subset of people who have made
>
> extraordinary contributions. The "emeritus" title seems to suggest this
>
> to a number of people. And the Eclipse project uses "ereritus" for this
>
> latter category and "former committers" for the first category.
Stormy Peters
Jan 9, 2013, 11:10:34 AM1/9/13
to Mitchell Baker, mozilla-g...@lists.mozilla.org
fyi, GNOME just quietly added an Emeritus membership. Their
module/maintainer/membership model is different so it doesn't apply
directly.
https://live.gnome.org/MembershipCommittee/EmeritusMembers
Stormy
On Wed, Nov 28, 2012 at 1:23 AM, Mitchell Baker <mitc...@mozilla.com>wrote:
> There seems to be discomfort with the word emeritus.
>
> So I'll start with the *very* factual Former Module Owners group.
>
> Also, at MozCamp Asia last week I gave a special recognition to Channy
> Yun, for his decade plus work in Korea, combined with the careful way he
> identified, mentored and passed on his role as community leader to another
> member. I'll try to get a video clip of this -- probably not more than a
> few minutes, so easy to watch -- so anyone interested can see it. That way
> we can see if it's a good basis for a program of the type described in item
> 2 below.
>
> mitchell
>
>
>>>>> http://www.eclipse.org/**projects/committers-emeritus.**php<http://www.eclipse.org/projects/committers-emeritus.php>
>>>>>> ______________________________**_________________
>>>>>> governance mailing list
>>>>>> gover...@lists.mozilla.org
>>>>>> https://lists.mozilla.org/**listinfo/governance<https://lists.mozilla.org/listinfo/governance>
>>>>>>
>>>>>>
>>>> ______________________________**_________________
>>>> governance mailing list
>>>> gover...@lists.mozilla.org
>>>> https://lists.mozilla.org/**listinfo/governance<https://lists.mozilla.org/listinfo/governance>
>>>>
>>>
>>>
>>
> ______________________________**_________________
> governance mailing list
> gover...@lists.mozilla.org
> https://lists.mozilla.org/**listinfo/governance<https://lists.mozilla.org/listinfo/governance>
>
module/maintainer/membership model is different so it doesn't apply
directly.
https://live.gnome.org/MembershipCommittee/EmeritusMembers
Stormy
On Wed, Nov 28, 2012 at 1:23 AM, Mitchell Baker <mitc...@mozilla.com>wrote:
> There seems to be discomfort with the word emeritus.
>
> So I'll start with the *very* factual Former Module Owners group.
>
> Also, at MozCamp Asia last week I gave a special recognition to Channy
> Yun, for his decade plus work in Korea, combined with the careful way he
> identified, mentored and passed on his role as community leader to another
> member. I'll try to get a video clip of this -- probably not more than a
> few minutes, so easy to watch -- so anyone interested can see it. That way
> we can see if it's a good basis for a program of the type described in item
> 2 below.
>
> mitchell
>
>
>>>>>
>>>>> Lawrence
>>>>>
>>>>> ----- Original Message -----
>>>>>
>>>>>> Over the years we've identified a few specific roles at Mozilla.
>>>>>> These
>>>>>> are described in the Roles and Responsibilities document
>>>>>> (http://www.mozilla.org/about/**roles.html<http://www.mozilla.org/about/roles.html>).
>>>>> Lawrence
>>>>>
>>>>> ----- Original Message -----
>>>>>
>>>>>> Over the years we've identified a few specific roles at Mozilla.
>>>>>> These
>>>>>> are described in the Roles and Responsibilities document
>>>>>> governance mailing list
>>>>>> gover...@lists.mozilla.org
>>>>>> https://lists.mozilla.org/**listinfo/governance<https://lists.mozilla.org/listinfo/governance>
>>>>>>
>>>>>>
>>>> ______________________________**_________________
>>>> governance mailing list
>>>> gover...@lists.mozilla.org
>>>> https://lists.mozilla.org/**listinfo/governance<https://lists.mozilla.org/listinfo/governance>
>>>>
>>>
>>>
>>
> ______________________________**_________________
> governance mailing list
> gover...@lists.mozilla.org
> https://lists.mozilla.org/**listinfo/governance<https://lists.mozilla.org/listinfo/governance>
>
0 new messages