Determine best home for Module Owners List -- still despot?

RESOLVED FIXED

Status

RESOLVED FIXED
12 years ago
7 years ago

People

(Reporter: mitchell, Assigned: mitchell)

Tracking

Details

(Assignee)

Description

12 years ago
Despot is automatically generated, which is good.  Some people prefer a wiki, which is easier to edit.  We'll need to do something to create a list for non-coding activities -- either put these in despot or create a non-despot list.

Updated

12 years ago
Summary: Dtermine best home for Module Owners List -- still despot? → Determine best home for Module Owners List -- still despot?

Updated

12 years ago
OS: Mac OS X 10.3 → All
Hardware: PC → All
(Assignee)

Updated

12 years ago
Status: NEW → ASSIGNED

Comment 1

12 years ago
Despot works for the existing list. 

This likely is a moot point until we have the list of non-coding module owners.
Depends on: 363541
(Assignee)

Comment 2

11 years ago
I'm going to create a couple of wiki pages shortly for the list of non-code (aka "Activities") modules.  We can get some experience with this and then see what we think of the wiki vs. despot for code modules. 

I'll add draft context for these to-be-created pages in the next few days (I hope). 
(Assignee)

Comment 3

11 years ago
Here's the text for the wiki home for Activities Modules.  When this (or a revised version) goes live I will probably close this bug.  We can open another one later if we decide we need further exploration as to whether despot is or isn't actually working well for code modules.  

My plan is to create two wiki pages, one an overview, and one the beginning of a list of Activities modules.  Comments welcome. Can't create the second page until the names of the Module Ownership module are finalized, which I expect to happen early next week.


 
1.  Overview Page

Modules and Module Ownership
The  Mozilla project operates under the principle of distributed authority, combined with an identified ultimate decision maker should escalation be required.  We do this through our Module Ownership system, [link to module ownership document] which we've used officially with code for many years.  This system was initially described in early policy documents from the 1990s and remains our basic organizing and operational principle.   

Today the Mozilla project encompasses many activities beyond writing code.     We're slowly bringing those activities into the official Module Ownership system.  

