https://wiki.mozilla.org/api.php?action=feedcontributions&user=MitchellBaker&feedformat=atomMozillaWiki - User contributions [en]2024-03-28T21:29:25ZUser contributionsMediaWiki 1.27.4https://wiki.mozilla.org/index.php?title=User:Ckoehler/About_wiki.mozilla.org&diff=981186User:Ckoehler/About wiki.mozilla.org2014-05-21T05:43:43Z<p>MitchellBaker: /* Comments */</p>
<hr />
<div>{| class="wikitable"<br />
|+ style="text-align:left; padding: 5px;" | Request for Comments<br />
|-<br />
| style="width: 20%; text-align: right; padding: 5px;" | '''date created''' || 2014-05-09<br />
|-<br />
| style="width: 20%; text-align: right; padding: 5px;" | '''comments deadline''' || style="color:red;" | 2014-05-26 14:00 UTC<br />
|-<br />
| style="width: 20%; text-align: right; padding: 5px;" | '''contributors''' || [[User:Ckoehler | Christie Koehler]], Lyre Calliope, Gordon Hemsley, Justin Crawford, Larissa Shapiro, Jennie Rose Halperin, Mark A. Hershberger, and Jason Crowe.<br />
|-<br />
| style="width: 20%; text-align: right; padding: 5px;" | '''status''' || draft<br />
|-<br />
| style="width: 20%; text-align: right; padding: 5px;" | '''To make comments:''' || Edit this page, putting your comments in the [[#Comments]] section. Include <nowiki>~~~~</nowiki> without the "nowiki" tags to include your signature.<br />
|}<br />
<br />
{| class="wikitable"<br />
|-<br />
| '''Preamble:''' The [[Contribute/Education/Wiki_Working_Group | Wiki Working Group]] has formed to kick-start a revitalization of the wiki and to create a framework for empowering the entire Mozilla community to participate in and sustain this revitalization effort. A first step in this revitalization effort is this '''About''' page, which seeks to clarify the ''purpose'', ''scope'' and ''governance'' of the Mozilla Wiki. Once adopted, this text will reside at [[About]] and serve as our guide for interacting and making decisions about wiki.mozilla.org.<br />
<br />
We are actively seeking comments from our community until '''26 May 2014'''. Those comments will be considered and incorporated and this page adopted into the wiki by 15 June 2014. In review this document, please consider the following questions as you review and make your comments:<br />
<br />
* what about the content does or does not make sense to you?<br />
* what about the content does or does not resonate with you?<br />
* to what extent does the content match your vision for wiki.mozilla.org?<br />
* to what extend can you support the purpose, scope and governance structured described?<br />
|}<br />
<br />
<br />
== Purpose ==<br />
This wiki (wiki.mozilla.org, AKA MozillaWiki or WikiMO) is the official public wiki of the Mozilla Project. It is the encyclopedia of the project and is intended to contain comprehensive and dynamic information about Mozilla products, initiatives and sub-projects. <br />
<br />
Additionally, the wiki seeks to facilitate lively community interaction that empowers contributors to coordinate activities, find support, and make their projects accessible to other contributors across Mozilla.<br />
<br />
== How is the Wiki a critical resource to the Mozilla Project? ==<br />
<br />
'''The Wiki provides the most comprehensive, overall picture of Mozilla's mission, strategy, and history.''' Information on the wiki tells the story of Mozilla and makes the organization navigable in a way that no other single resource does. The wiki, along with [https://bugzilla.mozilla.org Bugzilla] and our [https://www.mozilla.org/about/forums/ forums], form the core of Mozilla's long-term institutional record.<br />
<br />
'''The Wiki is a significant entry point for contributors into the Mozilla project.''' It serves as a primary and massively scalable on-boarding tool because it provides the opportunity for self-serve contribution pathways across all areas of the project. The wiki enables self-motivated individuals to take advantage of contribution opportunities immediately. The better organized the wiki, the more people are able to take advantage of these opportunities. <br />
<br />
'''Publicly available wikis, code repositories, and bug trackers are essential to our collaborative environment and connect our project to the greater open source eco-system.''' These tools are part of the established canon of open source organizational tools because they make the knowledge and tools required to participate immediately available to those who are interested. Experienced open source participants benefit from Mozilla providing these tools because it is what they are accustomed to, and those new to open source benefit because it prepares them for working with other projects in the open source ecosystem.<br />
<br />
== What content is appropriate for the Wiki? ==<br />
<br />
* Any content pertaining to Mozilla's products, initiatives and sub-projects that is '''not''' end-user documentation or developer documentation.<br />
* Any content pertaining to Mozilla's mission, strategy or history.<br />
* Any content that supports Mozilla's mission or community.<br />
* Any content that is related to the on-going planning, coordination or other contribution activities of Mozilla projects.<br />
* Any content related to the discussion of content on the wiki (e.g. Talk/Discussion pages).<br />
* Any content that is related to helping people use the Wiki.<br />
<br />
Content appearing to be completely unrelated to Mozilla and not falling into any of the categories above may be deleted as spam or moved elsewhere.<br />
<br />
'''End-user documentation''' is written for users of Mozilla's products and explains how are products work and how to use them. In general, this type of content belongs on [http://support.mozilla.org SUMO].<br />
<br />
'''Developer documentation''' is written for programmers developing for Mozilla products like Firefox as well as the Open Web. This type of content includes technical reference information for programming languages and platforms and is most suited for [http://developer.mozilla.org MDN].<br />
<br />
== Who own and maintains the Mozilla wiki? ==<br />
<br />
The wiki is owned and maintained by the Mozilla community. <br />
<br />
* '''Infrastructure''' for the wiki is provided by Mozilla Corp. <br />
* '''Governance''' issues are managed by the [[Modules/Mozilla_Websites#WikiMo | WikiMo module]], a sub-module of Websites. Its current module owner is [[User:Ckoehler | Christie Koehler]] and module peers are [[User:CaptainCalliope | Lyre Calliope]] and [[User:GPHemsley | Gordon Hemsley]].<br />
* '''Technical Support''' is provided jointly by the community and MoCo staff.<br />
* '''Content''' is managed by the community. Information here is public and can be modified by anyone in the Mozilla community with sufficient interest and knowledge to improve it (and an account).<br />
<br />
== Where can I report issues with wiki.mozilla.org? ==<br />
<br />
* '''Technical''' issues should be reported via [https://bugzilla.mozilla.org/enter_bug.cgi?product=Websites&component=wiki.mozilla.org bugzilla]. These include server or client-side errors, styling issues, problems with accounts or logging in, and feature requests.<br />
* '''Content''' issues should be addressed on the wiki itself using Talk/Discussion pages whenever possible.<br />
<br />
General questions can be addressed to [https://www.mozilla.org/about/forums/#tools-wiki tools-wiki] or #wiki on irc.mozilla.org.<br />
<br />
= Comments = <br />
<br />
Tips for adding comments:<br />
* Include <nowiki>~~~~</nowiki> (without "nowiki" tags) as the last text of your comment to include your signature.<br />
* Indent text to reply with a colon <nowiki>:</nowiki><br />
<br />
Examples:<br />
<br />
This is is the first comment! [[User:Ckoehler|Christie Koehler (ckoehler)]] ([[User talk:Ckoehler|talk]]) 12:53, 7 May 2014 (PDT)<br />
: this is the first reply! [[User:Ckoehler|Christie Koehler (ckoehler)]] ([[User talk:Ckoehler|talk]]) 12:53, 7 May 2014 (PDT)<br />
<br />
Add your comments and suggestions below. Please use this space to '''comment about this proposal specifically'''. If you have general comments about the wiki, use [[Contribute/Education/Wiki_Working_Group/Sandbox | this page]].<br />
<br />
'''About Developer documentation''': A lot of information on how to build and fix things are contained currently in the wiki and not the MDN. I'm faulty of that. Would you recommend that anything which is technically related and/or offer guidance on how to operate in the activity should be pushed to MDN. If yes it would be good to activate Inter wiki links to make it possible to benefit of redirections in between the two entities. For example in Web Compatibility how would we classify [[Compatibility/Guide|Guide]] and [[Compatibility/Mobile/WipeOutUAOverides#Updating_the_UA_override_list|Updating]]. I'm not sure it will be easy to do. Maybe a different way to go about it is to encourage people to think about it when they create a new page.[[User:Karlcow|Karlcow]] ([[User talk:Karlcow|talk]]) 15:40, 9 May 2014 (PDT)<br />
<br />
: Good question. Both of the pages you link to seem fine for the Mozilla Wiki. Web Compatibility is a Mozilla project and those pages document how to contribute to it. As I'm responding to this, I'm realizing that the section distinguishing what content belongs on MDN and what belongs on Mozilla Wiki needs further work. Do others have a good way to describe the delineation between the technical information that should go on MDN vs Mozilla Wiki? [[User:Ckoehler|Christie Koehler (ckoehler)]] ([[User talk:Ckoehler|talk]]) 16:52, 9 May 2014 (PDT)<br />
<br />
: Developer documentation can be confusing to think about because it's both produced and consumed by developers. In short, product documentation goes on MDN; process documentation goes on the wiki. In open source, the source code is part of the product, so things like building and debugging instructions are product documentation. Process documentation includes things like product plans and roadmaps, team meeting notes, bugzilla workflows, etc. Another way to think about it: MDN documents how to interact with code; the wiki documents how to interact with teams. For Karl's examples, I'd say that the Guide is a process doc (people interaction) and the Updating doc is a product doc (code interaction) that would go under the Mozilla Build section on MDN. [[User:Jswisher|Jswisher]] ([[User talk:Jswisher|talk]]) 10:23, 14 May 2014 (PDT)<br />
<br />
'''About WikiMo''': The about page says currently "Governance issues are managed by the WikiMo module, a sub-module of Websites." but it doesn't explain what is WikiMo and the link goes to a table which is not really about Governance. Is there a more appropriate place on the wiki or elsewhere? [[User:Karlcow|Karlcow]] ([[User talk:Karlcow|talk]]) 15:46, 9 May 2014 (PDT)<br />
<br />
'''David's comments''': The only thing that I’d add to the scope is that I think it’d be good to apply a bit of a product/UX lens to the wiki as a community infrastructure, because I believe it will result in more use, more people caring and valuing it, and a general virtuous cycle. Wikis in my experience work if a) the content is well gardened (just like any “content” site), and b) people find authoring & editing to be a fun, pleasant, productive experience (just like any other authoring product). Just because we say it's where stuff “should be” isn’t enough. To that end, I’ll opine that:<br />
<br />
* performance of an editing tool is critical to its continued use — it’s true for IDEs, it’s true for word processors, and it’s a place where wikis have traditionally been fairly weak, because of their dawn in the earliest age of CGI, etc. I have the impression that perf on wiki.m.o writes has gone up, and that’s great, and we need to do more to improve perceived perf. As a thought-provoking point: editing an etherpad feels 100x faster to me (even if it’s obviously different).<br />
* we need to encourage, train, and recognize & herald wiki gardeners. (Matt Thompson for example is doing a _stellar_ job of doing that and teaching others how to do that for Webmaker content).<br />
: -- Agreed, and already part of our discussions in the Wiki Working Group. [[User:Ckoehler|Christie Koehler (ckoehler)]] ([[User talk:Ckoehler|talk]]) 16:39, 9 May 2014 (PDT)<br />
* there’s a lot about wikimedia which feels hasn’t really kept up with our collective expectations around authoring environments. Case sensitivity of pages; wikimedia markup in general, clunky authoring environments, etc. There may be more configuration tweaks & add-ons that we could deploy, I’m not an expert there. <br />
: -- Some of this is due to technical debt due to neglect on our end and will get better with time as we bring things more up to date now that we have a dedicate resource working on the wiki. [[User:Ckoehler|Christie Koehler (ckoehler)]] ([[User talk:Ckoehler|talk]]) 16:39, 9 May 2014 (PDT)<br />
* the default skin is way better than it used to be and the pages are less painful to my eye anyway than before — we can still do more.<br />
: Indeed. We're planning to roll out an updated theme this year, one that is compatible with more recent version of MW.<br />
* having someone act as a product manager for wiki.m.o (and for example care and measure things like daily actives, etc. as a metric of utility of the wiki to the org) would be good — anyone can do that, and I and many others would be happy to coach that person on how to be a product manager with a soul if that coaching was desired.<br />
: -- As module owner, I'm also acting as product manager. Happy to have any mentoring you're willing to offer. [[User:Ckoehler|Christie Koehler (ckoehler)]] ([[User talk:Ckoehler|talk]]) 16:39, 9 May 2014 (PDT)<br />
* there are people with wiki.m.o superpowers, and we should figure out how to get those superpowers more evenly distributed. [and make it so that some of the things those folks can do don’t require super-anything]<br />
: -- Indeed, part of the wiki-gardening too. [[User:Ckoehler|Christie Koehler (ckoehler)]] ([[User talk:Ckoehler|talk]]) 16:39, 9 May 2014 (PDT)<br />
* there’s an obvious elephant-in-the-room about wiki.m.o vs. Mana and why we need two. That duality doesn’t bug me too much, but I know it bugs others. Understanding the reason why people use one or the other feels like a good thing to get shared understanding of, even if not everyone will agree w/ the specific decisions.<br />
: -- There needs to be two separate wikis because MoCo needs a resource to store privileged information that can't be public. Mediawiki does that very poorly and recommends that people setup a separate wiki if there is truly privileged information that needs to be separate. We might be able to achieve the same thing if we switched to a confluence-only setup, but that would remove ownership from the Mozilla community, to which I think there are huge downsides. [[User:Ckoehler|Christie Koehler (ckoehler)]] ([[User talk:Ckoehler|talk]]) 16:39, 9 May 2014 (PDT)<br />
[[User:DavidA|DavidA]] ([[User talk:DavidA|talk]]) 16:10, 9 May 2014 (PDT)<br />
<br />
: This is good feedback but not related to the about page. I think Christine wanted feedback about the About page [[User:Karlcow|Karlcow]] ([[User talk:Karlcow|talk]]) 16:12, 9 May 2014 (PDT)<br />
:: This is true. I've answered DavidA's comments inline. If there aren't any objections, I'll move his comments and the associated responses to this [[Contribute/Education/Wiki_Working_Group/Sandbox | Sandbox]] we have for collecting feedback. [[User:Ckoehler|Christie Koehler (ckoehler)]] ([[User talk:Ckoehler|talk]]) 16:39, 9 May 2014 (PDT)<br />
<br />
'''DavidB's comments''': Just one thing that occurred to me was around possibly needing to add an additional part to the section of who owns different parts of the wiki. There are some pages, like the main page, where the content isn't open for anyone to edit. I'm not entirely sure who can edit the main page or how I could become one of those people if I wanted to. It might be worth having a 'protected content' item to call that out.<br />
<br />
: Noted. I'll add something about protected pages. We don't yet have documentation on the process for becoming a user with administrative rights, nor have we audited our current user lists to see if they still make sense. Would you be okay moving forward with this policy while we are still figuring that out? Once we do, we can update it with a link to the appropriate information. [[User:Ckoehler|Christie Koehler (ckoehler)]] ([[User talk:Ckoehler|talk]]) 16:26, 9 May 2014 (PDT)<br />
<br />
'''Gerv's comments:''' Firstly, thanks for taking this on. The wiki is a vital resource and it's great to see it getting love. Comments on this page:<br />
<br />
The word "comprehensive" is in the purpose. That would suggest that the wiki needs to contain information about everything. The use of the term "encyclopaedia" also suggests this. I think that's actually an anti-goal, and I suspect you do too - we have better places for some info, like SUMO or MDN. It also seems to suggest that if the wiki is missing information on some topic, there is an obligation on someone to provide that information, to achieve comprehensiveness. I'm not sure that's true either.<br />
<br />
An alternate take: I would define the purpose of the Mozilla wiki as: "A low-barrier-to-entry place for Mozillians to choose to store dynamic but long-term-relevant information about Mozilla products, initiatives and sub-projects."<br />
<br />
"Dynamic" is its distinctive over www.mozilla.org. "long-term-relevant" is its distinctive over IRC or Etherpad. The wiki fits into an important niche between the permanance of one and the real-time collaborativeness of the other.<br />
<br />
[[User:Gerv|Gerv]] ([[User talk:Gerv|talk]]) 05:51, 13 May 2014 (PDT)<br />
<br />
: -- I think Gerv's distinction is really spot on: dynamic(wikimo) vs static (mdn) but both long-term-relevant. This is very important because the line between documentation in general and documentation for (new) contributors for a specific team is really thin, IMO. So the criteria dynamic and long-term-relevant seem a good way to guide the user in deciding. (The two cents of a new contributor who fought a bit to navigate the mare magnum of mozilla's documentation on contributing :))<br />
[[User:Madamezou|Madamezou]] ([[User talk:Madamezou|talk]]) 09:05, 18 May 2014 (PDT)<br />
<br />
'''Joelle's comments:''' Does the About page need to be written in a specific tone or language? As a new contributor to WikiMo, the Purpose and How is the Wiki… statements still seem a bit opaque and removed. I wonder if we can incorporate the language used in Wiki Working Group meetings into this About. Last Wiki Working Group meeting the wiki was described as "the innards" of an organization. That term clarified a few questions I had about the scope of WikiMo. It implies what is already stated on the About page in a more inviting way: that the Wiki is a publicly available internal platform; that it makes public information neither designed nor intended for end-users. While I understand that "innards" might not connote the same meaning for some readers, can we consider a tone that is more inviting, yet pithy?<br />
[[User:Jo as Queeniebee|Jo as Queeniebee]] ([[User talk:Jo as Queeniebee|talk]]) 17:02, 13 May 2014 (PDT)<br />
<br />
'''Tristan's comments:'''Very happy to see some effort put into the Wiki! I agree with its central role as a tool for participation and memory of the project along with Bugzilla. Nothing to add at this point but will do if anything comes up. Keep up the good work! [[User:Tnitot|Tnitot]] ([[User talk:Tnitot|talk]]) 02:58, 14 May 2014 (PDT)<br />
<br />
'''Mitchell's comments:''' I echo the appreciation for taking on these topics. I have a couple of questions. First, I wonder if the two purposes are complementary or at odds with each other. One is to the encyclopedia reference, the other is to facilitate interaction. I can imagine both working well if there is very clear separation and wiki-care. There's probably some development of good practices and some sustaining grass-roots encouragement of a good separation of these two activities as well. You may well already have thoughts about this, so I'll stop here.<br />
<br />
Secondly, it would also help me to get a clear picture of how the wiki relates to other workflows and results. Right now teams use a whole variety of tools to collaborate. I'll give a few examples here. The goal isn't to be picky; it's to give an idea of the kinds of questions I can see developing. If a team uses etherpads or google docs for example, how do we think about the relationship of that output to the wiki? If we have an official blog post, how does that relate to the wiki? A very specific example -- we just made statements about DRM and our products in the Mozilla blog. Would someone add something to wikiMO to point to that content? or copy it in the wiki? or is that kind of content outside the scope? <br />
<br />
And on a related note, are you thinking people will maintain wikiMO as a resource, or more of asking Mozillians to use the wiki as a workplace to create the encyclopedia?<br />
<br />
<>[[User:MitchellBaker|mitchell@mozilla.org]] ([[User talk:MitchellBaker|talk]]) 22:43, 20 May 2014 (PDT)</></div>MitchellBakerhttps://wiki.mozilla.org/index.php?title=Manifesto/1.0_Comparisons&diff=752418Manifesto/1.0 Comparisons2013-11-06T02:42:06Z<p>MitchellBaker: /* Comma Removal #10 */</p>
<hr />
<div>__NOTOC__<br />
<br />
It has been decided to have a Twitter English "translation" of the Manifesto. Now we have to decide which of the recently-proposed changes should be made in the Original Version, and which should be made only in the Twitter Version. Where needed, we've split the proposed changes for a principle into multiple independent items, so that they can be judged individually.<br />
<br />
==Changes Not Part of This Comparison==<br />
<br />
From the [[Manifesto/1.0_Changes|1.0 Changes]] document, we have already accepted and so are not considering:<br />
<br />
* Include explicit reference to privacy in #4<br />
* Beef up references to "web literacy" in #5<br />
<br />
'''Rationale''': These two changes were previously approved and will be made to both the Original Version and Twitter Version without further discussion.<br />
<br />
==Shortened Versions==<br />
<br />
'''Rationale''':There are three principles that in their original versions are longer than 118 characters. They need to be shortened for the Twitter English version to no more than 118 characters. (Note that the numbers in parentheses are character counts.) It needs to be decided whether these changes should also be made in the Original Version. The argument for changing them in both versions is that brevity leads to less wordy pages and increased engagement.<br />
<br />
===Shorten Principle #1===<br />
<br />
'''Original''': The Internet is an integral part of modern life—a key component in education, communication, collaboration, business, entertainment and society as a whole. (157)<br />
<br />
'''Altered''': The Internet is integral to modern life: education, communication, collaboration, business, entertainment and society. (118)<br />
<br />
Gerv and Stacy recommend: Twitter only. This list of things are possible without the internet, so the word "part" is significant. We don't want to make over-broad claims.<br />
<br />
Mitchell: I think the altered claim is probably true, but the manifesto should be relevent even for people who think "part" is necessary, so I agree with the recommendation.<br />
<br />
===Shorten Principle #6===<br />
<br />
'''Original''': The effectiveness of the Internet as a public resource depends upon interoperability (protocols, data formats, content), innovation and decentralized participation worldwide. (174)<br />
<br />
'''Altered''': As a public resource, the Internet depends on interoperability, innovation and decentralized participation worldwide. (118)<br />
<br />
Gerv and Stacy recommend: Twitter only. Removing "effectiveness" does alter the meaning.<br />
<br />
Mitchell: Agree re "effectiveness." Also find the original sentence to be easier to read and understand. Agree with the recommendation.<br />
<br />
===Shorten Principle #9===<br />
<br />
'''Original''': Commercial involvement in the development of the Internet brings many benefits; a balance between commercial goals and public benefit is critical. (146)<br />
<br />
'''Altered''': A balance between commercial profit and public benefit is critical to the development of the Internet. (105)<br />
<br />
Gerv and Stacy recommend: Twitter only. The shorter version says something a bit different to the longer one.<br />
<br />
Mitchell: Agree with the recommendation.<br />
<br />
==Other Proposed Changes==<br />
<br />
===Removal of 'Individuals'===<br />
<br />
'''Rationale''': Additional words that are not central to the meaning can be removed to make the Manifesto crisper. In #4, the word "Individuals'" can be removed. This has the added benefit of further differentiating the first word of #4 from the first word of #5.<br />
<br />
'''Approved #4''': Individuals' security and privacy on the Internet are fundamental and cannot be treated as optional.<br />
<br />
'''Altered #4''': Security and privacy on the Internet are fundamental and cannot be treated as optional.<br />
<br />
Gerv and Stacy recommend: neither. A focus on individuals here sharpens the principle; you can't then say the manifesto is simply arguing for anebulous "more security". And we don't need this for length reasons.<br />
<br />
Mitchell: Agree with recommendation. Keeping a focus on the individual human experience adds value.<br />
<br />
===Consistent Use of "Must" and "Must Not" ===<br />
<br />
'''Rationale''': Principles #2 and #5 set the tone by using "must", yet #3 uses "should" and #4 uses "cannot". Principles are thought to be stronger and crisper if all four use "must" or "must not".<br />
<br />
'''Original #3''': The Internet should enrich the lives of individual human beings.<br />
<br />
'''Altered #3''': The Internet must enrich the lives of individual human beings.<br />
<br />
'''Approved #4''': Individuals' security and privacy on the Internet are fundamental and cannot be treated as optional.<br />
<br />
'''Altered #4''': Individuals' security and privacy on the Internet are fundamental and must not be treated as optional.<br />
<br />
Gerv and Stacy recommend: both. Consistency is good, as is strength.<br />
<br />
Mitchell: Altered #4 seems better to me; agree here. Altered number 3 feels a bit weird. But I agree with the consistency piece. So agree with the recommendation of changing both.<br />
<br />
===Change 'goals' to 'profit'===<br />
<br />
'''Rationale''': "Commercial profit" and "public benefit" contrast much better than "commercial goals" and "public benefit".<br />
<br />
'''Original #9''': Commercial involvement in the development of the Internet brings many benefits; a balance between commercial goals and public benefit is critical.<br />
<br />
'''Altered #9''': Commercial involvement in the development of the Internet brings many benefits; a balance between commercial profit and public benefit is critical.<br />
<br />
Gerv and Stacy recommend: both.<br />
<br />
Mitchell: There are a bunch of nuances here, but I think this change is good. Commercial goals could include great user experience, etc, but the piece we want to balance is where the benefit ("profit" in a larger, non-monetary sense, e.g., "benefit") accrues.<br />
So, agree with recommendation.<br />
<br />
===Comma Removal #5===<br />
<br />
'''Rationale''': Removing commas can make the text crisper and in some cases make the meaning clearer.<br />
<br />
'''Approved #5''': Individuals must have the ability to shape the Internet, and their own experiences on it.<br />
<br />
'''Altered #5''': Individuals must have the ability to shape the Internet and their own experiences on it.<br />
<br />
Gerv and Stacy recommend: neither. In this case, the word "it" refers back to "Internet", and so putting the noun in a different clause from the pronoun reads better. Also, it's two related thoughts, so punctuation to separate them is appropriate.<br />
<br />
===Comma Removal #8===<br />
<br />
'''Rationale''': 'Oxford comma' is removed for consistency with the other principles. <br />
<br />
'''Original #8''': Transparent community-based processes promote participation, accountability, and trust.<br />
<br />
'''Altered #8''': Transparent community-based processes promote participation, accountability and trust.<br />
<br />
Gerv and Stacy recommend: both. Consistency is good.<br />
<br />
Mitchell: hah, i learned comma etiquette in law school, and perhaps acceptable style guides have changed even there. OK with recommendation.<br />
<br />
===Comma Removal #10===<br />
<br />
'''Rationale''': Removing commas can make the text crisper and in some cases make the meaning clearer.<br />
<br />
'''Original #10''': Magnifying the public benefit aspects of the Internet is an important goal, worthy of time, attention and commitment.<br />
<br />
'''Altered #10''': Magnifying the public benefit aspects of the Internet is an important goal worthy of time, attention and commitment.<br />
<br />
Gerv and Stacy recommend: neither. The mental pause caused by the comma is useful in parsing the sentence.<br />
<br />
Mitchell: OK either way, happy to defer to your sense of ease of parsing. So OK with recommendation.</div>MitchellBakerhttps://wiki.mozilla.org/index.php?title=Manifesto/1.0_Comparisons&diff=752417Manifesto/1.0 Comparisons2013-11-06T02:40:59Z<p>MitchellBaker: /* Comma Removal #8 */</p>
<hr />
<div>__NOTOC__<br />
<br />
It has been decided to have a Twitter English "translation" of the Manifesto. Now we have to decide which of the recently-proposed changes should be made in the Original Version, and which should be made only in the Twitter Version. Where needed, we've split the proposed changes for a principle into multiple independent items, so that they can be judged individually.<br />
<br />
==Changes Not Part of This Comparison==<br />
<br />
From the [[Manifesto/1.0_Changes|1.0 Changes]] document, we have already accepted and so are not considering:<br />
<br />
* Include explicit reference to privacy in #4<br />
* Beef up references to "web literacy" in #5<br />
<br />
'''Rationale''': These two changes were previously approved and will be made to both the Original Version and Twitter Version without further discussion.<br />
<br />
==Shortened Versions==<br />
<br />
'''Rationale''':There are three principles that in their original versions are longer than 118 characters. They need to be shortened for the Twitter English version to no more than 118 characters. (Note that the numbers in parentheses are character counts.) It needs to be decided whether these changes should also be made in the Original Version. The argument for changing them in both versions is that brevity leads to less wordy pages and increased engagement.<br />
<br />
===Shorten Principle #1===<br />
<br />
'''Original''': The Internet is an integral part of modern life—a key component in education, communication, collaboration, business, entertainment and society as a whole. (157)<br />
<br />
'''Altered''': The Internet is integral to modern life: education, communication, collaboration, business, entertainment and society. (118)<br />
<br />
Gerv and Stacy recommend: Twitter only. This list of things are possible without the internet, so the word "part" is significant. We don't want to make over-broad claims.<br />
<br />
Mitchell: I think the altered claim is probably true, but the manifesto should be relevent even for people who think "part" is necessary, so I agree with the recommendation.<br />
<br />
===Shorten Principle #6===<br />
<br />
'''Original''': The effectiveness of the Internet as a public resource depends upon interoperability (protocols, data formats, content), innovation and decentralized participation worldwide. (174)<br />
<br />
'''Altered''': As a public resource, the Internet depends on interoperability, innovation and decentralized participation worldwide. (118)<br />
<br />
Gerv and Stacy recommend: Twitter only. Removing "effectiveness" does alter the meaning.<br />
<br />
Mitchell: Agree re "effectiveness." Also find the original sentence to be easier to read and understand. Agree with the recommendation.<br />
<br />
===Shorten Principle #9===<br />
<br />
'''Original''': Commercial involvement in the development of the Internet brings many benefits; a balance between commercial goals and public benefit is critical. (146)<br />
<br />
'''Altered''': A balance between commercial profit and public benefit is critical to the development of the Internet. (105)<br />
<br />
Gerv and Stacy recommend: Twitter only. The shorter version says something a bit different to the longer one.<br />
<br />
Mitchell: Agree with the recommendation.<br />
<br />
==Other Proposed Changes==<br />
<br />
===Removal of 'Individuals'===<br />
<br />
'''Rationale''': Additional words that are not central to the meaning can be removed to make the Manifesto crisper. In #4, the word "Individuals'" can be removed. This has the added benefit of further differentiating the first word of #4 from the first word of #5.<br />
<br />
'''Approved #4''': Individuals' security and privacy on the Internet are fundamental and cannot be treated as optional.<br />
<br />
'''Altered #4''': Security and privacy on the Internet are fundamental and cannot be treated as optional.<br />
<br />
Gerv and Stacy recommend: neither. A focus on individuals here sharpens the principle; you can't then say the manifesto is simply arguing for anebulous "more security". And we don't need this for length reasons.<br />
<br />
Mitchell: Agree with recommendation. Keeping a focus on the individual human experience adds value.<br />
<br />
===Consistent Use of "Must" and "Must Not" ===<br />
<br />
'''Rationale''': Principles #2 and #5 set the tone by using "must", yet #3 uses "should" and #4 uses "cannot". Principles are thought to be stronger and crisper if all four use "must" or "must not".<br />
<br />
'''Original #3''': The Internet should enrich the lives of individual human beings.<br />
<br />
'''Altered #3''': The Internet must enrich the lives of individual human beings.<br />
<br />
'''Approved #4''': Individuals' security and privacy on the Internet are fundamental and cannot be treated as optional.<br />
<br />
'''Altered #4''': Individuals' security and privacy on the Internet are fundamental and must not be treated as optional.<br />
<br />
Gerv and Stacy recommend: both. Consistency is good, as is strength.<br />
<br />
Mitchell: Altered #4 seems better to me; agree here. Altered number 3 feels a bit weird. But I agree with the consistency piece. So agree with the recommendation of changing both.<br />
<br />
===Change 'goals' to 'profit'===<br />
<br />
'''Rationale''': "Commercial profit" and "public benefit" contrast much better than "commercial goals" and "public benefit".<br />
<br />
'''Original #9''': Commercial involvement in the development of the Internet brings many benefits; a balance between commercial goals and public benefit is critical.<br />
<br />
'''Altered #9''': Commercial involvement in the development of the Internet brings many benefits; a balance between commercial profit and public benefit is critical.<br />
<br />
Gerv and Stacy recommend: both.<br />
<br />
Mitchell: There are a bunch of nuances here, but I think this change is good. Commercial goals could include great user experience, etc, but the piece we want to balance is where the benefit ("profit" in a larger, non-monetary sense, e.g., "benefit") accrues.<br />
So, agree with recommendation.<br />
<br />
===Comma Removal #5===<br />
<br />
'''Rationale''': Removing commas can make the text crisper and in some cases make the meaning clearer.<br />
<br />
'''Approved #5''': Individuals must have the ability to shape the Internet, and their own experiences on it.<br />
<br />
'''Altered #5''': Individuals must have the ability to shape the Internet and their own experiences on it.<br />
<br />
Gerv and Stacy recommend: neither. In this case, the word "it" refers back to "Internet", and so putting the noun in a different clause from the pronoun reads better. Also, it's two related thoughts, so punctuation to separate them is appropriate.<br />
<br />
===Comma Removal #8===<br />
<br />
'''Rationale''': 'Oxford comma' is removed for consistency with the other principles. <br />
<br />
'''Original #8''': Transparent community-based processes promote participation, accountability, and trust.<br />
<br />
'''Altered #8''': Transparent community-based processes promote participation, accountability and trust.<br />
<br />
Gerv and Stacy recommend: both. Consistency is good.<br />
<br />
Mitchell: hah, i learned comma etiquette in law school, and perhaps acceptable style guides have changed even there. OK with recommendation.<br />
<br />
===Comma Removal #10===<br />
<br />
'''Rationale''': Removing commas can make the text crisper and in some cases make the meaning clearer.<br />
<br />
'''Original #10''': Magnifying the public benefit aspects of the Internet is an important goal, worthy of time, attention and commitment.<br />
<br />
'''Altered #10''': Magnifying the public benefit aspects of the Internet is an important goal worthy of time, attention and commitment.<br />
<br />
Gerv and Stacy recommend: neither. The mental pause caused by the comma is useful in parsing the sentence.</div>MitchellBakerhttps://wiki.mozilla.org/index.php?title=Manifesto/1.0_Comparisons&diff=752414Manifesto/1.0 Comparisons2013-11-06T02:39:05Z<p>MitchellBaker: /* Change 'goals' to 'profit' */</p>
<hr />
<div>__NOTOC__<br />
<br />
It has been decided to have a Twitter English "translation" of the Manifesto. Now we have to decide which of the recently-proposed changes should be made in the Original Version, and which should be made only in the Twitter Version. Where needed, we've split the proposed changes for a principle into multiple independent items, so that they can be judged individually.<br />
<br />
==Changes Not Part of This Comparison==<br />
<br />
From the [[Manifesto/1.0_Changes|1.0 Changes]] document, we have already accepted and so are not considering:<br />
<br />
* Include explicit reference to privacy in #4<br />
* Beef up references to "web literacy" in #5<br />
<br />
'''Rationale''': These two changes were previously approved and will be made to both the Original Version and Twitter Version without further discussion.<br />
<br />
==Shortened Versions==<br />
<br />
'''Rationale''':There are three principles that in their original versions are longer than 118 characters. They need to be shortened for the Twitter English version to no more than 118 characters. (Note that the numbers in parentheses are character counts.) It needs to be decided whether these changes should also be made in the Original Version. The argument for changing them in both versions is that brevity leads to less wordy pages and increased engagement.<br />
<br />
===Shorten Principle #1===<br />
<br />
'''Original''': The Internet is an integral part of modern life—a key component in education, communication, collaboration, business, entertainment and society as a whole. (157)<br />
<br />
'''Altered''': The Internet is integral to modern life: education, communication, collaboration, business, entertainment and society. (118)<br />
<br />
Gerv and Stacy recommend: Twitter only. This list of things are possible without the internet, so the word "part" is significant. We don't want to make over-broad claims.<br />
<br />
Mitchell: I think the altered claim is probably true, but the manifesto should be relevent even for people who think "part" is necessary, so I agree with the recommendation.<br />
<br />
===Shorten Principle #6===<br />
<br />
'''Original''': The effectiveness of the Internet as a public resource depends upon interoperability (protocols, data formats, content), innovation and decentralized participation worldwide. (174)<br />
<br />
'''Altered''': As a public resource, the Internet depends on interoperability, innovation and decentralized participation worldwide. (118)<br />
<br />
Gerv and Stacy recommend: Twitter only. Removing "effectiveness" does alter the meaning.<br />
<br />
Mitchell: Agree re "effectiveness." Also find the original sentence to be easier to read and understand. Agree with the recommendation.<br />
<br />
===Shorten Principle #9===<br />
<br />
'''Original''': Commercial involvement in the development of the Internet brings many benefits; a balance between commercial goals and public benefit is critical. (146)<br />
<br />
'''Altered''': A balance between commercial profit and public benefit is critical to the development of the Internet. (105)<br />
<br />
Gerv and Stacy recommend: Twitter only. The shorter version says something a bit different to the longer one.<br />
<br />
Mitchell: Agree with the recommendation.<br />
<br />
==Other Proposed Changes==<br />
<br />
===Removal of 'Individuals'===<br />
<br />
'''Rationale''': Additional words that are not central to the meaning can be removed to make the Manifesto crisper. In #4, the word "Individuals'" can be removed. This has the added benefit of further differentiating the first word of #4 from the first word of #5.<br />
<br />
'''Approved #4''': Individuals' security and privacy on the Internet are fundamental and cannot be treated as optional.<br />
<br />
'''Altered #4''': Security and privacy on the Internet are fundamental and cannot be treated as optional.<br />
<br />
Gerv and Stacy recommend: neither. A focus on individuals here sharpens the principle; you can't then say the manifesto is simply arguing for anebulous "more security". And we don't need this for length reasons.<br />
<br />
Mitchell: Agree with recommendation. Keeping a focus on the individual human experience adds value.<br />
<br />
===Consistent Use of "Must" and "Must Not" ===<br />
<br />
'''Rationale''': Principles #2 and #5 set the tone by using "must", yet #3 uses "should" and #4 uses "cannot". Principles are thought to be stronger and crisper if all four use "must" or "must not".<br />
<br />
'''Original #3''': The Internet should enrich the lives of individual human beings.<br />
<br />
'''Altered #3''': The Internet must enrich the lives of individual human beings.<br />
<br />
'''Approved #4''': Individuals' security and privacy on the Internet are fundamental and cannot be treated as optional.<br />
<br />
'''Altered #4''': Individuals' security and privacy on the Internet are fundamental and must not be treated as optional.<br />
<br />
Gerv and Stacy recommend: both. Consistency is good, as is strength.<br />
<br />
Mitchell: Altered #4 seems better to me; agree here. Altered number 3 feels a bit weird. But I agree with the consistency piece. So agree with the recommendation of changing both.<br />
<br />
===Change 'goals' to 'profit'===<br />
<br />
'''Rationale''': "Commercial profit" and "public benefit" contrast much better than "commercial goals" and "public benefit".<br />
<br />
'''Original #9''': Commercial involvement in the development of the Internet brings many benefits; a balance between commercial goals and public benefit is critical.<br />
<br />
'''Altered #9''': Commercial involvement in the development of the Internet brings many benefits; a balance between commercial profit and public benefit is critical.<br />
<br />
Gerv and Stacy recommend: both.<br />
<br />
Mitchell: There are a bunch of nuances here, but I think this change is good. Commercial goals could include great user experience, etc, but the piece we want to balance is where the benefit ("profit" in a larger, non-monetary sense, e.g., "benefit") accrues.<br />
So, agree with recommendation.<br />
<br />
===Comma Removal #5===<br />
<br />
'''Rationale''': Removing commas can make the text crisper and in some cases make the meaning clearer.<br />
<br />
'''Approved #5''': Individuals must have the ability to shape the Internet, and their own experiences on it.<br />
<br />
'''Altered #5''': Individuals must have the ability to shape the Internet and their own experiences on it.<br />
<br />
Gerv and Stacy recommend: neither. In this case, the word "it" refers back to "Internet", and so putting the noun in a different clause from the pronoun reads better. Also, it's two related thoughts, so punctuation to separate them is appropriate.<br />
<br />
===Comma Removal #8===<br />
<br />
'''Rationale''': 'Oxford comma' is removed for consistency with the other principles. <br />
<br />
'''Original #8''': Transparent community-based processes promote participation, accountability, and trust.<br />
<br />
'''Altered #8''': Transparent community-based processes promote participation, accountability and trust.<br />
<br />
Gerv and Stacy recommend: both. Consistency is good.<br />
<br />
===Comma Removal #10===<br />
<br />
'''Rationale''': Removing commas can make the text crisper and in some cases make the meaning clearer.<br />
<br />
'''Original #10''': Magnifying the public benefit aspects of the Internet is an important goal, worthy of time, attention and commitment.<br />
<br />
'''Altered #10''': Magnifying the public benefit aspects of the Internet is an important goal worthy of time, attention and commitment.<br />
<br />
Gerv and Stacy recommend: neither. The mental pause caused by the comma is useful in parsing the sentence.</div>MitchellBakerhttps://wiki.mozilla.org/index.php?title=Manifesto/1.0_Comparisons&diff=752413Manifesto/1.0 Comparisons2013-11-06T02:36:08Z<p>MitchellBaker: /* Consistent Use of "Must" and "Must Not" */</p>
<hr />
<div>__NOTOC__<br />
<br />
It has been decided to have a Twitter English "translation" of the Manifesto. Now we have to decide which of the recently-proposed changes should be made in the Original Version, and which should be made only in the Twitter Version. Where needed, we've split the proposed changes for a principle into multiple independent items, so that they can be judged individually.<br />
<br />
==Changes Not Part of This Comparison==<br />
<br />
From the [[Manifesto/1.0_Changes|1.0 Changes]] document, we have already accepted and so are not considering:<br />
<br />
* Include explicit reference to privacy in #4<br />
* Beef up references to "web literacy" in #5<br />
<br />
'''Rationale''': These two changes were previously approved and will be made to both the Original Version and Twitter Version without further discussion.<br />
<br />
==Shortened Versions==<br />
<br />
'''Rationale''':There are three principles that in their original versions are longer than 118 characters. They need to be shortened for the Twitter English version to no more than 118 characters. (Note that the numbers in parentheses are character counts.) It needs to be decided whether these changes should also be made in the Original Version. The argument for changing them in both versions is that brevity leads to less wordy pages and increased engagement.<br />
<br />
===Shorten Principle #1===<br />
<br />
'''Original''': The Internet is an integral part of modern life—a key component in education, communication, collaboration, business, entertainment and society as a whole. (157)<br />
<br />
'''Altered''': The Internet is integral to modern life: education, communication, collaboration, business, entertainment and society. (118)<br />
<br />
Gerv and Stacy recommend: Twitter only. This list of things are possible without the internet, so the word "part" is significant. We don't want to make over-broad claims.<br />
<br />
Mitchell: I think the altered claim is probably true, but the manifesto should be relevent even for people who think "part" is necessary, so I agree with the recommendation.<br />
<br />
===Shorten Principle #6===<br />
<br />
'''Original''': The effectiveness of the Internet as a public resource depends upon interoperability (protocols, data formats, content), innovation and decentralized participation worldwide. (174)<br />
<br />
'''Altered''': As a public resource, the Internet depends on interoperability, innovation and decentralized participation worldwide. (118)<br />
<br />
Gerv and Stacy recommend: Twitter only. Removing "effectiveness" does alter the meaning.<br />
<br />
Mitchell: Agree re "effectiveness." Also find the original sentence to be easier to read and understand. Agree with the recommendation.<br />
<br />
===Shorten Principle #9===<br />
<br />
'''Original''': Commercial involvement in the development of the Internet brings many benefits; a balance between commercial goals and public benefit is critical. (146)<br />
<br />
'''Altered''': A balance between commercial profit and public benefit is critical to the development of the Internet. (105)<br />
<br />
Gerv and Stacy recommend: Twitter only. The shorter version says something a bit different to the longer one.<br />
<br />
Mitchell: Agree with the recommendation.<br />
<br />
==Other Proposed Changes==<br />
<br />
===Removal of 'Individuals'===<br />
<br />
'''Rationale''': Additional words that are not central to the meaning can be removed to make the Manifesto crisper. In #4, the word "Individuals'" can be removed. This has the added benefit of further differentiating the first word of #4 from the first word of #5.<br />
<br />
'''Approved #4''': Individuals' security and privacy on the Internet are fundamental and cannot be treated as optional.<br />
<br />
'''Altered #4''': Security and privacy on the Internet are fundamental and cannot be treated as optional.<br />
<br />
Gerv and Stacy recommend: neither. A focus on individuals here sharpens the principle; you can't then say the manifesto is simply arguing for anebulous "more security". And we don't need this for length reasons.<br />
<br />
Mitchell: Agree with recommendation. Keeping a focus on the individual human experience adds value.<br />
<br />
===Consistent Use of "Must" and "Must Not" ===<br />
<br />
'''Rationale''': Principles #2 and #5 set the tone by using "must", yet #3 uses "should" and #4 uses "cannot". Principles are thought to be stronger and crisper if all four use "must" or "must not".<br />
<br />
'''Original #3''': The Internet should enrich the lives of individual human beings.<br />
<br />
'''Altered #3''': The Internet must enrich the lives of individual human beings.<br />
<br />
'''Approved #4''': Individuals' security and privacy on the Internet are fundamental and cannot be treated as optional.<br />
<br />
'''Altered #4''': Individuals' security and privacy on the Internet are fundamental and must not be treated as optional.<br />
<br />
Gerv and Stacy recommend: both. Consistency is good, as is strength.<br />
<br />
Mitchell: Altered #4 seems better to me; agree here. Altered number 3 feels a bit weird. But I agree with the consistency piece. So agree with the recommendation of changing both.<br />
<br />
===Change 'goals' to 'profit'===<br />
<br />
'''Rationale''': "Commercial profit" and "public benefit" contrast much better than "commercial goals" and "public benefit".<br />
<br />
'''Original #9''': Commercial involvement in the development of the Internet brings many benefits; a balance between commercial goals and public benefit is critical.<br />
<br />
'''Altered #9''': Commercial involvement in the development of the Internet brings many benefits; a balance between commercial profit and public benefit is critical.<br />
<br />
Gerv and Stacy recommend: both.<br />
<br />
===Comma Removal #5===<br />
<br />
'''Rationale''': Removing commas can make the text crisper and in some cases make the meaning clearer.<br />
<br />
'''Approved #5''': Individuals must have the ability to shape the Internet, and their own experiences on it.<br />
<br />
'''Altered #5''': Individuals must have the ability to shape the Internet and their own experiences on it.<br />
<br />
Gerv and Stacy recommend: neither. In this case, the word "it" refers back to "Internet", and so putting the noun in a different clause from the pronoun reads better. Also, it's two related thoughts, so punctuation to separate them is appropriate.<br />
<br />
===Comma Removal #8===<br />
<br />
'''Rationale''': 'Oxford comma' is removed for consistency with the other principles. <br />
<br />
'''Original #8''': Transparent community-based processes promote participation, accountability, and trust.<br />
<br />
'''Altered #8''': Transparent community-based processes promote participation, accountability and trust.<br />
<br />
Gerv and Stacy recommend: both. Consistency is good.<br />
<br />
===Comma Removal #10===<br />
<br />
'''Rationale''': Removing commas can make the text crisper and in some cases make the meaning clearer.<br />
<br />
'''Original #10''': Magnifying the public benefit aspects of the Internet is an important goal, worthy of time, attention and commitment.<br />
<br />
'''Altered #10''': Magnifying the public benefit aspects of the Internet is an important goal worthy of time, attention and commitment.<br />
<br />
Gerv and Stacy recommend: neither. The mental pause caused by the comma is useful in parsing the sentence.</div>MitchellBakerhttps://wiki.mozilla.org/index.php?title=Manifesto/1.0_Comparisons&diff=752410Manifesto/1.0 Comparisons2013-11-06T02:34:25Z<p>MitchellBaker: /* Removal of 'Individuals' */</p>
<hr />
<div>__NOTOC__<br />
<br />
It has been decided to have a Twitter English "translation" of the Manifesto. Now we have to decide which of the recently-proposed changes should be made in the Original Version, and which should be made only in the Twitter Version. Where needed, we've split the proposed changes for a principle into multiple independent items, so that they can be judged individually.<br />
<br />
==Changes Not Part of This Comparison==<br />
<br />
From the [[Manifesto/1.0_Changes|1.0 Changes]] document, we have already accepted and so are not considering:<br />
<br />
* Include explicit reference to privacy in #4<br />
* Beef up references to "web literacy" in #5<br />
<br />
'''Rationale''': These two changes were previously approved and will be made to both the Original Version and Twitter Version without further discussion.<br />
<br />
==Shortened Versions==<br />
<br />
'''Rationale''':There are three principles that in their original versions are longer than 118 characters. They need to be shortened for the Twitter English version to no more than 118 characters. (Note that the numbers in parentheses are character counts.) It needs to be decided whether these changes should also be made in the Original Version. The argument for changing them in both versions is that brevity leads to less wordy pages and increased engagement.<br />
<br />
===Shorten Principle #1===<br />
<br />
'''Original''': The Internet is an integral part of modern life—a key component in education, communication, collaboration, business, entertainment and society as a whole. (157)<br />
<br />
'''Altered''': The Internet is integral to modern life: education, communication, collaboration, business, entertainment and society. (118)<br />
<br />
Gerv and Stacy recommend: Twitter only. This list of things are possible without the internet, so the word "part" is significant. We don't want to make over-broad claims.<br />
<br />
Mitchell: I think the altered claim is probably true, but the manifesto should be relevent even for people who think "part" is necessary, so I agree with the recommendation.<br />
<br />
===Shorten Principle #6===<br />
<br />
'''Original''': The effectiveness of the Internet as a public resource depends upon interoperability (protocols, data formats, content), innovation and decentralized participation worldwide. (174)<br />
<br />
'''Altered''': As a public resource, the Internet depends on interoperability, innovation and decentralized participation worldwide. (118)<br />
<br />
Gerv and Stacy recommend: Twitter only. Removing "effectiveness" does alter the meaning.<br />
<br />
Mitchell: Agree re "effectiveness." Also find the original sentence to be easier to read and understand. Agree with the recommendation.<br />
<br />
===Shorten Principle #9===<br />
<br />
'''Original''': Commercial involvement in the development of the Internet brings many benefits; a balance between commercial goals and public benefit is critical. (146)<br />
<br />
'''Altered''': A balance between commercial profit and public benefit is critical to the development of the Internet. (105)<br />
<br />
Gerv and Stacy recommend: Twitter only. The shorter version says something a bit different to the longer one.<br />
<br />
Mitchell: Agree with the recommendation.<br />
<br />
==Other Proposed Changes==<br />
<br />
===Removal of 'Individuals'===<br />
<br />
'''Rationale''': Additional words that are not central to the meaning can be removed to make the Manifesto crisper. In #4, the word "Individuals'" can be removed. This has the added benefit of further differentiating the first word of #4 from the first word of #5.<br />
<br />
'''Approved #4''': Individuals' security and privacy on the Internet are fundamental and cannot be treated as optional.<br />
<br />
'''Altered #4''': Security and privacy on the Internet are fundamental and cannot be treated as optional.<br />
<br />
Gerv and Stacy recommend: neither. A focus on individuals here sharpens the principle; you can't then say the manifesto is simply arguing for anebulous "more security". And we don't need this for length reasons.<br />
<br />
Mitchell: Agree with recommendation. Keeping a focus on the individual human experience adds value.<br />
<br />
===Consistent Use of "Must" and "Must Not" ===<br />
<br />
'''Rationale''': Principles #2 and #5 set the tone by using "must", yet #3 uses "should" and #4 uses "cannot". Principles are thought to be stronger and crisper if all four use "must" or "must not".<br />
<br />
'''Original #3''': The Internet should enrich the lives of individual human beings.<br />
<br />
'''Altered #3''': The Internet must enrich the lives of individual human beings.<br />
<br />
'''Approved #4''': Individuals' security and privacy on the Internet are fundamental and cannot be treated as optional.<br />
<br />
'''Altered #4''': Individuals' security and privacy on the Internet are fundamental and must not be treated as optional.<br />
<br />
Gerv and Stacy recommend: both. Consistency is good, as is strength.<br />
<br />
===Change 'goals' to 'profit'===<br />
<br />
'''Rationale''': "Commercial profit" and "public benefit" contrast much better than "commercial goals" and "public benefit".<br />
<br />
'''Original #9''': Commercial involvement in the development of the Internet brings many benefits; a balance between commercial goals and public benefit is critical.<br />
<br />
'''Altered #9''': Commercial involvement in the development of the Internet brings many benefits; a balance between commercial profit and public benefit is critical.<br />
<br />
Gerv and Stacy recommend: both.<br />
<br />
===Comma Removal #5===<br />
<br />
'''Rationale''': Removing commas can make the text crisper and in some cases make the meaning clearer.<br />
<br />
'''Approved #5''': Individuals must have the ability to shape the Internet, and their own experiences on it.<br />
<br />
'''Altered #5''': Individuals must have the ability to shape the Internet and their own experiences on it.<br />
<br />
Gerv and Stacy recommend: neither. In this case, the word "it" refers back to "Internet", and so putting the noun in a different clause from the pronoun reads better. Also, it's two related thoughts, so punctuation to separate them is appropriate.<br />
<br />
===Comma Removal #8===<br />
<br />
'''Rationale''': 'Oxford comma' is removed for consistency with the other principles. <br />
<br />
'''Original #8''': Transparent community-based processes promote participation, accountability, and trust.<br />
<br />
'''Altered #8''': Transparent community-based processes promote participation, accountability and trust.<br />
<br />
Gerv and Stacy recommend: both. Consistency is good.<br />
<br />
===Comma Removal #10===<br />
<br />
'''Rationale''': Removing commas can make the text crisper and in some cases make the meaning clearer.<br />
<br />
'''Original #10''': Magnifying the public benefit aspects of the Internet is an important goal, worthy of time, attention and commitment.<br />
<br />
'''Altered #10''': Magnifying the public benefit aspects of the Internet is an important goal worthy of time, attention and commitment.<br />
<br />
Gerv and Stacy recommend: neither. The mental pause caused by the comma is useful in parsing the sentence.</div>MitchellBakerhttps://wiki.mozilla.org/index.php?title=Manifesto/1.0_Comparisons&diff=752408Manifesto/1.0 Comparisons2013-11-06T02:33:22Z<p>MitchellBaker: /* Shorten Principle #9 */</p>
<hr />
<div>__NOTOC__<br />
<br />
It has been decided to have a Twitter English "translation" of the Manifesto. Now we have to decide which of the recently-proposed changes should be made in the Original Version, and which should be made only in the Twitter Version. Where needed, we've split the proposed changes for a principle into multiple independent items, so that they can be judged individually.<br />
<br />
==Changes Not Part of This Comparison==<br />
<br />
From the [[Manifesto/1.0_Changes|1.0 Changes]] document, we have already accepted and so are not considering:<br />
<br />
* Include explicit reference to privacy in #4<br />
* Beef up references to "web literacy" in #5<br />
<br />
'''Rationale''': These two changes were previously approved and will be made to both the Original Version and Twitter Version without further discussion.<br />
<br />
==Shortened Versions==<br />
<br />
'''Rationale''':There are three principles that in their original versions are longer than 118 characters. They need to be shortened for the Twitter English version to no more than 118 characters. (Note that the numbers in parentheses are character counts.) It needs to be decided whether these changes should also be made in the Original Version. The argument for changing them in both versions is that brevity leads to less wordy pages and increased engagement.<br />
<br />
===Shorten Principle #1===<br />
<br />
'''Original''': The Internet is an integral part of modern life—a key component in education, communication, collaboration, business, entertainment and society as a whole. (157)<br />
<br />
'''Altered''': The Internet is integral to modern life: education, communication, collaboration, business, entertainment and society. (118)<br />
<br />
Gerv and Stacy recommend: Twitter only. This list of things are possible without the internet, so the word "part" is significant. We don't want to make over-broad claims.<br />
<br />
Mitchell: I think the altered claim is probably true, but the manifesto should be relevent even for people who think "part" is necessary, so I agree with the recommendation.<br />
<br />
===Shorten Principle #6===<br />
<br />
'''Original''': The effectiveness of the Internet as a public resource depends upon interoperability (protocols, data formats, content), innovation and decentralized participation worldwide. (174)<br />
<br />
'''Altered''': As a public resource, the Internet depends on interoperability, innovation and decentralized participation worldwide. (118)<br />
<br />
Gerv and Stacy recommend: Twitter only. Removing "effectiveness" does alter the meaning.<br />
<br />
Mitchell: Agree re "effectiveness." Also find the original sentence to be easier to read and understand. Agree with the recommendation.<br />
<br />
===Shorten Principle #9===<br />
<br />
'''Original''': Commercial involvement in the development of the Internet brings many benefits; a balance between commercial goals and public benefit is critical. (146)<br />
<br />
'''Altered''': A balance between commercial profit and public benefit is critical to the development of the Internet. (105)<br />
<br />
Gerv and Stacy recommend: Twitter only. The shorter version says something a bit different to the longer one.<br />
<br />
Mitchell: Agree with the recommendation.<br />
<br />
==Other Proposed Changes==<br />
<br />
===Removal of 'Individuals'===<br />
<br />
'''Rationale''': Additional words that are not central to the meaning can be removed to make the Manifesto crisper. In #4, the word "Individuals'" can be removed. This has the added benefit of further differentiating the first word of #4 from the first word of #5.<br />
<br />
'''Approved #4''': Individuals' security and privacy on the Internet are fundamental and cannot be treated as optional.<br />
<br />
'''Altered #4''': Security and privacy on the Internet are fundamental and cannot be treated as optional.<br />
<br />
Gerv and Stacy recommend: neither. A focus on individuals here sharpens the principle; you can't then say the manifesto is simply arguing for anebulous "more security". And we don't need this for length reasons.<br />
<br />
===Consistent Use of "Must" and "Must Not" ===<br />
<br />
'''Rationale''': Principles #2 and #5 set the tone by using "must", yet #3 uses "should" and #4 uses "cannot". Principles are thought to be stronger and crisper if all four use "must" or "must not".<br />
<br />
'''Original #3''': The Internet should enrich the lives of individual human beings.<br />
<br />
'''Altered #3''': The Internet must enrich the lives of individual human beings.<br />
<br />
'''Approved #4''': Individuals' security and privacy on the Internet are fundamental and cannot be treated as optional.<br />
<br />
'''Altered #4''': Individuals' security and privacy on the Internet are fundamental and must not be treated as optional.<br />
<br />
Gerv and Stacy recommend: both. Consistency is good, as is strength.<br />
<br />
===Change 'goals' to 'profit'===<br />
<br />
'''Rationale''': "Commercial profit" and "public benefit" contrast much better than "commercial goals" and "public benefit".<br />
<br />
'''Original #9''': Commercial involvement in the development of the Internet brings many benefits; a balance between commercial goals and public benefit is critical.<br />
<br />
'''Altered #9''': Commercial involvement in the development of the Internet brings many benefits; a balance between commercial profit and public benefit is critical.<br />
<br />
Gerv and Stacy recommend: both.<br />
<br />
===Comma Removal #5===<br />
<br />
'''Rationale''': Removing commas can make the text crisper and in some cases make the meaning clearer.<br />
<br />
'''Approved #5''': Individuals must have the ability to shape the Internet, and their own experiences on it.<br />
<br />
'''Altered #5''': Individuals must have the ability to shape the Internet and their own experiences on it.<br />
<br />
Gerv and Stacy recommend: neither. In this case, the word "it" refers back to "Internet", and so putting the noun in a different clause from the pronoun reads better. Also, it's two related thoughts, so punctuation to separate them is appropriate.<br />
<br />
===Comma Removal #8===<br />
<br />
'''Rationale''': 'Oxford comma' is removed for consistency with the other principles. <br />
<br />
'''Original #8''': Transparent community-based processes promote participation, accountability, and trust.<br />
<br />
'''Altered #8''': Transparent community-based processes promote participation, accountability and trust.<br />
<br />
Gerv and Stacy recommend: both. Consistency is good.<br />
<br />
===Comma Removal #10===<br />
<br />
'''Rationale''': Removing commas can make the text crisper and in some cases make the meaning clearer.<br />
<br />
'''Original #10''': Magnifying the public benefit aspects of the Internet is an important goal, worthy of time, attention and commitment.<br />
<br />
'''Altered #10''': Magnifying the public benefit aspects of the Internet is an important goal worthy of time, attention and commitment.<br />
<br />
Gerv and Stacy recommend: neither. The mental pause caused by the comma is useful in parsing the sentence.</div>MitchellBakerhttps://wiki.mozilla.org/index.php?title=Manifesto/1.0_Comparisons&diff=752407Manifesto/1.0 Comparisons2013-11-06T02:32:40Z<p>MitchellBaker: /* Shorten Principle #6 */</p>
<hr />
<div>__NOTOC__<br />
<br />
It has been decided to have a Twitter English "translation" of the Manifesto. Now we have to decide which of the recently-proposed changes should be made in the Original Version, and which should be made only in the Twitter Version. Where needed, we've split the proposed changes for a principle into multiple independent items, so that they can be judged individually.<br />
<br />
==Changes Not Part of This Comparison==<br />
<br />
From the [[Manifesto/1.0_Changes|1.0 Changes]] document, we have already accepted and so are not considering:<br />
<br />
* Include explicit reference to privacy in #4<br />
* Beef up references to "web literacy" in #5<br />
<br />
'''Rationale''': These two changes were previously approved and will be made to both the Original Version and Twitter Version without further discussion.<br />
<br />
==Shortened Versions==<br />
<br />
'''Rationale''':There are three principles that in their original versions are longer than 118 characters. They need to be shortened for the Twitter English version to no more than 118 characters. (Note that the numbers in parentheses are character counts.) It needs to be decided whether these changes should also be made in the Original Version. The argument for changing them in both versions is that brevity leads to less wordy pages and increased engagement.<br />
<br />
===Shorten Principle #1===<br />
<br />
'''Original''': The Internet is an integral part of modern life—a key component in education, communication, collaboration, business, entertainment and society as a whole. (157)<br />
<br />
'''Altered''': The Internet is integral to modern life: education, communication, collaboration, business, entertainment and society. (118)<br />
<br />
Gerv and Stacy recommend: Twitter only. This list of things are possible without the internet, so the word "part" is significant. We don't want to make over-broad claims.<br />
<br />
Mitchell: I think the altered claim is probably true, but the manifesto should be relevent even for people who think "part" is necessary, so I agree with the recommendation.<br />
<br />
===Shorten Principle #6===<br />
<br />
'''Original''': The effectiveness of the Internet as a public resource depends upon interoperability (protocols, data formats, content), innovation and decentralized participation worldwide. (174)<br />
<br />
'''Altered''': As a public resource, the Internet depends on interoperability, innovation and decentralized participation worldwide. (118)<br />
<br />
Gerv and Stacy recommend: Twitter only. Removing "effectiveness" does alter the meaning.<br />
<br />
Mitchell: Agree re "effectiveness." Also find the original sentence to be easier to read and understand. Agree with the recommendation.<br />
<br />
===Shorten Principle #9===<br />
<br />
'''Original''': Commercial involvement in the development of the Internet brings many benefits; a balance between commercial goals and public benefit is critical. (146)<br />
<br />
'''Altered''': A balance between commercial profit and public benefit is critical to the development of the Internet. (105)<br />
<br />
Gerv and Stacy recommend: Twitter only. The shorter version says something a bit different to the longer one.<br />
<br />
==Other Proposed Changes==<br />
<br />
===Removal of 'Individuals'===<br />
<br />
'''Rationale''': Additional words that are not central to the meaning can be removed to make the Manifesto crisper. In #4, the word "Individuals'" can be removed. This has the added benefit of further differentiating the first word of #4 from the first word of #5.<br />
<br />
'''Approved #4''': Individuals' security and privacy on the Internet are fundamental and cannot be treated as optional.<br />
<br />
'''Altered #4''': Security and privacy on the Internet are fundamental and cannot be treated as optional.<br />
<br />
Gerv and Stacy recommend: neither. A focus on individuals here sharpens the principle; you can't then say the manifesto is simply arguing for anebulous "more security". And we don't need this for length reasons.<br />
<br />
===Consistent Use of "Must" and "Must Not" ===<br />
<br />
'''Rationale''': Principles #2 and #5 set the tone by using "must", yet #3 uses "should" and #4 uses "cannot". Principles are thought to be stronger and crisper if all four use "must" or "must not".<br />
<br />
'''Original #3''': The Internet should enrich the lives of individual human beings.<br />
<br />
'''Altered #3''': The Internet must enrich the lives of individual human beings.<br />
<br />
'''Approved #4''': Individuals' security and privacy on the Internet are fundamental and cannot be treated as optional.<br />
<br />
'''Altered #4''': Individuals' security and privacy on the Internet are fundamental and must not be treated as optional.<br />
<br />
Gerv and Stacy recommend: both. Consistency is good, as is strength.<br />
<br />
===Change 'goals' to 'profit'===<br />
<br />
'''Rationale''': "Commercial profit" and "public benefit" contrast much better than "commercial goals" and "public benefit".<br />
<br />
'''Original #9''': Commercial involvement in the development of the Internet brings many benefits; a balance between commercial goals and public benefit is critical.<br />
<br />
'''Altered #9''': Commercial involvement in the development of the Internet brings many benefits; a balance between commercial profit and public benefit is critical.<br />
<br />
Gerv and Stacy recommend: both.<br />
<br />
===Comma Removal #5===<br />
<br />
'''Rationale''': Removing commas can make the text crisper and in some cases make the meaning clearer.<br />
<br />
'''Approved #5''': Individuals must have the ability to shape the Internet, and their own experiences on it.<br />
<br />
'''Altered #5''': Individuals must have the ability to shape the Internet and their own experiences on it.<br />
<br />
Gerv and Stacy recommend: neither. In this case, the word "it" refers back to "Internet", and so putting the noun in a different clause from the pronoun reads better. Also, it's two related thoughts, so punctuation to separate them is appropriate.<br />
<br />
===Comma Removal #8===<br />
<br />
'''Rationale''': 'Oxford comma' is removed for consistency with the other principles. <br />
<br />
'''Original #8''': Transparent community-based processes promote participation, accountability, and trust.<br />
<br />
'''Altered #8''': Transparent community-based processes promote participation, accountability and trust.<br />
<br />
Gerv and Stacy recommend: both. Consistency is good.<br />
<br />
===Comma Removal #10===<br />
<br />
'''Rationale''': Removing commas can make the text crisper and in some cases make the meaning clearer.<br />
<br />
'''Original #10''': Magnifying the public benefit aspects of the Internet is an important goal, worthy of time, attention and commitment.<br />
<br />
'''Altered #10''': Magnifying the public benefit aspects of the Internet is an important goal worthy of time, attention and commitment.<br />
<br />
Gerv and Stacy recommend: neither. The mental pause caused by the comma is useful in parsing the sentence.</div>MitchellBakerhttps://wiki.mozilla.org/index.php?title=Manifesto/1.0_Comparisons&diff=752405Manifesto/1.0 Comparisons2013-11-06T02:31:40Z<p>MitchellBaker: /* Shorten Principle #1 */</p>
<hr />
<div>__NOTOC__<br />
<br />
It has been decided to have a Twitter English "translation" of the Manifesto. Now we have to decide which of the recently-proposed changes should be made in the Original Version, and which should be made only in the Twitter Version. Where needed, we've split the proposed changes for a principle into multiple independent items, so that they can be judged individually.<br />
<br />
==Changes Not Part of This Comparison==<br />
<br />
From the [[Manifesto/1.0_Changes|1.0 Changes]] document, we have already accepted and so are not considering:<br />
<br />
* Include explicit reference to privacy in #4<br />
* Beef up references to "web literacy" in #5<br />
<br />
'''Rationale''': These two changes were previously approved and will be made to both the Original Version and Twitter Version without further discussion.<br />
<br />
==Shortened Versions==<br />
<br />
'''Rationale''':There are three principles that in their original versions are longer than 118 characters. They need to be shortened for the Twitter English version to no more than 118 characters. (Note that the numbers in parentheses are character counts.) It needs to be decided whether these changes should also be made in the Original Version. The argument for changing them in both versions is that brevity leads to less wordy pages and increased engagement.<br />
<br />
===Shorten Principle #1===<br />
<br />
'''Original''': The Internet is an integral part of modern life—a key component in education, communication, collaboration, business, entertainment and society as a whole. (157)<br />
<br />
'''Altered''': The Internet is integral to modern life: education, communication, collaboration, business, entertainment and society. (118)<br />
<br />
Gerv and Stacy recommend: Twitter only. This list of things are possible without the internet, so the word "part" is significant. We don't want to make over-broad claims.<br />
<br />
Mitchell: I think the altered claim is probably true, but the manifesto should be relevent even for people who think "part" is necessary, so I agree with the recommendation.<br />
<br />
===Shorten Principle #6===<br />
<br />
'''Original''': The effectiveness of the Internet as a public resource depends upon interoperability (protocols, data formats, content), innovation and decentralized participation worldwide. (174)<br />
<br />
'''Altered''': As a public resource, the Internet depends on interoperability, innovation and decentralized participation worldwide. (118)<br />
<br />
Gerv and Stacy recommend: Twitter only. Removing "effectiveness" does alter the meaning.<br />
<br />
===Shorten Principle #9===<br />
<br />
'''Original''': Commercial involvement in the development of the Internet brings many benefits; a balance between commercial goals and public benefit is critical. (146)<br />
<br />
'''Altered''': A balance between commercial profit and public benefit is critical to the development of the Internet. (105)<br />
<br />
Gerv and Stacy recommend: Twitter only. The shorter version says something a bit different to the longer one.<br />
<br />
==Other Proposed Changes==<br />
<br />
===Removal of 'Individuals'===<br />
<br />
'''Rationale''': Additional words that are not central to the meaning can be removed to make the Manifesto crisper. In #4, the word "Individuals'" can be removed. This has the added benefit of further differentiating the first word of #4 from the first word of #5.<br />
<br />
'''Approved #4''': Individuals' security and privacy on the Internet are fundamental and cannot be treated as optional.<br />
<br />
'''Altered #4''': Security and privacy on the Internet are fundamental and cannot be treated as optional.<br />
<br />
Gerv and Stacy recommend: neither. A focus on individuals here sharpens the principle; you can't then say the manifesto is simply arguing for anebulous "more security". And we don't need this for length reasons.<br />
<br />
===Consistent Use of "Must" and "Must Not" ===<br />
<br />
'''Rationale''': Principles #2 and #5 set the tone by using "must", yet #3 uses "should" and #4 uses "cannot". Principles are thought to be stronger and crisper if all four use "must" or "must not".<br />
<br />
'''Original #3''': The Internet should enrich the lives of individual human beings.<br />
<br />
'''Altered #3''': The Internet must enrich the lives of individual human beings.<br />
<br />
'''Approved #4''': Individuals' security and privacy on the Internet are fundamental and cannot be treated as optional.<br />
<br />
'''Altered #4''': Individuals' security and privacy on the Internet are fundamental and must not be treated as optional.<br />
<br />
Gerv and Stacy recommend: both. Consistency is good, as is strength.<br />
<br />
===Change 'goals' to 'profit'===<br />
<br />
'''Rationale''': "Commercial profit" and "public benefit" contrast much better than "commercial goals" and "public benefit".<br />
<br />
'''Original #9''': Commercial involvement in the development of the Internet brings many benefits; a balance between commercial goals and public benefit is critical.<br />
<br />
'''Altered #9''': Commercial involvement in the development of the Internet brings many benefits; a balance between commercial profit and public benefit is critical.<br />
<br />
Gerv and Stacy recommend: both.<br />
<br />
===Comma Removal #5===<br />
<br />
'''Rationale''': Removing commas can make the text crisper and in some cases make the meaning clearer.<br />
<br />
'''Approved #5''': Individuals must have the ability to shape the Internet, and their own experiences on it.<br />
<br />
'''Altered #5''': Individuals must have the ability to shape the Internet and their own experiences on it.<br />
<br />
Gerv and Stacy recommend: neither. In this case, the word "it" refers back to "Internet", and so putting the noun in a different clause from the pronoun reads better. Also, it's two related thoughts, so punctuation to separate them is appropriate.<br />
<br />
===Comma Removal #8===<br />
<br />
'''Rationale''': 'Oxford comma' is removed for consistency with the other principles. <br />
<br />
'''Original #8''': Transparent community-based processes promote participation, accountability, and trust.<br />
<br />
'''Altered #8''': Transparent community-based processes promote participation, accountability and trust.<br />
<br />
Gerv and Stacy recommend: both. Consistency is good.<br />
<br />
===Comma Removal #10===<br />
<br />
'''Rationale''': Removing commas can make the text crisper and in some cases make the meaning clearer.<br />
<br />
'''Original #10''': Magnifying the public benefit aspects of the Internet is an important goal, worthy of time, attention and commitment.<br />
<br />
'''Altered #10''': Magnifying the public benefit aspects of the Internet is an important goal worthy of time, attention and commitment.<br />
<br />
Gerv and Stacy recommend: neither. The mental pause caused by the comma is useful in parsing the sentence.</div>MitchellBakerhttps://wiki.mozilla.org/index.php?title=Modules/Activities&diff=499082Modules/Activities2013-01-11T23:35:01Z<p>MitchellBaker: /* Governance Sub Modules */</p>
<hr />
<div>{{Module<br />
|name=Governance<br />
|description=Policies and process for how we distribute authority and govern ourselves; including:<br />
* Development and Implementation of new policies as appropriate for delegation of authority and responsibility<br />
* Management of the source tree<br />
* Balancing different constituencies of the Mozilla project<br />
* Maintaining the Mozilla identity as we take on new activities<br />
<br />
[http://www.mozilla.org/about/roles.html#ultimate-decision-makers Ultimate authority] within the project rests with the owner and peer(s) of this module, and project decisions can be escalated to here.<br />
|owner=[mailto:mitchell@mozilla.org Mitchell Baker]<br />
|peers=[mailto:brendan@mozilla.org Brendan Eich]<br />
|group=governance<br />
|url=https://wiki.mozilla.org/GovernanceIssues<br />
|components=mozilla.org::Governance<br />
}}<br />
<br />
===Governance Sub Modules===<br />
<br />
{{Module<br />
|name=Module Ownership System<br />
|description=Healthy operation of the module ownership system, including topics such as:<br />
* Filling vacant roles where appropriate<br />
* Ensuring module owners are fulfilling their responsibilities, and replacing those who are not<br />
* Creating and staffing new modules where new parts of the project evolve.<br />
* Figuring out what to do if a module isn't getting enough attention<br />
* Resolving conflicts among module owners <br />
|owner=[mailto:brendan@mozilla.org Brendan Eich]<br />
|peers=[mailto:pavlov@pavlov.net Stuart Parmenter], [mailto:dmose@mozilla.org Dan Mosedale], [mailto:kairo@kairo.at Robert Kaiser], [mailto:mconnor@steelgryphon.com Mike Connor], [mailto:dbaron@dbaron.org David Baron], [mailto:hecker@hecker.org Frank Hecker], [mailto:dascher@mozilla.com David Ascher], [mailto:mitchell@mozilla.org Mitchell Baker]. Guillermo Movia is an 'observer'. (This is a new role we're trying out as of Jan 2012. The observers are watching and learning how the module operates, since there's no code in this module to serve as a learning /participation tool.)<br />
|group=<br />
|url=<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=Commit Access Policy<br />
|description=<br />
|owner=[mailto:mitchell@mozilla.org Mitchell Baker]<br />
|peers=<br />
|group=<br />
|url=http://www.mozilla.org/hacking/committer/<br />
|components=mozilla.org::Repository Account Requests<br />
}}<br />
<br />
{{Module<br />
|name=Security Policy<br />
|description=<br />
|owner=[mailto:hecker@hecker.org Frank Hecker]<br />
|peers=<br />
|group=<br />
|url=http://www.mozilla.org/projects/security/security-bugs-policy.html<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=Mozilla CA Certificate Policy<br />
|description=<br />
|owner=[mailto:kwilson@mozilla.com Kathleen Wilson]<br />
|peers=[mailto:hecker@hecker.org Frank Hecker], [mailto:gerv@mozilla.org Gervase Markham], [mailto:johnath@mozilla.com Johnathan Nightingale], [mailto:sid@mozilla.com Sid Stamm]<br />
|group=<br />
|url=http://www.mozilla.org/projects/security/certs/policy/<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=Code Review Policy<br />
|description=<br />
|owner=[mailto:mitchell@mozilla.org Mitchell Baker]<br />
|peers=[mailto:brendan@mozilla.org Brendan Eich]<br />
|group=<br />
|url=http://www.mozilla.org/hacking/reviewers.html<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=Performance Regression Policy<br />
|description=<br />
|owner=[mailto:mitchell@mozilla.org Mitchell Baker]<br />
|peers=<br />
|group=<br />
|url=<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=Planet Mozilla<br />
|description=Content and policy for planet.mozilla.org, including topics such as:<br />
* which blogs are syndicated to planet.mozilla.org<br />
* which content from syndicated blogs is included<br />
* other planet.mozilla.org policy issues <br />
|owner=[mailto:robert@accettura.com Robert Accettura]<br />
|peers=[mailto:asa@mozilla.org Asa Dotzler], [mailto:reed@reedloden.com Reed Loden], [mailto:mozpreed@sigkill.com J. Paul Reed] -- collectively, [mailto:planet@mozilla.org planet@mozilla.org] (preferred)<br />
|group=<br />
|url=<br />
|components=Websites::planet.mozilla.org<br />
}}<br />
<br />
{{Module<br />
|name=Mozilla Public License<br />
|description=Maintenance and development of the MPL<br />
* changes in the legal landscape which could /should be reflected<br />
* changes in FLOSS development practices which could / should be reflected <br />
|owner=[mailto:mitchell@mozilla.org Mitchell Baker]<br />
|peers=[mailto:handerson@mozilla.com Harvey Anderson], [mailto:gerv@mozilla.org Gervase Markham], [mailto:MeekerH@gtlaw.com Heather Meeker], [mailto:villalu@gtlaw.com Luis Villa]<br />
|group=governance-mpl-update<br />
|url=<br />
|components=mozilla.org::Licensing<br />
}}<br />
<br />
{{Module<br />
|name=www.mozilla.org<br />
|description=Content and policy for www.mozilla.org. Sub-modules and their owners can be found [[Mozilla.org/Owners_List|here]].<br />
|owner=[mailto:reed@reedloden.com Reed Loden] (technical issues), [mailto:david@mozillafoundation.org David Boswell] (content issues)<br />
|peers=[mailto:etemad@mozilla.com Elika Etemad], [mailto:kairo@kairo.at Robert Kaiser], [mailto:eshepherd@mozilla.com Eric Shepherd]<br />
|group=dev-mozilla-org<br />
|url=<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=CA Certificates<br />
|description=Determine which root certificates should be included in Mozilla software products and which trust bits should be set on them, and evaluate requests from Certification Authorities (CAs) for inclusion of new root certificates.<br />
|owner=[mailto:kwilson@mozilla.com Kathleen Wilson]<br />
|peers=[mailto:hecker@hecker.org Frank Hecker], [mailto:gerv@mozilla.org Gervase Markham], [mailto:johnath@mozilla.com Johnathan Nightingale], [mailto:sid@mozilla.com Sid Stamm]<br />
|group=dev-security-policy <br />
|url=http://www.mozilla.org/projects/security/certs/policy/<br />
|components=mozilla.org::CA Certificates<br />
}}<br />
<br />
{{Module<br />
|name=Participation Metrics<br />
|description=Develop, monitor and analyze metrics relating to participation in the Mozilla project, including such things as:<br />
* determining which questions are most important to ask (how many people do X?)<br />
* determining what data is relevant to answer these questions<br />
* designing and operating a system to generate the requested data<br />
* analyzing the resulting metrics<br />
* notifying appropriate people when participation starts to change significantly<br />
* assisting various groups to understand and use the metrics to strengthen participation<br />
* produce periodic report/analysis of participation metrics <br />
|owner=[mailto:dboswell@mozilla.com David Boswell]<br />
|peers=[mailto:asa@mozilla.com Asa Dotzler], [mailto:deinspanjer@mozilla.com Daniel Einspanjer], [mailto:aelliott@mozilla.com Annie Elliott], [mailto:david@eaves.ca David Eaves], [mailto:ppapadeas@mozilla.com Pierros Papadeas], [mailto:michelle@mozillafoundation.org Michelle Thorne], [mailto:ryan@mozillafoundation.org Ryan Merkley]<br />
|group=mozillians<br />
|url=https://wiki.mozilla.org/Contribute/Dashboards<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=Productive Communications Module (aka the "Conductors")<br />
|description=Promotion of productive communications styles within Mozilla, where "productive" means simultaneously honest and civil. This includes topics such as:<br />
*coaching people on who to respond to nasty settings;<br />
*coaching people to think a little before they hit post/send/submit.<br />
*coaching people on how to be direct and yet civil, notifying people they are at or past the boundary;<br />
*coaching people to recognize legitimate comments/ complaints / differences of opinion despite poor communication style<br />
*redirecting conversations into a better place,<br />
*building a culture of respect in how we communicate with difficult and contentious issues<br />
*when necessary, letting people know they've gone beyond the boundaries.<br />
|owner=[mailto:stormy@mozilla.com Stormy Peters]<br />
|peers=David Ascher , Dietrich Ayala, Mike Beltzner, Matt Claypotch, David Eaves, Gen Kanai, Michelle Luna, Kev Needham, Johnathan Nightingale, Melissa Shapiro, Gavin Sharp, Benjamin Smedberg, Mike Taylor (Bear), David Tenser, Daniel Veditz - collectively, [mailto:conductors@mozilla.org conductors@mozilla.org].<br />
|group=mozilla.governance<br />
|url=http://wiki.mozilla.org/Conductors<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=Internet Public Policy<br />
|description=Mozilla activities related to Public Policy issues that affect the health of the Internet. Our working definition of Public Policy is taken from Wikipedia: "courses of action, regulatory measures, laws, and funding priorities concerning a given topic promulgated by a governmental entity or its representatives." <br />
This includes topics such as:<br />
*determining if Mozilla should take an official position on a particular public policy issue<br />
*determining what that position is <br />
*determining how mozilla communicates our position <br />
**global, multi-regional, regional or local action<br />
**direct action, or support of action by other aligned groups<br />
**public campaigns or opinion pieces or educational activities, dialog with policy makers, other techniques TBD<br />
*strengthening local community capabilities to address public policy issues <br />
|owner=Harvey Anderson<br />
|peers=Mitchell Baker, Alex Fowler, Mark Surman<br />
|advisors=tbd<br />
|url=http://<br />
|group=mozilla.governance<br />
|components=<br />
}}<br />
Area Expert Advisors are people with particular expertise who have agreed to assist Mozilla with their area-specific expertise. The Area Expert Advisors are different from peers. A peer is someone to whom the module owner has delegated some of her/his authority and a peer is expected to provide leadership for Mozilla within our specific context. Area Expert Advisors are advisors to Mozilla. They may become peers, but they need not. <br />
<br />
<br />
{{Module<br />
|name=Weekly Project All Hands Meeting<br />
|description=Responsibility for the weekly meetings, including:<br />
* determining and implementing the best organization and structure for the meeting<br />
* Determining and implementing the most useful content<br />
* Identifying and implementing technical means to make the meeting accessible and interactive for participants around the globe<br />
|owner=[mailto:jono@mozilla.com Jono Xia]<br />
|peers=[mailto:asa@mozilla.org Asa Dotzler], MoCo Desktop IT services<br />
|group=mozilla.governance<br />
|url=https://wiki.mozilla.org/WeeklyUpdates<br />
|components=<br />
}}<br />
<br />
(It's a new thing to have a group such as "MoCo Desktop IT services" as a<br />
"peer." We're trying this based on the idea that anyone in the Desktop IT group<br />
should be able to resolve problems and make fixes to the systems.)<br />
<br />
===Other===<br />
<br />
{{Module<br />
|name=Popcorn Events<br />
|description=Events to support and grow the popcorn project. These include hack days pairing web developers and media creators, as well as Learning Labs to teach popcorn.js and Popcorn Maker.<br />
|owner=[mailto:brett@mozillafoundation.org Brett Gaylor]<br />
|peers=[mailto:michelle@mozillafoundation.org Michelle Thorne]<br />
|group=mozilla.community.popcorn<br />
|url=http://www.mozillapopcorn.org/<br />
|components=<br />
}}</div>MitchellBakerhttps://wiki.mozilla.org/index.php?title=Modules/Activities&diff=499075Modules/Activities2013-01-11T23:17:27Z<p>MitchellBaker: /* Governance Sub Modules */</p>
<hr />
<div>{{Module<br />
|name=Governance<br />
|description=Policies and process for how we distribute authority and govern ourselves; including:<br />
* Development and Implementation of new policies as appropriate for delegation of authority and responsibility<br />
* Management of the source tree<br />
* Balancing different constituencies of the Mozilla project<br />
* Maintaining the Mozilla identity as we take on new activities<br />
<br />
[http://www.mozilla.org/about/roles.html#ultimate-decision-makers Ultimate authority] within the project rests with the owner and peer(s) of this module, and project decisions can be escalated to here.<br />
|owner=[mailto:mitchell@mozilla.org Mitchell Baker]<br />
|peers=[mailto:brendan@mozilla.org Brendan Eich]<br />
|group=governance<br />
|url=https://wiki.mozilla.org/GovernanceIssues<br />
|components=mozilla.org::Governance<br />
}}<br />
<br />
===Governance Sub Modules===<br />
<br />
{{Module<br />
|name=Module Ownership System<br />
|description=Healthy operation of the module ownership system, including topics such as:<br />
* Filling vacant roles where appropriate<br />
* Ensuring module owners are fulfilling their responsibilities, and replacing those who are not<br />
* Creating and staffing new modules where new parts of the project evolve.<br />
* Figuring out what to do if a module isn't getting enough attention<br />
* Resolving conflicts among module owners <br />
|owner=[mailto:brendan@mozilla.org Brendan Eich]<br />
|peers=[mailto:pavlov@pavlov.net Stuart Parmenter], [mailto:dmose@mozilla.org Dan Mosedale], [mailto:kairo@kairo.at Robert Kaiser], [mailto:mconnor@steelgryphon.com Mike Connor], [mailto:dbaron@dbaron.org David Baron], [mailto:hecker@hecker.org Frank Hecker], [mailto:dascher@mozilla.com David Ascher], [mailto:mitchell@mozilla.org Mitchell Baker]. Guillermo Movia is an 'observer'. (This is a new role we're trying out as of Jan 2012. The observers are watching and learning how the module operates, since there's no code in this module to serve as a learning /participation tool.)<br />
|group=<br />
|url=<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=Commit Access Policy<br />
|description=<br />
|owner=[mailto:mitchell@mozilla.org Mitchell Baker]<br />
|peers=<br />
|group=<br />
|url=http://www.mozilla.org/hacking/committer/<br />
|components=mozilla.org::Repository Account Requests<br />
}}<br />
<br />
{{Module<br />
|name=Security Policy<br />
|description=<br />
|owner=[mailto:hecker@hecker.org Frank Hecker]<br />
|peers=<br />
|group=<br />
|url=http://www.mozilla.org/projects/security/security-bugs-policy.html<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=Mozilla CA Certificate Policy<br />
|description=<br />
|owner=[mailto:kwilson@mozilla.com Kathleen Wilson]<br />
|peers=[mailto:hecker@hecker.org Frank Hecker], [mailto:gerv@mozilla.org Gervase Markham], [mailto:johnath@mozilla.com Johnathan Nightingale], [mailto:sid@mozilla.com Sid Stamm]<br />
|group=<br />
|url=http://www.mozilla.org/projects/security/certs/policy/<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=Code Review Policy<br />
|description=<br />
|owner=[mailto:mitchell@mozilla.org Mitchell Baker]<br />
|peers=[mailto:brendan@mozilla.org Brendan Eich]<br />
|group=<br />
|url=http://www.mozilla.org/hacking/reviewers.html<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=Performance Regression Policy<br />
|description=<br />
|owner=[mailto:mitchell@mozilla.org Mitchell Baker]<br />
|peers=<br />
|group=<br />
|url=<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=Planet Mozilla<br />
|description=Content and policy for planet.mozilla.org, including topics such as:<br />
* which blogs are syndicated to planet.mozilla.org<br />
* which content from syndicated blogs is included<br />
* other planet.mozilla.org policy issues <br />
|owner=[mailto:robert@accettura.com Robert Accettura]<br />
|peers=[mailto:asa@mozilla.org Asa Dotzler], [mailto:reed@reedloden.com Reed Loden], [mailto:mozpreed@sigkill.com J. Paul Reed] -- collectively, [mailto:planet@mozilla.org planet@mozilla.org] (preferred)<br />
|group=<br />
|url=<br />
|components=Websites::planet.mozilla.org<br />
}}<br />
<br />
{{Module<br />
|name=Mozilla Public License<br />
|description=Maintenance and development of the MPL<br />
* changes in the legal landscape which could /should be reflected<br />
* changes in FLOSS development practices which could / should be reflected <br />
|owner=[mailto:mitchell@mozilla.org Mitchell Baker]<br />
|peers=[mailto:handerson@mozilla.com Harvey Anderson], [mailto:gerv@mozilla.org Gervase Markham], [mailto:MeekerH@gtlaw.com Heather Meeker], [mailto:villalu@gtlaw.com Luis Villa]<br />
|group=governance-mpl-update<br />
|url=<br />
|components=mozilla.org::Licensing<br />
}}<br />
<br />
{{Module<br />
|name=www.mozilla.org<br />
|description=Content and policy for www.mozilla.org. Sub-modules and their owners can be found [[Mozilla.org/Owners_List|here]].<br />
|owner=[mailto:reed@reedloden.com Reed Loden] (technical issues), [mailto:david@mozillafoundation.org David Boswell] (content issues)<br />
|peers=[mailto:etemad@mozilla.com Elika Etemad], [mailto:kairo@kairo.at Robert Kaiser], [mailto:eshepherd@mozilla.com Eric Shepherd]<br />
|group=dev-mozilla-org<br />
|url=<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=CA Certificates<br />
|description=Determine which root certificates should be included in Mozilla software products and which trust bits should be set on them, and evaluate requests from Certification Authorities (CAs) for inclusion of new root certificates.<br />
|owner=[mailto:kwilson@mozilla.com Kathleen Wilson]<br />
|peers=[mailto:hecker@hecker.org Frank Hecker], [mailto:gerv@mozilla.org Gervase Markham], [mailto:johnath@mozilla.com Johnathan Nightingale], [mailto:sid@mozilla.com Sid Stamm]<br />
|group=dev-security-policy <br />
|url=http://www.mozilla.org/projects/security/certs/policy/<br />
|components=mozilla.org::CA Certificates<br />
}}<br />
<br />
{{Module<br />
|name=Participation Metrics<br />
|description=Develop, monitor and analyze metrics relating to participation in the Mozilla project, including such things as:<br />
* determining which questions are most important to ask (how many people do X?)<br />
* determining what data is relevant to answer these questions<br />
* designing and operating a system to generate the requested data<br />
* analyzing the resulting metrics<br />
* notifying appropriate people when participation starts to change significantly<br />
* assisting various groups to understand and use the metrics to strengthen participation<br />
* produce periodic report/analysis of participation metrics <br />
|owner=[mailto:dboswell@mozilla.com David Boswell]<br />
|peers=[mailto:asa@mozilla.com Asa Dotzler], [mailto:deinspanjer@mozilla.com Daniel Einspanjer], [mailto:aelliott@mozilla.com Annie Elliott], [mailto:david@eaves.ca David Eaves], [mailto:ppapadeas@mozilla.com Pierros Papadeas], [mailto:michelle@mozillafoundation.org Michelle Thorne], [mailto:ryan@mozillafoundation.org Ryan Merkley]<br />
|group=mozillians<br />
|url=https://wiki.mozilla.org/Contribute/Dashboards<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=Productive Communications Module (aka the "Conductors")<br />
|description=Promotion of productive communications styles within Mozilla, where "productive" means simultaneously honest and civil. This includes topics such as:<br />
*coaching people on who to respond to nasty settings;<br />
*coaching people to think a little before they hit post/send/submit.<br />
*coaching people on how to be direct and yet civil, notifying people they are at or past the boundary;<br />
*coaching people to recognize legitimate comments/ complaints / differences of opinion despite poor communication style<br />
*redirecting conversations into a better place,<br />
*building a culture of respect in how we communicate with difficult and contentious issues<br />
*when necessary, letting people know they've gone beyond the boundaries.<br />
|owner=[mailto:stormy@mozilla.com Stormy Peters]<br />
|peers=David Ascher , Dietrich Ayala, Mike Beltzner, Matt Claypotch, David Eaves, Gen Kanai, Michelle Luna, Kev Needham, Johnathan Nightingale, Melissa Shapiro, Gavin Sharp, Benjamin Smedberg, Mike Taylor (Bear), David Tenser, Daniel Veditz - collectively, [mailto:conductors@mozilla.org conductors@mozilla.org].<br />
|group=mozilla.governance<br />
|url=http://wiki.mozilla.org/Conductors<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=Internet Public Policy<br />
|description=Mozilla activities related to Public Policy issues that affect the health of the Internet. Our working definition of Public Policy is taken from Wikipedia: "courses of action, regulatory measures, laws, and funding priorities concerning a given topic promulgated by a governmental entity or its representatives." <br />
This includes topics such as:<br />
*determining if Mozilla should take an official position on a particular public policy issue<br />
*determining what that position is <br />
*determining how mozilla communicates our position <br />
**global, multi-regional, regional or local action<br />
**direct action, or support of action by other aligned groups<br />
**public campaigns or opinion pieces or educational activities, dialog with policy makers, other techniques TBD<br />
*strengthening local community capabilities to address public policy issues <br />
|owner=Harvey Anderson<br />
|peers=Mitchell Baker, Alex Fowler, Mark Surman<br />
|url=http://<br />
|group=mozilla.governance<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=Weekly Project All Hands Meeting<br />
|description=Responsibility for the weekly meetings, including:<br />
* determining and implementing the best organization and structure for the meeting<br />
* Determining and implementing the most useful content<br />
* Identifying and implementing technical means to make the meeting accessible and interactive for participants around the globe<br />
|owner=[mailto:jono@mozilla.com Jono Xia]<br />
|peers=[mailto:asa@mozilla.org Asa Dotzler], MoCo Desktop IT services<br />
|group=mozilla.governance<br />
|url=https://wiki.mozilla.org/WeeklyUpdates<br />
|components=<br />
}}<br />
<br />
(It's a new thing to have a group such as "MoCo Desktop IT services" as a<br />
"peer." We're trying this based on the idea that anyone in the Desktop IT group<br />
should be able to resolve problems and make fixes to the systems.)<br />
<br />
===Other===<br />
<br />
{{Module<br />
|name=Popcorn Events<br />
|description=Events to support and grow the popcorn project. These include hack days pairing web developers and media creators, as well as Learning Labs to teach popcorn.js and Popcorn Maker.<br />
|owner=[mailto:brett@mozillafoundation.org Brett Gaylor]<br />
|peers=[mailto:michelle@mozillafoundation.org Michelle Thorne]<br />
|group=mozilla.community.popcorn<br />
|url=http://www.mozillapopcorn.org/<br />
|components=<br />
}}</div>MitchellBakerhttps://wiki.mozilla.org/index.php?title=Modules/Activities&diff=490385Modules/Activities2012-11-28T07:34:24Z<p>MitchellBaker: /* Governance Sub Modules */</p>
<hr />
<div>{{Module<br />
|name=Governance<br />
|description=Policies and process for how we distribute authority and govern ourselves; including:<br />
* Development and Implementation of new policies as appropriate for delegation of authority and responsibility<br />
* Management of the source tree<br />
* Balancing different constituencies of the Mozilla project<br />
* Maintaining the Mozilla identity as we take on new activities<br />
<br />
[http://www.mozilla.org/about/roles.html#ultimate-decision-makers Ultimate authority] within the project rests with the owner and peer(s) of this module, and project decisions can be escalated to here.<br />
|owner=[mailto:mitchell@mozilla.org Mitchell Baker]<br />
|peers=[mailto:brendan@mozilla.org Brendan Eich]<br />
|group=governance<br />
|url=https://wiki.mozilla.org/GovernanceIssues<br />
|components=mozilla.org::Governance<br />
}}<br />
<br />
===Governance Sub Modules===<br />
<br />
{{Module<br />
|name=Module Ownership System<br />
|description=Healthy operation of the module ownership system, including topics such as:<br />
* Filling vacant roles where appropriate<br />
* Ensuring module owners are fulfilling their responsibilities, and replacing those who are not<br />
* Creating and staffing new modules where new parts of the project evolve.<br />
* Figuring out what to do if a module isn't getting enough attention<br />
* Resolving conflicts among module owners <br />
|owner=[mailto:brendan@mozilla.org Brendan Eich]<br />
|peers=[mailto:pavlov@pavlov.net Stuart Parmenter], [mailto:dmose@mozilla.org Dan Mosedale], [mailto:kairo@kairo.at Robert Kaiser], [mailto:mconnor@steelgryphon.com Mike Connor], [mailto:dbaron@dbaron.org David Baron], [mailto:hecker@hecker.org Frank Hecker], [mailto:dascher@mozilla.com David Ascher], [mailto:mitchell@mozilla.org Mitchell Baker]. Guillermo Movia is an 'observer'. (This is a new role we're trying out as of Jan 2012. The observers are watching and learning how the module operates, since there's no code in this module to serve as a learning /participation tool.)<br />
|group=<br />
|url=<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=Commit Access Policy<br />
|description=<br />
|owner=[mailto:mitchell@mozilla.org Mitchell Baker]<br />
|peers=<br />
|group=<br />
|url=http://www.mozilla.org/hacking/committer/<br />
|components=mozilla.org::Repository Account Requests<br />
}}<br />
<br />
{{Module<br />
|name=Security Policy<br />
|description=<br />
|owner=[mailto:hecker@hecker.org Frank Hecker]<br />
|peers=<br />
|group=<br />
|url=http://www.mozilla.org/projects/security/security-bugs-policy.html<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=Mozilla CA Certificate Policy<br />
|description=<br />
|owner=[mailto:kwilson@mozilla.com Kathleen Wilson]<br />
|peers=[mailto:hecker@hecker.org Frank Hecker], [mailto:gerv@mozilla.org Gervase Markham], [mailto:johnath@mozilla.com Johnathan Nightingale], [mailto:sid@mozilla.com Sid Stamm]<br />
|group=<br />
|url=http://www.mozilla.org/projects/security/certs/policy/<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=Code Review Policy<br />
|description=<br />
|owner=[mailto:mitchell@mozilla.org Mitchell Baker]<br />
|peers=[mailto:brendan@mozilla.org Brendan Eich]<br />
|group=<br />
|url=http://www.mozilla.org/hacking/reviewers.html<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=Performance Regression Policy<br />
|description=<br />
|owner=[mailto:mitchell@mozilla.org Mitchell Baker]<br />
|peers=<br />
|group=<br />
|url=<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=Planet Mozilla<br />
|description=Content and policy for planet.mozilla.org, including topics such as:<br />
* which blogs are syndicated to planet.mozilla.org<br />
* which content from syndicated blogs is included<br />
* other planet.mozilla.org policy issues <br />
|owner=[mailto:robert@accettura.com Robert Accettura]<br />
|peers=[mailto:asa@mozilla.org Asa Dotzler], [mailto:reed@reedloden.com Reed Loden], [mailto:mozpreed@sigkill.com J. Paul Reed] -- collectively, [mailto:planet@mozilla.org planet@mozilla.org] (preferred)<br />
|group=<br />
|url=<br />
|components=Websites::planet.mozilla.org<br />
}}<br />
<br />
{{Module<br />
|name=Mozilla Public License<br />
|description=Maintenance and development of the MPL<br />
* changes in the legal landscape which could /should be reflected<br />
* changes in FLOSS development practices which could / should be reflected <br />
|owner=[mailto:mitchell@mozilla.org Mitchell Baker]<br />
|peers=[mailto:handerson@mozilla.com Harvey Anderson], [mailto:gerv@mozilla.org Gervase Markham], [mailto:MeekerH@gtlaw.com Heather Meeker], [mailto:villalu@gtlaw.com Luis Villa]<br />
|group=governance-mpl-update<br />
|url=<br />
|components=mozilla.org::Licensing<br />
}}<br />
<br />
{{Module<br />
|name=www.mozilla.org<br />
|description=Content and policy for www.mozilla.org. Sub-modules and their owners can be found [[Mozilla.org/Owners_List|here]].<br />
|owner=[mailto:reed@reedloden.com Reed Loden] (technical issues), [mailto:david@mozillafoundation.org David Boswell] (content issues)<br />
|peers=[mailto:etemad@mozilla.com Elika Etemad], [mailto:kairo@kairo.at Robert Kaiser], [mailto:eshepherd@mozilla.com Eric Shepherd]<br />
|group=dev-mozilla-org<br />
|url=<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=CA Certificates<br />
|description=Determine which root certificates should be included in Mozilla software products and which trust bits should be set on them, and evaluate requests from Certification Authorities (CAs) for inclusion of new root certificates.<br />
|owner=[mailto:kwilson@mozilla.com Kathleen Wilson]<br />
|peers=[mailto:hecker@hecker.org Frank Hecker], [mailto:gerv@mozilla.org Gervase Markham], [mailto:johnath@mozilla.com Johnathan Nightingale], [mailto:sid@mozilla.com Sid Stamm]<br />
|group=dev-security-policy <br />
|url=http://www.mozilla.org/projects/security/certs/policy/<br />
|components=mozilla.org::CA Certificates<br />
}}<br />
<br />
{{Module<br />
|name=Participation Metrics<br />
|description=Develop, monitor and analyze metrics relating to participation in the Mozilla project, including such things as:<br />
* determining which questions are most important to ask (how many people do X?)<br />
* determining what data is relevant to answer these questions<br />
* designing and operating a system to generate the requested data<br />
* analyzing the resulting metrics<br />
* notifying appropriate people when participation starts to change significantly<br />
* assisting various groups to understand and use the metrics to strengthen participation<br />
* produce periodic report/analysis of participation metrics <br />
|owner=[mailto:asa@mozilla.com Asa Dotzler]<br />
|peers=[mailto:deinspanjer@mozilla.com Daniel Einspanjer], [mailto:kkovash@mozilla.com Ken Kovash]<br />
|group=<br />
|url=https://wiki.mozilla.org/ParticipationMetrics/roadmap<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=Productive Communications Module (aka the "Conductors")<br />
|description=Promotion of productive communications styles within Mozilla, where "productive" means simultaneously honest and civil. This includes topics such as:<br />
*coaching people on who to respond to nasty settings;<br />
*coaching people to think a little before they hit post/send/submit.<br />
*coaching people on how to be direct and yet civil, notifying people they are at or past the boundary;<br />
*coaching people to recognize legitimate comments/ complaints / differences of opinion despite poor communication style<br />
*redirecting conversations into a better place,<br />
*building a culture of respect in how we communicate with difficult and contentious issues<br />
*when necessary, letting people know they've gone beyond the boundaries.<br />
|owner=[mailto:stormy@mozilla.com Stormy Peters]<br />
|peers=David Ascher , Dietrich Ayala, Mike Beltzner, Matt Claypotch, David Eaves, Gen Kanai, Michelle Luna, Kev Needham, Johnathan Nightingale, Melissa Shapiro, Gavin Sharp, Benjamin Smedberg, Mike Taylor (Bear), David Tenser, Daniel Veditz - collectively, [mailto:conductors@mozilla.org conductors@mozilla.org].<br />
|group=mozilla.governance<br />
|url=http://wiki.mozilla.org/Conductors<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=Weekly Project All Hands Meeting<br />
|description=Responsibility for the weekly meetings, including:<br />
* determining and implementing the best organization and structure for the meeting<br />
* Determining and implementing the most useful content<br />
* Identifying and implementing technical means to make the meeting accessible and interactive for participants around the globe<br />
|owner=[mailto:jono@mozilla.com Jono Xia]<br />
|peers=[mailto:asa@mozilla.org Asa Dotzler], MoCo Desktop IT services<br />
|group=mozilla.governance<br />
|url=https://wiki.mozilla.org/WeeklyUpdates<br />
|components=<br />
}}<br />
<br />
(It's a new thing to have a group such as "MoCo Desktop IT services" as a<br />
"peer." We're trying this based on the idea that anyone in the Desktop IT group<br />
should be able to resolve problems and make fixes to the systems.)<br />
<br />
===Other===<br />
<br />
{{Module<br />
|name=Popcorn Events<br />
|description=Events to support and grow the popcorn project. These include hack days pairing web developers and media creators, as well as Learning Labs to teach popcorn.js and Popcorn Maker.<br />
|owner=[mailto:brett@mozillafoundation.org Brett Gaylor]<br />
|peers=[mailto:michelle@mozillafoundation.org Michelle Thorne]<br />
|group=mozilla.community.popcorn<br />
|url=http://www.mozillapopcorn.org/<br />
|components=<br />
}}</div>MitchellBakerhttps://wiki.mozilla.org/index.php?title=Modules&diff=409069Modules2012-03-19T18:09:47Z<p>MitchellBaker: /* Creating A New Module */</p>
<hr />
<div>Mozilla operates under a [http://www.mozilla.org/hacking/module-ownership.html module ownership governance system]. A '''module''' is a discrete unit of code or activity. An '''owner''' is the person in charge of a module or sub-module. A '''peer''' is a person whom the owner has appointed to help them. A module may have multiple peers and, very occasionally, multiple owners.<br />
<br />
The system is overseen by the owner and peers of the [[Modules/Activities#Module_Ownership_System|Module Ownership module]]. Owners may add and remove peers from their modules as they wish, without reference to anyone else.<br />
<br />
===Creating A New Module===<br />
<br />
Ideally, a Module should exist for all significant chunks of work or code in the Mozilla project. Who you talk to about this depends on the area of the project concerned.<br />
<br />
For many areas, the ability to create, alter ownership of and destroy sub-modules has been delegated to the owner of the module whose broad scope covers that area. This is true for Firefox, Thunderbird, and all of the other areas listed below except for [[Modules/Core|Core]], [[Modules/Activities|Activities]] and [[Modules/Other|Other]]. The controlling module is the first one listed on the page. Please contact that person about getting new modules created.<br />
<br />
For Core modules and Activities (non-code) modules, please post your enquiry in the mozilla.governance newsgroup, cc'ing the owner and peers of the [[Modules/Activities#Module_Ownership_System|Module Ownership module]] at module-ownership [at] mozilla [dot] org. If there is something sensitive about your enquiry that you aren't comfortable writing in the newsgroup, or in case of uncertainty, please send it to module-ownership [at] mozilla [dot] org.<br />
<br />
===Module Lists===<br />
<br />
These pages list the owners and their peers for all Mozilla modules, broken down by different areas of the project.<br />
<br />
* [[Modules/All|All in one big list]]<br />
<br />
* [[Modules/Firefox|Firefox]]<br />
* [[Modules/Thunderbird|Thunderbird]]<br />
* [[Modules/SeaMonkey|SeaMonkey]]<br />
* [[Modules/Calendar|Calendar]]<br />
* [[Modules/Boot2Gecko|Boot2Gecko]]<br />
<br />
* [[Modules/Toolkit|Toolkit]]<br />
* [[Modules/Core|Core]]<br />
* [[Modules/MailNews_Core|MailNews Core]]<br />
<br />
* [[Modules/Bugzilla|Bugzilla]] - the Bugzilla software itself<br />
* [[Modules/bugzilla.mozilla.org|bugzilla.mozilla.org]] - the particular Bugzilla installation run by the Mozilla project<br />
* [[Modules/Other|Other]] (code modules which aren't in any of the above categories)<br />
* [[Modules/Activities|Activities]] (non-code)</div>MitchellBakerhttps://wiki.mozilla.org/index.php?title=WeeklyUpdates/2012-03-19&diff=409030WeeklyUpdates/2012-03-192012-03-19T17:45:28Z<p>MitchellBaker: /* Speakers */</p>
<hr />
<div><br />
<small>[[WeeklyUpdates/{{#time:Y-m-d|{{SUBPAGENAME}} -1 week}}|« previous week]] | [[WeeklyUpdates|index]] | [[WeeklyUpdates/{{#time:Y-m-d|{{SUBPAGENAME}} +1 week}}|next week »]]</small><br />
<br />
{{conf|8600}}<br />
<br />
__TOC__<br />
<br />
= All-hands Status Meeting Agenda =<br />
<br />
Items in this section will be shared during the live all-hand status meeting.<br />
<br />
== Friends of the Tree [[Image:Tree.gif|Friends of the Tree]] ==<br />
<br />
== Upcoming Events ==<br />
<br />
=== This Week ===<br />
* Help QA name our new tool!<br />
** QA has been working on a new Test Case Management tool (to replace Litmus later in 2012). And for some tl;dr reasons, we're looking for a new name before the 3/30 release of 1.0. We have a short list of names and would love for YOU, the Community, to chime in this week with your opinions and creativity. We'll choose the new name this weekend.<br />
** [http://caseconductor.wordpress.com/ Blog post] <br />
** [http://www.surveymonkey.com/s/9PCCMCF Take the Survey]<br />
<br />
=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===<br />
<br />
=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===<br />
<br />
=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===<br />
<br />
=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===<br />
<br />
=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===<br />
<br />
=== Next Week ===<br />
* Contributor Engagement BrownBag - Friday, 3/37, @ 12pm Pacific.<br />
<br />
== Product Status Updates (voice updates) ==<br />
<br />
=== Firefox Desktop ===<br />
''Speaker Location: '''no voice update (hello from London!) (there's a lot of jetlag here!)''''' <br />
<br />
* 4 -- yes 4! -- exciting pieces of UI updates coming soon!<br />
** new about:home landing progress {{bug|711157}}<br />
** new new-tab designs {{bug|729878}}<br />
** new download manager landing progress {{bug|564934}}<br />
** new web apps UI {{bug|697006}}, {{bug|702363}}<br />
<br />
=== Mobile Firefox ===<br />
''Speaker Location:'' <br />
<br />
=== Thunderbird ===<br />
''Speaker Location:'' Toronto<br />
<br />
* Two new features landed in [http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-comm-central/ Daily] & [http://www.mozilla.org/en-US/thunderbird/channel/ Earlybird]:<br />
** Instant Messaging<br />
*** Add Twitter, Facebook Chat, Google Talk, IRC to Thunderbird<br />
*** Search through your instant messaging conversations<br />
** Filelink<br />
*** Use online storage services to store large size email file attachments<br />
<br />
=== Older Branch Work ===<br />
''Speaker Location:'' <br />
<br />
=== Mozilla Popcorn ===<br />
''Speaker Location:''<br />
<br />
=== Identity ===<br />
''Speaker Location:''<br />
<br />
=== Services ===<br />
''Speaker Location:''<br />
<br />
== Speakers ==<br />
<br />
The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation.<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
! Title<br />
! Presenter<br />
! Topic<br />
! Media<br />
! More Details<br />
|-<br />
| Chief Lizard Wrangler<br />
| Mitchell Baker<br />
| Audio / Video Codecs<br />
| Links to slides or images you want displayed on screen<br />
| http://hacks.mozilla.org/2012/03/video-mobile-and-the-open-web/;<br />
http://blog.lizardwrangler.com/2012/03/18/video-user-experience-and-our-mission/<br />
<br />
|-<br />
|}<br />
<br />
== Introducing New Hires ==<br />
{| class="fullwidth-table"<br />
|-<br />
! New Hire<br />
! Introduced by<br />
! Speaker location<br />
! Will be working on<br />
|-<br />
| ''Who is the new hire?''<br />
| ''Who will be introducing that person?''<br />
| ''From which office will that introduction be transmitted?''<br />
| ''What will the new person be working on?''<br />
|-<br />
<!-- Insert new rows here --><br />
|- <br />
| ''Desiree Almendral''<br />
| ''James Murdock''<br />
| ''Mountain View, CA''<br />
| ''Legal Counsel''<br />
|-<br />
| ''Adrian Fernandez''<br />
| ''Phong Tran''<br />
| ''Mountain View, CA''<br />
| ''Site Reliability Engineer''<br />
|-<br />
| ''David Hylands''<br />
| ''Faramarz Rashed''<br />
| ''Mountain View, CA''<br />
| ''System Engineer, Boot to Gecko''<br />
|-<br />
| ''Joanne Nagel''<br />
| ''Susan Chen''<br />
| ''Mountain View, CA''<br />
| ''Strategic Partner Manager''<br />
|-<br />
|}<br />
<br />
== Introducing New Interns ==<br />
{| class="fullwidth-table"<br />
|-<br />
! New Intern<br />
! Introduced by<br />
! Speaker location<br />
! Will be working on<br />
|-<br />
| ''Who is the new intern?''<br />
| ''Who will be introducing that person?''<br />
| ''From which office will that introduction be transmitted?''<br />
| ''What will the new person be working on?''<br />
|-<br />
<!-- Insert new rows here --><br />
|-<br />
|}<br />
<br />
== Roundtable ==<br />
<br />
= &lt;meta&gt; =<br />
<br />
Notes and non-voice status updates that aren't part of the live meeting go here.<br />
<br />
== Status Updates By Team (*non-voice* updates) ==<br />
<br />
=== Firefox ===<br />
<br />
=== Platform ===<br />
<br />
=== Services ===<br />
<br />
Standing up the preliminary Apps-in-the-Cloud servers this week for the Apps team to develop against.<br />
<br />
=== Messaging ===<br />
<br />
=== Mobile ===<br />
<br />
=== IT ===<br />
<br />
=== Release Engineering ===<br />
<br />
=== QA ===<br />
<br />
==== Test Execution ====<br />
<br />
==== WebQA ====<br />
*Affiliates<br />
** Successful [https://wiki.mozilla.org/Websites/Affiliates/Release/2012/3#Mar._14 3/14 release] - push [https://bugzilla.mozilla.org/show_bug.cgi?id=735679 bug 735679]<br />
** [fromAutomation] [https://bugzilla.mozilla.org/show_bug.cgi?id=735058 bug 735058]<br />
*AMO<br />
** lots of cleanup/refactoring of tests<br />
** Marlena will be focused on Browser Quest<br />
** Testday scheduled for March 28 (Thx Teodosia)<br />
*Mozilla.com<br />
** parts of 1.10 shipped<br />
*Mozillians<br />
** [http://bit.ly/yypzre 3/14] release was at risk and missed<br />
** next release scheduled for 3/21<br />
*MDN<br />
** 2.4.5 release shipped<br />
*Socorro<br />
** Successful [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced;target_milestone=2.5.1;product=Socorro;list_id=2596620 2.5.1 milestone] 3/14 release<br />
** [fromAutomation] [https://bugzilla.mozilla.org/show_bug.cgi?id=735860 bug 735860]<br />
*SUMO<br />
** Fully on continuous deployment<br />
** Migrated to WD, will migrate the Jenkins job very soon<br />
*Case Conductor<br />
** Testing .9, discussing the new name for the product<br />
<br />
==== QA Community ====<br />
<br />
==== Automation Services ====<br />
Blog post: [http://www.hskupin.info/2012/03/17/memchaser-0-2-1-released/ MemChaser 0.2.1 released]<br />
<br />
=== Automation & Tools ===<br />
<br />
=== Security ===<br />
<br />
=== Engagement ===<br />
<br />
==== PR ====<br />
<br />
==== Events ====<br />
<br />
==== Creative Team ====<br />
<br />
==== Community Marketing ====<br />
<br />
=== Support ===<br />
<br />
=== Metrics ===<br />
<br />
=== Evangelism ===<br />
<br />
=== Labs ===<br />
<br />
=== Apps ===<br />
<br />
=== Developer Tools ===<br />
<br />
=== Add-ons ===<br />
<br />
=== Webdev ===<br />
<br />
=== L10n ===<br />
<br />
=== People Team ===<br />
<br />
=== WebFWD ===<br />
We are in the throes of planning our 2nd WebFWD Summit. The theme is "Making it Work - Building successful Open Source Projects." Tentative dates (pending confirmations from some outside participants) is May 11 - 14. Stay tuned for details!<br />
<br />
== Foundation Updates ==</div>MitchellBakerhttps://wiki.mozilla.org/index.php?title=Modules&diff=408933Modules2012-03-19T15:02:39Z<p>MitchellBaker: /* Creating A New Module */</p>
<hr />
<div>Mozilla operates under a [http://www.mozilla.org/hacking/module-ownership.html module ownership governance system]. A '''module''' is a discrete unit of code or activity. An '''owner''' is the person in charge of a module or sub-module. A '''peer''' is a person whom the owner has appointed to help them. A module may have multiple peers and, very occasionally, multiple owners.<br />
<br />
The system is overseen by the owner and peers of the [[Modules/Activities#Module_Ownership_System|Module Ownership module]]. Owners may add and remove peers from their modules as they wish, without reference to anyone else.<br />
<br />
===Creating A New Module===<br />
<br />
Ideally, a Module should exist for all significant chunks of work or code in the Mozilla project. Who you talk to about this depends on the area of the project concerned.<br />
<br />
For many areas, the ability to create, alter ownership of and destroy sub-modules has been delegated to the owner of the module whose broad scope covers that area. This is true for Firefox, Thunderbird, and all of the other areas listed below except for [[Modules/Core|Core]], [[Modules/Activities|Activities]] and [[Modules/Other|Other]]. The controlling module is the first one listed on the page. Please contact that person about getting new modules created.<br />
<br />
For Core modules and Activities (non-code) modules, please post your enquiry in the mozilla.governance newsgroup, cc'ing the owner and peers of the [[Modules/Activities#Module_Ownership_System|Module Ownership module]] at module-ownership [at] mozilla [dot] com. If there is something sensitive about your enquiry that you aren't comfortable writing in the newsgroup, or in case of uncertainty, please send it to module-ownership [at] mozilla [dot] com.<br />
<br />
===Module Lists===<br />
<br />
These pages list the owners and their peers for all Mozilla modules, broken down by different areas of the project.<br />
<br />
* [[Modules/All|All in one big list]]<br />
<br />
* [[Modules/Firefox|Firefox]]<br />
* [[Modules/Thunderbird|Thunderbird]]<br />
* [[Modules/SeaMonkey|SeaMonkey]]<br />
* [[Modules/Calendar|Calendar]]<br />
* [[Modules/Boot2Gecko|Boot2Gecko]]<br />
<br />
* [[Modules/Toolkit|Toolkit]]<br />
* [[Modules/Core|Core]]<br />
* [[Modules/MailNews_Core|MailNews Core]]<br />
<br />
* [[Modules/Bugzilla|Bugzilla]] - the Bugzilla software itself<br />
* [[Modules/bugzilla.mozilla.org|bugzilla.mozilla.org]] - the particular Bugzilla installation run by the Mozilla project<br />
* [[Modules/Other|Other]] (code modules which aren't in any of the above categories)<br />
* [[Modules/Activities|Activities]] (non-code)</div>MitchellBakerhttps://wiki.mozilla.org/index.php?title=Modules&diff=408851Modules2012-03-19T04:35:11Z<p>MitchellBaker: /* Creating A New Module */</p>
<hr />
<div>Mozilla operates under a [http://www.mozilla.org/hacking/module-ownership.html module ownership governance system]. A '''module''' is a discrete unit of code or activity. An '''owner''' is the person in charge of a module or sub-module. A '''peer''' is a person whom the owner has appointed to help them. A module may have multiple peers and, very occasionally, multiple owners.<br />
<br />
The system is overseen by the owner and peers of the [[Modules/Activities#Module_Ownership_System|Module Ownership module]]. Owners may add and remove peers from their modules as they wish, without reference to anyone else.<br />
<br />
===Creating A New Module===<br />
<br />
Ideally, a Module should exist for all significant chunks of work or code in the Mozilla project. Who you talk to about this depends on the area of the project concerned.<br />
<br />
For many areas, the ability to create, alter ownership of and destroy sub-modules has been delegated to the owner of the module whose broad scope covers that area. This is true for Firefox, Thunderbird, and all of the other areas listed below except for [[Modules/Core|Core]], [[Modules/Activities|Activities]] and [[Modules/Other|Other]]. The controlling module is the first one listed on the page. Please contact that person about getting new modules created.<br />
<br />
For Core modules, Activities (non-code) modules, please post your enquiry in the mozilla.governance newsgroup, with a cc to the owner and peers of the [[Modules/Activities#Module_Ownership_System|Module Ownership module]]. If there is something sensitive about your enquiry that you aren't comfortable adding to the newsgroup, or in caes of uncertainty, please send it to the owner and peers of the [[Modules/Activities#Module_Ownership_System|Module Ownership module]].<br />
<br />
===Module Lists===<br />
<br />
These pages list the owners and their peers for all Mozilla modules, broken down by different areas of the project.<br />
<br />
* [[Modules/All|All in one big list]]<br />
<br />
* [[Modules/Firefox|Firefox]]<br />
* [[Modules/Thunderbird|Thunderbird]]<br />
* [[Modules/SeaMonkey|SeaMonkey]]<br />
* [[Modules/Calendar|Calendar]]<br />
* [[Modules/Boot2Gecko|Boot2Gecko]]<br />
<br />
* [[Modules/Toolkit|Toolkit]]<br />
* [[Modules/Core|Core]]<br />
* [[Modules/MailNews_Core|MailNews Core]]<br />
<br />
* [[Modules/Bugzilla|Bugzilla]] - the Bugzilla software itself<br />
* [[Modules/bugzilla.mozilla.org|bugzilla.mozilla.org]] - the particular Bugzilla installation run by the Mozilla project<br />
* [[Modules/Other|Other]] (code modules which aren't in any of the above categories)<br />
* [[Modules/Activities|Activities]] (non-code)</div>MitchellBakerhttps://wiki.mozilla.org/index.php?title=Modules/Other&diff=386816Modules/Other2012-01-13T02:02:36Z<p>MitchellBaker: -Adding BrowserID Module</p>
<hr />
<div>{{Module<br />
|name=Batucada<br />
|description=The software platform for the Drumbeat website<br />
|owner=[mailto:paul@mozillafoundation.org Paul Osman]<br />
|peers=<br />
|group=drumbeat-website<br />
|source_dirs=http://github.com/mozilla/batucada<br />
|url=http://www.drumbeat.org/project/batucada<br />
}}<br />
<br />
{{Module<br />
|name=BrowserID<br />
|description=(a) Server Code, (b) Server deployment (during labs / prototype phase); and (c) *navigator.id.* API across Mozilla codebases (desktop, mobile, WebRT,..) <br />
|owner=[mailto:benadida@mozilla.com Ben Adida]<br />
|peers=Mike Hanson, Lloyd Hilaiel, Jonas Sicking<br />
|group=<br />
|source_dirs=<br />
BrowserID server code: https://github.com/mozilla/browserid, <br />
BrowserID server deployment: https://browserid.org <br />
<br />
|mailing list=https://lists.mozilla.org/listinfo/dev-identity <br />
url=<br />
<br />
}}<br />
<br />
{{Module<br />
|name=Camino<br />
|description=Mac only standalone browser<br />
|owner=[mailto:pinkerton@aol.net Mike Pinkerton], [mailto:stuart.morgan@alumni.case.edu Stuart Morgan]<br />
|peers=[mailto:mark@moxienet.com Mark Mentovai], [mailto:smfr@smfr.org Simon Fraser]<br />
|group=<br />
|source_dirs=camino/<br />
|url=<br />
|components=Camino<br />
}}<br />
<br />
{{Module<br />
|name=ChatZilla<br />
|description=IRC client<br />
|owner=[mailto:rginda@hacksrus.com Rob Ginda]<br />
|peers=[mailto:gijskruitbosch@gmail.com Gijs Kruitbosch], [mailto:samuel@sieb.net Samuel Sieb], [mailto:silver@warwickcompsoc.co.uk James Ross]<br />
|group=dev-apps-chatzilla<br />
|source_dirs=extensions/irc/<br />
|url=http://chatzilla.hacksrus.com/<br />
|components=Other Applications::ChatZilla<br />
}}<br />
<br />
{{Module<br />
|name=Composer<br />
|description=Editor/Composer<br />
|owner=[mailto:daniel@glazman.org Daniel Glazman]<br />
|peers=[mailto:brade@comcast.net Kathy Brade], [mailto:neil@parkwaycc.co.uk Neil Rashbrook], [mailto:smfr@smfr.org Simon Fraser], [mailto:timeless@mozdev.org Josh 'timeless' Soref]<br />
|group=dev-tech-editor<br />
|source_dirs=editor/<br />
|url=http://www.mozilla.org/editor<br />
|components=Composer<br />
}}<br />
<br />
{{Module<br />
|name=Devtools<br />
|description=Mozilla Developer Tools<br />
|owner=[mailto:rcampbell@mozilla.com Rob Campbell]<br />
|peers=[mailto:ddahl@mozilla.com David Dahl], [mailto:mihai.sucan@gmail.com Mihai Sucan], [mailto:dcamp@mozilla.com Dave Camp], [mailto:jwalker@mozilla.com Joe Walker], [mailto:prouget@mozilla.com Paul Rouget]<br />
|group=dev-apps-firefox<br />
|source_dirs=browser/devtools, toolkit/devtools<br />
|url=http://www.mozilla.org/projects/firefox/<br />
|components=Firefox::Developer Tools<br />
}}<br />
<br />
{{Module<br />
|name=Directory SDK<br />
|description=Tools and SDKs for accessing LDAP Directories.<br />
|owner=[mailto:mcs@pearlcrescent.com Mark C. Smith]<br />
|peers=[mailto:anton.bobrov@sun.com Anton Bobrov], [mailto:richm@stanfordalumni.org Rich Megginson]<br />
|group=dev-tech-ldap<br />
|source_dirs=directory/<br />
|url=http://www.mozilla.org/directory<br />
|components=Directory<br />
}}<br />
<br />
{{Module<br />
|name=DOM Inspector<br />
|description=An extension that allows the user to inspect and edit the DOM of documents being displayed.<br />
|owner=[mailto:sdwilsh@shawnwilsher.com Shawn Wilsher]<br />
|peers=[mailto:neil@parkwaycc.co.uk Neil Rashbrook], [mailto:sevenspade@gmail.com Colby Russell]<br />
|group=dev-apps-firefox<br />
|source_dirs=extensions/inspector/, layout/inspector/<br />
|url=http://www.mozilla.org/projects/firefox/<br />
|components=Other Applications::DOM Inspector<br />
}}<br />
<br />
{{Module<br />
|name=Fennec<br />
|description=Mobile Web Browser<br />
|owner=[mailto:mark.finkle@gmail.com Mark Finkle]<br />
|peers=[mailto:ben@stechz.com Ben Stover], [mailto:21@vingtetun.org Vivien Nicolas], [mailto:mbrubeck@limpet.net Matt Brubeck], [mailto:wjohnston@mozilla.com Wes Johnston]<br />
|group=dev-platforms-mobile<br />
|source_dirs=mobile/<br />
|url=https://wiki.mozilla.org/Fennec<br />
|components=Fennec<br />
}}<br />
<br />
{{Module<br />
|name=Sync<br />
|description=Firefox Sync client<br />
|owner=[mailto:mconnor@mozilla.com Mike Connor]<br />
|peers=[mailto:rnewman@mozilla.com Richard Newman], Philipp von Weitershausen<br />
|group=<br />
|source_dirs=services/sync/<br />
|url=https://wiki.mozilla.org/Services/Process/Code_Review<br />
|components=Sync<br />
}}<br />
<br />
{{Module<br />
|name=Party Tool<br />
|description=PHP-based party tool used for Firefox Party<br />
|owner=[mailto:rflint@ryanflint.com Ryan Flint]<br />
|peers=[mailto:morgamic@mozilla.com Mike Morgan], [mailto:reed@reedloden.com Reed Loden]<br />
|group=dev-apps-webtools<br />
|source_dirs=webtools/partytool/<br />
|url=http://wiki.mozilla.org/Webtools:PartyTool<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=Penelope<br />
|description=Eudora-like functionality and theme added to Thunderbird.<br />
|owner=[mailto:beckley@qualcomm.com Jeff Beckley]<br />
|peers=<br />
|group=<br />
|source_dirs=penelope/<br />
|url=https://wiki.mozilla.org/Penelope<br />
|components=Penelope<br />
}}<br />
<br />
{{Module<br />
|name=Rhino<br />
|description=JavaScript interpreter implemented in Java<br />
|owner=[mailto:norrisboyd@gmail.com Norris Boyd]<br />
|peers=[mailto:hannesw@gmail.com Hannes Wallnöfer], [mailto:inonit@inonit.com David Caldwell], [mailto:szegedia@freemail.hu Attila Szegedi]<br />
|group=dev-tech-js-engine<br />
|source_dirs=js/rhino/<br />
|url=http://www.mozilla.org/rhino/<br />
|components=Rhino<br />
}}<br />
<br />
{{Module<br />
|name=Standalone Composer<br />
|description=Standalone editor/composer based on mozilla/toolkit<br />
|owner=[mailto:daniel@glazman.org Daniel Glazman]<br />
|peers=[mailto:brade@comcast.net Kathy Brade], [mailto:neil@parkwaycc.co.uk Neil Rashbrook]<br />
|group=dev-tech-editor,dev-apps-other<br />
|source_dirs=composer/<br />
|url=http://www.mozilla.org/editor/, http://www.nvu.com/, http://glazman.org/weblog/dotclear/index.php?Nvu<br />
|components=<br />
}}<br />
<br />
{{Module<br />
|name=Venkman<br />
|description=JavaScript Debugger frontend<br />
|owner=[mailto:rginda@hacksrus.com Rob Ginda]<br />
|peers=[mailto:brendan@mozilla.org Brendan Eich], [mailto:gijskruitbosch@gmail.com Gijs Kruitbosch], [mailto:shaver@mozilla.org Mike Shaver], [mailto:silver@warwickcompsoc.co.uk James Ross], [mailto:timeless@mozdev.org Josh 'timeless' Soref]<br />
|group=dev-apps-js-debugger<br />
|source_dirs=extensions/venkman/<br />
|url=http://www.mozilla.org/projects/venkman<br />
http://www.hacksrus.com/~ginda/venkman/<br />
|components=Other Applications::Venkman JS Debugger<br />
}}</div>MitchellBakerhttps://wiki.mozilla.org/index.php?title=Module_Owners_Activities_Modules&diff=386425Module Owners Activities Modules2012-01-12T00:31:29Z<p>MitchellBaker: /* Governance Submodule: Module Ownership System */</p>
<hr />
<div>'''Activities Modules'''<br />
<br />
== Overview ==<br />
Activities [[Modules_and_Module_Ownership|modules]] are a part of Mozilla's [http://www.mozilla.org/hacking/module-ownership.html Module Ownership system], a basic organizing and governance principle of the Mozilla project. (The name "activities" may change. It's a bit too generic and could apply to<br />
anything, including code modules. If you've got a good idea, please let Mitchell Baker know.)<br />
<br />
== Governance Module ==<br />
<br />
* owner: Mitchell Baker<br />
* peer(s): Brendan Eich<br />
* newsgroup: mozilla.governance<br />
* scope: project-wide<br />
* governing policy document: <br />
* responsibilities: Policies and process for how we distribute authority and govern ourselves; including:<br />
** Development and Implementation of new policies as appropriate for delegation of authority and responsibility<br />
** Management of the source tree<br />
** Balancing different constituencies of the Mozilla project<br />
** Maintaining the Mozilla identity as we take on new activities<br />
* 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.<br />
* final decision-makers: the final decision maker -- when needed -- for the Mozilla project in technical matters is Brendan Eich and for other matters is Mitchell Baker; this has been the case since 1998 for Brendan and 1999 for Mitchell. I haven't figured out how to capture that clearly here. That authority is broader than "policy and process." I don't know if that is a property that attaches to the owner / peer of the governance module or if it is more personal. It should be stated somewhere clearly though. <br />
<br />
There is a [[GovernanceIssues|list of open governance issues]].<br />
<br />
Due to the large and diverse nature of topics included in the Governance<br />
module, we will divide responsibilities by sub-module, in order to delegate<br />
authority for specific pieces and identify particular areas of expertise. <br />
<br />
===Governance Submodule: Module Ownership System=== <br />
<br />
* owner: Brendan Eich<br />
* peers: Stuart Parmenter, Dan Mosedale, Robert Kaiser, Mike Connor, David Baron, Frank Hecker, Mitchell Baker [mailto:module-ownership@mozilla.org E-mail this group]<br />
* observers: Guillermo Movia (this is a new role we're trying out as of Jan 2012. The observers are watching and learning how the module operates, since there's no code in this module to serve as a learning /participation tool)<br />
* newsgroup: mozilla.governance<br />
* scope: project-wide<br />
* responsibilities: Healthy operation of the module ownership system, including topics such as:<br />
** Filling vacant roles where appropriate<br />
** Ensuring module owners are fulfilling their responsibilities, and replacing those who are not<br />
** Creating and staffing new modules where new parts of the project evolve.<br />
** Figuring out what to do if a module isn't getting enough attention<br />
** Resolving conflicts among module owners<br />
<br />
===Governance Submodule: Incubator Repositories=== <br />
<br />
* owner: Stuart Parmenter<br />
* peer(s): Jonas Sicking, Mike Connor, Mike Shaver, Christian Sejersen <br />
*newsgroup: mozilla.governance<br />
* governing policy document: http://www.mozilla.org/hacking/incubator-repository.html<br />
* scope: project-wide<br />
* responsibilities: Implementing the Incubator Repository Policy including topics such as:<br />
** Evaluating requests for new incubator repositories<br />
** Determining if an incubatory repository may live longer than six months<br />
** Other issues that come up in the operation of incubator repositories<br />
<br />
===Governance Submodule: Commit Access Policy===<br />
* owner: Mitchell Baker<br />
* peers:<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/hacking/committer/ Commit Access Policy ]<br />
* scope: project-wide<br />
<br />
===Governance Submodule: Security Policy===<br />
* owner: Frank Hecker<br />
* peers:<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/projects/security/security-bugs-policy.html Handling Mozilla Security Bugs]<br />
* scope: project-wide (applies to all Mozilla projects)<br />
<br />
===Governance Submodule: Mozilla CA Certificate Policy===<br />
* owner: Frank Hecker<br />
* peers: Kathleen Wilson<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/projects/security/certs/policy/ Mozilla CA Certificate Policy]<br />
* scope: project-wide (applies to all Mozilla projects that includes root certificates)<br />
<br />
===Governance Submodule: Code Review Policy===<br />
* owner: Mitchell Baker<br />
* peers: Brendan Eich<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/hacking/reviewers.html Mozilla "super-review"]<br />
* scope: project-wide<br />
<br />
===Governance Submodule: Performance Regression Policy===<br />
* owner: Mitchell Baker<br />
* peers:<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/hacking/reviewers.html Mozilla "super-review"]<br />
* scope: project-wide<br />
<br />
==Planet Mozilla Module== <br />
* owner: Robert Accettura<br />
* peers: Asa Dotzler, Reed Loden, J. Paul Reed<br />
* newsgroup: <br />
* scope: project-wide<br />
* responsibilities: content and policy for planet.mozilla.org, including topics such as:<br />
** which blogs are syndicated to planet.mozilla.org<br />
** which content from syndicated blogs in included<br />
** other planet.mozilla.org policy issues<br />
<br />
==Mozilla Public License Module==<br />
<br />
* owner: Mitchell Baker<br />
*peers: Heather Meeker, Luis Villa, Harvey Anderson, Gervase Markham<br />
*newsgroup: mozilla.governance; and mozilla.governance-mpl-update (at least during the process of updating the MPL 1.1, beginning March 10, 2010)<br />
*scope: project-wide, and affects other projects using the MPL<br />
*responsibilities: maintenance and development of the MPL<br />
** changes in the legal landscape which could /should be reflected<br />
** changes in FLOSS development practices which could / should be reflected<br />
<br />
==www.mozilla.org Module==<br />
* owners: Reed Loden (technical issues), David Boswell (content issues)<br />
* peers: Elika Etemad, Robert Kaiser, Eric Shepherd<br />
* sub-modules: [[Mozilla.org/Owners_List|Owners List]]<br />
* newsgroup: [http://groups.google.com/group/mozilla.dev.mozilla-org/topics mozilla.dev.mozilla-org]<br />
* scope: project-wide<br />
* responsibilities: content and policy for www.mozilla.org<br />
<br />
==CA Certificates Module== <br />
*owner: Kathleen Wilson<br />
*peers: Frank Hecker<br />
*newsgroup: mozilla.dev.security.policy<br />
*governing policy document: <br />
*http://www.mozilla.org/projects/security/certs/policy/<br />
*scope: project-wide (applies to all Mozilla software that includes root certificates)<br />
*responsibilities: Determine which root certificates should be included in Mozilla software products and which trust bits should be set on them, and evaluate requests from Certification Authorities (CAs) for inclusion of new root certificates.<br />
<br />
==Participation Metrics Module==<br />
<br />
* owner: Asa Dotzler<br />
* peers: Daniel Einspanjer, Ken Kovash<br />
* newsgroup: <br />
* governing policy document: N/A<br />
* https://wiki.mozilla.org/ParticipationMetrics/roadmap<br />
* scope: project-wide <br />
* responsibilities: develop, monitor and analyze metrics relating to participation in the Mozilla project, including such things as: <br />
** determining which questions are most important to ask (how many people do X?)<br />
** determining what data is relevant to answer these questions<br />
** designing and operating a system to generate the requested data<br />
** analyzing the resulting metrics<br />
** notifying appropriate people when participation starts to change significantly<br />
** assisting various groups to understand and use the metrics to strengthen participation<br />
** produce periodic report/analysis of participation metrics <br />
*other: This module is explicitly NOT a "maintain community health" module. This responsibility lives across the Mozilla project. Every group working on Mozilla is responsible for developing participation in their area. The role of this module is to add metrics as a tool for various groups to use to help understand the state of participation.<br />
<br />
<br />
==Productive Communications Module (aka the "Conductors")==<br />
*owner: Stormy Peters<br />
*peers: David Ascher , Dietrich Ayala, Mike Beltzner, Matt Claypotch, David Eaves, Gen Kanai, Michelle Luna, Kev Needham, Johnathan Nightingale, Melissa Shapiro, Gavin Sharp, Benjamin Smedberg, Mike Taylor (Bear), David Tenser, Daniel Veditz<br />
<br />
*newsgroup: mozilla.governance<br />
*email: conductors [at] mozilla [dot] org<br />
*governing policy document: N/A<br />
*http://wiki.mozilla.org/Conductors<br />
*scope: project-wide<br />
*responsibilities: promotion of productive communications styles within Mozilla, where "productive" means simultaneously honest and civil. This includes topics such as:<br />
**coaching people on who to respond to nasty settings;<br />
**coaching people to think a little before they hit post/send/submit.<br />
**coaching people on how to be direct and yet civil, notifying people they are at or past the boundary;<br />
**coaching people to recognize legitimate comments/ complaints / differences of opinion despite poor communication style<br />
**redirecting conversations into a better place,<br />
**building a culture of respect in how we communicate with difficult and contentious issues<br />
**when necessary, letting people know they've gone beyond the boundaries.</div>MitchellBakerhttps://wiki.mozilla.org/index.php?title=Module_Owners_Activities_Modules&diff=378099Module Owners Activities Modules2011-12-13T07:16:11Z<p>MitchellBaker: /* Productive Communications Module (aka the "Conductors") */</p>
<hr />
<div>'''Activities Modules'''<br />
<br />
== Overview ==<br />
Activities [[Modules_and_Module_Ownership|modules]] are a part of Mozilla's [http://www.mozilla.org/hacking/module-ownership.html Module Ownership system], a basic organizing and governance principle of the Mozilla project. (The name "activities" may change. It's a bit too generic and could apply to<br />
anything, including code modules. If you've got a good idea, please let Mitchell Baker know.)<br />
<br />
== Governance Module ==<br />
<br />
* owner: Mitchell Baker<br />
* peer(s): Brendan Eich<br />
* newsgroup: mozilla.governance<br />
* scope: project-wide<br />
* governing policy document: <br />
* responsibilities: Policies and process for how we distribute authority and govern ourselves; including:<br />
** Development and Implementation of new policies as appropriate for delegation of authority and responsibility<br />
** Management of the source tree<br />
** Balancing different constituencies of the Mozilla project<br />
** Maintaining the Mozilla identity as we take on new activities<br />
* 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.<br />
* final decision-makers: the final decision maker -- when needed -- for the Mozilla project in technical matters is Brendan Eich and for other matters is Mitchell Baker; this has been the case since 1998 for Brendan and 1999 for Mitchell. I haven't figured out how to capture that clearly here. That authority is broader than "policy and process." I don't know if that is a property that attaches to the owner / peer of the governance module or if it is more personal. It should be stated somewhere clearly though. <br />
<br />
There is a [[GovernanceIssues|list of open governance issues]].<br />
<br />
Due to the large and diverse nature of topics included in the Governance<br />
module, we will divide responsibilities by sub-module, in order to delegate<br />
authority for specific pieces and identify particular areas of expertise. <br />
<br />
===Governance Submodule: Module Ownership System=== <br />
<br />
* owner: Brendan Eich<br />
* peers: Stuart Parmenter, Dan Mosedale, Robert Kaiser, Mike Connor, David Baron, Frank Hecker, Mitchell Baker [mailto:module-ownership@mozilla.org E-mail this group]<br />
* newsgroup: mozilla.governance<br />
* scope: project-wide<br />
* responsibilities: Healthy operation of the module ownership system, including topics such as:<br />
** Filling vacant roles where appropriate<br />
** Ensuring module owners are fulfilling their responsibilities, and replacing those who are not<br />
** Creating and staffing new modules where new parts of the project evolve.<br />
** Figuring out what to do if a module isn't getting enough attention<br />
** Resolving conflicts among module owners<br />
<br />
===Governance Submodule: Incubator Repositories=== <br />
<br />
* owner: Stuart Parmenter<br />
* peer(s): Jonas Sicking, Mike Connor, Mike Shaver, Christian Sejersen <br />
*newsgroup: mozilla.governance<br />
* governing policy document: http://www.mozilla.org/hacking/incubator-repository.html<br />
* scope: project-wide<br />
* responsibilities: Implementing the Incubator Repository Policy including topics such as:<br />
** Evaluating requests for new incubator repositories<br />
** Determining if an incubatory repository may live longer than six months<br />
** Other issues that come up in the operation of incubator repositories<br />
<br />
===Governance Submodule: Commit Access Policy===<br />
* owner: Mitchell Baker<br />
* peers:<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/hacking/committer/ Commit Access Policy ]<br />
* scope: project-wide<br />
<br />
===Governance Submodule: Security Policy===<br />
* owner: Frank Hecker<br />
* peers:<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/projects/security/security-bugs-policy.html Handling Mozilla Security Bugs]<br />
* scope: project-wide (applies to all Mozilla projects)<br />
<br />
===Governance Submodule: Mozilla CA Certificate Policy===<br />
* owner: Frank Hecker<br />
* peers: Kathleen Wilson<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/projects/security/certs/policy/ Mozilla CA Certificate Policy]<br />
* scope: project-wide (applies to all Mozilla projects that includes root certificates)<br />
<br />
===Governance Submodule: Code Review Policy===<br />
* owner: Mitchell Baker<br />
* peers: Brendan Eich<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/hacking/reviewers.html Mozilla "super-review"]<br />
* scope: project-wide<br />
<br />
===Governance Submodule: Performance Regression Policy===<br />
* owner: Mitchell Baker<br />
* peers:<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/hacking/reviewers.html Mozilla "super-review"]<br />
* scope: project-wide<br />
<br />
==Planet Mozilla Module== <br />
* owner: Robert Accettura<br />
* peers: Asa Dotzler, Reed Loden, J. Paul Reed<br />
* newsgroup: <br />
* scope: project-wide<br />
* responsibilities: content and policy for planet.mozilla.org, including topics such as:<br />
** which blogs are syndicated to planet.mozilla.org<br />
** which content from syndicated blogs in included<br />
** other planet.mozilla.org policy issues<br />
<br />
==Mozilla Public License Module==<br />
<br />
* owner: Mitchell Baker<br />
*peers: Heather Meeker, Luis Villa, Harvey Anderson, Gervase Markham<br />
*newsgroup: mozilla.governance; and mozilla.governance-mpl-update (at least during the process of updating the MPL 1.1, beginning March 10, 2010)<br />
*scope: project-wide, and affects other projects using the MPL<br />
*responsibilities: maintenance and development of the MPL<br />
** changes in the legal landscape which could /should be reflected<br />
** changes in FLOSS development practices which could / should be reflected<br />
<br />
==www.mozilla.org Module==<br />
* owners: Reed Loden (technical issues), David Boswell (content issues)<br />
* peers: Elika Etemad, Robert Kaiser, Eric Shepherd<br />
* sub-modules: [[Mozilla.org/Owners_List|Owners List]]<br />
* newsgroup: [http://groups.google.com/group/mozilla.dev.mozilla-org/topics mozilla.dev.mozilla-org]<br />
* scope: project-wide<br />
* responsibilities: content and policy for www.mozilla.org<br />
<br />
==CA Certificates Module== <br />
*owner: Kathleen Wilson<br />
*peers: Frank Hecker<br />
*newsgroup: mozilla.dev.security.policy<br />
*governing policy document: <br />
*http://www.mozilla.org/projects/security/certs/policy/<br />
*scope: project-wide (applies to all Mozilla software that includes root certificates)<br />
*responsibilities: Determine which root certificates should be included in Mozilla software products and which trust bits should be set on them, and evaluate requests from Certification Authorities (CAs) for inclusion of new root certificates.<br />
<br />
==Participation Metrics Module==<br />
<br />
* owner: Asa Dotzler<br />
* peers: Daniel Einspanjer, Ken Kovash<br />
* newsgroup: <br />
* governing policy document: N/A<br />
* https://wiki.mozilla.org/ParticipationMetrics/roadmap<br />
* scope: project-wide <br />
* responsibilities: develop, monitor and analyze metrics relating to participation in the Mozilla project, including such things as: <br />
** determining which questions are most important to ask (how many people do X?)<br />
** determining what data is relevant to answer these questions<br />
** designing and operating a system to generate the requested data<br />
** analyzing the resulting metrics<br />
** notifying appropriate people when participation starts to change significantly<br />
** assisting various groups to understand and use the metrics to strengthen participation<br />
** produce periodic report/analysis of participation metrics <br />
*other: This module is explicitly NOT a "maintain community health" module. This responsibility lives across the Mozilla project. Every group working on Mozilla is responsible for developing participation in their area. The role of this module is to add metrics as a tool for various groups to use to help understand the state of participation.<br />
<br />
<br />
==Productive Communications Module (aka the "Conductors")==<br />
*owner: Stormy Peters<br />
*peers: David Ascher , Dietrich Ayala, Mike Beltzner, Matt Claypotch, David Eaves, Michelle Luna, Kev Needham, Johnathan Nightingale, Melissa Shapiro, Gavin Sharp, Benjamin Smedberg, Mike Taylor (Bear), David Tenser, Daniel Veditz<br />
<br />
*newsgroup: mozilla.governance<br />
*email: conductors [at] mozilla [dot] org<br />
*governing policy document: N/A<br />
*http://wiki.mozilla.org/Conductors<br />
*scope: project-wide<br />
*responsibilities: promotion of productive communications styles within Mozilla, where "productive" means simultaneously honest and civil. This includes topics such as:<br />
**coaching people on who to respond to nasty settings;<br />
**coaching people to think a little before they hit post/send/submit.<br />
**coaching people on how to be direct and yet civil, notifying people they are at or past the boundary;<br />
**coaching people to recognize legitimate comments/ complaints / differences of opinion despite poor communication style<br />
**redirecting conversations into a better place,<br />
**building a culture of respect in how we communicate with difficult and contentious issues<br />
**when necessary, letting people know they've gone beyond the boundaries.</div>MitchellBakerhttps://wiki.mozilla.org/index.php?title=Module_Owners_Activities_Modules&diff=378098Module Owners Activities Modules2011-12-13T07:14:40Z<p>MitchellBaker: /* Productive Communications Module */</p>
<hr />
<div>'''Activities Modules'''<br />
<br />
== Overview ==<br />
Activities [[Modules_and_Module_Ownership|modules]] are a part of Mozilla's [http://www.mozilla.org/hacking/module-ownership.html Module Ownership system], a basic organizing and governance principle of the Mozilla project. (The name "activities" may change. It's a bit too generic and could apply to<br />
anything, including code modules. If you've got a good idea, please let Mitchell Baker know.)<br />
<br />
== Governance Module ==<br />
<br />
* owner: Mitchell Baker<br />
* peer(s): Brendan Eich<br />
* newsgroup: mozilla.governance<br />
* scope: project-wide<br />
* governing policy document: <br />
* responsibilities: Policies and process for how we distribute authority and govern ourselves; including:<br />
** Development and Implementation of new policies as appropriate for delegation of authority and responsibility<br />
** Management of the source tree<br />
** Balancing different constituencies of the Mozilla project<br />
** Maintaining the Mozilla identity as we take on new activities<br />
* 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.<br />
* final decision-makers: the final decision maker -- when needed -- for the Mozilla project in technical matters is Brendan Eich and for other matters is Mitchell Baker; this has been the case since 1998 for Brendan and 1999 for Mitchell. I haven't figured out how to capture that clearly here. That authority is broader than "policy and process." I don't know if that is a property that attaches to the owner / peer of the governance module or if it is more personal. It should be stated somewhere clearly though. <br />
<br />
There is a [[GovernanceIssues|list of open governance issues]].<br />
<br />
Due to the large and diverse nature of topics included in the Governance<br />
module, we will divide responsibilities by sub-module, in order to delegate<br />
authority for specific pieces and identify particular areas of expertise. <br />
<br />
===Governance Submodule: Module Ownership System=== <br />
<br />
* owner: Brendan Eich<br />
* peers: Stuart Parmenter, Dan Mosedale, Robert Kaiser, Mike Connor, David Baron, Frank Hecker, Mitchell Baker [mailto:module-ownership@mozilla.org E-mail this group]<br />
* newsgroup: mozilla.governance<br />
* scope: project-wide<br />
* responsibilities: Healthy operation of the module ownership system, including topics such as:<br />
** Filling vacant roles where appropriate<br />
** Ensuring module owners are fulfilling their responsibilities, and replacing those who are not<br />
** Creating and staffing new modules where new parts of the project evolve.<br />
** Figuring out what to do if a module isn't getting enough attention<br />
** Resolving conflicts among module owners<br />
<br />
===Governance Submodule: Incubator Repositories=== <br />
<br />
* owner: Stuart Parmenter<br />
* peer(s): Jonas Sicking, Mike Connor, Mike Shaver, Christian Sejersen <br />
*newsgroup: mozilla.governance<br />
* governing policy document: http://www.mozilla.org/hacking/incubator-repository.html<br />
* scope: project-wide<br />
* responsibilities: Implementing the Incubator Repository Policy including topics such as:<br />
** Evaluating requests for new incubator repositories<br />
** Determining if an incubatory repository may live longer than six months<br />
** Other issues that come up in the operation of incubator repositories<br />
<br />
===Governance Submodule: Commit Access Policy===<br />
* owner: Mitchell Baker<br />
* peers:<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/hacking/committer/ Commit Access Policy ]<br />
* scope: project-wide<br />
<br />
===Governance Submodule: Security Policy===<br />
* owner: Frank Hecker<br />
* peers:<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/projects/security/security-bugs-policy.html Handling Mozilla Security Bugs]<br />
* scope: project-wide (applies to all Mozilla projects)<br />
<br />
===Governance Submodule: Mozilla CA Certificate Policy===<br />
* owner: Frank Hecker<br />
* peers: Kathleen Wilson<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/projects/security/certs/policy/ Mozilla CA Certificate Policy]<br />
* scope: project-wide (applies to all Mozilla projects that includes root certificates)<br />
<br />
===Governance Submodule: Code Review Policy===<br />
* owner: Mitchell Baker<br />
* peers: Brendan Eich<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/hacking/reviewers.html Mozilla "super-review"]<br />
* scope: project-wide<br />
<br />
===Governance Submodule: Performance Regression Policy===<br />
* owner: Mitchell Baker<br />
* peers:<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/hacking/reviewers.html Mozilla "super-review"]<br />
* scope: project-wide<br />
<br />
==Planet Mozilla Module== <br />
* owner: Robert Accettura<br />
* peers: Asa Dotzler, Reed Loden, J. Paul Reed<br />
* newsgroup: <br />
* scope: project-wide<br />
* responsibilities: content and policy for planet.mozilla.org, including topics such as:<br />
** which blogs are syndicated to planet.mozilla.org<br />
** which content from syndicated blogs in included<br />
** other planet.mozilla.org policy issues<br />
<br />
==Mozilla Public License Module==<br />
<br />
* owner: Mitchell Baker<br />
*peers: Heather Meeker, Luis Villa, Harvey Anderson, Gervase Markham<br />
*newsgroup: mozilla.governance; and mozilla.governance-mpl-update (at least during the process of updating the MPL 1.1, beginning March 10, 2010)<br />
*scope: project-wide, and affects other projects using the MPL<br />
*responsibilities: maintenance and development of the MPL<br />
** changes in the legal landscape which could /should be reflected<br />
** changes in FLOSS development practices which could / should be reflected<br />
<br />
==www.mozilla.org Module==<br />
* owners: Reed Loden (technical issues), David Boswell (content issues)<br />
* peers: Elika Etemad, Robert Kaiser, Eric Shepherd<br />
* sub-modules: [[Mozilla.org/Owners_List|Owners List]]<br />
* newsgroup: [http://groups.google.com/group/mozilla.dev.mozilla-org/topics mozilla.dev.mozilla-org]<br />
* scope: project-wide<br />
* responsibilities: content and policy for www.mozilla.org<br />
<br />
==CA Certificates Module== <br />
*owner: Kathleen Wilson<br />
*peers: Frank Hecker<br />
*newsgroup: mozilla.dev.security.policy<br />
*governing policy document: <br />
*http://www.mozilla.org/projects/security/certs/policy/<br />
*scope: project-wide (applies to all Mozilla software that includes root certificates)<br />
*responsibilities: Determine which root certificates should be included in Mozilla software products and which trust bits should be set on them, and evaluate requests from Certification Authorities (CAs) for inclusion of new root certificates.<br />
<br />
==Participation Metrics Module==<br />
<br />
* owner: Asa Dotzler<br />
* peers: Daniel Einspanjer, Ken Kovash<br />
* newsgroup: <br />
* governing policy document: N/A<br />
* https://wiki.mozilla.org/ParticipationMetrics/roadmap<br />
* scope: project-wide <br />
* responsibilities: develop, monitor and analyze metrics relating to participation in the Mozilla project, including such things as: <br />
** determining which questions are most important to ask (how many people do X?)<br />
** determining what data is relevant to answer these questions<br />
** designing and operating a system to generate the requested data<br />
** analyzing the resulting metrics<br />
** notifying appropriate people when participation starts to change significantly<br />
** assisting various groups to understand and use the metrics to strengthen participation<br />
** produce periodic report/analysis of participation metrics <br />
*other: This module is explicitly NOT a "maintain community health" module. This responsibility lives across the Mozilla project. Every group working on Mozilla is responsible for developing participation in their area. The role of this module is to add metrics as a tool for various groups to use to help understand the state of participation.<br />
<br />
<br />
==Productive Communications Module (aka the "Conductors")==<br />
*owner: Stormy Peters<br />
*peers: David Ascher , Dietrich Ayala, Mike Beltzner, Matt Claypotch, David Eaves, Michelle Luna, Kev Needham, Johnathan Nightingale, Melissa Shapiro, Gavin Sharp, Benjamin Smedberg, Mike Taylor (Bear), David Tenser, Daniel Veditz (Email conductors [at] mozilla [dot] org)<br />
<br />
*newsgroup: mozilla.governance<br />
*governing policy document: N/A<br />
*http://wiki.mozilla.org/Conductors<br />
*scope: project-wide<br />
*responsibilities: promotion of productive communications styles within Mozilla, where "productive" means simultaneously honest and civil. This includes topics such as:<br />
<br />
**coaching people on who to respond to nasty settings;<br />
**coaching people to think a little before they hit post/send/submit.<br />
**coaching people on how to be direct and yet civil, notifying people they are at or past the boundary;<br />
**coaching people to recognize legitimate comments/ complaints / differences of opinion despite poor communication style<br />
**redirecting conversations into a better place,<br />
**building a culture of respect in how we communicate with difficult and contentious issues<br />
**when necessary, letting people know they've gone beyond the boundaries.</div>MitchellBakerhttps://wiki.mozilla.org/index.php?title=Module_Owners_Activities_Modules&diff=341652Module Owners Activities Modules2011-08-21T00:28:07Z<p>MitchellBaker: /* Mozilla Public License Module */</p>
<hr />
<div>'''Activities Modules'''<br />
<br />
== Overview ==<br />
Activities [[Modules_and_Module_Ownership|modules]] are a part of Mozilla's [http://www.mozilla.org/hacking/module-ownership.html Module Ownership system], a basic organizing and governance principle of the Mozilla project. (The name "activities" may change. It's a bit too generic and could apply to<br />
anything, including code modules. If you've got a good idea, please let Mitchell Baker know.)<br />
<br />
== Governance Module ==<br />
<br />
* owner: Mitchell Baker<br />
* peer(s): Brendan Eich<br />
* newsgroup: mozilla.governance<br />
* scope: project-wide<br />
* governing policy document: <br />
* responsibilities: Policies and process for how we distribute authority and govern ourselves; including:<br />
** Development and Implementation of new policies as appropriate for delegation of authority and responsibility<br />
** Management of the source tree<br />
** Balancing different constituencies of the Mozilla project<br />
** Maintaining the Mozilla identity as we take on new activities<br />
* 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.<br />
* final decision-makers: the final decision maker -- when needed -- for the Mozilla project in technical matters is Brendan Eich and for other matters is Mitchell Baker; this has been the case since 1998 for Brendan and 1999 for Mitchell. I haven't figured out how to capture that clearly here. That authority is broader than "policy and process." I don't know if that is a property that attaches to the owner / peer of the governance module or if it is more personal. It should be stated somewhere clearly though. <br />
<br />
There is a [[GovernanceIssues|list of open governance issues]].<br />
<br />
Due to the large and diverse nature of topics included in the Governance<br />
module, we will divide responsibilities by sub-module, in order to delegate<br />
authority for specific pieces and identify particular areas of expertise. <br />
<br />
===Governance Submodule: Module Ownership System=== <br />
<br />
* owner: Brendan Eich<br />
* peers: Stuart Parmenter, Dan Mosedale, Robert Kaiser, Mike Connor, David Baron, Frank Hecker, Mitchell Baker [mailto:module-ownership@mozilla.org E-mail this group]<br />
* newsgroup: mozilla.governance<br />
* scope: project-wide<br />
* responsibilities: Healthy operation of the module ownership system, including topics such as:<br />
** Filling vacant roles where appropriate<br />
** Ensuring module owners are fulfilling their responsibilities, and replacing those who are not<br />
** Creating and staffing new modules where new parts of the project evolve.<br />
** Figuring out what to do if a module isn't getting enough attention<br />
** Resolving conflicts among module owners<br />
<br />
===Governance Submodule: Incubator Repositories=== <br />
<br />
* owner: Stuart Parmenter<br />
* peer(s): Jonas Sicking, Mike Connor, Mike Shaver, Christian Sejersen <br />
*newsgroup: mozilla.governance<br />
* governing policy document: http://www.mozilla.org/hacking/incubator-repository.html<br />
* scope: project-wide<br />
* responsibilities: Implementing the Incubator Repository Policy including topics such as:<br />
** Evaluating requests for new incubator repositories<br />
** Determining if an incubatory repository may live longer than six months<br />
** Other issues that come up in the operation of incubator repositories<br />
<br />
===Governance Submodule: Commit Access Policy===<br />
* owner: Mitchell Baker<br />
* peers:<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/hacking/committer/ Commit Access Policy ]<br />
* scope: project-wide<br />
<br />
===Governance Submodule: Security Policy===<br />
* owner: Frank Hecker<br />
* peers:<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/projects/security/security-bugs-policy.html Handling Mozilla Security Bugs]<br />
* scope: project-wide (applies to all Mozilla projects)<br />
<br />
===Governance Submodule: Mozilla CA Certificate Policy===<br />
* owner: Frank Hecker<br />
* peers: Kathleen Wilson<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/projects/security/certs/policy/ Mozilla CA Certificate Policy]<br />
* scope: project-wide (applies to all Mozilla projects that includes root certificates)<br />
<br />
===Governance Submodule: Code Review Policy===<br />
* owner: Mitchell Baker<br />
* peers: Brendan Eich<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/hacking/reviewers.html Mozilla "super-review"]<br />
* scope: project-wide<br />
<br />
===Governance Submodule: Performance Regression Policy===<br />
* owner: Mitchell Baker<br />
* peers:<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/hacking/reviewers.html Mozilla "super-review"]<br />
* scope: project-wide<br />
<br />
==Planet Mozilla Module== <br />
* owner: Robert Accettura<br />
* peers: Asa Dotzler, Reed Loden, J. Paul Reed<br />
* newsgroup: <br />
* scope: project-wide<br />
* responsibilities: content and policy for planet.mozilla.org, including topics such as:<br />
** which blogs are syndicated to planet.mozilla.org<br />
** which content from syndicated blogs in included<br />
** other planet.mozilla.org policy issues<br />
<br />
==Mozilla Public License Module==<br />
<br />
* owner: Mitchell Baker<br />
*peers: Heather Meeker, Luis Villa, Harvey Anderson, Gervase Markham<br />
*newsgroup: mozilla.governance; and mozilla.governance-mpl-update (at least during the process of updating the MPL 1.1, beginning March 10, 2010)<br />
*scope: project-wide, and affects other projects using the MPL<br />
*responsibilities: maintenance and development of the MPL<br />
** changes in the legal landscape which could /should be reflected<br />
** changes in FLOSS development practices which could / should be reflected<br />
<br />
==www.mozilla.org Module==<br />
* owners: Reed Loden (technical issues), David Boswell (content issues)<br />
* peers: Elika Etemad, Robert Kaiser, Eric Shepherd<br />
* sub-modules: [[Mozilla.org/Owners_List|Owners List]]<br />
* newsgroup: [http://groups.google.com/group/mozilla.dev.mozilla-org/topics mozilla.dev.mozilla-org]<br />
* scope: project-wide<br />
* responsibilities: content and policy for www.mozilla.org<br />
<br />
==CA Certificates Module== <br />
*owner: Kathleen Wilson<br />
*peers: Frank Hecker<br />
*newsgroup: mozilla.dev.security.policy<br />
*governing policy document: <br />
*http://www.mozilla.org/projects/security/certs/policy/<br />
*scope: project-wide (applies to all Mozilla software that includes root certificates)<br />
*responsibilities: Determine which root certificates should be included in Mozilla software products and which trust bits should be set on them, and evaluate requests from Certification Authorities (CAs) for inclusion of new root certificates.<br />
<br />
==Participation Metrics Module==<br />
<br />
* owner: Asa Dotzler<br />
* peers: Daniel Einspanjer, Ken Kovash<br />
* newsgroup: <br />
* governing policy document: N/A<br />
* https://wiki.mozilla.org/ParticipationMetrics/roadmap<br />
* scope: project-wide <br />
* responsibilities: develop, monitor and analyze metrics relating to participation in the Mozilla project, including such things as: <br />
** determining which questions are most important to ask (how many people do X?)<br />
** determining what data is relevant to answer these questions<br />
** designing and operating a system to generate the requested data<br />
** analyzing the resulting metrics<br />
** notifying appropriate people when participation starts to change significantly<br />
** assisting various groups to understand and use the metrics to strengthen participation<br />
** produce periodic report/analysis of participation metrics <br />
*other: This module is explicitly NOT a "maintain community health" module. This responsibility lives across the Mozilla project. Every group working on Mozilla is responsible for developing participation in their area. The role of this module is to add metrics as a tool for various groups to use to help understand the state of participation.</div>MitchellBakerhttps://wiki.mozilla.org/index.php?title=WeeklyUpdates/2011-03-07&diff=289314WeeklyUpdates/2011-03-072011-03-07T20:58:21Z<p>MitchellBaker: /* Introducing New Hires */</p>
<hr />
<div><small>[[WeeklyUpdates/2011-02-28|« previous week]] | [[WeeklyUpdates|index]] | [[WeeklyUpdates/2011-03-14|next week »]]</small><br />
<br />
= Video for today's meeting =<br />
<br />
<video controls="controls"><source src="http://videos.mozilla.org/serv/air_mozilla/monday_meetings/status-2011-03-07.ogg" type="video/ogg; codecs=&quot;theora, vorbis&quot;" /></video> <br />
<br />
= Friends of the Tree [[Image:Tree.gif|Friends of the Tree]] =<br />
* Kris Maglione, Andreas Wagner, Nils Maier and Archaeopteryx, winners of the top 4 positions in the AMO Editor Competition, totaling a combined '''2500 add-on reviews''' in the past 2 months.<br />
* Henrik Skupin nominates pxbugs, Aleksej, and bytehead for their efforts in testing Firefox 4 RC1 during the [http://bit.ly/hkzyEV add-ons testday] last Friday.<br />
<br />
= Upcoming Events =<br />
'''This Week'''<br />
<br />
'''Monday, 7 March'''<br />
<br />
'''Tuesday, 8 March'''<br />
<br />
'''Wednesday, 9 March'''<br />
<br />
'''Thursday, 10 March'''<br />
<br />
* [[Websites/Taskforce/2011_03_10|Websites Task Force meeting]] on Thursday at 10 pacific (Mozilla web font, End of Life processes and more)<br />
<br />
'''Friday, 11 March'''<br />
*Firefox Test Day - focusing on Unconfirmed Bugs: See [http://quality.mozilla.org/events/2011/03/04/unconfirmed-bugs-testday-friday-march-11th/ UNCO Bugs March 11 Test Day] for more details.<br />
<br />
'''Next Week'''<br />
<br />
= Product Status Updates =<br />
<br />
== Firefox 4 ==<br />
* Built RC1 last week, great work everyone!<br />
* On the look out for any bugs that would require a RC2<br />
** If you see one, please nominate it for blocking and/or email [mailto:release-drivers@mozilla.org release-drivers]<br />
<br />
== Firefox 3.6 and 3.5 ==<br />
* Shipped 3.6.14 and 3.5.17 on Tuesday<br />
* Shipped 3.6.15 on Friday, fixing an issue where Firefox 3.6.14 would fail to load certain Java applets<br />
** Bugs will be adjusted to reflect the current state of branch fixes<br />
<br />
== Mobile Firefox ==<br />
* Code freeze TOMORROW<br />
* Need feedback from everyone running the build<br />
<br />
== Thunderbird ==<br />
* Miramar <br />
** tab re-ordering and undo close {{bug|468808}} have landed<br />
** Alpha 3 may ship this week; depending on outstanding landing & Lanikai issues<br />
<br />
* Lanikai stability releases<br />
** released 3.1.8 and 3.1.9 in quick succession last week to deal with updater problems<br />
** still have outstanding updater issues to work through, including {{bug|635161}}<br />
<br />
== Drumbeat ==<br />
<br />
* The [http://hackasaurus.org Hackasaurus] team is here in Mountain View this week. Meet [https://twitter.com/OpenMatt @openmatt], [https://twitter.com/toolness @toolness], and [https://twitter.com/iamjessklein @iamjessklein] to chat more about the project!<br />
<br />
= Speakers =<br />
<br />
The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. <br />
<br />
{| class="fullwidth-table"<br />
|-<br />
! Title <br />
! Presenter <br />
! Topic <br />
! Media <br />
! More Details<br />
|-<br />
| Hackasaurus<br />
| Atul Varma and Jessica Klein <br />
| We'll be giving an overview of Hackasaurus, a toolkit and curriculum to help kids/non-techies understand the Open Web and how to hack it.<br />
| [https://docs.google.com/present/edit?id=0AXzegrtT-IU_ZGhnNWRrd21fMTEyMWRqcHBtM3di&hl=en&authkey=CLmlnYYH Google Docs Presentation], [http://labs.toolness.com/temp/hackasaurus-15-sec-hack-march-2011.ogv Hackasaurus 15-second hack Ogg Theora (slide 9)]<br />
| [http://hackasaurus.org Hackasaurus]<br />
|-<br />
| Field Report - Press tour update <br />
| Shappy<br />
| Quick update of how the FF4 press tour is progressing<br><br />
| n/a<br />
| n/a<br />
|-<br />
| Quick update on some automated crowd-source-y test tools for your nightly<br />
| Ctalbert<br />
| [https://wiki.mozilla.org/WeeklyUpdates/2011-03-07#Automation_.26_Tools Check out the A-Team section of the wiki]<br />
| [http://brasstacks.mozilla.com/speedtestssvr/nexttest/ JS Speed Tests]<br />
| [http://people.mozilla.org/~jgriffin/grafxbot-0.2.00.xpi New Grafx Bot]<br />
|}<br />
<br />
= Status Updates By Team =<br />
<br />
== Firefox ==<br />
<br />
== Platform ==<br />
<br />
== Messaging ==<br />
<br />
== Mobile ==<br />
<br />
== IT ==<br />
<br />
== Release Engineering ==<br />
<br />
== QA ==<br />
; General<br />
* A Browser Automation Standard<br />
** Initial discussion can be found in this [http://etherpad.mozilla.com:9000/browser-automation-standard Etherpad]<br />
** Simon Stewart (Google) checked in the initial [http://code.google.com/p/selenium/source/browse/wiki/standard/webdriver.idl WebDriver browser automation standard IDL] ([http://groups.google.com/group/selenium-developers/browse_thread/thread/c2ae43992fc3e3d4 Announcement thread])<br />
<br />
;Browser Technologies<br />
*Tested and assisted deployment of Production servers: Python sreg, Account Portal, and Storage Server<br />
* Tested and Shipped Jetpack SDK 1.0beta 3 rc3<br />
<br />
;WebQA<br />
* David Burns Keynoted Selenium Camp [http://www.theautomatedtester.co.uk/blog/2011/selenium-camp-slides-and-thoughts.html Blog Post]<br />
<br />
;QA Automation<br />
* Blog posts<br />
** [http://blargon7.com/2011/03/introducing-firefox-endurance-testing/ Introducing Firefox Endurance Testing]<br />
<br />
;QA Community<br />
* [http://bit.ly/hkzyEV Results of the Firefox 4 add-ons testday]<br />
<br />
;Test Dev<br />
<br />
== Automation & Tools ==<br />
* [http://mxr.mozilla.org/mozilla-central/source/testing/firebug/ Firebug test runner code] has now landed in mozilla-central, waiting on a reconfig to the slaves in order to run in buildbot<br />
* First edition of cross-browser automated JS speed tests are live. Check your speed [http://brasstacks.mozilla.com/speedtestssvr/nexttest/ here]<br />
* Grafx Bot testing tool with ability to run webgl tests in addition to reftests is released. Try it out [http://people.mozilla.org/~jgriffin/grafxbot-0.2.00.xpi today]!<br />
* More news available [[Auto-tools/Meetings/2011-03-07|here]]<br />
<br />
== Security ==<br />
<br />
== Engagement ==<br />
<br />
'''PR''' <br />
*[http://www.theregister.co.uk/2011/03/07/mozilla_web_apps_code/ Mozilla challenges Apple, Google with 'open' app store] <br />
*[http://www.conceivablytech.com/6016/products/mozilla-demos-open-web-app-store Mozilla Demos Open Web App Store ] <br />
*[http://www.informationweek.com/news/internet/browsers/showArticle.jhtml?articleID=229300435&cid=RSSfeed_IWK_All Mozilla Web Application Project Debuts ] <br />
*[http://www.pcworld.com/article/221427/mozilla_shows_off_web_app_product_in_bits_and_pieces.html Mozilla Shows Off Web App Product in Bits and Pieces] <br />
<br />
*[https://wiki.mozilla.org/index.php?title=WeeklyUpdates/2011-03-07&action=edit&section=22 With Pwn2Own looming, Mozilla and Google ship browser patches] <br />
*[http://www.pcmag.com/article2/0,2817,2381244,00.asp Mozilla Follows Google in Fixing Firefox Bugs Before Hacking Contest] <br />
<br />
'''Events''' <br />
<br />
'''Creative Team''' <br />
<br />
'''Contributor Engagement'''<br />
* Firefox 4 Launch:<br />
** Our party [http://www.meetup.com/everywhere/firefox page] is live - please register if you'd like to host a party. Our team is "Team Firefox" to celebrate all the team work that has gone into Firefox 4 for desktop and mobile!<br />
** Our launch team is now over 200+ strong. If you'd like to join still please sign up at http://bit.ly/joinFxLaunch.<br />
* ReMo: <br />
** Join Pierros Pappadeas and William Quivigier tomorrow March 8th at 1 p.m. PST for a brownbag on Remo.<br />
** This will be streamed over AirMoz + dial-in is 1-800-707-2533 (password 369) or 1-650-215-1282 (extension 92#), Conference number 8600#<br />
* about:mozilla newsletter:<br />
** Have news for tomorrow's newsletter? Please add it [http://etherpad.mozilla.com:9000/newsletter-mar8 here].<br />
<br />
== Support ==<br />
<br />
== Metrics ==<br />
<br />
== Evangelism ==<br />
<br />
== Labs ==<br />
<br />
== Developer Tools ==<br />
<br />
== Add-ons ==<br />
<br />
== Webdev ==<br />
<br />
== L10n ==<br />
<br />
= Introducing New Hires =<br />
<br />
*Nicholas Hurley ~ Robert Sayre <br />
*David Mason ~ Jay Sullivan <br />
*Noah Meyerhans ~ Corey Shields <br />
*Matej Novak ~ John Slater <br />
*Valerie Ponell ~ Melissa Shapiro<br />
*Pierros Papadeas ~ William Quiviger<br />
*Rowe Hoffer ~ Mitchell Baker<br />
<br />
= Foundation Updates =<br />
<br />
= Roundtable =</div>MitchellBakerhttps://wiki.mozilla.org/index.php?title=Reps&diff=286369Reps2011-02-23T02:11:23Z<p>MitchellBaker: /* Use Cases and User Tasks */</p>
<hr />
<div>{| class="wikitable" style="float: right;"<br />
| bgcolor="00FF00" | Pre-Planning<br />
|-<br />
| bgcolor="#CC3300" | '''Planning'''<br />
|-<br />
| bgcolor="cyan" | Deploying<br />
|-<br />
| bgcolor="cyan" | Live<br />
|}<br />
<br />
<br />
<br />
{{Admon/important | Draft | This is a draft outline of an upcoming program. Edit furiously! }}<br />
ReMo is the code name for the '''Mozilla Representatives Program''', a program that aims to empower and support volunteer Mozillians who want to be “official” Mozilla representatives in their region/locale.<br />
[[Image:Remo_skaff_2.png|350px|thumb|right|We are building this! Join Us!]]<br />
== Purpose ==<br />
<br />
ReMo will provide a simple and structured framework to inform, assist and support Mozilla volunteers who want to become official representatives of Mozilla in their region. They will be known as Mozilla Reps (or MozReps).<br />
<br />
A Mozilla Rep will have the following responsibilities:<br />
<br />
* '''represent''' Mozilla in their region and have a clear understanding of Mozilla in her/his local tech/social/cultural context<br />
* '''promote''' the Mozilla Project and our mission<br />
* '''build''' on existing contributor-building efforts and programs<br />
* '''inspire''', '''recruit''' and '''support''' new contributors<br />
* '''mentor''' future Mozilla Reps<br />
<br />
== Anti-Purpose ==<br />
<br />
Here are some things ReMo specificly aims '''NOT''' to do : <br />
<br />
* replace or undermine efforts by existing communities of Mozilla volunteers around the world to recruit new contributors<br />
* become a top-down ambassador program run exclusively by Mozilla staff<br />
<br />
== Characteristics of the ReMo program ==<br />
<br />
* open to EVERYONE but rigorous membership process<br />
* community-driven (once ReMo has reached mature stage)<br />
* vertical distribution of responsibilities<br />
* structured and well documented<br />
* meritocratic<br />
* regular monitoring/assessment of activity<br />
<br />
== Who can be a Mozilla Rep? ==<br />
<br />
Anyone who is:<br />
<br />
* '''passionate''' about Mozilla Project <br />
* '''knowledgeable''' of the Mozilla organization, its mission and its products<br />
* '''willing''' to communicate all those, to as many people as possible<br />
<br />
== ReMo Website ==<br />
<br />
In order to accommodate the needs of this program, infrastructure and outreach website is needed. <br />
<br />
More info on [[ReMo/Website|Website planning page]]<br />
<br />
=== Use Cases and User Tasks ===<br />
<br />
A list of most common use cases and user tasks for ReMo:<br />
<br />
* Apply to become a Mozilla Rep (once application sent, each applicant will go through a simple but rigorous screening process)<br />
* Log in with your ReMo LDAP account and start updating your profile<br />
* See / Browse through various Events happening near him<br />
* Add events to ReMo calendar and become owner of these events<br />
* Use ReMo ticketing system to request swag or sponsorship for events<br />
* Peruse ReMo file repository for slide decks, presentation templates, printable materials (ie. posters, flyers, stickers)<br />
* Represent Mozilla at events<br />
* Customize and order swag for your community <br />
* Customize and order your ReMo business card<br />
* Regularly update your ReMo profile with recent activities (ie. events, presentations, contributions etc...)<br />
* Mentor recent Mozilla Reps and monitor their progress<br />
* See other ReMo activities through the ReMo planet<br />
* Add his blog on ReMo planet<br />
<br />
{{Admon/note | Note | Please add more usage scenarios!}}<br />
<br />
== Schedule ==<br />
<br />
The aim is to have 25 ReMo test-pilots (all veteran Mozilla contributors) signed up to test the platform by end of Q1 2011 and have ReMo officially roll out some time in Q2 2011<br />
<br />
The detailed timeline and status of project components can be found at [[ReMo/Phase_1_Plan|Phase 1 Plan]]<br />
<br />
=== Summary Plan ===<br />
<br />
A summary plan is available that contains details on the thinking behind ReMo as well as the structure of the program.<br />
<br />
It can be found <br />
<br />
* Ver 1.0 [https://wiki.mozilla.org/File:ReMo_Summary_Plan_v1.0.pdf here]<br />
* Ver 1.1 [https://wiki.mozilla.org/File:ReMo_Summary_Plan_v1.1.pdf here]<br />
<br />
== Outreach ==<br />
<br />
Content and resources made to communicate initially ReMo to the rest of Mozilla and the public in general can be found on our [[ReMo/outreach|Outreach]] page.<br />
<br />
<br />
== Contact ==<br />
<br />
In order to communicate throughout the planning and deploying stage of ReMo, we have created several ways of communication:<br />
<br />
* '''IRC''' You can join us on these channels on irc.mozilla.org<br />
** #remo General Channel for ReMo (will be used as our main one)<br />
** #remo-dev Channel on planning and deploying ReMo<br />
* '''Mailing List''' (stay tuned for that)<br />
* '''Meetings''' (stay tuned for that)<br />
<br />
== Resources ==<br />
<br />
* William Quiviger is project lead<br />
* Pierros Papadeas is assistant project lead<br />
* WebDev needs:<br />
** TBD<br />
* Design needs:<br />
** We'll need someone to help design ReMo logo and ReMo collateral (ie. tshirt, bags, business cards etc...)<br />
* Legal needs: <br />
** TBD</div>MitchellBakerhttps://wiki.mozilla.org/index.php?title=WeeklyUpdates/2010-11-29&diff=270497WeeklyUpdates/2010-11-292010-11-29T18:35:21Z<p>MitchellBaker: /* Speakers */</p>
<hr />
<div><small>[[WeeklyUpdates/2010-11-22|« previous week]] | [[WeeklyUpdates|index]] | [[WeeklyUpdates/2010-12-06|next week »]]</small><br />
<br />
= Video for today's meeting =<br />
<br />
<video controls="controls"><source src="http://videos.mozilla.org/serv/air_mozilla/monday_meetings/status-2010-11-29.ogg" type="video/ogg; codecs=&quot;theora, vorbis&quot;" /></video> <br />
<br />
= Friends of the Tree [[Image:Tree.gif|Friends of the Tree]] =<br />
* Henrik Skupin would like to nominate the following people, who made our [http://bit.ly/dWtT6l Mozmill test day] last Friday a success by running our general and the brand-new landed l10n tests: adriank, kbrosnan, tanner, jan, merike, linostar, and especially aleksej for his all-day attendance.<br />
<br />
= Upcoming Events =<br />
'''This Week'''<br />
<br />
'''Monday, 29 November'''<br />
<br />
'''Tuesday, 30 November'''<br />
<br />
'''Wednesday, 1 December'''<br />
<br />
'''Thursday, 2 December'''<br />
<br />
'''Friday, 3 December''' <br />
<br />
'''Next Week'''<br />
<br />
= Product Status Updates =<br />
<br />
== Firefox 4 ==<br />
<br />
== Firefox 3.6 ==<br />
<br />
== Mobile Firefox ==<br />
<br />
== Thunderbird ==<br />
<br />
== Drumbeat ==<br />
<br />
= Speakers =<br />
<br />
The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation.<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
! Title<br />
! Presenter<br />
! Topic<br />
! Media<br />
! More Details<br />
|-<br />
| State of Mozilla<br />
| Mitchell Baker<br />
| Reactions, Responses, Survey<br />
| ---<br />
| http://www.mozilla.org/foundation/annualreport/2009/<br />
|-<br />
|}<br />
<br />
= Status Updates By Team =<br />
<br />
== Firefox ==<br />
<br />
== Platform ==<br />
<br />
== Messaging ==<br />
<br />
== Mobile ==<br />
<br />
== IT ==<br />
<br />
== Release Engineering ==<br />
<br />
== QA ==<br />
<br />
;QA Community<br />
* [http://quality.mozilla.org/events/2010/11/29/add-ons-manager-test-day-friday-december-3rd/ Add-ons Manager test day] on Friday, Dec. 3rd<br />
<br />
== Automation & Tools ==<br />
<br />
== Security ==<br />
<br />
== Engagement ==<br />
<br />
'''PR''' <br />
<br />
'''Events''' <br />
<br />
'''Creative Team''' <br />
<br />
'''Community Marketing'''<br />
<br />
== Support ==<br />
<br />
== Metrics ==<br />
<br />
== Evangelism ==<br />
<br />
== Labs ==<br />
<br />
== Developer Tools ==<br />
<br />
== Add-ons ==<br />
<br />
== Webdev ==<br />
<br />
== L10n ==<br />
<br />
= Introducing New Hires =<br />
* Corey Shields - IT/Ops Manager<br />
<br />
= Foundation Updates =<br />
<br />
= Roundtable =</div>MitchellBakerhttps://wiki.mozilla.org/index.php?title=WeeklyUpdates/2010-11-22&diff=269113WeeklyUpdates/2010-11-222010-11-22T05:48:22Z<p>MitchellBaker: /* Friends of the Tree Friends of the Tree */</p>
<hr />
<div><small>[[WeeklyUpdates/2010-11-15|« previous week]] | [[WeeklyUpdates|index]] | [[WeeklyUpdates/2010-11-29|next week »]]</small><br />
<br />
= Video for today's meeting =<br />
<br />
<video controls="controls"><source src="http://videos.mozilla.org/serv/air_mozilla/monday_meetings/status-2010-11-22.ogg" type="video/ogg; codecs=&quot;theora, vorbis&quot;" /></video> <br />
<br />
= Friends of the Tree [[Image:Tree.gif|Friends of the Tree]] =<br />
<br />
Professors Jason Schultz (Berkeley), Eric Goldman (Santa Clara), and Anthony Falzone (Stanford) for their comments on Mozilla's submission to the Internet Policy Task Force on Protecting Copyrighted Works on the Web.<br />
<br />
Melissa Shapiro for being the force behind the creation of the State of Mozilla microsite, and Shannon Prior and Melissa for implementing it<br />
<br />
= Upcoming Events =<br />
'''This Week'''<br />
<br />
'''Monday, 22 November'''<br />
<br />
'''Tuesday, 23 November'''<br />
<br />
'''Wednesday, 24 November'''<br />
<br />
'''Thursday, 25 November'''<br />
<br />
'''Friday, 26 November''' <br />
<br />
'''Next Week'''<br />
<br />
= Product Status Updates =<br />
<br />
== Firefox 4 ==<br />
<br />
== Firefox 3.6 ==<br />
<br />
== Mobile Firefox ==<br />
<br />
== Thunderbird ==<br />
<br />
== Older Branch Work ==<br />
<br />
== Drumbeat ==<br />
<br />
= Speakers =<br />
<br />
The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation.<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
! Title<br />
! Presenter<br />
! Topic<br />
! Media<br />
! More Details<br />
|-<br />
| Drumbeat Festival Recap<br />
| Mark Surman<br />
| What happened in Barcelona? Why is it important?<br />
| [http://htmlpad.org/Drumbeat-Festival-2010-Recap HTML slides] - click to follow along<br />
| [http://www.delicious.com/msurman/drumbeat+bcn?sort=date&order=desc Blog, press ] and [http://www.flickr.com/photos/mozilladrumbeat/favorites/with/5154535556/ photo] highlights<br />
|-<br />
| Keeping the Web Open for UGC<br />
| Julie Martin<br />
| Mozilla's Comment to the Internet Policy Task Force<br />
|<br />
|}<br />
<br />
= Status Updates By Team =<br />
<br />
== Firefox ==<br />
<br />
== Platform ==<br />
<br />
== Messaging ==<br />
<br />
== Mobile ==<br />
<br />
== IT ==<br />
<br />
== Release Engineering ==<br />
<br />
== QA ==<br />
<br />
;Test Execution<br />
<br />
;WebQA<br />
<br />
;QA Community<br />
<br />
;Test Dev<br />
<br />
== Automation & Tools ==<br />
<br />
== Security ==<br />
<br />
== Engagement ==<br />
<br />
'''PR''' <br />
<br />
'''Events''' <br />
<br />
'''Creative Team''' <br />
<br />
'''Community Marketing'''<br />
<br />
== Support ==<br />
<br />
== Metrics ==<br />
<br />
== Evangelism ==<br />
<br />
== Labs ==<br />
<br />
== Developer Tools ==<br />
<br />
== Add-ons ==<br />
<br />
== Webdev ==<br />
<br />
== L10n ==<br />
<br />
= Introducing New Hires =<br />
<br />
= Foundation Updates =<br />
<br />
= Roundtable =</div>MitchellBakerhttps://wiki.mozilla.org/index.php?title=WeeklyUpdates/2010-11-08&diff=266139WeeklyUpdates/2010-11-082010-11-07T18:27:43Z<p>MitchellBaker: /* Speakers */</p>
<hr />
<div><small>[[WeeklyUpdates/2010-11-01|« previous week]] | [[WeeklyUpdates|index]] | [[WeeklyUpdates/2010-11-15|next week »]]</small><br />
<br />
= Video for today's meeting =<br />
<br />
<video controls="controls"><source src="http://videos.mozilla.org/serv/air_mozilla/monday_meetings/status-2010-11-08.ogg" type="video/ogg; codecs=&quot;theora, vorbis&quot;" /></video> <br />
<br />
= Friends of the Tree [[Image:Tree.gif|Friends of the Tree]] =<br />
<br />
= Upcoming Events =<br />
'''This Week'''<br />
<br />
'''Monday, 08 November'''<br />
<br />
'''Tuesday, 09 November'''<br />
<br />
'''Wednesday, 10 November'''<br />
<br />
'''Thursday, 11 November'''<br />
<br />
'''Friday, 12 November''' <br />
<br />
* [http://master.support.mozilla.com/ SUMO 2.3] [[QA/Execution/Web_Testing/SUMO/2.3|Community Test Date]]<br />
<br />
'''Next Week'''<br />
<br />
= Product Status Updates =<br />
<br />
== Firefox 4 ==<br />
<br />
== Firefox 3.6 ==<br />
<br />
== Mobile Firefox ==<br />
<br />
== Thunderbird ==<br />
<br />
== Older Branch Work ==<br />
<br />
== Drumbeat ==<br />
<br />
= Speakers =<br />
<br />
The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. <br />
<br />
{| class="fullwidth-table"<br />
|-<br />
! Title <br />
! Presenter <br />
! Topic <br />
! Media <br />
! More Details<br />
|-<br />
| Trip Summary: Mid-East, Moscow, Drumbeat <br />
| Mitchell Baker <br />
| Lightning Talk version of recent travels <br />
| photos from Amman: http://picasaweb.google.com/ArabicMozilla/OpenWebGetInvolved#5532462205190656514 <br />
<br />
|}<br />
<br />
= Status Updates By Team =<br />
<br />
== Firefox ==<br />
<br />
== Platform ==<br />
<br />
== Messaging ==<br />
<br />
== Mobile ==<br />
<br />
== IT ==<br />
<br />
== Release Engineering ==<br />
<br />
== QA ==<br />
<br />
;Test Execution<br />
<br />
;WebQA<br />
<br />
;QA Community<br />
<br />
;Test Dev<br />
<br />
== Automation & Tools ==<br />
<br />
== Security ==<br />
<br />
== Engagement ==<br />
<br />
'''PR''' <br />
<br />
'''Events''' <br />
<br />
'''Creative Team''' <br />
<br />
'''Community Marketing'''<br />
<br />
== Support ==<br />
<br />
== Metrics ==<br />
<br />
== Evangelism ==<br />
<br />
== Labs ==<br />
<br />
== Developer Tools ==<br />
<br />
== Add-ons ==<br />
<br />
== Webdev ==<br />
<br />
== L10n ==<br />
<br />
= Introducing New Hires =<br />
<br />
= Foundation Updates =<br />
<br />
= Roundtable =</div>MitchellBakerhttps://wiki.mozilla.org/index.php?title=WeeklyUpdates/2010-11-08&diff=266138WeeklyUpdates/2010-11-082010-11-07T18:18:15Z<p>MitchellBaker: </p>
<hr />
<div><small>[[WeeklyUpdates/2010-11-01|« previous week]] | [[WeeklyUpdates|index]] | [[WeeklyUpdates/2010-11-15|next week »]]</small><br />
<br />
= Video for today's meeting =<br />
<br />
<video controls="controls"><source src="http://videos.mozilla.org/serv/air_mozilla/monday_meetings/status-2010-11-08.ogg" type="video/ogg; codecs=&quot;theora, vorbis&quot;" /></video> <br />
<br />
= Friends of the Tree [[Image:Tree.gif|Friends of the Tree]] =<br />
<br />
= Upcoming Events =<br />
'''This Week'''<br />
<br />
'''Monday, 08 November'''<br />
<br />
'''Tuesday, 09 November'''<br />
<br />
'''Wednesday, 10 November'''<br />
<br />
'''Thursday, 11 November'''<br />
<br />
'''Friday, 12 November''' <br />
<br />
* [http://master.support.mozilla.com/ SUMO 2.3] [[QA/Execution/Web_Testing/SUMO/2.3|Community Test Date]]<br />
<br />
'''Next Week'''<br />
<br />
= Product Status Updates =<br />
<br />
== Firefox 4 ==<br />
<br />
== Firefox 3.6 ==<br />
<br />
== Mobile Firefox ==<br />
<br />
== Thunderbird ==<br />
<br />
== Older Branch Work ==<br />
<br />
== Drumbeat ==<br />
<br />
= Speakers =<br />
<br />
The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. <br />
<br />
{| class="fullwidth-table"<br />
|-<br />
! Title <br />
! Presenter <br />
! Topic <br />
! Media <br />
! More Details<br />
|-<br />
| Trip Summary: Mid-East, Moscow, Drumbeat <br />
| Mitchell Baker <br />
| Lightning Talk version of recent travels <br />
| photos from Amman: http://picasaweb.google.com/ArabicMozilla/OpenWebGetInvolved#5532462205190656514 <br />
[[Media:Qatar_Press_2010.pdf]] <br />
[[File:QatarEventPhoto.png|200px|thumb|left|Qatar speakers, Mitchell Baker et al]]<br />
<br />
|}<br />
<br />
= Status Updates By Team =<br />
<br />
== Firefox ==<br />
<br />
== Platform ==<br />
<br />
== Messaging ==<br />
<br />
== Mobile ==<br />
<br />
== IT ==<br />
<br />
== Release Engineering ==<br />
<br />
== QA ==<br />
<br />
;Test Execution<br />
<br />
;WebQA<br />
<br />
;QA Community<br />
<br />
;Test Dev<br />
<br />
== Automation & Tools ==<br />
<br />
== Security ==<br />
<br />
== Engagement ==<br />
<br />
'''PR''' <br />
<br />
'''Events''' <br />
<br />
'''Creative Team''' <br />
<br />
'''Community Marketing'''<br />
<br />
== Support ==<br />
<br />
== Metrics ==<br />
<br />
== Evangelism ==<br />
<br />
== Labs ==<br />
<br />
== Developer Tools ==<br />
<br />
== Add-ons ==<br />
<br />
== Webdev ==<br />
<br />
== L10n ==<br />
<br />
= Introducing New Hires =<br />
<br />
= Foundation Updates =<br />
<br />
= Roundtable =</div>MitchellBakerhttps://wiki.mozilla.org/index.php?title=WeeklyUpdates/2010-11-08&diff=266137WeeklyUpdates/2010-11-082010-11-07T18:09:25Z<p>MitchellBaker: </p>
<hr />
<div><small>[[WeeklyUpdates/2010-11-01|« previous week]] | [[WeeklyUpdates|index]] | [[WeeklyUpdates/2010-11-15|next week »]]</small><br />
<br />
= Video for today's meeting =<br />
<br />
<video controls="controls"><source src="http://videos.mozilla.org/serv/air_mozilla/monday_meetings/status-2010-11-08.ogg" type="video/ogg; codecs=&quot;theora, vorbis&quot;" /></video> <br />
<br />
= Friends of the Tree [[Image:Tree.gif|Friends of the Tree]] =<br />
<br />
= Upcoming Events =<br />
'''This Week'''<br />
<br />
'''Monday, 08 November'''<br />
<br />
'''Tuesday, 09 November'''<br />
<br />
'''Wednesday, 10 November'''<br />
<br />
'''Thursday, 11 November'''<br />
<br />
'''Friday, 12 November''' <br />
<br />
* [http://master.support.mozilla.com/ SUMO 2.3] [[QA/Execution/Web_Testing/SUMO/2.3|Community Test Date]]<br />
<br />
'''Next Week'''<br />
<br />
= Product Status Updates =<br />
<br />
== Firefox 4 ==<br />
<br />
== Firefox 3.6 ==<br />
<br />
== Mobile Firefox ==<br />
<br />
== Thunderbird ==<br />
<br />
== Older Branch Work ==<br />
<br />
== Drumbeat ==<br />
<br />
= Speakers =<br />
<br />
The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. <br />
<br />
{| class="fullwidth-table"<br />
|-<br />
! Title <br />
! Presenter <br />
! Topic <br />
! Media <br />
! More Details<br />
|-<br />
| Trip Summary: Mid-East, Moscow, Drumbeat <br />
| Mitchell Baker <br />
| Lightning Talk version of recent travels <br />
| photos from Amman: http://picasaweb.google.com/ArabicMozilla/OpenWebGetInvolved#5532462205190656514<br />
[[Media:Qatar_Press_2010.pdf]]<br />
|}<br />
<br />
= Status Updates By Team =<br />
<br />
== Firefox ==<br />
<br />
== Platform ==<br />
<br />
== Messaging ==<br />
<br />
== Mobile ==<br />
<br />
== IT ==<br />
<br />
== Release Engineering ==<br />
<br />
== QA ==<br />
<br />
;Test Execution<br />
<br />
;WebQA<br />
<br />
;QA Community<br />
<br />
;Test Dev<br />
<br />
== Automation & Tools ==<br />
<br />
== Security ==<br />
<br />
== Engagement ==<br />
<br />
'''PR''' <br />
<br />
'''Events''' <br />
<br />
'''Creative Team''' <br />
<br />
'''Community Marketing'''<br />
<br />
== Support ==<br />
<br />
== Metrics ==<br />
<br />
== Evangelism ==<br />
<br />
== Labs ==<br />
<br />
== Developer Tools ==<br />
<br />
== Add-ons ==<br />
<br />
== Webdev ==<br />
<br />
== L10n ==<br />
<br />
= Introducing New Hires =<br />
<br />
= Foundation Updates =<br />
<br />
= Roundtable =</div>MitchellBakerhttps://wiki.mozilla.org/index.php?title=File:QatarEventPhoto.png&diff=266136File:QatarEventPhoto.png2010-11-07T18:03:06Z<p>MitchellBaker: Dr. Hassa, Mitchell, et al</p>
<hr />
<div>Dr. Hassa, Mitchell, et al</div>MitchellBakerhttps://wiki.mozilla.org/index.php?title=File:Qatar_Press_2010.pdf&diff=266135File:Qatar Press 2010.pdf2010-11-07T17:59:31Z<p>MitchellBaker: Press Coverage of Digitally Open event in Qatar</p>
<hr />
<div>Press Coverage of Digitally Open event in Qatar</div>MitchellBakerhttps://wiki.mozilla.org/index.php?title=WeeklyUpdates/2010-11-08&diff=266134WeeklyUpdates/2010-11-082010-11-07T17:15:52Z<p>MitchellBaker: /* Speakers */</p>
<hr />
<div><small>[[WeeklyUpdates/2010-11-01|« previous week]] | [[WeeklyUpdates|index]] | [[WeeklyUpdates/2010-11-15|next week »]]</small><br />
<br />
= Video for today's meeting =<br />
<br />
<video controls="controls"><source src="http://videos.mozilla.org/serv/air_mozilla/monday_meetings/status-2010-11-08.ogg" type="video/ogg; codecs=&quot;theora, vorbis&quot;" /></video> <br />
<br />
= Friends of the Tree [[Image:Tree.gif|Friends of the Tree]] =<br />
<br />
= Upcoming Events =<br />
'''This Week'''<br />
<br />
'''Monday, 08 November'''<br />
<br />
'''Tuesday, 09 November'''<br />
<br />
'''Wednesday, 10 November'''<br />
<br />
'''Thursday, 11 November'''<br />
<br />
'''Friday, 12 November''' <br />
<br />
* [http://master.support.mozilla.com/ SUMO 2.3] [[QA/Execution/Web_Testing/SUMO/2.3|Community Test Date]]<br />
<br />
'''Next Week'''<br />
<br />
= Product Status Updates =<br />
<br />
== Firefox 4 ==<br />
<br />
== Firefox 3.6 ==<br />
<br />
== Mobile Firefox ==<br />
<br />
== Thunderbird ==<br />
<br />
== Older Branch Work ==<br />
<br />
== Drumbeat ==<br />
<br />
= Speakers =<br />
<br />
The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation.<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
! Title<br />
! Presenter<br />
! Topic<br />
! Media<br />
! More Details<br />
|-<br />
| Trip Summary: Mid-East, Moscow, Drumbeat<br />
| Mitchell Baker<br />
| Lightning Talk version of recent travels<br />
| photos from Amman: http://picasaweb.google.com/ArabicMozilla/OpenWebGetInvolved#5532462205190656514<br />
|-<br />
|}<br />
<br />
= Status Updates By Team =<br />
<br />
== Firefox ==<br />
<br />
== Platform ==<br />
<br />
== Messaging ==<br />
<br />
== Mobile ==<br />
<br />
== IT ==<br />
<br />
== Release Engineering ==<br />
<br />
== QA ==<br />
<br />
;Test Execution<br />
<br />
;WebQA<br />
<br />
;QA Community<br />
<br />
;Test Dev<br />
<br />
== Automation & Tools ==<br />
<br />
== Security ==<br />
<br />
== Engagement ==<br />
<br />
'''PR''' <br />
<br />
'''Events''' <br />
<br />
'''Creative Team''' <br />
<br />
'''Community Marketing'''<br />
<br />
== Support ==<br />
<br />
== Metrics ==<br />
<br />
== Evangelism ==<br />
<br />
== Labs ==<br />
<br />
== Developer Tools ==<br />
<br />
== Add-ons ==<br />
<br />
== Webdev ==<br />
<br />
== L10n ==<br />
<br />
= Introducing New Hires =<br />
<br />
= Foundation Updates =<br />
<br />
= Roundtable =</div>MitchellBakerhttps://wiki.mozilla.org/index.php?title=WeeklyUpdates/2010-11-08&diff=266133WeeklyUpdates/2010-11-082010-11-07T16:49:06Z<p>MitchellBaker: /* Speakers */</p>
<hr />
<div><small>[[WeeklyUpdates/2010-11-01|« previous week]] | [[WeeklyUpdates|index]] | [[WeeklyUpdates/2010-11-15|next week »]]</small><br />
<br />
= Video for today's meeting =<br />
<br />
<video controls="controls"><source src="http://videos.mozilla.org/serv/air_mozilla/monday_meetings/status-2010-11-08.ogg" type="video/ogg; codecs=&quot;theora, vorbis&quot;" /></video> <br />
<br />
= Friends of the Tree [[Image:Tree.gif|Friends of the Tree]] =<br />
<br />
= Upcoming Events =<br />
'''This Week'''<br />
<br />
'''Monday, 08 November'''<br />
<br />
'''Tuesday, 09 November'''<br />
<br />
'''Wednesday, 10 November'''<br />
<br />
'''Thursday, 11 November'''<br />
<br />
'''Friday, 12 November''' <br />
<br />
* [http://master.support.mozilla.com/ SUMO 2.3] [[QA/Execution/Web_Testing/SUMO/2.3|Community Test Date]]<br />
<br />
'''Next Week'''<br />
<br />
= Product Status Updates =<br />
<br />
== Firefox 4 ==<br />
<br />
== Firefox 3.6 ==<br />
<br />
== Mobile Firefox ==<br />
<br />
== Thunderbird ==<br />
<br />
== Older Branch Work ==<br />
<br />
== Drumbeat ==<br />
<br />
= Speakers =<br />
<br />
The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation.<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
! Title<br />
! Presenter<br />
! Topic<br />
! Media<br />
! More Details<br />
|-<br />
| Trip Summary: Mid-East, Moscow, Drumbeat<br />
| Mitchell Baker<br />
| Lightning Talk version of recent travels<br />
|<br />
|-<br />
|}<br />
<br />
= Status Updates By Team =<br />
<br />
== Firefox ==<br />
<br />
== Platform ==<br />
<br />
== Messaging ==<br />
<br />
== Mobile ==<br />
<br />
== IT ==<br />
<br />
== Release Engineering ==<br />
<br />
== QA ==<br />
<br />
;Test Execution<br />
<br />
;WebQA<br />
<br />
;QA Community<br />
<br />
;Test Dev<br />
<br />
== Automation & Tools ==<br />
<br />
== Security ==<br />
<br />
== Engagement ==<br />
<br />
'''PR''' <br />
<br />
'''Events''' <br />
<br />
'''Creative Team''' <br />
<br />
'''Community Marketing'''<br />
<br />
== Support ==<br />
<br />
== Metrics ==<br />
<br />
== Evangelism ==<br />
<br />
== Labs ==<br />
<br />
== Developer Tools ==<br />
<br />
== Add-ons ==<br />
<br />
== Webdev ==<br />
<br />
== L10n ==<br />
<br />
= Introducing New Hires =<br />
<br />
= Foundation Updates =<br />
<br />
= Roundtable =</div>MitchellBakerhttps://wiki.mozilla.org/index.php?title=Module_Owners_Activities_Modules&diff=244793Module Owners Activities Modules2010-08-12T00:44:02Z<p>MitchellBaker: /* Governance Submodule: Mozilla CA Certificate Policy */</p>
<hr />
<div>'''Activities Modules'''<br />
<br />
== Overview ==<br />
Activities [[Modules_and_Module_Ownership|modules]] are a part of Mozilla's [http://www.mozilla.org/hacking/module-ownership.html Module Ownership system], a basic organizing and governance principle of the Mozilla project. (The name "activities" may change. It's a bit too generic and could apply to<br />
anything, including code modules. If you've got a good idea, please let Mitchell Baker know.)<br />
<br />
== Governance Module ==<br />
<br />
* owner: Mitchell Baker<br />
* peer(s): Brendan Eich<br />
* newsgroup: mozilla.governance<br />
* scope: project-wide<br />
* governing policy document: <br />
* responsibilities: Policies and process for how we distribute authority and govern ourselves; including:<br />
** Development and Implementation of new policies as appropriate for delegation of authority and responsibility<br />
** Management of the source tree<br />
** Balancing different constituencies of the Mozilla project<br />
** Maintaining the Mozilla identity as we take on new activities<br />
* 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.<br />
* final decision-makers: the final decision maker -- when needed -- for the Mozilla project in technical matters is Brendan Eich and for other matters is Mitchell Baker; this has been the case since 1998 for Brendan and 1999 for Mitchell. I haven't figured out how to capture that clearly here. That authority is broader than "policy and process." I don't know if that is a property that attaches to the owner / peer of the governance module or if it is more personal. It should be stated somewhere clearly though. <br />
<br />
There is a [[GovernanceIssues|list of open governance issues]].<br />
<br />
Due to the large and diverse nature of topics included in the Governance<br />
module, we will divide responsibilities by sub-module, in order to delegate<br />
authority for specific pieces and identify particular areas of expertise. <br />
<br />
===Governance Submodule: Module Ownership System=== <br />
<br />
* owner: Brendan Eich<br />
* peers: Stuart Parmenter, Dan Mosedale, Robert Kaiser, Mike Connor, David Baron, Frank Hecker, Mitchell Baker [mailto:module-ownership@mozilla.org E-mail this group]<br />
* newsgroup: mozilla.governance<br />
* scope: project-wide<br />
* responsibilities: Healthy operation of the module ownership system, including topics such as:<br />
** Filling vacant roles where appropriate<br />
** Ensuring module owners are fulfilling their responsibilities, and replacing those who are not<br />
** Creating and staffing new modules where new parts of the project evolve.<br />
** Figuring out what to do if a module isn't getting enough attention<br />
** Resolving conflicts among module owners<br />
<br />
===Governance Submodule: Incubator Repositories=== <br />
<br />
* owner: Stuart Parmenter<br />
* peer(s): Jonas Sicking, Mike Connor, Mike Shaver, Christian Sejersen <br />
*newsgroup: mozilla.governance<br />
* governing policy document: http://www.mozilla.org/hacking/incubator-repository.html<br />
* scope: project-wide<br />
* responsibilities: Implementing the Incubator Repository Policy including topics such as:<br />
** Evaluating requests for new incubator repositories<br />
** Determining if an incubatory repository may live longer than six months<br />
** Other issues that come up in the operation of incubator repositories<br />
<br />
===Governance Submodule: Commit Access Policy===<br />
* owner: Mitchell Baker<br />
* peers:<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/hacking/committer/ Commit Access Policy ]<br />
* scope: project-wide<br />
<br />
===Governance Submodule: Security Policy===<br />
* owner: Frank Hecker<br />
* peers:<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/projects/security/security-bugs-policy.html Handling Mozilla Security Bugs]<br />
* scope: project-wide (applies to all Mozilla projects)<br />
<br />
===Governance Submodule: Mozilla CA Certificate Policy===<br />
* owner: Frank Hecker<br />
* peers: Kathleen Wilson<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/projects/security/certs/policy/ Mozilla CA Certificate Policy]<br />
* scope: project-wide (applies to all Mozilla projects that includes root certificates)<br />
<br />
===Governance Submodule: Code Review Policy===<br />
* owner: Mitchell Baker<br />
* peers: Brendan Eich<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/hacking/reviewers.html Mozilla "super-review"]<br />
* scope: project-wide<br />
<br />
===Governance Submodule: Performance Regression Policy===<br />
* owner: Mitchell Baker<br />
* peers:<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/hacking/reviewers.html Mozilla "super-review"]<br />
* scope: project-wide<br />
<br />
==Planet Mozilla Module== <br />
* owner: Robert Accettura<br />
* peers: Asa Dotzler, Reed Loden, J. Paul Reed, Deb Richardson<br />
* newsgroup: <br />
* scope: project-wide<br />
* responsibilities: content and policy for planet.mozilla.org, including topics such as:<br />
** which blogs are syndicated to planet.mozilla.org<br />
** which content from syndicated blogs in included<br />
** other planet.mozilla.org policy issues<br />
<br />
==Mozilla Public License Module==<br />
<br />
* owner: Mitchell Baker<br />
*peers: (TBD)<br />
*newsgroup: mozilla.governance; and mozilla.governance-mpl-update (at least during the process of updating the MPL 1.1, beginning March 10, 2010)<br />
*scope: project-wide, and affects other projects using the MPL<br />
*responsibilities: maintenance and development of the MPL<br />
** changes in the legal landscape which could /should be reflected<br />
** changes in FLOSS development practices which could / should be reflected<br />
<br />
==www.mozilla.org Module==<br />
* owners: Reed Loden (technical issues), David Boswell (content issues)<br />
* peers: Elika Etemad, Robert Kaiser, Eric Shepherd<br />
* newsgroup: [http://groups.google.com/group/mozilla.dev.mozilla-org/topics mozilla.dev.mozilla-org]<br />
* scope: project-wide<br />
* responsibilities: content and policy for www.mozilla.org<br />
<br />
==CA Certificates Module== <br />
*owner: Kathleen Wilson<br />
*peers: Frank Hecker<br />
*newsgroup: mozilla.dev.security.policy<br />
*governing policy document: <br />
*http://www.mozilla.org/projects/security/certs/policy/<br />
*scope: project-wide (applies to all Mozilla software that includes root certificates)<br />
*responsibilities: Determine which root certificates should be included in Mozilla software products and which trust bits should be set on them, and evaluate requests from Certification Authorities (CAs) for inclusion of new root certificates.<br />
<br />
==Participation Metrics Module==<br />
<br />
* owner: Asa Dotzler<br />
* peers: Daniel Einspanjer, Ken Kovash<br />
* newsgroup: <br />
* governing policy document: N/A<br />
* https://wiki.mozilla.org/ParticipationMetrics/roadmap<br />
* scope: project-wide <br />
* responsibilities: develop, monitor and analyze metrics relating to participation in the Mozilla project, including such things as: <br />
** determining which questions are most important to ask (how many people do X?)<br />
** determining what data is relevant to answer these questions<br />
** designing and operating a system to generate the requested data<br />
** analyzing the resulting metrics<br />
** notifying appropriate people when participation starts to change significantly<br />
** assisting various groups to understand and use the metrics to strengthen participation<br />
** produce periodic report/analysis of participation metrics <br />
*other: This module is explicitly NOT a "maintain community health" module. This responsibility lives across the Mozilla project. Every group working on Mozilla is responsible for developing participation in their area. The role of this module is to add metrics as a tool for various groups to use to help understand the state of participation.</div>MitchellBakerhttps://wiki.mozilla.org/index.php?title=Module_Owners_Activities_Modules&diff=244791Module Owners Activities Modules2010-08-12T00:42:48Z<p>MitchellBaker: /* CA Certificates Module */</p>
<hr />
<div>'''Activities Modules'''<br />
<br />
== Overview ==<br />
Activities [[Modules_and_Module_Ownership|modules]] are a part of Mozilla's [http://www.mozilla.org/hacking/module-ownership.html Module Ownership system], a basic organizing and governance principle of the Mozilla project. (The name "activities" may change. It's a bit too generic and could apply to<br />
anything, including code modules. If you've got a good idea, please let Mitchell Baker know.)<br />
<br />
== Governance Module ==<br />
<br />
* owner: Mitchell Baker<br />
* peer(s): Brendan Eich<br />
* newsgroup: mozilla.governance<br />
* scope: project-wide<br />
* governing policy document: <br />
* responsibilities: Policies and process for how we distribute authority and govern ourselves; including:<br />
** Development and Implementation of new policies as appropriate for delegation of authority and responsibility<br />
** Management of the source tree<br />
** Balancing different constituencies of the Mozilla project<br />
** Maintaining the Mozilla identity as we take on new activities<br />
* 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.<br />
* final decision-makers: the final decision maker -- when needed -- for the Mozilla project in technical matters is Brendan Eich and for other matters is Mitchell Baker; this has been the case since 1998 for Brendan and 1999 for Mitchell. I haven't figured out how to capture that clearly here. That authority is broader than "policy and process." I don't know if that is a property that attaches to the owner / peer of the governance module or if it is more personal. It should be stated somewhere clearly though. <br />
<br />
There is a [[GovernanceIssues|list of open governance issues]].<br />
<br />
Due to the large and diverse nature of topics included in the Governance<br />
module, we will divide responsibilities by sub-module, in order to delegate<br />
authority for specific pieces and identify particular areas of expertise. <br />
<br />
===Governance Submodule: Module Ownership System=== <br />
<br />
* owner: Brendan Eich<br />
* peers: Stuart Parmenter, Dan Mosedale, Robert Kaiser, Mike Connor, David Baron, Frank Hecker, Mitchell Baker [mailto:module-ownership@mozilla.org E-mail this group]<br />
* newsgroup: mozilla.governance<br />
* scope: project-wide<br />
* responsibilities: Healthy operation of the module ownership system, including topics such as:<br />
** Filling vacant roles where appropriate<br />
** Ensuring module owners are fulfilling their responsibilities, and replacing those who are not<br />
** Creating and staffing new modules where new parts of the project evolve.<br />
** Figuring out what to do if a module isn't getting enough attention<br />
** Resolving conflicts among module owners<br />
<br />
===Governance Submodule: Incubator Repositories=== <br />
<br />
* owner: Stuart Parmenter<br />
* peer(s): Jonas Sicking, Mike Connor, Mike Shaver, Christian Sejersen <br />
*newsgroup: mozilla.governance<br />
* governing policy document: http://www.mozilla.org/hacking/incubator-repository.html<br />
* scope: project-wide<br />
* responsibilities: Implementing the Incubator Repository Policy including topics such as:<br />
** Evaluating requests for new incubator repositories<br />
** Determining if an incubatory repository may live longer than six months<br />
** Other issues that come up in the operation of incubator repositories<br />
<br />
===Governance Submodule: Commit Access Policy===<br />
* owner: Mitchell Baker<br />
* peers:<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/hacking/committer/ Commit Access Policy ]<br />
* scope: project-wide<br />
<br />
===Governance Submodule: Security Policy===<br />
* owner: Frank Hecker<br />
* peers:<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/projects/security/security-bugs-policy.html Handling Mozilla Security Bugs]<br />
* scope: project-wide (applies to all Mozilla projects)<br />
<br />
===Governance Submodule: Mozilla CA Certificate Policy===<br />
* owner: Frank Hecker<br />
* peers:<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/projects/security/certs/policy/ Mozilla CA Certificate Policy]<br />
* scope: project-wide (applies to all Mozilla projects that includes root certificates)<br />
<br />
===Governance Submodule: Code Review Policy===<br />
* owner: Mitchell Baker<br />
* peers: Brendan Eich<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/hacking/reviewers.html Mozilla "super-review"]<br />
* scope: project-wide<br />
<br />
===Governance Submodule: Performance Regression Policy===<br />
* owner: Mitchell Baker<br />
* peers:<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/hacking/reviewers.html Mozilla "super-review"]<br />
* scope: project-wide<br />
<br />
==Planet Mozilla Module== <br />
* owner: Robert Accettura<br />
* peers: Asa Dotzler, Reed Loden, J. Paul Reed, Deb Richardson<br />
* newsgroup: <br />
* scope: project-wide<br />
* responsibilities: content and policy for planet.mozilla.org, including topics such as:<br />
** which blogs are syndicated to planet.mozilla.org<br />
** which content from syndicated blogs in included<br />
** other planet.mozilla.org policy issues<br />
<br />
==Mozilla Public License Module==<br />
<br />
* owner: Mitchell Baker<br />
*peers: (TBD)<br />
*newsgroup: mozilla.governance; and mozilla.governance-mpl-update (at least during the process of updating the MPL 1.1, beginning March 10, 2010)<br />
*scope: project-wide, and affects other projects using the MPL<br />
*responsibilities: maintenance and development of the MPL<br />
** changes in the legal landscape which could /should be reflected<br />
** changes in FLOSS development practices which could / should be reflected<br />
<br />
==www.mozilla.org Module==<br />
* owners: Reed Loden (technical issues), David Boswell (content issues)<br />
* peers: Elika Etemad, Robert Kaiser, Eric Shepherd<br />
* newsgroup: [http://groups.google.com/group/mozilla.dev.mozilla-org/topics mozilla.dev.mozilla-org]<br />
* scope: project-wide<br />
* responsibilities: content and policy for www.mozilla.org<br />
<br />
==CA Certificates Module== <br />
*owner: Kathleen Wilson<br />
*peers: Frank Hecker<br />
*newsgroup: mozilla.dev.security.policy<br />
*governing policy document: <br />
*http://www.mozilla.org/projects/security/certs/policy/<br />
*scope: project-wide (applies to all Mozilla software that includes root certificates)<br />
*responsibilities: Determine which root certificates should be included in Mozilla software products and which trust bits should be set on them, and evaluate requests from Certification Authorities (CAs) for inclusion of new root certificates.<br />
<br />
==Participation Metrics Module==<br />
<br />
* owner: Asa Dotzler<br />
* peers: Daniel Einspanjer, Ken Kovash<br />
* newsgroup: <br />
* governing policy document: N/A<br />
* https://wiki.mozilla.org/ParticipationMetrics/roadmap<br />
* scope: project-wide <br />
* responsibilities: develop, monitor and analyze metrics relating to participation in the Mozilla project, including such things as: <br />
** determining which questions are most important to ask (how many people do X?)<br />
** determining what data is relevant to answer these questions<br />
** designing and operating a system to generate the requested data<br />
** analyzing the resulting metrics<br />
** notifying appropriate people when participation starts to change significantly<br />
** assisting various groups to understand and use the metrics to strengthen participation<br />
** produce periodic report/analysis of participation metrics <br />
*other: This module is explicitly NOT a "maintain community health" module. This responsibility lives across the Mozilla project. Every group working on Mozilla is responsible for developing participation in their area. The role of this module is to add metrics as a tool for various groups to use to help understand the state of participation.</div>MitchellBakerhttps://wiki.mozilla.org/index.php?title=Module_Owners_Activities_Modules&diff=224461Module Owners Activities Modules2010-05-20T02:27:08Z<p>MitchellBaker: /* Participation Metrics Module */</p>
<hr />
<div>'''Activities Modules'''<br />
<br />
== Overview ==<br />
Activities [[Modules_and_Module_Ownership|modules]] are a part of Mozilla's [http://www.mozilla.org/hacking/module-ownership.html Module Ownership system], a basic organizing and governance principle of the Mozilla project. (The name "activities" may change. It's a bit too generic and could apply to<br />
anything, including code modules. If you've got a good idea, please let Mitchell Baker know.)<br />
<br />
== Governance Module ==<br />
<br />
* owner: Mitchell Baker<br />
* peer(s): Brendan Eich<br />
* newsgroup: mozilla.governance<br />
* scope: project-wide<br />
* governing policy document: <br />
* responsibilities: Policies and process for how we distribute authority and govern ourselves; including:<br />
** Development and Implementation of new policies as appropriate for delegation of authority and responsibility<br />
** Management of the source tree<br />
** Balancing different constituencies of the Mozilla project<br />
** Maintaining the Mozilla identity as we take on new activities<br />
* 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.<br />
* final decision-makers: the final decision maker -- when needed -- for the Mozilla project in technical matters is Brendan Eich and for other matters is Mitchell Baker; this has been the case since 1998 for Brendan and 1999 for Mitchell. I haven't figured out how to capture that clearly here. That authority is broader than "policy and process." I don't know if that is a property that attaches to the owner / peer of the governance module or if it is more personal. It should be stated somewhere clearly though. <br />
<br />
Due to the large and diverse nature of topics included in the Governance<br />
module, we will divide responsibilities by sub-module, in order to delegate<br />
authority for specific pieces and identify particular areas of expertise. <br />
<br />
===Governance Submodule: Module Ownership System=== <br />
<br />
* owner: Brendan Eich<br />
* peers: Stuart Parmenter, Dan Mosedale, Robert Kaiser, Mike Connor, David Baron, Frank Hecker, Mitchell Baker [mailto:module-ownership@mozilla.org E-mail this group]<br />
* newsgroup: mozilla.governance<br />
* scope: project-wide<br />
* responsibilities: Healthy operation of the module ownership system, including topics such as:<br />
** Filling vacant roles where appropriate<br />
** Ensuring module owners are fulfilling their responsibilities, and replacing those who are not<br />
** Creating and staffing new modules where new parts of the project evolve.<br />
** Figuring out what to do if a module isn't getting enough attention<br />
** Resolving conflicts among module owners<br />
<br />
===Governance Submodule: Incubator Repositories=== <br />
<br />
* owner: Stuart Parmenter<br />
* peer(s): Jonas Sicking, Mike Connor, Mike Shaver, Christian Sejersen <br />
*newsgroup: mozilla.governance<br />
* governing policy document: http://www.mozilla.org/hacking/incubator-repository.html<br />
* scope: project-wide<br />
* responsibilities: Implementing the Incubator Repository Policy including topics such as:<br />
** Evaluating requests for new incubator repositories<br />
** Determining if an incubatory repository may live longer than six months<br />
** Other issues that come up in the operation of incubator repositories<br />
<br />
===Governance Submodule: Commit Access Policy===<br />
* owner: Mitchell Baker<br />
* peers:<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/hacking/committer/ Commit Access Policy ]<br />
* scope: project-wide<br />
<br />
===Governance Submodule: Security Policy===<br />
* owner: Frank Hecker<br />
* peers:<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/projects/security/security-bugs-policy.html Handling Mozilla Security Bugs]<br />
* scope: project-wide (applies to all Mozilla projects)<br />
<br />
===Governance Submodule: Mozilla CA Certificate Policy===<br />
* owner: Frank Hecker<br />
* peers:<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/projects/security/certs/policy/ Mozilla CA Certificate Policy]<br />
* scope: project-wide (applies to all Mozilla projects that includes root certificates)<br />
<br />
===Governance Submodule: Code Review Policy===<br />
* owner: Mitchell Baker<br />
* peers: Brendan Eich<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/hacking/reviewers.html Mozilla "super-review"]<br />
* scope: project-wide<br />
<br />
===Governance Submodule: Performance Regression Policy===<br />
* owner: Mitchell Baker<br />
* peers:<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/hacking/reviewers.html Mozilla "super-review"]<br />
* scope: project-wide<br />
<br />
==Planet Mozilla Module== <br />
* owner: Deb Richardson<br />
* peers: Robert Accettura, Asa Dotzler, Reed Loden, J. Paul Reed<br />
* newsgroup: <br />
* scope: project-wide<br />
* responsibilities: content and policy for planet.mozilla.org, including topics such as:<br />
** which blogs are syndicated to planet.mozilla.org<br />
** which content from syndicated blogs in included<br />
** other planet.mozilla.org policy issues<br />
<br />
==Mozilla Public License Module==<br />
<br />
* owner: Mitchell Baker<br />
*peers: (TBD)<br />
*newsgroup: mozilla.governance; and mozilla.governance-mpl-update (at least during the process of updating the MPL 1.1, beginning March 10, 2010)<br />
*scope: project-wide, and affects other projects using the MPL<br />
*responsibilities: maintenance and development of the MPL<br />
** changes in the legal landscape which could /should be reflected<br />
** changes in FLOSS development practices which could / should be reflected<br />
<br />
==www.mozilla.org Module==<br />
* owners: Reed Loden (technical issues), David Boswell (content issues)<br />
* peers: Elika Etemad, Robert Kaiser, Eric Shepherd<br />
* newsgroup: [http://groups.google.com/group/mozilla.dev.mozilla-org/topics mozilla.dev.mozilla-org]<br />
* scope: project-wide<br />
* responsibilities: content and policy for www.mozilla.org<br />
<br />
==CA Certificates Module== <br />
*owner: Frank Hecker<br />
*peers: Kathleen Wilson<br />
*newsgroup: mozilla.dev.security.policy<br />
*governing policy document: <br />
*http://www.mozilla.org/projects/security/certs/policy/<br />
*scope: project-wide (applies to all Mozilla software that includes root certificates)<br />
*responsibilities: Determine which root certificates should be included in Mozilla software products and which trust bits should be set on them, and evaluate requests from Certification Authorities (CAs) for inclusion of new root certificates.<br />
<br />
==Participation Metrics Module==<br />
<br />
* owner: Asa Dotzler<br />
* peers: Daniel Einspanjer, Ken Kovash<br />
* newsgroup: <br />
* governing policy document: N/A<br />
* https://wiki.mozilla.org/ParticipationMetrics/roadmap<br />
* scope: project-wide <br />
* responsibilities: develop, monitor and analyze metrics relating to participation in the Mozilla project, including such things as: <br />
** determining which questions are most important to ask (how many people do X?)<br />
** determining what data is relevant to answer these questions<br />
** designing and operating a system to generate the requested data<br />
** analyzing the resulting metrics<br />
** notifying appropriate people when participation starts to change significantly<br />
** assisting various groups to understand and use the metrics to strengthen participation<br />
** produce periodic report/analysis of participation metrics <br />
*other: This module is explicitly NOT a "maintain community health" module. This responsibility lives across the Mozilla project. Every group working on Mozilla is responsible for developing participation in their area. The role of this module is to add metrics as a tool for various groups to use to help understand the state of participation.</div>MitchellBakerhttps://wiki.mozilla.org/index.php?title=Module_Owners_Activities_Modules&diff=224460Module Owners Activities Modules2010-05-20T02:22:34Z<p>MitchellBaker: /* CA Certificates Module */</p>
<hr />
<div>'''Activities Modules'''<br />
<br />
== Overview ==<br />
Activities [[Modules_and_Module_Ownership|modules]] are a part of Mozilla's [http://www.mozilla.org/hacking/module-ownership.html Module Ownership system], a basic organizing and governance principle of the Mozilla project. (The name "activities" may change. It's a bit too generic and could apply to<br />
anything, including code modules. If you've got a good idea, please let Mitchell Baker know.)<br />
<br />
== Governance Module ==<br />
<br />
* owner: Mitchell Baker<br />
* peer(s): Brendan Eich<br />
* newsgroup: mozilla.governance<br />
* scope: project-wide<br />
* governing policy document: <br />
* responsibilities: Policies and process for how we distribute authority and govern ourselves; including:<br />
** Development and Implementation of new policies as appropriate for delegation of authority and responsibility<br />
** Management of the source tree<br />
** Balancing different constituencies of the Mozilla project<br />
** Maintaining the Mozilla identity as we take on new activities<br />
* 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.<br />
* final decision-makers: the final decision maker -- when needed -- for the Mozilla project in technical matters is Brendan Eich and for other matters is Mitchell Baker; this has been the case since 1998 for Brendan and 1999 for Mitchell. I haven't figured out how to capture that clearly here. That authority is broader than "policy and process." I don't know if that is a property that attaches to the owner / peer of the governance module or if it is more personal. It should be stated somewhere clearly though. <br />
<br />
Due to the large and diverse nature of topics included in the Governance<br />
module, we will divide responsibilities by sub-module, in order to delegate<br />
authority for specific pieces and identify particular areas of expertise. <br />
<br />
===Governance Submodule: Module Ownership System=== <br />
<br />
* owner: Brendan Eich<br />
* peers: Stuart Parmenter, Dan Mosedale, Robert Kaiser, Mike Connor, David Baron, Frank Hecker, Mitchell Baker [mailto:module-ownership@mozilla.org E-mail this group]<br />
* newsgroup: mozilla.governance<br />
* scope: project-wide<br />
* responsibilities: Healthy operation of the module ownership system, including topics such as:<br />
** Filling vacant roles where appropriate<br />
** Ensuring module owners are fulfilling their responsibilities, and replacing those who are not<br />
** Creating and staffing new modules where new parts of the project evolve.<br />
** Figuring out what to do if a module isn't getting enough attention<br />
** Resolving conflicts among module owners<br />
<br />
===Governance Submodule: Incubator Repositories=== <br />
<br />
* owner: Stuart Parmenter<br />
* peer(s): Jonas Sicking, Mike Connor, Mike Shaver, Christian Sejersen <br />
*newsgroup: mozilla.governance<br />
* governing policy document: http://www.mozilla.org/hacking/incubator-repository.html<br />
* scope: project-wide<br />
* responsibilities: Implementing the Incubator Repository Policy including topics such as:<br />
** Evaluating requests for new incubator repositories<br />
** Determining if an incubatory repository may live longer than six months<br />
** Other issues that come up in the operation of incubator repositories<br />
<br />
===Governance Submodule: Commit Access Policy===<br />
* owner: Mitchell Baker<br />
* peers:<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/hacking/committer/ Commit Access Policy ]<br />
* scope: project-wide<br />
<br />
===Governance Submodule: Security Policy===<br />
* owner: Frank Hecker<br />
* peers:<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/projects/security/security-bugs-policy.html Handling Mozilla Security Bugs]<br />
* scope: project-wide (applies to all Mozilla projects)<br />
<br />
===Governance Submodule: Mozilla CA Certificate Policy===<br />
* owner: Frank Hecker<br />
* peers:<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/projects/security/certs/policy/ Mozilla CA Certificate Policy]<br />
* scope: project-wide (applies to all Mozilla projects that includes root certificates)<br />
<br />
===Governance Submodule: Code Review Policy===<br />
* owner: Mitchell Baker<br />
* peers: Brendan Eich<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/hacking/reviewers.html Mozilla "super-review"]<br />
* scope: project-wide<br />
<br />
===Governance Submodule: Performance Regression Policy===<br />
* owner: Mitchell Baker<br />
* peers:<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/hacking/reviewers.html Mozilla "super-review"]<br />
* scope: project-wide<br />
<br />
==Planet Mozilla Module== <br />
* owner: Deb Richardson<br />
* peers: Robert Accettura, Asa Dotzler, Reed Loden, J. Paul Reed<br />
* newsgroup: <br />
* scope: project-wide<br />
* responsibilities: content and policy for planet.mozilla.org, including topics such as:<br />
** which blogs are syndicated to planet.mozilla.org<br />
** which content from syndicated blogs in included<br />
** other planet.mozilla.org policy issues<br />
<br />
==Mozilla Public License Module==<br />
<br />
* owner: Mitchell Baker<br />
*peers: (TBD)<br />
*newsgroup: mozilla.governance; and mozilla.governance-mpl-update (at least during the process of updating the MPL 1.1, beginning March 10, 2010)<br />
*scope: project-wide, and affects other projects using the MPL<br />
*responsibilities: maintenance and development of the MPL<br />
** changes in the legal landscape which could /should be reflected<br />
** changes in FLOSS development practices which could / should be reflected<br />
<br />
==www.mozilla.org Module==<br />
* owners: Reed Loden (technical issues), David Boswell (content issues)<br />
* peers: Elika Etemad, Robert Kaiser, Eric Shepherd<br />
* newsgroup: [http://groups.google.com/group/mozilla.dev.mozilla-org/topics mozilla.dev.mozilla-org]<br />
* scope: project-wide<br />
* responsibilities: content and policy for www.mozilla.org<br />
<br />
==CA Certificates Module== <br />
*owner: Frank Hecker<br />
*peers: Kathleen Wilson<br />
*newsgroup: mozilla.dev.security.policy<br />
*governing policy document: <br />
*http://www.mozilla.org/projects/security/certs/policy/<br />
*scope: project-wide (applies to all Mozilla software that includes root certificates)<br />
*responsibilities: Determine which root certificates should be included in Mozilla software products and which trust bits should be set on them, and evaluate requests from Certification Authorities (CAs) for inclusion of new root certificates.<br />
<br />
==Participation Metrics Module==</div>MitchellBakerhttps://wiki.mozilla.org/index.php?title=Module_Owners_Activities_Modules&diff=208063Module Owners Activities Modules2010-03-12T23:19:02Z<p>MitchellBaker: /* Planet Mozilla Module */</p>
<hr />
<div>'''Activities Modules'''<br />
<br />
== Overview ==<br />
Activities [[Modules_and_Module_Ownership|modules]] are a part of Mozilla's [http://www.mozilla.org/hacking/module-ownership.html Module Ownership system], a basic organizing and governance principle of the Mozilla project. (The name "activities" may change. It's a bit too generic and could apply to<br />
anything, including code modules. If you've got a good idea, please let Mitchell Baker know.)<br />
<br />
== Governance Module ==<br />
<br />
* owner: Mitchell Baker<br />
* peer(s): Brendan Eich<br />
* newsgroup: mozilla.governance<br />
* scope: project-wide<br />
* governing policy document: <br />
* responsibilities: Policies and process for how we distribute authority and govern ourselves; including:<br />
** Development and Implementation of new policies as appropriate for delegation of authority and responsibility<br />
** Management of the source tree<br />
** Balancing different constituencies of the Mozilla project<br />
** Maintaining the Mozilla identity as we take on new activities<br />
* 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.<br />
* final decision-makers: the final decision maker -- when needed -- for the Mozilla project in technical matters is Brendan Eich and for other matters is Mitchell Baker; this has been the case since 1998 for Brendan and 1999 for Mitchell. I haven't figured out how to capture that clearly here. That authority is broader than "policy and process." I don't know if that is a property that attaches to the owner / peer of the governance module or if it is more personal. It should be stated somewhere clearly though. <br />
<br />
Due to the large and diverse nature of topics included in the Governance<br />
module, we will divide responsibilities by sub-module, in order to delegate<br />
authority for specific pieces and identify particular areas of expertise. <br />
<br />
===Governance Submodule: Module Ownership System=== <br />
<br />
* owner: Brendan Eich<br />
* peers: Stuart Parmenter, Dan Mosedale, Robert Kaiser, Mike Connor, David Baron, Frank Hecker, Mitchell Baker [mailto:module-ownership@mozilla.org E-mail this group]<br />
* newsgroup: mozilla.governance<br />
* scope: project-wide<br />
* responsibilities: Healthy operation of the module ownership system, including topics such as:<br />
** Filling vacant roles where appropriate<br />
** Ensuring module owners are fulfilling their responsibilities, and replacing those who are not<br />
** Creating and staffing new modules where new parts of the project evolve.<br />
** Figuring out what to do if a module isn't getting enough attention<br />
** Resolving conflicts among module owners<br />
<br />
===Governance Submodule: Incubator Repositories=== <br />
<br />
* owner: Stuart Parmenter<br />
* peer(s): Jonas Sicking, Mike Connor, Mike Shaver, Christian Sejersen <br />
*newsgroup: mozilla.governance<br />
* governing policy document: http://www.mozilla.org/hacking/incubator-repository.html<br />
* scope: project-wide<br />
* responsibilities: Implementing the Incubator Repository Policy including topics such as:<br />
** Evaluating requests for new incubator repositories<br />
** Determining if an incubatory repository may live longer than six months<br />
** Other issues that come up in the operation of incubator repositories<br />
<br />
===Governance Submodule: Commit Access Policy===<br />
* owner: Mitchell Baker<br />
* peers:<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/hacking/committer/ Commit Access Policy ]<br />
* scope: project-wide<br />
<br />
===Governance Submodule: Security Policy===<br />
* owner: Frank Hecker<br />
* peers:<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/projects/security/security-bugs-policy.html Handling Mozilla Security Bugs]<br />
* scope: project-wide (applies to all Mozilla projects)<br />
<br />
===Governance Submodule: Mozilla CA Certificate Policy===<br />
* owner: Frank Hecker<br />
* peers:<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/projects/security/certs/policy/ Mozilla CA Certificate Policy]<br />
* scope: project-wide (applies to all Mozilla projects that includes root certificates)<br />
<br />
===Governance Submodule: Code Review Policy===<br />
* owner: Mitchell Baker<br />
* peers: Brendan Eich<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/hacking/reviewers.html Mozilla "super-review"]<br />
* scope: project-wide<br />
<br />
===Governance Submodule: Performance Regression Policy===<br />
* owner: Mitchell Baker<br />
* peers:<br />
* newsgroup: mozilla.governance<br />
* governing policy document: [http://www.mozilla.org/hacking/reviewers.html Mozilla "super-review"]<br />
* scope: project-wide<br />
<br />
==Planet Mozilla Module== <br />
* owner: Deb Richardson<br />
* peers: Robert Accettura, Asa Dotzler, Reed Loden, J. Paul Reed<br />
* newsgroup: <br />
* scope: project-wide<br />
* responsibilities: content and policy for planet.mozilla.org, including topics such as:<br />
** which blogs are syndicated to planet.mozilla.org<br />
** which content from syndicated blogs in included<br />
** other planet.mozilla.org policy issues<br />
<br />
==Mozilla Public License Module==<br />
<br />
* owner: Mitchell Baker<br />
*peers: (TBD)<br />
*newsgroup: mozilla.governance; and mozilla.governance-mpl-update (at least during the process of updating the MPL 1.1, beginning March 10, 2010)<br />
*scope: project-wide, and affects other projects using the MPL<br />
*responsibilities: maintenance and development of the MPL<br />
** changes in the legal landscape which could /should be reflected<br />
** changes in FLOSS development practices which could / should be reflected<br />
<br />
==www.mozilla.org Module==<br />
* owners: Reed Loden (technical issues), David Boswell (content issues)<br />
* peers: Elika Etemad, Robert Kaiser, Eric Shepherd<br />
* newsgroup: [http://groups.google.com/group/mozilla.dev.mozilla-org/topics mozilla.dev.mozilla-org]<br />
* scope: project-wide<br />
* responsibilities: content and policy for www.mozilla.org<br />
<br />
==CA Certificates Module== <br />
*owner: Frank Hecker<br />
*peers: Kathleen Wilson<br />
*newsgroup: mozilla.dev.security.policy<br />
*governing policy document: <br />
*http://www.mozilla.org/projects/security/certs/policy/<br />
*scope: project-wide (applies to all Mozilla software that includes root certificates)<br />
*responsibilities: Determine which root certificates should be included in Mozilla software products and which trust bits should be set on them, and evaluate requests from Certification Authorities (CAs) for inclusion of new root certificates.</div>MitchellBakerhttps://wiki.mozilla.org/index.php?title=WeeklyUpdates/2009-07-06&diff=153691WeeklyUpdates/2009-07-062009-07-06T18:12:12Z<p>MitchellBaker: /* Other Business */</p>
<hr />
<div><small>[[WeeklyUpdates/2009-06-29| « previous week]] | [[WeeklyUpdates|index]] | [[WeeklyUpdates/2009-07-13|next week »]]</small><br />
<br />
= Friends of the Tree [[Image:Tree.gif|Friends of the Tree]] =<br />
<br />
= Development Updates =<br />
== Firefox ==<br />
* we shipped a browser last week - perhaps you noticed?<br />
* 15M downloads and [http://downloadstats.mozilla.com/ counting]<br />
* Windows CE builds are becoming a higher priority<br />
<br />
'''[[Firefox/Namoroka|Namoroka]]'''<br />
* Explorations and sprints to determine what will become the cornerstones of 3.next/Namoroka<br />
<br />
'''Team News'''<br />
* Stephen Horlander starts today as a visual designer for Firefox! Stephen has been involved with Firefox since 1.0, working on the primary theme for Windows. Mac and Linux for 1.0 and 1.5, and the default OSX theme for Firefox 3.0<br />
<br />
== Gecko ==<br />
<br />
== Branch work: Firefox 3.0.x / Thunderbird 2.0.0.x ==<br />
* '''[[Releases/Firefox 3.0.12|Firefox 3.0.12]]'''<br />
** handed off to build a couple hours ago<br />
** still targeting mid-late July for release<br />
* '''[[Releases/Firefox 3.0.13|Firefox 3.0.13]]'''<br />
** proposed schedule to become final this week<br />
** will have a final list of blockers this week as well<br />
* '''[[Releases/Firefox 3.5.1|Firefox 3.5.1]]'''<br />
** starting to build out a schedule this week<br />
** stay tuned, come to tomorrow's development meeting<br />
<br />
== TB 3 ==<br />
* [[3.0b3 schedule updated]]<br />
<br />
== Mobile ==<br />
<br />
<br />
<br />
== IT ==<br />
* [http://twitter.com/mozdashboard @mozdashboard] Experiment & Data<br />
** Peaks as seen from the ZXTM Load Balancer:<br />
*** addons.mozilla.org: 6127 hits/second, 210Mbps<br />
*** versioncheck.addons.mozilla.org: 4175 hits/second, 30Mbps<br />
*** fxfeeds.mozilla.org: 7628 hits/second, 38Mbps<br />
* Old builds & ftp.mozilla.org <br />
** Still working with Metrics on usage analysis<br />
** [http://groups.google.com/group/mozilla.dev.builds/browse_thread/thread/35449ab28f4ed2ed/8bf29b3ad848e957#8bf29b3ad848e957 moz.dev.builds discussion]<br />
<br />
== Release Engineering ==<br />
* New Talos TP4 pageset enabled on mozilla-central {{bug|473821}}<br />
** faster then tp3, beginning of the end for fast talos.<br />
* Graph Server migration {{bug|487329}}<br />
<br />
== QA ==<br />
<br />
'''Test Execution '''<br />
* Shipped Firefox 3.5!<br />
** Includes Firefox 3.0.11 to 3.5 MU<br />
* Smoketest automation is 92% completed. 2 tests remain (1 blocked, 1 assigned, 0 pending).<br />
* started BFT code coverage runs (murali)<br />
<br />
'''Web Dev Testing''' <br />
* [https://wiki.mozilla.org/Update:Remora_Meeting_Notepad AMO]: Testing AMO 5.0.7 features.Filed [http://tinyurl.com/nfhg3k 28 bugs]. Created test cases for Tagging features. Created test cases for AMO homepage.<br />
* Mozilla service week: Triaged around 30 bugs<br />
<br />
'''Metrics, Accessibility, Localization, Community''' <br />
* Our community will be triaging remaining Firefox 3.5 bugs at [http://quality.mozilla.org/events/2009/jun/30/firefox-bugday-catch-missed-blocker-critical-and-major-35-bugs Bugday]. Please join us this tuesday, July 7th all day. <br />
* This week's testday is on [http://quality.mozilla.org/blogs/firefox-35-security-testday-next-week Security]. Please join us this friday, July 10th, from 7am-5pm PDT.<br />
* Assisted with the SUMO team with release day LiveChat support<br />
<br />
''' Test Development '''<br />
<br />
== Security ==<br />
Fuzz-testers Martijn Wargers and Paul Nickerson are visiting Mountain View this week. We'll be scheduling meetings with lots of groups, such as the people working on the HTML5 parser.<br />
<br />
There might be areas that need fuzzing that we're not aware of. If you need something fuzzed, find us near the QA area this week!<br />
<br />
== Marketing/PR ==<br />
<br />
<br />
'''Firefox 3.5 Launch'''<br />
*Firefox 3.5 Swag Requests: We now have 205 requests for swag packs for 3.5 launch parties (up from 106 requests last week). Some of the new requests this week have come from India, Macedonia, Spain and Mexico.<br />
* Firefox 3.5 Parties: Over 20 parties this week alone on [http://www.spreadfirefox.com/event Spread Firefox]. Some parties this week are taking place in Romania, Mexico and the UK.<br />
<br />
<br />
'''PR'''<br />
* Press coverage highlights: [http://www.abcnews.go.com/Video/playerIndex?id=7974979 ABC News], [http://bit.ly/a1Ts1 MTV], [http://digg.com/software/How_Mozilla_Deploys_Volunteer_Developers_BusinessWeek BusinessWeek], [http://news.cnet.com/8301-17939_109-10275863-2.html CNET], [http://www.npr.org/blogs/alltechconsidered/2009/06/new_firefox_released.html NPR], [http://www.techcrunch.com/2009/06/30/firefox-35-soars-past-a-million-downloads-approaching-100-downloads-a-second/ TechCrunch], [http://arstechnica.com/open-source/news/2009/07/firefox-35-downloaded-5-million-times-in-first-24-hours.ars Ars Technica], [http://download.cnet.com/8301-2007_4-10276067-12.html CNET], [http://www.crn.com/software/218400469;jsessionid=BBJVGOLKNWCRIQSNDLOSKHSCJUNN2JVN CRN]<br />
* Mark Surman in the [http://blog.estadao.com.br/blog/link/?title=no_novo_firefox_videos_interagem_com_sit&more=1&c=1&tb=1&pb=1 Brazilian press]<br />
* [http://news.cnet.com/8301-13505_3-10278933-16.html CNET] takes a look at open source<br />
* John Lilly talks with [http://www.h-online.com/open/Mozilla-CEO-The-browser-has-a-long-way-to-go--/features/113681/0 The H] and [http://gigaom.com/2009/07/05/for-firefox-a-challenging-future-awaits/ GigaOm]<br />
<br />
'''Mozilla Service Week'''<br />
<br />
'''Events''' <br />
*[[Renegade Craft Fair|Renegade Craft Festival]], July 18 - 19, 2009, San Francisco - Opportunity to garner awareness for Personas and to get new ones created. Also a great place to expose add-ons. Sign-ups to work at the festival are on the [[Renegade Craft Fair#Signups|wiki]]. <br />
*[[Event:Maker Faire Africa|Maker Faire Africa]] August 14 - 16, 2009, Accra, Ghana - Looking to sponsor the event and bring together the local L10n community. Check out the wiki for early details.<br />
<br />
'''General'''<br />
*New Spread Firefox Affiliate Reward program: http://www.spreadfirefox.com/affiliates/rewards<br />
<br />
== Support ==<br />
* Firefox 3.5 launch stats<br />
** KB CSAT was at an all-time high at 89%<br />
** Over 1000 users were getting help using Live Chat<br />
** Lowest average response time in the forum of the whole quarter<br />
** '''Over 130 active SUMO contributors last week'''<br />
* Huge thanks to all the amazing people who helped making the 3.5 release a success for SUMO!<br />
<br />
== Metrics ==<br />
* Fx3.5 stats<br />
** In less than a week, we've seen 16 million downloads (thanks to Daniel for the [http://downloadstats.mozilla.com/ cool visualization and live counter])<br />
** A couple different sources for real-time market share data ([http://whos.amung.us/firefox/ here's one example]) show Fx3.5 at nearly 4% worldwide market share<br />
* June market share – [http://marketshare.hitslink.com Net Applications] is still working through some issues. Almost all data has been temporarily removed from their site and a note states, "Browser and O/S June stats under review. We are investigating some significant variations in browser and operating system statistics. The reports will not be available until we complete our review."<br />
<br />
== Evangelism ==<br />
<br />
(Update from Arun in Blizzard's absence)<br />
<br />
* hacks.mozilla.org awesomeness continues<br />
** Recently: XS-XHR, Video, etc.<br />
<br />
== Labs ==<br />
<br />
== Developer Tools ==<br />
<br />
== Add-ons ==<br />
* [http://moxie.fligtar.com/amo/5.0.7 5.0.7] pushed to next Wednesday (7/15) ([https://preview.addons.mozilla.org help us test!])<br />
* Upcoming projects welcoming discussion<br />
** [http://groups.google.com/group/mozilla.dev.amo/browse_thread/thread/85dcccf4f1bbf88e Collections Phase II]<br />
** [http://groups.google.com/group/mozilla.dev.amo/browse_thread/thread/d8c2bf3f9a0c1997 Removing the sandbox]<br />
** [https://bugzilla.mozilla.org/show_bug.cgi?id=499738 developer.AMO designs]<br />
* 365 pending updates and 268 nominated add-ons ([http://people.mozilla.com/~jscott/queue-length.png graph])<br />
* [https://addons.mozilla.org/en-US/firefox/compatibility 90%] of hosted add-ons compatible with 3.5.*<br />
<br />
== Webdev ==<br />
* [http://moxie.fligtar.com/bugstats/amo/5.0.7 AMO 5.0.7] freeze was 7/2<br />
* 3.5 launch stuff<br />
** assisted with mozilla.com stuff where needed<br />
** added dolphins and stylin' to [http://downloadstats.mozilla.com/ the download counter]<br />
* [https://wiki.mozilla.org/Webdev:Cesium Cesium alpha almost done], which is really exciting!<br />
* [http://graphs.mozilla.org/ Graph Server 1.0] launched; had to wait until after 3.5 to make Talos changes<br />
* [http://www.spreadfirefox.com/affiliates/utw Upgrade the web] campaign on Spreadfirefox launched last week -- buttons are super cool, check them out!<br />
<br />
== L10n ==<br />
<br />
'''Firefox 3.5'''<br />
<br />
'''Web'''<br />
<br />
'''Tools'''<br />
<br />
= Foundation Updates =<br />
* '''Chelsea Novak joins the Mozilla Foundation''' this week as fundraising manager, working out of the Toronto office; please join us in extending a warm welcome to Chelsea!<br />
* We continue to prepare for the '''[http://www-stage.mozilla.org/ relaunch of www.mozilla.org]''':<br />
** Our launch date has been delayed slightly<br />
** If you are interested in helping us embed [https://bespin.mozilla.com/ Bespin] as a site editor, please let us know<br />
** If you own any documentation on the site, please review the open [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=migrate&product=Websites&component=www.mozilla.org&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&resolution=DUPLICATE&resolution=---&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= documentation migration bugs]<br />
** See our [https://wiki.mozilla.org/Mozilla.org/Roadmap site roadmap] for our plans for after relaunch<br />
** The [http://www.mozilla.org/hacking/ Hacking] page on www.mozilla.org has been migrated to the [http://developer.mozilla.org/ Mozilla Developer Center], and the original URL redirected.<br />
* We're '''continuing work on improving Bugzilla''', with meetings of an advisory group to discuss overall issues and Gerv reaching out to major Bugzilla users; for more information see the [[BugzillaImprovements|wiki page]].<br />
* Gerv '''updated the [http://www.gerv.net/hacking/l10n-stats/ Firefox Language coverage data] for Firefox 3.5''' and [http://weblogs.mozillazine.org/gerv/archives/2009/06/firefox_35_language_coverage.html reblogged it].<br />
* In grant news, the '''Mozilla Corporation made a $10,000 grant to the [http://conservancy.softwarefreedom.org/ Software Freedom Conservancy]''' to help the Conservancy expand its activities in support of free and open source software projects.<br />
<br />
= Roundtable =<br />
<br />
== New Interns ==<br />
<br />
== Show & Tell ==<br />
<br />
This week we have the following interns presenting:<br><br />
William (Marketing)<br><br />
Margaret (FFx)<br><br />
Mark (Web Dev)<br><br />
Sully (Platform)<br><br />
<br />
= Other Business =<br />
<br />
Firefox 3.5 is not the first browser release with 650 Castro St in Mountain View as headquarters. That marker goes to Netscape Navigator 1.0.<br />
<br />
dmose and I were part of that release as well. If anyone is interested I'd be happy to tell a few stories from dec. 1994, and maybe dmose has a few stories as well.</div>MitchellBaker