On 20.02.13 06:59, Lukas Blakk wrote:
If the chair of the council is a rotating position, I am a bit concerned about module
ownership churn. Most of our module owners seem to get the position and then stay
attached to their module(s) for a fairly long time. Of course we are welcome to
experiment, and Mozilla Reps is a pretty unique program, but reading Gerv's statement
makes me have a bit of a knee-jerk reaction, wanting more continuity than "the
current chair" if that position rotates often and I'm not sure what that would look
like. Perhaps the current and most recent former chair so that there's some coverage
from the past at the same time?
I had a similar reaction when the reps program proposed the current mode
of operations for the council. But I consider that to be a purposeful
decision on behalf of the reps program itself.
I'm wondering if the council needs to be reflected as a module at all.
Maybe the following is a closer description of reality?
Make the council as a group a peer of the reps module. As-a-group would
mean that as it's elected and makes decisions. The individual members of
the council wouldn't have a role in the module ownership per se, aside
of overlap in individuals.
Axel
-Lukas
On Feb 19, 2013, at 4:46 AM, William Quiviger <[email protected]> wrote:
On Feb 19, 2013, at 12:44 PM, Axel Hecht <[email protected]> wrote:
On 19.02.13 11:45, Gervase Markham wrote:
The Mozilla Reps program is not covered by the module owner system; we'd
like to propose some new Activities Modules to cover it. The proposed
module descriptions are here:
https://wiki.mozilla.org/Modules/Mozilla_Reps
We've done something a bit unusual, in that there is not a named module
owner for the Mozilla Reps Council. The chair of the council is a
rotating position among the members, both employee and volunteer. So we
decided to propose specifying the module owner as "the current chair of
the council". We would want to specify a way of finding out who it was.
By similar logic, the peers are "all the other council members".
Please do comment.
Gerv
In which situations would I talk to reps module owner/peers and in which to the
reps council?
The Reps module owner/peers oversee the general health of the program and makes
sure that the Council is doing its job. If you have a very general question
or concern about the program as a whole and how it fits within the Mozilla
project, you would contact the Reps module owner/peers.
The Reps Council module owner/peers oversee the day to day of the program,
manage Mozilla Reps Mentors, represents Mozilla Reps and serves as an advisory
body within the Mozilla organization. The module owner/peers change regularly
with the Mozilla Reps 6-month election cycle. If you have a specific question
related to the program's governance structure, finances, day-to-day management,
then you would ask the Reps Council module owner/peers.
Also, in which situations would I talk to the mentors owner/peers and in which
to the council?
The Reps Mentors module owner/peers look after the Mozilla Reps program's
mentorship base. Mentors on-board new applicants, look after and mentor Reps,
monitor their activities and help them grow in the program.
If you have a question related to what Mozilla Reps do and how they are
supported (eg. resources, tools, materials etc..), you should ask the Reps
Mentor module owner/peers.
Right now, there's a good deal of overlap in individuals, so the questions are
mutually exclusive, but as we codify them, I wonder if we can get this more
crisp.
I agree. Thanks for the feedback. I'll work with the Council and Gerv to make
the text a bit crisper.
William
---
William Quiviger
Mozilla Reps Council Chair
https://reps.mozilla.org/u/wquiviger/
_______________________________________________
governance mailing list
[email protected]
https://lists.mozilla.org/listinfo/governance
_______________________________________________
governance mailing list
[email protected]
https://lists.mozilla.org/listinfo/governance