The list of[ Module Owners for code modules] is auto-generated from one of our databases known as "despot.mozilla.org".  [text inside the brackets is a link to http://www.mozilla.org/owners.html ]

The [list of Module Owners for activities modules] is maintained manually..  [text inside brackets is link to new wiki.m.o page, see below]  
The policy documents governing the module ownership system are linked below.  Some of the details are outdated, but the overall system remains our basic organizing and operational principle for the project.  There is also a list of [potential Activities Modules] that a contributor compiled in 2007.  There are a bunch of things on that list that we might decide are more like job functions than project roles, but I'm not sure yet.  I'm hoping we can derive some guiding principles as we look at the early Activities Modules.    [text in brackets is a link to the doc "Modules_Scratchpad" which is currently linked from the Main_Page, and which I want to move one layer deeper in]
I
* http://www.mozilla.org/hacking/module-ownership.html
* http://www.mozilla.org/about/roles.html

 2.  Page for Activities Modules   [Is it possible to set this page so that it can only be edited by specified people?  If not then we should set it up so only the wiki administrators can edit it.]

Activities Modules 
(The name "activities" may change.  It's a bit too generic and could apply to anything, including code modules.  If you've got a good idea, please let me know.)

1.  Governance -- 	
	owner:  mitchell baker
	peer(s):  brendan eich
	newsgroup:  mozilla.governance
	scope: project-wide
	responsibilities:  Policies and process for how we distribute authority and govern ourselves. This includes topics such as:
		Management and update of existing policies governing modules and module ownership, our source tree, security vulnerabilities
		Development and Implementation of new policies as appropriate for delegation of authority and responsibility
		Integration of new Activities (non-coding) modules into our module framework
	other:  in the past there has been a group of people deeply involved in these topics regularly.  We may create a group for this again as we go forward; perhaps as peers, perhaps as  "members", perhaps as advisors.  

Due to the large and diverse nature of topics included in the Governance module, we will divide responsibilities by sub-module, in order to delegate authority for specific pieces and identify particular areas of expertise. 
 
1A.  Governance Submodule:  Module Ownership System [Note:  I'd like to make this a specific section with a corresponding section heading so we can link to it directly/]

	owner:  Brendan Eich
	peers:  Stuart Parmenter, Dan Mosedale, Robert Kaiser, Mike Connor, David Baron, Frank Hecker, Mitchell Baker
	newsgroup:  mozilla.governance
	scope:  project-wide
	responsibilities:  Healthy operation of the module ownership system.  This includes topics such as:

Filling vacant roles where appropriate
Ensuring module owners are fulfilling their responsibilities, and replacing those who are not
Creating and staffing new modules where new parts of the project evolve.
Figuring out what to do if  a module isn't getting enough attention
Resolving conflicts among module owners

	
2.  Planet Mozilla -- 
	owner:  Asa Dotzler
	peers:  Robert Accettura, Deb Richardson, J. Paul Reed. 
	newsgroup:  
	scope:  project-wide
	responsibilities:  content and policy for planet.mozilla.org.  This includes topics such as:
which blogs are syndicated to planet.mozilla.org
which content from syndicated blogs in included
other planet.mozilla.org policy issues
(In reply to comment #3)

> 2.  Planet Mozilla -- 
>         owner:  Asa Dotzler
>         peers:  Robert Accettura, Deb Richardson, J. Paul Reed. 

Please remove "J. Paul Reed" and add me ("Reed Loden") instead. Thanks.
(Assignee)

Comment 5

11 years ago
Reed

is this a change, or just I misheard Asa?
(In reply to comment #5)
> is this a change, or just I misheard Asa?

I've been a module peer of planet since last September. preed was one of the original module peers, but he is no longer active, as far as I'm aware.

Comment 7

11 years ago
reed is an addition, yes. preed hasn't been active but I haven't talked to him about whether or not he's still interested or not so let's not remove him just yet.
(Assignee)

Comment 8

11 years ago
I copied the entire text here; added Reed.  lengthly, but leaves us with text one can grab and jam into a wiki.





1.  Overview Page

Modules and Module Ownership
The  Mozilla project operates under the principle of distributed authority,
combined with an identified ultimate decision maker should escalation be
required.  We do this through our Module Ownership system, [link to module
ownership document] which we've used officially with code for many years.  This
system was initially described in early policy documents from the 1990s and
remains our basic organizing and operational principle.   

Today the Mozilla project encompasses many activities beyond writing code.    
We're slowly bringing those activities into the official Module Ownership
system.  

The list of[ Module Owners for code modules] is auto-generated from one of our
databases known as "despot.mozilla.org".  [text inside the brackets is a link
to http://www.mozilla.org/owners.html ]

The [list of Module Owners for activities modules] is maintained manually.. 
[text inside brackets is link to new wiki.m.o page, see below]  
The policy documents governing the module ownership system are linked below. 
Some of the details are outdated, but the overall system remains our basic
organizing and operational principle for the project.  There is also a list of
[potential Activities Modules] that a contributor compiled in 2007.  There are
a bunch of things on that list that we might decide are more like job functions
than project roles, but I'm not sure yet.  I'm hoping we can derive some
guiding principles as we look at the early Activities Modules.    [text in
brackets is a link to the doc "Modules_Scratchpad" which is currently linked
from the Main_Page, and which I want to move one layer deeper in]
I
* http://www.mozilla.org/hacking/module-ownership.html
* http://www.mozilla.org/about/roles.html

 2.  Page for Activities Modules   [Is it possible to set this page so that it
can only be edited by specified people?  If not then we should set it up so
only the wiki administrators can edit it.]

Activities Modules 
(The name "activities" may change.  It's a bit too generic and could apply to
anything, including code modules.  If you've got a good idea, please let me
know.)

1.  Governance --       
        owner:  mitchell baker
        peer(s):  brendan eich
        newsgroup:  mozilla.governance
        scope: project-wide
        responsibilities:  Policies and process for how we distribute authority
and govern ourselves. This includes topics such as:
                Management and update of existing policies governing modules
and module ownership, our source tree, security vulnerabilities
                Development and Implementation of new policies as appropriate
for delegation of authority and responsibility
                Integration of new Activities (non-coding) modules into our
module framework
        other:  in the past there has been a group of people deeply involved in
these topics regularly.  We may create a group for this again as we go forward;
perhaps as peers, perhaps as  "members", perhaps as advisors.  

Due to the large and diverse nature of topics included in the Governance
module, we will divide responsibilities by sub-module, in order to delegate
authority for specific pieces and identify particular areas of expertise. 

1A.  Governance Submodule:  Module Ownership System [Note:  I'd like to make
this a specific section with a corresponding section heading so we can link to
it directly/]

        owner:  Brendan Eich
        peers:  Stuart Parmenter, Dan Mosedale, Robert Kaiser, Mike Connor,
David Baron, Frank Hecker, Mitchell Baker
        newsgroup:  mozilla.governance
        scope:  project-wide
        responsibilities:  Healthy operation of the module ownership system. 
This includes topics such as:

Filling vacant roles where appropriate
Ensuring module owners are fulfilling their responsibilities, and replacing
those who are not
Creating and staffing new modules where new parts of the project evolve.
Figuring out what to do if  a module isn't getting enough attention
Resolving conflicts among module owners


2.  Planet Mozilla -- 
        owner:  Asa Dotzler
        peers:  Robert Accettura, Deb Richardson, J. Paul Reed, Reed Loden
        newsgroup:  
        scope:  project-wide
        responsibilities:  content and policy for planet.mozilla.org.  This
includes topics such as:
which blogs are syndicated to planet.mozilla.org
which content from syndicated blogs in included
other planet.mozilla.org policy issues
(Assignee)

Comment 9

11 years ago
Reed

I see that one needs sysops privileges to edit the Main_Page; don't think I have these.  Here's a change I'd like to see made.  Can you review and either give me access to implement or I suppose, implement them yourself?

At http://wiki.mozilla.org/Main_Page there is a "Global" section.  In this section there is a link to "Modules_Scratchpad."  I would like that link to change, so that the title in the "Global" section becomes "Modules and Module Ownership" and the link goes to a new page, called "Module Ownership Overview."  (The text for the new page is in the Overview part of 
> https://bugzilla.mozilla.org/show_bug.cgi?id=363542.

giving me sysops privileges is one solution.  Otherwise can you edit at least the Main_Page?  (I don't really want all the sysops privileges, but I would like to be able to edit.)
(In reply to comment #9)
> giving me sysops privileges is one solution.

I can just do that. What is your wikimo username?
(In reply to comment #10)
> (In reply to comment #9)
> > giving me sysops privileges is one solution.
> 
> I can just do that. What is your wikimo username?

There seems to be a "Mitchell Baker" that already has the following privileges: Bureaucrat, canmove, Sysop. Is that you? If so, you already have the needed permissions...
20:18, 30 April 2008 Dria (Talk | contribs) changed group membership for User:Mitchell Baker from (none) to sysop, bureaucrat, canmove (needed access to move some pages)

Looks like dria did it...
(Assignee)

Comment 13

11 years ago
Ah.  I chatted with deb about editing this page; didn't realize she had made this change as a result. thanks!
(Assignee)

Comment 14

11 years ago
I've created these pages
    http://wiki.mozilla.org/Modules_and_Module_Ownership
    and http://wiki.mozilla.org/Module_Owners_Activities_Modules

added a bit of text in the governance module re final decision making.

I'll make a public announcement about these once IT has updated despot so the related new text there is public (436015) and (b) the revised policy document on module ownership is checked in (431945)

      
(Assignee)

Comment 15

11 years ago
Right now I'm not going to try to move the auto list from despot into a list maintained by hand on the wiki.

so i'm going to close this bug as fixed, at least for now.

it may still be that we have to figure out if despot works with mercurial and the question will come up again.
Status: ASSIGNED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.