Foundation/Core: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Minor corrections/revisions)
No edit summary
Line 1: Line 1:
''These are the raw notes from the team meeting and discussions w/ others. My next step is to process them and come up w. a proposal.''
This wiki page outlines a set of core Mozilla Foundation roles and tasks, most of which are related to the overall support of the Mozilla project, Mozilla community and related Mozilla organizations. These roles are listed here with the aim of ensuring that they are widely understood and adequately resourced. The shorthand title for the roles and tasks listed here is Mozilla Core.  


==Team meetings notes==
'''This is a draft intended for discussion, comment and refinement''' ''Sept 2009''


"Mozilla Core" is stuff that needs to get done at the Mozilla Foundation no matter what else gets done. It's often taken for granted by the board and others, and seen simply as overhead.
== Context  ==
<blockquote>
''The Mozilla Foundation seeks to effectuate these goals both by building broadly-used products that impact Internet development as a whole, and by empowering people to act in highly decentralized, experimental ways. The work of creating general consumer products that influence broad aspects of Internet development is currently handled through the Mozilla Corporation. The Foundation plans to increase its direct involvement in other activities that enable people to participate in the development and enjoyment of the Internet in a decentralized, self-directed manner.''


Key questions around Mozilla Core:
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mozilla Foundation Statement of Direction, 2007 (?)
* Is it worth thinking about and defining Mozilla Core as a category? (Consensus was, yes it is.)
</blockquote>
* What activities do we think are part of Mozilla Core?
Much of the Mozilla Foundation's work in 2009 has been focused on this last statement: creating new activities that enable people to participate in the development and enjoyment of the Internet. The result is Mozilla Drumbeat and Mozilla Catalyst (or 'Mozilla Grants'?), which are currently under discussion.
* Can we express in one sentence what Mozilla Core is?
* What specific activities are (or should be) part of Mozilla Core?


The overall goal in discussing Mozilla Core is to define a baseline set of tasks and an associated budget for 2010 and beyond.
While these new activities are tremendously important, they cannot be the sole focus of the Mozilla Foundation. The Foundation also has a set of '''roles related to supporting the Mozilla project and community as a whole'''. These roles are outlined (and open for debate) here under the banner 'Mozilla Core'.  


Attempts at defining Mozilla Core in one sentence:
== Core Roles - Direct ==
* Support other Mozilla organizations and the Mozilla community.
* It's horizontal (vs. vertical) activities, filling in gaps, a thin layer of oversight, etc., on top.
* Supporting ourselves, i.e., the Mozilla community.
* Keeping the Mozilla project going in spirit and in fact.


What's inside Mozilla Core? Some ideas:
This list includes essential roles and tasks that the Mozilla Foundation carries out directly.  
* Being the sole shareholder (i.e., of the Mozilla Corporation and Mozilla Messaging)
* Dealing with legal and fiduciary issues (e.g., dealing with IRS, publishing financial statements and tax returns)
* Maintaining and enhancing www.mozilla.org
* Trademark ownership and management, brand stewardship (e.g., present "one Mozilla")
* Defining, managing, and overseeing "one Mozilla" grant process
* Supporting smaller Mozilla-related projects (e.g., Bugzilla, Seamonkey, Camino)
* Supporting and helping to maintain project governance
* Fundraising
* Representing Mozilla to audiences and in regions where being nonprofit matters (David Ascher)
* Playing a core thought leadership role on issues related to web (Brendan Eich)
* Promoting public benefit aspects of the Mozilla project and Mozilla organizations (John Lilly)
* Representing mozilla to governments, NGOs (public policy aspect)


Question: Is Strategy 1 (now Catalyst) stuff part of Mozilla Core? Consensus was that it was not: Strategy 1 programs (e.g., Mozilla Education) are not critical in same sense as governance, etc. (Per Mark, Brendan also thinks we should have a separate Strategy 1 component.)
*Stewardship of Mozilla as an umbrella social brand, presenting 'one Mozilla'.
*Communicating about Mozilla's public benefit mission, refining this message.
*Stewardship of core Mozilla assets: public-benefit tax status, subsidiaries, trademarks.  
*Maintaining and enhancing www.mozilla.org, supporting the mozilla.org community.
*Support for the Mozilla project governance system.


Proposed priorities (ranked by number of people mentioning):
These roles need to fully be staffed or resourced within the Mozilla Foundation.  
* legal and fiduciary stuff
* www.mozilla.org
* governance
* promoting Mozilla public benefit aspects
* supporting smaller Mozilla projects
* community leadership


==Other notes==
== Core Roles - Indirect ==


* big picture path dependent problems (radar)
This list includes roles and tasks carried out by various parties within the Mozilla community, but with active support and oversight from Mozilla Foundation.
* looking at where we're putting attention
 
* org structure
*Maintenance of existing Mozilla trademarks in use by other Mozilla orgs.
* umbrella brand
*Support for smaller Mozilla community-run software projects.
* being a foundation-y public face
*Review and approval of SSL Certificate Authorities.
* connection between product and mission (narrative)
 
While Mozilla Foundation needs some staffing for these support roles are well owned, this can be minimal / lightweight.
 
== Idea Parking Lot ==
 
The roles above have been mentioned by most or all of the people interviewed about Mozilla core. The following is a list of other ideas mentioned by one or more people.
 
*Representing Mozilla to audiences and in regions where being a .org is especially important
*Thought leadership on big-picture, 'path dependent' internet issues (fits in Drumbeat or Catalyst?)  
*Keeping an eye on the big picture of where Mozilla is putting it's attention  
*Defining, managing, and overseeing a Mozilla-wide grant making process
*Making the communications / narrative link between product and mission  
*Representing mozilla to governments, NGOs, etc.
 
== Resourcing and Staffing ==
 
&lt;will fill this section in after public discussion of the items above&gt;

Revision as of 13:54, 24 September 2009

This wiki page outlines a set of core Mozilla Foundation roles and tasks, most of which are related to the overall support of the Mozilla project, Mozilla community and related Mozilla organizations. These roles are listed here with the aim of ensuring that they are widely understood and adequately resourced. The shorthand title for the roles and tasks listed here is Mozilla Core.

This is a draft intended for discussion, comment and refinement Sept 2009

Context

The Mozilla Foundation seeks to effectuate these goals both by building broadly-used products that impact Internet development as a whole, and by empowering people to act in highly decentralized, experimental ways. The work of creating general consumer products that influence broad aspects of Internet development is currently handled through the Mozilla Corporation. The Foundation plans to increase its direct involvement in other activities that enable people to participate in the development and enjoyment of the Internet in a decentralized, self-directed manner.

                                                     Mozilla Foundation Statement of Direction, 2007 (?)

Much of the Mozilla Foundation's work in 2009 has been focused on this last statement: creating new activities that enable people to participate in the development and enjoyment of the Internet. The result is Mozilla Drumbeat and Mozilla Catalyst (or 'Mozilla Grants'?), which are currently under discussion.

While these new activities are tremendously important, they cannot be the sole focus of the Mozilla Foundation. The Foundation also has a set of roles related to supporting the Mozilla project and community as a whole. These roles are outlined (and open for debate) here under the banner 'Mozilla Core'.

Core Roles - Direct

This list includes essential roles and tasks that the Mozilla Foundation carries out directly.

  • Stewardship of Mozilla as an umbrella social brand, presenting 'one Mozilla'.
  • Communicating about Mozilla's public benefit mission, refining this message.
  • Stewardship of core Mozilla assets: public-benefit tax status, subsidiaries, trademarks.
  • Maintaining and enhancing www.mozilla.org, supporting the mozilla.org community.
  • Support for the Mozilla project governance system.

These roles need to fully be staffed or resourced within the Mozilla Foundation.

Core Roles - Indirect

This list includes roles and tasks carried out by various parties within the Mozilla community, but with active support and oversight from Mozilla Foundation.

  • Maintenance of existing Mozilla trademarks in use by other Mozilla orgs.
  • Support for smaller Mozilla community-run software projects.
  • Review and approval of SSL Certificate Authorities.

While Mozilla Foundation needs some staffing for these support roles are well owned, this can be minimal / lightweight.

Idea Parking Lot

The roles above have been mentioned by most or all of the people interviewed about Mozilla core. The following is a list of other ideas mentioned by one or more people.

  • Representing Mozilla to audiences and in regions where being a .org is especially important
  • Thought leadership on big-picture, 'path dependent' internet issues (fits in Drumbeat or Catalyst?)
  • Keeping an eye on the big picture of where Mozilla is putting it's attention
  • Defining, managing, and overseeing a Mozilla-wide grant making process
  • Making the communications / narrative link between product and mission
  • Representing mozilla to governments, NGOs, etc.

Resourcing and Staffing

<will fill this section in after public discussion of the items above>

Retrieved from "https://wiki.mozilla.org/index.php?title=Foundation/Core&oldid=170561"