MozillaWiki - User contributions [en]

Websites/Taskforce/Proposals/Domain Name Strategy

2013-11-12T13:38:37Z

Nuss: /* mozilla.com domains to switch */

'''Domain Name Strategy'''

If you have any questions about how this document applies to any work you are doing or if you have feedback or comments or need clarification, please contact david at mozillafoundation dot org and jslater at mozilla dot com.

''This strategy applies only to websites and does not intend to cover anything to do with email addresses.''

=Working Group=

John Slater, Janet Swisher, Laura Forrest and David Boswell

=Status=

This proposal was approved at the [[Websites/Taskforce/2010_10_21|10/21/10 task force meeting]].

=Problem=

We are currently using our organizational structure as a way to set up domain
names and this is presenting irrelevant information to people and diverting our
message away from more important things, such as what we do and why we do it.

For example, the following are some of the organizational domains currently in
use:

* mozilla.com

* mozillamessaging.com

* mozilla-europe.org*

* mozillaonline.com*

* mozilla.jp*

Note that mozilla.org is not an organizational domain -- it is the community's
domain that was set up and used long before there was any Mozilla organization.
It isn't the Foundation's organizational domain -- that is mozillafoundation.org
that was in use briefly but has been retired.

''*Affiliate URLs act as both an organization site and a local site, so there is no need to move away from using those domains. The more important issue with affiliate sites is making the content as relevant as possible by de-emphasizing the organizational information and highlighting the locale specific information.''

=Solution=

To be able to stop using organizations as a basis for our domain name
strategy, we need to develop an alternative that uses something else for its structure. There seem to be two main options:

* Structure a strategy based on product/activity: firefox.com, thunderbird.com, drumbeat.org, etc.

* Structure a strategy based on everything being a part of Mozilla: www.mozilla.org, addons.mozilla.org, foo.mozilla.org

Both options have advantages and disadvantages, but they are mutually exclusive so we need to pick one (although we can certainly maintain redirects for any URLs we want).

=="One Mozilla" Strategy==

To create a "One Mozilla" strategy for domain names, we propose using sub-domains for functional areas and sub-directories for products and programs (programs in the initiative sense) with some exceptions. So:

* service.mozilla.org/sub-category

The following breaks out how this general rule applies to different types of sites.

===Product and Program Sites===

Sites related to the major activities backed by Mozilla organizations should use sub-directories on www.mozilla.org. The service being offered here is delivery of web pages (compared with delivery of a web app providing specific functionality).

Examples:

* www.mozilla.org/firefox

* www.mozilla.org/thunderbird

* www.mozilla.org/drumbeat

Note: Other community-backed projects such as seamonkey-project.org can show affiliation with Mozilla on their site in a number of other ways without having to change their URL structure.

===Web Application Sites===

Sites that exist to host services should have sub-domains based on the service offered and sub-directories based on products or programs. This is the existing addons.mozilla.org model.

Examples:

* addons.mozilla.org/firefox, addons.mozilla.org/mobile, addons.mozilla.org/thunderbird, etc.

* support.mozilla.org/firefox, support.mozilla.org/mobile, support.mozilla.org/thunderbird, etc.

* nightly.mozilla.org/firefox, nightly.mozilla.org/mobile, nightly.mozilla.org/thunderbird, etc.

For sites that provide a service for the community as a whole and not for specific programs or products, there is no need to divide things by sub-directory.

Examples:

* air.mozilla.org

* developer.mozilla.org

* feeds.mozilla.org

===Campaign Sites===

Mini-sites set up for a specific campaign should be able to use whatever URL makes sense. Because these sites are usually relevant to a specific time, an archiving plan should be put in place so this content isn't abandoned.

Examples:

* firefoxflicks.com

* opentochoice.org

* operationfirefox.com

===Local Sites===

There are two main URL styles being used today by local sites.

Examples:

* mozilla.country: mozilla.jp, mozilla.ro, etc.

* mozilla-country.org: mozilla-mexico.org, mozilla-russia.org, etc.

There are also a variety of other URLs in use such as bgzilla.org and mozilla.org.ua. It may make sense to make these more consistent, but there is no plan to do that now. On the other hand, having flexibility with local site URLs allows us to deal with issues relevant to different locales.

===Mobile Sites===

Ideally each site would have one URL which would present its content in a form optimized for any device. For complex sites though, the functionality available on mobile versions may differ greatly and switching style sheets alone may not be sufficient.

When it isn't possible to maintain a single URL for a site, we recommend adding a "m." at the beginning of the domain, such as

* m.foo.mozilla.org.

In the cases when we do choose to go with separate mobile URLs, once we take the time to do things the ideal way we can just redirect mobile URLs to their desktop equivalents for a seamless transition.

===Other Sites===

Mozilla is a big community with many people doing many things and there's no benefit to making every site fit in some structure. It is fine for some sites to have unique URLs as long as they avoid organization specific domains or trademark violations.

Examples of sites with unique URLs that are fine:

* accessfirefox.org

* geckozone.org

* mozillamemory.org

==Proposed URL Changes==

Using the principles of the "One Mozilla" strategy, we suggest the following URL changes (this is just an initial batch and not comprehensive of all possible URL changes).

{| border="1px" cellspacing="0px"
! Existing URL !! Proposed URL !! Comment
|-
| mozilla.com || www.mozilla.org/firefox ||
|-
| mozillamessaging.com || www.mozilla.org/thunderbird ||
|-
| support.mozilla.com || support.mozilla.org ||
|-
| mobile.support.mozilla.com || support.mozilla.org/mobile ||
|-
| support.mozillamessaging.com || support.mozilla.org/thunderbird ||
|-
| air.mozilla.com || air.mozilla.org ||
|-
| feeds.mozilla.com || feeds.mozilla.org ||
|-
| input.mozilla.com || input.mozilla.org ||
|}

== Technical Considerations ==

=== Localization ===

The best practices around how to use locale codes in URLs shouldn't need to be changed due to this proposal. Sites can still use the following scheme (with the example here of Mozilla Europe's German Firefox page):

* www.mozilla-europe.org/de/firefox/

The bigger issue with the l10n process is how will this proposal change how localizers determine what to work on? If sites are aggregated into fewer domains will more content need to be localized or would we create less cohesive experiences with partially localized sites?

=== Security ===

Moving from multiple unique domains to subdomains of a single domain, and in some cases subdirectories within that subdomain, will require changes to the security requirements that are imposed upon these websites. Specifically, all websites that are grouped within the same subdomain will be subject to the highest security requirements of any site within that subdomain.

In some cases this may mean that a site that was previously not hosting or performing critical operations, and thus had more lenient security controls, would be required to significantly enhance the security controls before it could be added as a subdirectory of a more security restrictive subdomain.

In addition, depending upon the criticality of a given group of websites within a subdomain this may result in a more strictly controlled security review process including requirements to review any new code before it is pushed live to the site.

=== Webtrends Tracking ===

From Webtrends - You should be fine changing over from the .com domain to the .org domain, as long as the primary domain designated in the Webtrends JavaScript tag points to what you consider the primary domain. Additionally, if you plan on having both domains concurrently available, you may want to modify the JavaScript tag to include mozilla.com at a value for the this.onsitedoms=""; entry in the JavaScript include. This would then consider all traffic from mozilla.com to be considered part of the traffic on the primary domain and would not prefix entries in reports with "Offsite:"

=== SEO Best Practices ===

SEO Best Practices When Switching Domains

Please take the following into consideration when making these switches to minimize any possible dips in natural search traffic.

Redirect Treatment (Technical Owner)

*The most important thing to avoid is 404 (file not found) errors when searchers click on Mozilla site links that show up on the search engine response page (SERP)
*Use a permanent 301 redirect to redirect the pages on the old site to the new site. This also lets Google know all the pages have officially moved. 
*Change all internal site links to point to the correct domain
*Use link checking software to find any broken links
*Submit a new sitemap to Google Webmaster Tools and Yahoo Site Submit
*Do this in phases if possible, moving one subdirectory over at a time, monitoring the results 

Incoming Links (Business Owner)

*If possible, contact the main owners of our largest incoming traffic and have them change the link (Google Snippets, YouTube, Affiliate Programs, and many more)
*Closely monitor SERP results and incoming organic search traffic for major changes

 

References http://googlewebmastercentral.blogspot.com/2008/04/best-practices-when-moving-your-site.html http://www.clickz.com/clickz/column/1699947/seo-best-practices-when-moving-web-site http://www.seomoz.org/blog/seo-guide-how-to-properly-move-domains 

Also a recent quote from Matt Cutts of Google:  

''When done correctly, a 301 redirect shouldn't cause any drop in traffic, says Matt Cutts, a Google software engineer. He says instead of moving its entire website at once, Evo would have been better off moving the site very slowly, starting with the least-trafficked areas of its website. Changing something like the structure of a site during a move can also cause problems. "If someone changes to a new template, that can affect the rankings," says Cutts. "Sometimes it takes Google a little while to figure out how best to process, index, and rank a page."'' 

And input from Rand Fishkin of SEOmoz on our particular case: 

''On the switch over - I suspect it will be relatively painless, but you might want to do as Google recommends and switch part of the content first, then move over in batches, rather than all at once. You can see Matt Cutts discussing this in an Inc article recently...It's not critical, IMO, but it might save some pain in that "Google's figuring things out" timeframe.'' 

 

 

=== Product Links ===

The following is quoted from [https://bugzilla.mozilla.org/show_bug.cgi?id=606278 bug 606278] as part of a discussion about issues involving switching domains for sites that are linked to from within our products:

Same thing goes for byob.mozilla.com, as I mentioned in bug 607129. Not so much
that it's coded into Fx4, but that the domain name is part of the configuration
distributed with custom browsers.

FWIW, this is not something I see mentioned in the strategy: Existing sites are
linked to by other sites and coded into products / configurations in the wild
(ie. outside our control). Cleanly moving things may not be possible in all
cases, so we'll need some consideration around transitions.

Some sites may need to be served up at both the new and old locations, if only
with a 301 redirect at the legacy URL. However, some URLs may not be amenable
to redirects - ie. sites offering APIs like addons.mozilla.org

It's also possible that there may be some URL namespace collisions where
old/new URLs need to co-exist for an extended period of time. I can't think of
any off the top of my head, though

== Implementation ==

Once we've agreed on the plan we want to roll out these changes incrementally. Doing everything at once would be too big a project and we expect there will be things to learn about the process as we start making changes.

To follow along with the progress of things, see [https://bugzilla.mozilla.org/show_bug.cgi?id=606278 bug 606278]

==== mozilla.com domains to switch ====

The following is the list of mozilla.com domains to switch and the associated bugs.

*<strike>air.mozilla.com</strike> - [https://bugzilla.mozilla.org/show_bug.cgi?id=606326 bug 606326]

*<strike>blog.mozilla.com [https://bugzilla.mozilla.org/show_bug.cgi?id=618095 bug 618095]</strike>

*<strike>brasstacks.mozilla.com</strike>

*<strike>browserchoice.mozilla.com</strike> [https://bugzilla.mozilla.org/show_bug.cgi?id=618159 bug 618159]

*<strike>etherpad.mozilla.com</strike>

*<strike>feeds.mozilla.com</strike> - [https://bugzilla.mozilla.org/show_bug.cgi?id=613648 bug 613648]

*<strike>input.mozilla.com [https://bugzilla.mozilla.org/show_bug.cgi?id=618157 bug 618157]</strike>

*<strike>krakenbenchmark.mozilla.com</strike> - [https://bugzilla.mozilla.org/show_bug.cgi?id=613649 bug 613649]

*<strike>support.mozilla.com</strike> [https://bugzilla.mozilla.org/show_bug.cgi?id=683674 bug 683674]

*<strike>tools.mozilla.com</strike> [https://bugzilla.mozilla.org/show_bug.cgi?id=618147 bug 618147]

*<strike>www.mozilla.com</strike> - [https://bugzilla.mozilla.org/show_bug.cgi?id=610724 bug 610724]

*byob.mozilla.com - [https://bugzilla.mozilla.org/show_bug.cgi?id=607129 bug 607129]

*crash-stats.mozilla.com [https://bugzilla.mozilla.org/show_bug.cgi?id=618153 bug 618153]

*identity.mozilla.com

*metrics.mozilla.com

*services.mozilla.com

*status.mozilla.com

==== mozillalabs.com domains to switch ====

The plan here is for Labs to switch over to mozillalabs.org. They will implement and we can check in as needed.

*<strike>apps.mozillalabs.com</strike>

*<strike>design-challenge.mozillalabs.com</strike>

*<strike>jetpack.mozillalabs.com</strike>

*<strike>gaming.mozillalabs.com</strike>

*bespin.mozillalabs.com

*builder.mozillalabs.com

*heatmap.mozillalabs.com

*prism.mozillalabs.com

*testpilot.mozillalabs.com

*www.mozillalabs.com

==== mozillamessaging.com domains to switch ====

Mozilla Messaging will switch the domains and we can help as needed.

*<strike>www.mozillamessaging.com</strike> [https://bugzilla.mozilla.org/show_bug.cgi?id=666785 bug 666785]

*<strike>chat.mozillamessaging.com</strike> [https://bugzilla.mozilla.org/show_bug.cgi?id=664049 bug 664049]

*f1.mozillamessaging.com

*ispdb.mozillamessaging.com

*support.mozillamessaging.com

Websites/Taskforce/Proposals/Domain Name Strategy

2013-01-12T18:29:56Z

Nuss: /* mozillalabs.com domains to switch */

'''Domain Name Strategy'''

If you have any questions about how this document applies to any work you are doing or if you have feedback or comments or need clarification, please contact david at mozillafoundation dot org and jslater at mozilla dot com.

''This strategy applies only to websites and does not intend to cover anything to do with email addresses.''

=Working Group=

John Slater, Janet Swisher, Laura Forrest and David Boswell

=Status=

This proposal was approved at the [[Websites/Taskforce/2010_10_21|10/21/10 task force meeting]].

=Problem=

We are currently using our organizational structure as a way to set up domain
names and this is presenting irrelevant information to people and diverting our
message away from more important things, such as what we do and why we do it.

For example, the following are some of the organizational domains currently in
use:

* mozilla.com

* mozillamessaging.com

* mozilla-europe.org*

* mozillaonline.com*

* mozilla.jp*

Note that mozilla.org is not an organizational domain -- it is the community's
domain that was set up and used long before there was any Mozilla organization.
It isn't the Foundation's organizational domain -- that is mozillafoundation.org
that was in use briefly but has been retired.

''*Affiliate URLs act as both an organization site and a local site, so there is no need to move away from using those domains. The more important issue with affiliate sites is making the content as relevant as possible by de-emphasizing the organizational information and highlighting the locale specific information.''

=Solution=

To be able to stop using organizations as a basis for our domain name
strategy, we need to develop an alternative that uses something else for its structure. There seem to be two main options:

* Structure a strategy based on product/activity: firefox.com, thunderbird.com, drumbeat.org, etc.

* Structure a strategy based on everything being a part of Mozilla: www.mozilla.org, addons.mozilla.org, foo.mozilla.org

Both options have advantages and disadvantages, but they are mutually exclusive so we need to pick one (although we can certainly maintain redirects for any URLs we want).

=="One Mozilla" Strategy==

To create a "One Mozilla" strategy for domain names, we propose using sub-domains for functional areas and sub-directories for products and programs (programs in the initiative sense) with some exceptions. So:

* service.mozilla.org/sub-category

The following breaks out how this general rule applies to different types of sites.

===Product and Program Sites===

Sites related to the major activities backed by Mozilla organizations should use sub-directories on www.mozilla.org. The service being offered here is delivery of web pages (compared with delivery of a web app providing specific functionality).

Examples:

* www.mozilla.org/firefox

* www.mozilla.org/thunderbird

* www.mozilla.org/drumbeat

Note: Other community-backed projects such as seamonkey-project.org can show affiliation with Mozilla on their site in a number of other ways without having to change their URL structure.

===Web Application Sites===

Sites that exist to host services should have sub-domains based on the service offered and sub-directories based on products or programs. This is the existing addons.mozilla.org model.

Examples:

* addons.mozilla.org/firefox, addons.mozilla.org/mobile, addons.mozilla.org/thunderbird, etc.

* support.mozilla.org/firefox, support.mozilla.org/mobile, support.mozilla.org/thunderbird, etc.

* nightly.mozilla.org/firefox, nightly.mozilla.org/mobile, nightly.mozilla.org/thunderbird, etc.

For sites that provide a service for the community as a whole and not for specific programs or products, there is no need to divide things by sub-directory.

Examples:

* air.mozilla.org

* developer.mozilla.org

* feeds.mozilla.org

===Campaign Sites===

Mini-sites set up for a specific campaign should be able to use whatever URL makes sense. Because these sites are usually relevant to a specific time, an archiving plan should be put in place so this content isn't abandoned.

Examples:

* firefoxflicks.com

* opentochoice.org

* operationfirefox.com

===Local Sites===

There are two main URL styles being used today by local sites.

Examples:

* mozilla.country: mozilla.jp, mozilla.ro, etc.

* mozilla-country.org: mozilla-mexico.org, mozilla-russia.org, etc.

There are also a variety of other URLs in use such as bgzilla.org and mozilla.org.ua. It may make sense to make these more consistent, but there is no plan to do that now. On the other hand, having flexibility with local site URLs allows us to deal with issues relevant to different locales.

===Mobile Sites===

Ideally each site would have one URL which would present its content in a form optimized for any device. For complex sites though, the functionality available on mobile versions may differ greatly and switching style sheets alone may not be sufficient.

When it isn't possible to maintain a single URL for a site, we recommend adding a "m." at the beginning of the domain, such as

* m.foo.mozilla.org.

In the cases when we do choose to go with separate mobile URLs, once we take the time to do things the ideal way we can just redirect mobile URLs to their desktop equivalents for a seamless transition.

===Other Sites===

Mozilla is a big community with many people doing many things and there's no benefit to making every site fit in some structure. It is fine for some sites to have unique URLs as long as they avoid organization specific domains or trademark violations.

Examples of sites with unique URLs that are fine:

* accessfirefox.org

* geckozone.org

* mozillamemory.org

==Proposed URL Changes==

Using the principles of the "One Mozilla" strategy, we suggest the following URL changes (this is just an initial batch and not comprehensive of all possible URL changes).

{| border="1px" cellspacing="0px"
! Existing URL !! Proposed URL !! Comment
|-
| mozilla.com || www.mozilla.org/firefox ||
|-
| mozillamessaging.com || www.mozilla.org/thunderbird ||
|-
| support.mozilla.com || support.mozilla.org ||
|-
| mobile.support.mozilla.com || support.mozilla.org/mobile ||
|-
| support.mozillamessaging.com || support.mozilla.org/thunderbird ||
|-
| air.mozilla.com || air.mozilla.org ||
|-
| feeds.mozilla.com || feeds.mozilla.org ||
|-
| input.mozilla.com || input.mozilla.org ||
|}

== Technical Considerations ==

=== Localization ===

The best practices around how to use locale codes in URLs shouldn't need to be changed due to this proposal. Sites can still use the following scheme (with the example here of Mozilla Europe's German Firefox page):

* www.mozilla-europe.org/de/firefox/

The bigger issue with the l10n process is how will this proposal change how localizers determine what to work on? If sites are aggregated into fewer domains will more content need to be localized or would we create less cohesive experiences with partially localized sites?

=== Security ===

Moving from multiple unique domains to subdomains of a single domain, and in some cases subdirectories within that subdomain, will require changes to the security requirements that are imposed upon these websites. Specifically, all websites that are grouped within the same subdomain will be subject to the highest security requirements of any site within that subdomain.

In some cases this may mean that a site that was previously not hosting or performing critical operations, and thus had more lenient security controls, would be required to significantly enhance the security controls before it could be added as a subdirectory of a more security restrictive subdomain.

In addition, depending upon the criticality of a given group of websites within a subdomain this may result in a more strictly controlled security review process including requirements to review any new code before it is pushed live to the site.

=== Webtrends Tracking ===

From Webtrends - You should be fine changing over from the .com domain to the .org domain, as long as the primary domain designated in the Webtrends JavaScript tag points to what you consider the primary domain. Additionally, if you plan on having both domains concurrently available, you may want to modify the JavaScript tag to include mozilla.com at a value for the this.onsitedoms=""; entry in the JavaScript include. This would then consider all traffic from mozilla.com to be considered part of the traffic on the primary domain and would not prefix entries in reports with "Offsite:"

=== SEO Best Practices ===

SEO Best Practices When Switching Domains

Please take the following into consideration when making these switches to minimize any possible dips in natural search traffic.

Redirect Treatment (Technical Owner)

*The most important thing to avoid is 404 (file not found) errors when searchers click on Mozilla site links that show up on the search engine response page (SERP)
*Use a permanent 301 redirect to redirect the pages on the old site to the new site. This also lets Google know all the pages have officially moved. 
*Change all internal site links to point to the correct domain
*Use link checking software to find any broken links
*Submit a new sitemap to Google Webmaster Tools and Yahoo Site Submit
*Do this in phases if possible, moving one subdirectory over at a time, monitoring the results 

Incoming Links (Business Owner)

*If possible, contact the main owners of our largest incoming traffic and have them change the link (Google Snippets, YouTube, Affiliate Programs, and many more)
*Closely monitor SERP results and incoming organic search traffic for major changes

 

References http://googlewebmastercentral.blogspot.com/2008/04/best-practices-when-moving-your-site.html http://www.clickz.com/clickz/column/1699947/seo-best-practices-when-moving-web-site http://www.seomoz.org/blog/seo-guide-how-to-properly-move-domains 

Also a recent quote from Matt Cutts of Google:  

''When done correctly, a 301 redirect shouldn't cause any drop in traffic, says Matt Cutts, a Google software engineer. He says instead of moving its entire website at once, Evo would have been better off moving the site very slowly, starting with the least-trafficked areas of its website. Changing something like the structure of a site during a move can also cause problems. "If someone changes to a new template, that can affect the rankings," says Cutts. "Sometimes it takes Google a little while to figure out how best to process, index, and rank a page."'' 

And input from Rand Fishkin of SEOmoz on our particular case: 

''On the switch over - I suspect it will be relatively painless, but you might want to do as Google recommends and switch part of the content first, then move over in batches, rather than all at once. You can see Matt Cutts discussing this in an Inc article recently...It's not critical, IMO, but it might save some pain in that "Google's figuring things out" timeframe.'' 

 

 

=== Product Links ===

The following is quoted from [https://bugzilla.mozilla.org/show_bug.cgi?id=606278 bug 606278] as part of a discussion about issues involving switching domains for sites that are linked to from within our products:

Same thing goes for byob.mozilla.com, as I mentioned in bug 607129. Not so much
that it's coded into Fx4, but that the domain name is part of the configuration
distributed with custom browsers.

FWIW, this is not something I see mentioned in the strategy: Existing sites are
linked to by other sites and coded into products / configurations in the wild
(ie. outside our control). Cleanly moving things may not be possible in all
cases, so we'll need some consideration around transitions.

Some sites may need to be served up at both the new and old locations, if only
with a 301 redirect at the legacy URL. However, some URLs may not be amenable
to redirects - ie. sites offering APIs like addons.mozilla.org

It's also possible that there may be some URL namespace collisions where
old/new URLs need to co-exist for an extended period of time. I can't think of
any off the top of my head, though

== Implementation ==

Once we've agreed on the plan we want to roll out these changes incrementally. Doing everything at once would be too big a project and we expect there will be things to learn about the process as we start making changes.

To follow along with the progress of things, see [https://bugzilla.mozilla.org/show_bug.cgi?id=606278 bug 606278]

==== mozilla.com domains to switch ====

The following is the list of mozilla.com domains to switch and the associated bugs.

*<strike>krakenbenchmark.mozilla.com</strike> - [https://bugzilla.mozilla.org/show_bug.cgi?id=613649 bug 613649]

*<strike>feeds.mozilla.com</strike> - [https://bugzilla.mozilla.org/show_bug.cgi?id=613648 bug 613648]

*<strike>air.mozilla.com</strike> - [https://bugzilla.mozilla.org/show_bug.cgi?id=606326 bug 606326]

*<strike>www.mozilla.com</strike> - [https://bugzilla.mozilla.org/show_bug.cgi?id=610724 bug 610724]

*<strike>support.mozilla.com</strike> [https://bugzilla.mozilla.org/show_bug.cgi?id=683674 bug 683674]

*<strike>etherpad.mozilla.com</strike>

*<strike>blog.mozilla.com [https://bugzilla.mozilla.org/show_bug.cgi?id=618095 bug 618095]</strike>

*<strike>input.mozilla.com [https://bugzilla.mozilla.org/show_bug.cgi?id=618157 bug 618157]</strike>

*byob.mozilla.com - [https://bugzilla.mozilla.org/show_bug.cgi?id=607129 bug 607129]

*tools.mozilla.com [https://bugzilla.mozilla.org/show_bug.cgi?id=618147 bug 618147]

*crash-stats.mozilla.com [https://bugzilla.mozilla.org/show_bug.cgi?id=618153 bug 618153]

*browserchoice.mozilla.com [https://bugzilla.mozilla.org/show_bug.cgi?id=618159 bug 618159]

*identity.mozilla.com

*services.mozilla.com

*status.mozilla.com

*brasstacks.mozilla.com

*metrics.mozilla.com

==== mozillalabs.com domains to switch ====

The plan here is for Labs to switch over to mozillalabs.org. They will implement and we can check in as needed.

*<strike>apps.mozillalabs.com</strike>

*<strike>design-challenge.mozillalabs.com</strike>

*<strike>jetpack.mozillalabs.com</strike>

*<strike>gaming.mozillalabs.com</strike>

*bespin.mozillalabs.com

*builder.mozillalabs.com

*heatmap.mozillalabs.com

*prism.mozillalabs.com

*testpilot.mozillalabs.com

*www.mozillalabs.com

==== mozillamessaging.com domains to switch ====

Mozilla Messaging will switch the domains and we can help as needed.

*<strike>www.mozillamessaging.com</strike> [https://bugzilla.mozilla.org/show_bug.cgi?id=666785 bug 666785]

*<strike>chat.mozillamessaging.com</strike> [https://bugzilla.mozilla.org/show_bug.cgi?id=664049 bug 664049]

*f1.mozillamessaging.com

*ispdb.mozillamessaging.com

*support.mozillamessaging.com

Labs/Ubiquity

2012-07-22T10:58:08Z

Nuss: Removed spam - Undo revision 373125 by Ionutpop (talk)

Back to [[Labs]].

= What is Ubiquity? =

Ubiquity was a Mozilla Labs experiment that was in development from 2008 to 2009. Its purpose was to explore whether a radically different type of interface to the Web — a task-centric, natural-language-based command line — could help us get common Web tasks done faster.

Development is currently on indefinite hiatus. We will most likely revisit the experiment at some point in the future. In the meantime, the Ubiquity extension for Firefox is still available for download (see below). Also, some of the ideas from Ubiquity are being implemented in [[Labs/Jetpack|Jetpack]].

You can learn more about Ubiquity by reading Atul's blog post entitled [http://www.toolness.com/wp/?p=54 Ubiquitous Interfaces, Ubiquitous Functionality], or try it out via the [[Labs/Ubiquity/Latest Ubiquity User Tutorial|User Tutorial]].

Other informative blog posts about Ubiquity include:
# [http://www.toolness.com/wp/?p=64 Trusting Functionality] by Atul
# [http://www.azarask.in/blog/post/can-ubiquity-be-used-only-with-the-mouse/ Mouse-Based Ubiquity]
# [http://azarask.in/blog/post/sharing-streamable-functionality/ Sharing Streamable Functionality] by Aza
# [http://jonoscript.wordpress.com/2008/07/21/language-based-interfaces-part-1-the-problem/ Language-Based Interfaces, part 1: The Problem] by Jono
# [http://jonoscript.wordpress.com/2008/07/25/our-presentation-at-labs-night/ Our Presentation at Labs Night] by Jono
# [http://jonoscript.wordpress.com/2008/07/26/why-verbs/ Why Verbs?] by Jono
# [[Labs/Ubiquity/Selected Press|Selected Press]]

= Install =

== For Firefox 3.6 ==

[https://addons.mozilla.org/en-US/firefox/addon/9527 Install Ubiquity 0.1.9.1 for Firefox 3.6]

[https://bitbucket.org/satyr/ubiquity/downloads/tip.xpi Install the latest beta of Ubiquity for Firefox 3.6] - Maintained by community member Satyr

== For Older Versions of Firefox ==

[https://ubiquity.mozilla.com/xpi/ubiquity-latest.xpi Install latest version of Ubiquity for Firefox 3.5]

[https://ubiquity.mozilla.com/xpi/ubiquity-latest-beta.xpi Install the latest beta of Ubiquity for Firefox 3.5]

[https://ubiquity.mozilla.com/xpi/ Install older versions (if the current version is breaking for you)]

= Participation =
# [http://groups.google.com/group/ubiquity-firefox General Google Group/mailing list] - Useful for discussion of command development, user interface, feature suggestions, and other high-level discussions.
# [http://groups.google.com/group/ubiquity-core Core Google Group/mailing list] - Discussion of low-level internals of Ubiquity.
# [http://getsatisfaction.com/mozilla/products/mozilla_ubiquity Get Satisfaction - Ideas, Complaints, Forum, and "Customer Service"]
# [irc://irc.mozilla.org/ubiquity #ubiquity irc.mozilla.org] - Live internet relay chat discussion.
# [http://ubiquity.mozilla.com/trac/search?q=good-for-beginners Good-for-beginners bugs] - bug tickets which may be good for a Ubiquity beginner to attack
# [[Labs/Ubiquity/Frequently Encountered Bugs|Frequently Encountered Bugs]] - bugs that get reported a lot on the [http://groups.google.com/group/ubiquity-firefox mailing list] and [http://getsatisfaction.com/mozilla/products/mozilla_ubiquity Get Satisfaction] that would make lots of people happy if they got fixed
# [[Labs/Ubiquity/Commands In The Wild|Commands In The Wild]] Add links to your commands here.
# [https://ubiquity.mozilla.com/trac/report/1 Issue Tracker] - Used to report/discuss bugs and submit patches for Ubiquity.
# [[Labs/Ubiquity/Trac Components and Keywords|Trac Components and Keywords]] - Keywords and categories to use when filing Trac tickets.
# [https://ubiquity.mozilla.com/hg/ubiquity-firefox/ Ubiquity HG Repository] - The Mercurial source code repository for Ubiquity.
# [http://ubiquity.mozilla.com/buildbot/ Buildbot] - Continuous integration that runs Ubiquity unit tests after every commit. If the tests fail, they're reported immediately to the mailing list.
# [[Labs/Ubiquity/Credits|Credits]]

= Meetings =

* [[Labs/Ubiquity/Meetings|Meeting notes & times]]

= Documentation =
# [[Labs/Ubiquity/Latest Ubiquity User Tutorial|Ubiquity User Tutorial]]
# The latest [[Labs/Ubiquity/Ubiquity_Source_Tip_Author_Tutorial|Command Authoring Tutorial]] (for command authors using a Ubiquity source checkout); or the frozen [[Labs/Ubiquity/Ubiquity 0.5_Author_Tutorial|Ubiquity 0.5 Command Authoring Tutorial]] for those using version 0.5 of the extension.
# [[Labs/Ubiquity/Parser_2_API_Conversion_Tutorial|Command Update Tutorial]] for how to take a command written for Ubiquity 0.1 and make it work in Ubiquity 0.5.
# [[Labs/Ubiquity/Locked-Down_Feed_Tutorial|Locked-Down Feed Tutorial]]
# [[Labs/Ubiquity/Secure_Coding_Practices|Secure Coding Practices]]
# [[Labs/Ubiquity/Skins_v0.5|Skinning Ubiquity Tutorial]]
# [https://ubiquity.mozilla.com/hg/ubiquity-firefox/raw-file/tip/ubiquity/index.html Ubiquity Code Documentation] - Generated from the latest source code via [http://code.google.com/p/code-illuminated Code Illuminated].
# [[Labs/Ubiquity/Ubiquity 0.1_Development_Tutorial|Contributing to Core Development]]
# [[Labs/Ubiquity/Parser_2/Localization_Tutorial|Localizing Ubiquity to Your Language]]
# [[Labs/Ubiquity/Ubiquity_0.5_Command_Localization_Tutorial|Localizing Commands to Your Language]]
# [[Labs/Ubiquity/Ubiquity 0.1_Nountypes_Reference|Noun-types Reference]]
# [[Labs/Ubiquity/Bundled Libraries|Bundled libraries]]
# [[Labs/Ubiquity/jQuery in Ubiquity|Using jQuery in Ubiquity]]
# [https://developer.mozilla.org/en/JavaScript_style_guide JavaScript style guide]
# [[Labs/Ubiquity/Ubiquity_0.1.3_Architecture|Ubiquity 0.1.3 Architecture]]
# [[Labs/Ubiquity/Parser_Documentation]]
# [[Labs/Ubiquity/Parser_Interface]]
# [[Labs/Ubiquity/0.5_Documentation|Help Document the 0.5 code here]] - working copies of the wiki documentation for the latest source version
# [[Labs/Ubiquity/Command_Documentation_Workspace|Help us improve the built-in command documentation by editing this page]]
# [[Labs/Ubiquity/Interactive_Tutorial_Workspace|Help us improve the interactive tutorial by editing this page]]

= Blogs =

# [http://ubiquity.mozilla.com/planet Planet Ubiquity]
# [http://www.azarask.in/blog/ Aza]
# [http://www.toolness.com/ Atul]
# [http://blog.reybango.com/ Rey]
# [http://jonoscript.wordpress.com/ Jono]
# [http://abcdefu.wordpress.com/ Abi]
# [http://theunfocused.net/ Blair]
# [http://www.indolering.com/indolering.com/Ubiquity_Blog/Ubiquity_Blog.html Zach]
# [http://mitcho.com/blog/ mitcho] (see also his [[User:Mitcho/ResearchTopics|future topics to blog on]])
# [http://www.betsomesports.com Bet]
# [http://www.free-bets.ro/ Pariuri]
# [http://geeksbynature.dk cers]

= Twitter =
# [http://twitter.com/mozillaubiquity @mozillaubiquity]: The main source of news & info about the Ubiquity project via Twitter. Be sure to follow.
# [http://twitter.com/azaaza @azaaza]: Mozilla's co-lead developer for the Ubiquity project
# [http://twitter.com/toolness @toolness]: Mozilla's co-lead developer for the Ubiquity project
# [http://twitter.com/reybango @reybango]: Evangelist for the Ubiquity project
# [http://twitter.com/theunfocused @theunfocused]: Fellow Mozillian Blair McBride
# [http://twitter.com/_abi_ @_abi_]: Created the Devo Firefox extension which provided a keyboard command launcher similar to what Ubiquity is today.
# [http://twitter.com/fernando_takai @fernando_takai]: Major supporter of Ubiquity.
# [http://twitter.com/mitchoyoshitaka @mitchoyoshitaka]: Resident linguist
# [http://twitter.com/bpung @bpung]: Mozilla labs intern, developer for Ubiquity
# [http://twitter.com/ChristianSonne @ChristianSonne]: Developer for Ubiquity

= The Herd =
The Herd keeps track of all Ubiquity scripts. For more information, see the following links:
# [http://ubiquity.mozilla.com/hg/ubiquity-site/ Herd HG Repository]
# [http://ubiquity.mozilla.com/hg/ubiquity-site/file/tip/README Herd Developer FAQ]
# [http://wiki.apache.org/couchdb/HttpViewApi CouchDB] - database used for Herd
# [https://ubiquity.mozilla.com/herd/ The Herd]-The Herd Itself.

= Proposals =

# [[Labs/Ubiquity/Roadmap|Ubiquity Roadmap]] - from 0.5 to 1.0
# [[Labs/Ubiquity/Ubiquity Command Suggestions|Command Suggestions]] - use this page to suggest new Ubiquity commands you'd like to see.
# [[Labs/Ubiquity/Nouns | Proposals for New Nouns]]
# [[Labs/Ubiquity/Magic_Words | Proposals for new "Magic Words"]]
# [[Labs/Ubiquity/Ubiquity_Commands_Center | Ubiquity Commands Center]] - an idea for a web-panel that maintains a database of Ubiquity scripts.
# [[Labs/Ubiquity/TrustNetwork | Ubiquity Trust Network]] - a proposal for a distributed trust network
# [[Labs/Ubiquity/Thunderbird | Ubiquity In Thunderbird]] - let's make Ubiquity work in Thunderbird!
# [[Labs/Ubiquity/0.2 Roadmap Proposals | 0.2 Roadmap Proposals]] - Brainstorming on possible directions to go for Ubiquity 0.2.
# [[Labs/Ubiquity/0.2 Design: UI and Security Extensibility|0.2 Design: UI and Security Extensibility]] - Design-related thoughts on how to make Ubiquity extensible in regards to security/command-execution and access by other Firefox UIs.
# [[Labs/Ubiquity/0.2 Proposed Uplift Commands| Proposed commands for uplift into Ubiquity 0.2]]
# [http://mitcho.com/blog/projects/writing-commands-with-semantic-roles/ Writing commands with semantic roles] - would enable commands to be automagically localized
# [[Labs/Ubiquity/The Great Renaming|The Great Renaming]] -- proposal for renaming all built-in commands for consistency and to work with the Overlord Verbs system.

= Internationalization and Localization =

# [[Labs/Ubiquity/i18n|internationalization and localization pages]]
# [http://groups.google.com/group/ubiquity-i18n Ubiquity i18n Google Group/mailing list] for discussion of internationalization and localization topics
# [[Labs/Ubiquity/Ubiquity_0.5_Command_Localization_Tutorial|Command Localization Tutorial]] for how to translate commands to your language

= Release Notes =
# [[Labs/Ubiquity/Ubiquity_0.5.4_Release_Notes|Ubiquity 0.5.4 Release Notes]]
# [[Labs/Ubiquity/Ubiquity_0.5.3_Release_Notes|Ubiquity 0.5.3 Release Notes]]
# [[Labs/Ubiquity/Ubiquity_0.5.2_Release_Notes|Ubiquity 0.5.2 Release Notes]]
# [[Labs/Ubiquity/Ubiquity_0.5.1_Release_Notes|Ubiquity 0.5.1 Release Notes]]
# [[Labs/Ubiquity/Ubiquity_0.5_Release_Notes|Ubiquity 0.5 Release Notes]]
# [[Labs/Ubiquity/Ubiquity_0.1.9_Release_Notes|Ubiquity 0.1.9 Release Notes]]
# [[Labs/Ubiquity/Ubiquity_0.1.8_Release_Notes|Ubiquity 0.1.8 Release Notes]]
# [[Labs/Ubiquity/Ubiquity_0.1.7_Release_Notes|Ubiquity 0.1.7 Release Notes]]
# [[Labs/Ubiquity/Ubiquity_0.1.6_Release_Notes|Ubiquity 0.1.6 Release Notes]]
# [[Labs/Ubiquity/Ubiquity_0.1.5_Release_Notes|Ubiquity 0.1.5 Release Notes]]
# [[Labs/Ubiquity/Ubiquity 0.1.3 Release Notes|Ubiquity 0.1.3 Release Notes]]
# [[Labs/Ubiquity/Ubiquity 0.1.2 Release Notes (Raging Stream)|Ubiquity 0.1.2 Release Notes]]
# [[Labs/Ubiquity/Ubiquity 0.1.1 Release Notes|Ubiquity 0.1.1 Release Notes]]

Labs/Jetpack/Weekly Meeting/2011-10-18

2012-07-22T10:54:12Z

Nuss: Removed spam

= Agenda =
* FlightDeck
* SDK
** 1.2 Release today!
** Need to replace translate docs examples, brain-storming etherpad: https://jetpack.etherpad.mozilla.org/replace-gtranslate-example
* Bugs
* Roundtable
** (dcm) Our goals have to change thanks to Mobile UI shift:
***Goals for end of Q4
l10n - Build an API that allows devs to localize js strings
l10n - Have a plan for localizing html files
e10s - Build a prototype SDK that supports content processes on desktop
e10s - Build a prototype SDK that can build add-ons that run in their own process
mobile - Build a prototype SDK that can build add-ons that use non-UI based features for Fennec
** SDK Hack Day update

= Attendees =

* canuckistani
* dcm
* mossop
* kwierso
* warner
* myk
* gozala
* ochameau
* wbamberg
* ejpbruel
* dhorner
* krizsa
* zalewa
* dbuc
* arron
* jorge

= Minutes =

== SDK 1.2 ==

* dcm: SDK 1.2 to be released today!

* Jeff: need to replace Google Translate example by December 1
* have some ideas, have etherpad for brainstorming
* https://jetpack.etherpad.mozilla.org/replace-gtranslate-example
* dcm: ask forum for ideas

* myk: saw references to addon.mozilla.org, but current docs are at addons.mozilla.org
* want to make sure docs expect to be at correct URL
* wbamberg: some references to one, some to the other
* but docs correctly expect to be at addons.mozilla.org

== FlightDeck ==

* dbuc: repacker changes pushing to production on Wednesday
* new SDK will be made available once it is released today
* frontend and backend changes happening (new template system)
* search template being redone

* would like to meet this week to discuss docs and hosting examples
* -> wbamberg to set up meeting

== Roundtable ==

* dcm: mobile team deciding to switch to native ui on android
* this impacts timeline
* adjusted Q4 goals for team
* mobile goal at risk
* other stuff we should be able to do by end of quarter

* ejpbruel: does this mean e10s work is only relevant on desktop for now?
* all: yes
* ejpbruel: potential opportunity to do platform work on new native interface?
* dcm: probably best discussed with mossop

* myk: keep in mind that a future version of android will have better support for multi-process
* and current android has support for multi-thread, which we could take advantage of
* dbuc: android 4 announced soon, should have support for multi-process

* canuckistani: hack day venue has changed
* r2d2/c3po not available (mobile war room), we're going to do it in 10forward
* single track instead of dual track
* room booked, catering booked

* canuckistani: how do developers test on mobile fennec?
* ...

* ochameau: update on mozcamp?
* canuckistani: we're doing a talk
* dcm: canuckistani got arky to give talk at kuala lumpur mozcamp
* canuckistani: he'll also be in berlin and is localization coordinator for southeast asia region

* ochameau: any plan to simplify xpis? would be useful for uploading xpis to localization service
* warner: i think we should do it; i'll help
* ochameau: any particular simplifications in mind?
* warner: general idea is to have only one resource protocol mapping and break the directory whose name has several components (like the package name) into individual directories
* ochameau: i have a patch that does some simplification
* gozala: my "no runtime search" patch depends on it
* ochameaeu: i'll keep in touch with daniel to make sure repacks continue to work

* dcm: we decided to do repacks for all addons again for 1.2, as we did for 1.1
* partly because we don't yet have way of distinguishing between Builder and local addons
* will also allow people to digest our change to not do repacks for local addons
* dcm: also myk says we might not need to repack for 1.3

* myk: yes, 1.2 currently passes tests on aurora, central branches
* which means compatibility with firefox 9, 10
* 10 compatibility can change nightly, but 9 compatibility is less likely to change
* and if we make it through aurora period, it probably won't change

* dbuc: we have a flag in AMO to identify addons that shouldn't be updated
* we could expose this better to developers and let them decide
* gozala: what about the addon that checked that box and got repacked anyway?
* dbuc: yes, the flag wasn't being respected but will be

Grendel

2012-07-22T10:52:59Z

Nuss: Removed spam - Undo revision 398139 by Ionutpop (talk)

{{Grendel}}
Maintained by [mailto:rj.keller@beonex.com R.J. Keller] and [mailto:kieran@eternal.undonet.com Kieran Maclean] 
May 4, 2005  

You may recall that in 1997, Netscape embarked on a project to rewrite Navigator/Communicator in Java. This project (code named "Xena," but sometimes referred to by the press as "Javagator") was cancelled before completion.

Grendel is the mail-news portion of the Xena project written in Java. Its goal is to be a true cross-platform application with a feature set that satisfies the poweruser.

==News==

'''Grendel project restarted''' 
Grendel project has been restarted. The new Grendel will feature better toolbar icons, ant compilation, and the new wiki site!!! Feedback on what you'd like to see would be appreciated! Post any Grendel feedback to netscape.public.mozilla.mail-news or feel free to email [mailto:rj.keller@beonex.com R.J. Keller] with any feedback.

==History==

Grendel was originally developed as a part of the "Javagator" project at Netscape. This project was cancelled before completion after 3 years of development. After the source for Grendel was released other people started to work toward completing it for about another 2 years. The [http://www.mozilla.org/projects/grendel/announce.html original release] was therefore incomplete.

==Current state==

Lots of changes were recently checked into the Grendel source tree to make it compile in a modern Java compiler. The new Grendel tree will currently require Java 1.5 to run and require a new set of libraries.

The build system is currently being redone to use [http://ant.apache.org Apache Ant] instead of Makefiles. The easiest way to compile Grendel in its current state is to grab a copy of [http://www.jcreator.com JCreator] and create a Grendel project in the directory and compile it. A lot of test files are currently being separated out into different directories so if a certain file isn't compiling nicely, it's probably because it's a broken test file that can be deleted from your tree safely.

We're also in the process of moving Grendel from its own XML format to a Mozilla-friendly XUL format using the [http://mozcreator.mozdev.org/xulParser.html MozCreator Java XUL Parser API]. We'd also like to contain all resources into one easy to manage resource folder instead of dumping them all over the source tree.

The [[Grendel:Development|Development Document]] gives further details on the current state and future plans.

==Community==

Discussion takes place in the newsgroup [news://news.mozilla.org/netscape.public.mozilla.mail-news netscape.public.mozilla.mail-news]. This newsgroup is also gatewayed to a mailing list. More information can be found on [http://www.mozilla.org/community/developer-forums.html Mozilla's Development Forum pages].

There is also a channel for Grendel developers on mozilla's IRC server [irc://irc.mozilla.org/grendel]

==Tools==
To aid the development all mozilla.org tools are available for Grendel hackers:

# CVS - Grendel is a module on its own inside the mozilla CVS repository. More information is on the [http://developer.mozilla.org/en/docs/Mozilla_Source_Code_Via_CVS CVS page].
# [http://lxr.mozilla.org/mozilla/ LXR] is a great tool to browse the source
# [http://bonsai.mozilla.org/cvsqueryform.cgi?cvsroot=/cvsroot&module=Grendel Bonsai] is the tree control tool which can be used to track the changes to the tree. An interesting query is this one, which shows all checkins to Grendel during the last week.
# [http://bugzilla.mozilla.org/ Bugzilla] keeps track of all bugs in Grendel and who is working on them.

==Why have Grendel when we have Thunderbird?==

A primary goal with Grendel is restoring the libraries contained in the email client to full state as well as providing a working email program. Having a Java port of many of the Mozilla libraries from C++ to Java would be very valuable to many projects. The code has a lot of potential and having the Mozilla platform available for Java programmers can be a invaluable resource for Java programmers wishing to utilize email features easily. Its Java design eliminates some of the problems of a C++ design like Thunderbird. For example, Java has garbage collection and no restriction of language features in order to maintain cross-platform compatibility (like with C++ and lack of feature usage like templates for compatibility).

==Contributions==

We need Java programmers badly! Send email to [mailto:rj.keller@beonex.com R.J. Keller] if you're interested and we'll help you get set up! Contributing to Grendel can be an exciting and rewarding experience so I encourage you to contribute. It can be worthwhile.

Session Restore

2012-07-22T10:52:05Z

Nuss: Revoved spam

''Please comment in the Talk page (use the Discussion tab above)''

= Goals & Objectives =

After a forced restart, restore the user's workspace exactly as it was.

= Overview =

The state of various window, tab and user-data will be saved, and reloaded upon application start. The feature will be passive, reacting only to forced-restarts such as extension installation and crashes. This minimal implementation provides an unobtrusive user-experience while meeting the broadest use-cases. The API will provide a stable and intuitive base which power-user oriented extensions, or expanded features in future releases, can build upon.

= Features =

* Save data for each window and tab (P1)
* Automatically restore the session data upon restarting from a forced closure (P1)
* If post-crash, allow the user to choose whether to restore (P1)
* Allow the user to "undo" closing a tab or window (P2)

= UI =

* Prompt for restore upon application start, post-crash.
<center>
http://static.flickr.com/51/143165490_72557bc74c.jpg
</center>

= Usage and Configuration =

The default settings will restore the session after a crash and previous history will be restored to a certain point.

== Preferences ==

See [http://mxr.mozilla.org/mozilla-central/source/browser/app/profile/firefox.js#750 the source] for currently available settings and their default values.

* browser.sessionstore.enabled (bool) - Activate the service. Default is true. May not appear in about:config until changed. Valid for Firefox 2 and 3, superseded since Version 3.5.
* browser.sessionstore.interval (integer) - minimal interval between saving operations in milliseconds. Default is 10000.
* browser.sessionstore.max_resumed_crashes (integer) - Number of crashes that can occur before the about:sessionrestore page is displayed. Default is 1. So the user is asked after the second crash which pages he wants to restore.
* browser.sessionstore.resume_from_crash (bool) - Resume sessions post-crash. Default is true.
* browser.sessionstore.resume_session_once (bool) - Resume session at the next application start, but not again. Default is false. This is used for restarting the browser after application updates and extension installation.
* browser.startup.page (int) - What is displayed when Browser starts: 0 = blank page; 1 = homepage; 3 = previous session. Default is 1. (Note: Firefox exposes this preference in the Startup section of the Main pane of the Options/Preferences dialog.)

= Technical Design =

== Implementation ==

The feature is implemented as an XPCOM service. It registers for events such as windows and tab open/close, collects the current state of the browser, and periodically writes that state to disk.

* Code location: http://lxr.mozilla.org/seamonkey/source/browser/components/sessionstore/
* Data location: File sessionstore.js in profile directory, backup in sessionstore.bak

== Data to be saved ==

* All open windows and tabs
* Width, height, and position of each window
* Scroll position within each scrollable area in each window
* Tab histories
* Cookies
* Text typed in forms
* Restart downloads

== API ==

The API should allow session information to be easily accessed by extensions. An extension could store session info on a remote server, and allow users to restore the same session from multiple computers. This is currently a feature of the SessionSaver extension that doesn't really fit into the core browser.

The API details and discussion are at [[SessionRestoreAPI]].

= Privacy =

Currently, the saved session data is cleared at shutdown, except in scenarios where the feature has been directed to intentionally save it, which are:

* The application crashed
* A forced restart, such as extension install or application update
* The user has chosen to always resume sessions

The saved session data is also cleared upon receiving the "browser:purge-session-history" notification.

The data is stored on disk as a serialized javascript data structure (though it's possible that it will be converted to JSON once that becomes natively supported by Gecko/Spidermonkey). An open question is to whether this should be encrypted in some manner. See the Discussion page for more ideas about this.

= To-do =

* Implement undo close window
* Implement user saving/loading of sessions
* Can we use FastBack data to speed up undo close tab/window?

= Unresolved Questions =

* Storing cookies: Is it okay to persist cookies that are supposed to expire when the session ends? What about SSL cookies?

* If we store cookies, should they also be stored when the user manually saves a session?

* GET URLs: Bad things can happen if we reload a URL with a GET request that has side-effects. This has definitely been a problem for Google Web Accelerator.

* <s>Do we ever want to store cached copies of the pages (i.e. for offline access) or do we just store the URLs and load them all? Loading from cache would be snappier. If any caching is done, should obey whatever caching directives.</s> - Pages are currently pulled from the browser cache, if available.

* <s>Make sure that if the state of the current session crashes the browser, it doesn't reload at startup and crash over and over again. Look into how SessionSaver and Total Recall detect this.</s> - If the previous session crashed, the user is prompted with a choice as to whether to reload it.

* If there are multiple windows open, how do we decide what was the last session? The last window closed, or the last group of windows?

* Should form state include saving checkbox and selectbox state as well as text input?

= User-friendly documentation =

See this Knowledge Base entry: http://support.mozilla.com/en-US/kb/Session+Restore

== Relevant Bugs ==

Current implementation:

* [https://bugzilla.mozilla.org/show_bug.cgi?id=356050 bz356050]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=328154 bz328154] - Tracking bug for feature inclusion in Fx2
* [https://bugzilla.mozilla.org/show_bug.cgi?id=343876 Session restore when all last sessions tabs were closed should obey user homepage choice for the initial blank tab]
Older:

* [https://bugzilla.mozilla.org/show_bug.cgi?id=19454 bz19454]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=36810 bz36810]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=63094 bz63094]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=159357 bz159357]

== Relevant Extensions==

* MultiZilla's Tab Session Manager
** http://multizilla.mozdev.org/features/session-manager.html
* Session-Saver
** http://forums.mozillazine.org/viewtopic.php?t=47184
** http://kb.mozillazine.org/SessionSaver
* [http://tmp.garyr.net/ Tab Mix Plus]
* [http://forums.mozillazine.org/viewtopic.php?t=164513 Crash Recovery] / [http://forums.mozillazine.org/viewtopic.php?t=380534 Session Manager]
* [http://recall.mozdev.org/ Total Recall]

= Other Features =

Some features that should be either P2, FF3 or left to extensions:

* Allow the user to �save�? a particular session at any time, and load saved sessions either by default at startup or from a menu
* Allow the user to choose which pages to restore, post-crash

Mozilla.org/How to Work with Site

2012-07-22T10:49:53Z

Nuss: Revoved spam – Undo revision 437059 by Ionutpop (talk)

Docs for people getting involved with site.

= Asking Questions =

The best way to learn about how to work with the www.mozilla.org site is to ask questions. Community members are happy to help, but it can be difficult to know who to talk to. Here are a few good places to go with questions:

Email: [http://groups.google.com/group/mozilla.dev.mozilla-org/ mozilla.dev.mozilla-org]

Chat: [irc://irc.mozilla.org/siteplanning #siteplanning on irc.mozilla.org]

Phone: [[Mozilla.org:Planning#Planning_Meetings|Monthly planning meetings]]

= Bugzilla =

We use [http://bugzilla.mozilla.org Bugzilla] to track bugs as well as enhancements to the site, so we recommend that you get familiar with this tool. You can look through bugs without a [https://bugzilla.mozilla.org/createaccount.cgi Bugzilla account], but you will need one to update an existing bug or open a new one. Please feel free to look through open bugs, comment in a bug, submit a patch or assign a bug to yourself.

*[https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&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&bug_status=REOPENED&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= All open www.mozilla.org bugs]

*[https://bugzilla.mozilla.org/enter_bug.cgi?product=Websites;component=www.mozilla.org Enter a new bug]

= Viewing The Source =

The site uses a templating system to add the header, side navigation and footer to all of the pages. If you view the source of a page through your browser you are seeing the results of merging a page with a template. To see what the HTML files look like before they are merged, you can look at the files in our Subversion repository at:

*http://viewvc.svn.mozilla.org/vc/projects/mozilla.org/trunk/

Our repository is open, so feel free to look around at different files to see how things are put together.

= Making Site Changes =

There are several ways to edit the site and you are welcome to pick the option that works best for you.

''Note: Most pages on the site are static HTML and can be edited directly, although there are some dynamic and [[Mozilla.org/Generated pages|generated pages]] that are not straight forward to edit. Feel free to [[Mozilla.org#Contact_Us|contact us]] with questions about any specific page.''

== Submitting Patches ==

The easiest way to make a change is to work with someone who already has access to edit the site. You can send them the change in a variety of formats. Attaching a [https://developer.mozilla.org/En/Creating_a_patch patch] to a bug is the most common way to do that, but it is also possible to simply email a change to someone. How changes are submitted will vary on your technical experience and on who you are working with.

== Using Bespin (Web-based Editor) ==

We will soon have a web-based editor available for the site. Our goal is to embed [https://bespin.mozilla.com/ Bespin] to make it easy for people to edit pages. When this is available, we'll post more information here about how to use it.

== Using Subversion ==

The files for the site are kept in version control using the Subversion tool. You can edit the site by checking out these files, editing them on your computer and then checking them back in.

The following provides information specifically about Subversion for www.mozilla.org. General information about [[SVN|Mozilla's Subversion server]] is also available.

=== Repository ===
'''Note: mozilla.org is setup differently that most Mozilla web properties''', so read this section closely before committing any code.

Both stage and production '''auto-update from svn'''. Their is no traditional deployment process, so be careful.

Work locally, test in the stage branch, before merging to trunk (live).

==== Stage ====
Location of repository: http://svn.mozilla.org/projects/mozilla.org/branches/staging/

==== Production ====
Location of repository: http://svn.mozilla.org/projects/mozilla.org/trunk/

=== Authentication ===

Access to the repository is based on either your LDAP account or on an SSH key. People have reported problems trying to use SVN+SSH though, so LDAP authentication is the recommended option (the commands below are based on LDAP authentication).

If you need an SVN account or if you have one and need permission to edit the www.mozilla.org files, please [https://bugzilla.mozilla.org/enter_bug.cgi?product=mozilla.org;component=Server%20Operations file a bug] to request access. For people without existing Mozilla commit rights, please follow the process described in [http://www.mozilla.org/hacking/committer/ becoming a committer].

=== Commands ===

To check out repository (''note the use of the S in https://''):

<code>svn co https://svn.mozilla.org/projects/mozilla.org/trunk</code>

Check-in an edit to a page:

<code>svn ci -m "Comment goes here" foo.html</code>

= Staging Site =

If you'd like to look at your changes before committing them to the live site, there are a couple of options—viewing things on our staging site or viewing them locally.

There is a staging site available at http://www-stage.mozilla.org. However, this isn't the best place to work on changes since the site is set up just to automatically pass on changes to the live site (this gives you a chance to check on things after committing a change to the repository).

Another staging option is to run a version of the site locally based on the files checked out from the repository. This set-up for your computer is documented below (''note that we could use some help with making these instructions more user-friendly''):

== Localhost Site Setup ==

The following directions will show you how to setup a version of MozWeb ([http://mozilla.org mozilla.org]) on your local machine under the domain name [http://mozilla.dev mozilla.dev]

'''Note:''' ''Once you are done with this guide, [http://mozilla.dev mozilla.dev] should link to your local instance of MozWeb''.

=== [[MAC OSX Setup]] ===

This setup was conducted on an Intel Mac running OS X 10.5.8 which was the latest version of Leopard at the time of this writing. 10.6 (Snow Leopard) has just come out but, this setup has not been tested on Snow Leopard.

''If people could test the setup and give feedback for the setup on OS X 10.4+ (Tiger) and 10.6 (Snow Leopard)''

=== Setup for Other Platforms ===

==== TODO: More Guides ====

More guides are coming for Windows and Ubuntu to help developers get up and running on hacking Mozweb.

==== Ubuntu ====

* Do 1, 2 and optionally 3 from the instructions below
* You need php5 and php5-curl installed ("sudo apt-get install php5 php5-curl")
* You need to enable the "Actions" Apache module ("a2enmod actions")
* You need to add "mozilla.dev" to the 127.0.0.1 line in /etc/hosts
* You need a file in /etc/apache2/sites-enabled with the following contents:

<VirtualHost mozilla.dev:80>
ServerName mozilla.dev
DocumentRoot /path/to/your/checkout
AddType application/x-httpd-php .php .html
DirectoryIndex index.php index.html
Options -Indexes

RewriteEngine On
RewriteMap toupper int:toupper
</VirtualHost>

==== Generic Setup ====

1) Check out [http://svn.mozilla.org/projects/mozilla.org/trunk/ trunk] somewhere

2) Copy [http://svn.mozilla.org/projects/mozilla.org/trunk/includes/config.inc.php-dist includes/config.inc.php-dist] to includes/config.inc.php and edit appropriately

3) Add cronjob for front-page feed parser. Example would be:

<code>*/10 * * * * root cd /data/www/www.mozilla.org/includes/; ./feed-parser.php -c ./feed-parser-config.xml</code>

4) Add Apache vhost for site (example vhost is in [http://svn.mozilla.org/projects/mozilla.org/trunk/README README])

In the future we may change how staging works, but [[Mozilla.org#Contact_Us|let us know]] if you have any questions about this current setup.

= Style Guides and References =

Once you're able to make changes to the site, please take a look at the following pages that offer suggestions about writing and coding. Since the site is edited by a range of people across the community, following some guidelines will help maintain a consistent experience for users.

*[http://www.mozilla.org/contribute/writing/guidelines.html mozilla.org Documentation Style Guide]
*[http://www.mozilla.org/contribute/writing/markup.html mozilla.org Markup Reference]
*Design style guide (coming soon)

Websites/Taskforce/Proposals

2012-07-11T22:38:10Z

Nuss:

This page lists the various proposals made to the web site task force and their current status.

''Note: Please feel free to add additional proposals for discussion at future meetings. You can copy the [[Websites/Taskforce/Proposals/Template|Proposal Template]] as a starting place.''

{| class="wikitable"
|-
! Proposal
! Proposed by
! Status
|-
| [https://wiki.mozilla.org/Websites/Taskforce/Proposals/Retirement_Strategy Website Retirement Strategy]
| Chrissie Brodigan
| Pending Presentation
|-
| [[Websites/Taskforce/Proposals/Domain Name Strategy|Domain Name Strategy]]
| John, Janet and David
| Approved at [[Websites/Taskforce/2010 10 21|10/21/10 meeting]], Implementation in progress
|-
| [[Websites/Taskforce/Proposals/Abandoned Sites|Abandoned Sites]]
| Ryan, David, Frederic, Mike, Chris and Steve
| Approved at [[Websites/Taskforce/2010 11 18|11/18/10 meeting]], Implementation in progress
|-
| [[Websites/Taskforce/Proposals/End of Life|Website End of Life Process]]
| Ryan
| Approved at [[Websites/Taskforce/2011 06 02|06/02/11 meeting]]
|-
| [[Websites/Taskforce/Proposals/Site Checklist|Site Checklist]]
| FuzzyFox, David, Stephen Donner
| Living Document
|-
| [[Websites/Taskforce/Proposals/Documenting Ownership|Documenting Ownership]]
| Ryan
| Living Document
|-
| [[Websites/Taskforce/Proposals/Web Fonts|Web Fonts]]
| Ned, John, Sean and David
| Draft
|-
| [[Websites/Taskforce/Proposals/Universal tab|Universal Tab]]
| Sean Martell, David, John, Potch
| Implementation in progress
|-
| [[Websites/Taskforce/Proposals/Common Color Palette|Common Color Palette]]
| [[User:Nuss|Nuss]]
| Draft
|-
| [[Websites/Taskforce/Proposals/Typefaces for Body Text|Typefaces for Body Text]]
| [[User:Nuss|Nuss]]
| Draft
|-
| [[Websites/Taskforce/Proposals/Common Licensing|Common Licensing]]
| Ken, Liz, David
| Draft
|-
| [[Websites/Taskforce/Proposals/Universal Subtitles|Universal Subtitles Deployment]]
| Dean and David
| Draft
|-
| [[Websites/Taskforce/Proposals/Common Footer|Common Footer]]
| Julie, Liz, FuzzyFox and David
| Draft
|-
| [[Websites/Taskforce/Proposals/CSS Framework|CSS Framework]]
| [[User:Theinterned|Ned Schwartz]], David
| Concept
|-
| [[Websites/Taskforce/Proposals/Official communities badges|Official community badges]]
| Milos, David
| Concept
|}

[[Category:Webdev/Taskforce|Proposals]]

Websites/Taskforce/Proposals/Abandoned Sites/2012

2012-07-11T22:36:10Z

Nuss:

[[Category:Webdev/Taskforce/Abandoned Sites|2012]]

The following is a list of websites that have been nominated for retirement, have been retired or are in the process of being retired.

= Meetings =

= Nominated Sites =
* http://byob.mozilla.com/
* http://www.discovershiretoko.org
* http://download-cdnetworks.mozilla.net/
* http://download-speed-test.mozilla.net/
* http://dromaeo.com/
* http://eklentiler.mozillazine-tr.org
* http://extendfirefox.com/
* http://filer.mozilladanmark.dk/
* http://virtualpark.mozilla.org/

= Websites in Process of Retirement =

* [http://doctor.mozilla.org doctor.mozilla.org]
** Bug:

* [http://spark.mozilla.org spark.mozilla.org] - Spark
** {{bug|636785}}

* [http://userpanel.mozilla.com userpanel.mozilla.com]
** Bug: -

* [http://webtools.mozilla.org webtools.mozilla.org]
** Bug: -

= Retired Websites =

* [http://guides.mozilla.org guides.mozilla.org]
** Status: COMPLETED
** Decision: Retire, point to WikiMO
** Retirement Date: 2012-01-04
** {{bug|663711}} and {{bug|663712}}

* [http://www.mozilla24.com mozilla24.com], [http://www.firefoxccstudio.org firefoxccstudio.org], [http://www.firefoxfestival.com firefoxfestival.com]
** Status: COMPLETED?
** Decision: Redirect to http://www.mozilla.jp/events/2007/mozilla24/
** Retirement Date: Spring/summer 2012
** Bug ?

* [http://events.mozilla-europe.org events.mozilla-europe.org]
** Status: COMPLETED
** Decision: Redirect to WikiMO
** Retirement Date: Spring/summer 2012
** Bug ?

* [http://designchallenges.org/ designchallenges.org]
** Status: COMPLETED
** Decision: Redirect to WikiMO
** Retirement Date: 2012-06-06
** {{bug|760622}}

Websites/Taskforce/Proposals/Abandoned Sites/2012

2012-07-11T22:22:39Z

Nuss:

[[Category:Webdev/Taskforce/Abandoned Sites|2012]]

The following is a list of websites that have been nominated for retirement, have been retired or are in the process of being retired.

= Meetings =

= Nominated Sites =
* http://www.discovershiretoko.org
* http://download-cdnetworks.mozilla.net/
* http://download-speed-test.mozilla.net/
* http://dromaeo.com/
* http://eklentiler.mozillazine-tr.org
* http://extendfirefox.com/
* http://filer.mozilladanmark.dk/
* http://virtualpark.mozilla.org/

= Websites in Process of Retirement =

* [http://doctor.mozilla.org doctor.mozilla.org]
** Bug:

* [http://spark.mozilla.org spark.mozilla.org] - Spark
** {{bug|636785}}

* [http://userpanel.mozilla.com userpanel.mozilla.com]
** Bug: -

* [http://webtools.mozilla.org webtools.mozilla.org]
** Bug: -

= Retired Websites =

* [http://guides.mozilla.org guides.mozilla.org]
** Status: COMPLETED
** Decision: Retire, point to WikiMO
** Retirement Date: 2012-01-04
** {{bug|663711}} and {{bug|663712}}

* [http://www.mozilla24.com mozilla24.com], [http://www.firefoxccstudio.org firefoxccstudio.org], [http://www.firefoxfestival.com firefoxfestival.com]
** Status: COMPLETED?
** Decision: Redirect to http://www.mozilla.jp/events/2007/mozilla24/
** Retirement Date: Spring/summer 2012
** Bug ?

* [http://events.mozilla-europe.org events.mozilla-europe.org]
** Status: COMPLETED
** Decision: Redirect to WikiMO
** Retirement Date: Spring/summer 2012
** Bug ?

* [http://designchallenges.org/ designchallenges.org]
** Status: COMPLETED
** Decision: Redirect to WikiMO
** Retirement Date: 2012-06-06
** {{bug|760622}}

Websites/Taskforce/Proposals/Abandoned Sites/2012

2012-07-11T22:12:51Z

Nuss:

[[Category:Webdev/Taskforce/Abandoned Sites|2012]]

The following is a list of websites that have been nominated for retirement, have been retired or are in the process of being retired.

= Meetings =

= Nominated Sites =
* http://artzilla.org/
* http://bb.mozillazine-tr.org/
* http://build.mozillamessaging.com/
* https://despot.mozilla.org/
* http://www.discovershiretoko.org
* http://download-cdnetworks.mozilla.net/
* http://download-speed-test.mozilla.net/
* http://dromaeo.com/
* http://eklentiler.mozillazine-tr.org
* http://extendfirefox.com/
* http://filer.mozilladanmark.dk/
* http://virtualpark.mozilla.org/

= Websites in Process of Retirement =

* [http://doctor.mozilla.org doctor.mozilla.org]
** Bug:

* [http://spark.mozilla.org spark.mozilla.org] - Spark
** {{bug|636785}}

* [http://userpanel.mozilla.com userpanel.mozilla.com]
** Bug: -

* [http://webtools.mozilla.org webtools.mozilla.org]
** Bug: -

= Retired Websites =

* [http://guides.mozilla.org guides.mozilla.org]
** Status: COMPLETED
** Decision: Retire, point to WikiMO
** Retirement Date: 2012-01-04
** {{bug|663711}} and {{bug|663712}}

* [http://www.mozilla24.com mozilla24.com], [http://www.firefoxccstudio.org firefoxccstudio.org], [http://www.firefoxfestival.com firefoxfestival.com]
** Status: COMPLETED?
** Decision: Redirect to http://www.mozilla.jp/events/2007/mozilla24/
** Retirement Date: Spring/summer 2012
** Bug ?

* [http://events.mozilla-europe.org events.mozilla-europe.org]
** Status: COMPLETED
** Decision: Redirect to WikiMO
** Retirement Date: Spring/summer 2012
** Bug ?

* [http://designchallenges.org/ designchallenges.org]
** Status: COMPLETED
** Decision: Redirect to WikiMO
** Retirement Date: 2012-06-06
** {{bug|760622}}

Websites/Taskforce/Proposals/Abandoned Sites/2011

2012-07-11T22:11:26Z

Nuss:

[[Category:Webdev/Taskforce/Abandoned Sites|2011]]

The following is a list of websites that have been nominated for retirement, have been retired or are in the process of being retired.

= Meetings =
* [[Websites/Taskforce/Proposals/Abandoned_Sites/Meetings/2011-09-28|2011-09-28]]
* [[Websites/Taskforce/Proposals/Abandoned_Sites/Meetings/2011-06-09|2011-06-09]]

= Nominated Sites =
* http://build-graphs.mozilla.org/ (Laura to check into it)
* http://designchallenges.org/
* http://www.discovershiretoko.org
* http://download-cdnetworks.mozilla.net/
* http://download-speed-test.mozilla.net/
* http://dromaeo.com/
* http://eklentiler.mozillazine-tr.org
* http://extendfirefox.com/
* http://filer.mozilladanmark.dk/
* http://virtualpark.mozilla.org/

== Stalled/WONTFIX ==
* http://ankeena.mozilla.org/ per {{bug|690949}}
* http://artzilla.org/ per [[Websites/Taskforce/Proposals/Abandoned_Sites/Meetings/2011-09-28|Meeting notes 2011-09-28]]
* https://despot.mozilla.org/ per {{bug|663713}}
* http://bb.mozillazine-tr.org/ per [[Websites/Taskforce/Proposals/Abandoned_Sites/Meetings/2011-09-28|Meeting notes 2011-09-28]]
* http://build.mozillamessaging.com/ per [[Websites/Taskforce/Proposals/Abandoned_Sites/Meetings/2011-09-28|Meeting notes 2011-09-28]]

== Mozilla Japan ==

The Mozilla Japan team will shutdown and archive the following inactive sites during this Q3 2011:

* [http://www.firefoxccstudio.org firefoxccstudio.org] - Firefox CC Studio
* [http://www.firefoxfestival.com firefoxfestival.com] - Firefox ROCK FESTIVAL '07 Supported by mF247
* [http://www.mozilla24.com mozilla24.com] - Mozilla 24

= Websites in Process of Retirement =

* [http://doctor.mozilla.org doctor.mozilla.org]
** Bug:

* [http://events.mozilla-europe.org/ events.mozilla-europe.org]
** Bug: -

* [http://guides.mozilla.org guides.mozilla.org]
** {{bug|663711}} and {{bug|663712}}

* [http://spark.mozilla.org spark.mozilla.org] - Spark
** {{bug|636785}}

* [http://userpanel.mozilla.com userpanel.mozilla.com]
** Bug: -

* [http://webtools.mozilla.org webtools.mozilla.org]
** Bug: -

= Retired Websites =

* [http://chat.mozillamessaging.com chat.mozillamessaging.com]
** {{bug|664049}}
** Retirement date: 2011-09-23

* [http://ostats.mozilla.com/ ostats.mozilla.com]
** {{bug|664262}}
** Status: COMPLETED
** Retirement date: 2011-08-24

* [http://glow.mozilla.org glow.mozilla.org]
** Status: COMPLETED
** Decision: Retire
** Retirement Date: 2011-06-29
** {{bug|668323}}

* [http://hendrix.mozilla.org hendrix.mozilla.org]
** Status: COMPLETED
** Decision: Retire and redirect to input.mozilla.com
** Redirement date: 2011-05-18
** {{bug|622621}}
** See Gerv's [http://weblogs.mozillazine.org/gerv/archives/2010/12/goodbye_hendrix.html blog post] for more

* [http://fashionyourfirefox.com fashionyourfirefox.com] - Fashion your Firefox
** Status: COMPLETED
** Decision: Retire
** Retirement Date: Q1 2011
** {{bug|618366}}

* [http://firefoxlive.mozilla.org/ firefoxlive.mozilla.org] - Firefox Live
** Status: COMPLETED
** Decision: Retire
** Retirement Date: 2011-04-14
** {{bug|644775}}

* [http://irc.mozilla.org irc.mozilla.org]
** Status: COMPLETED
** Decision: Retire; publish as wiki
** Bug: {{bug|650460}}

* [http://www.spreadfirefox.com/ spreadfirefox.com] - Spread Firefox
** Status: COMPLETED
** Decision: Retire
** {{bug|633650}}

* [http://survey.mozilla.com survey.mozilla.com] - Uninstall Survey
** Status: COMPLETED
** Decision: Archive
** {{bug|614475}}

* [http://surveys.mozilla.org surveys.mozilla.org] - Community Surveys
** Status: COMPLETED
** Decision: Retire
** {{bug|615557}}

* [http://bespin.mozillalabs.com/ bespin.mozillalabs.com]
** Status: COMPLETED
** Decision Retire, redirect to blog post
** Retirement Date: Sept, 2011
** {{bug|692813}}

* [http://markup.mozilla.org markup.mozilla.org] - Markup
** Status: COMPLETED
** Decision: Archive
** Retirement Date: 2011-10-10
** {{bug|636781}}

* [http://build-graphs.mozilla.org/ build-graphs.mozilla.org]
** Status: COMPLETED?
** Decision: Retire
** Retirement Date: 2011-10-31
** {{bug|698070}}

* [http://www.webifyme.org webifyme.org]
** Status: COMPLETED
** Decision: Archive
** Retirement Date: 2011-11-15
** {{bug|641133}}?

* [http://www.webowonder.com/ webowonder.com], [http://demos.mozilla.org/ demos.mozilla.org] - WebOWonder
** Status: COMPLETED
** Decision: Retire, redirect to MDN
** Retirement Date: Q4 2011
** {{bug|642340}}

* [http://banners.mozilla-europe.org banners.mozilla-europe.org]
** Status: COMPLETED
** Decision Retire, redirect to mozilla.org/firefox
** Retirement Date: 2011-12-07
** {{bug|691378}}

* [http://firefoxflicks.com/ firefoxflicks.com] - Firefox Flicks
** Status: COMPLETED
** Decision: Retire
** Retirement Date: Dec, 2011
** Bug: {{bug|667719}}

Websites/Taskforce/Proposals/Abandoned Sites/2012

2012-07-11T22:08:29Z

Nuss: /* Retired Websites */

[[Category:Webdev/Taskforce/Abandoned Sites|2012]]

The following is a list of websites that have been nominated for retirement, have been retired or are in the process of being retired.

= Meetings =

= Nominated Sites =
* http://ankeena.mozilla.org/
* http://artzilla.org/
* http://bb.mozillazine-tr.org/
* http://build-graphs.mozilla.org/ (Laura to check into it)
* http://build.mozillamessaging.com/
* https://despot.mozilla.org/
* http://www.discovershiretoko.org
* http://download-cdnetworks.mozilla.net/
* http://download-speed-test.mozilla.net/
* http://dromaeo.com/
* http://eklentiler.mozillazine-tr.org
* http://extendfirefox.com/
* http://filer.mozilladanmark.dk/
* http://virtualpark.mozilla.org/

= Websites in Process of Retirement =

* [http://doctor.mozilla.org doctor.mozilla.org]
** Bug:

* [http://spark.mozilla.org spark.mozilla.org] - Spark
** {{bug|636785}}

* [http://userpanel.mozilla.com userpanel.mozilla.com]
** Bug: -

* [http://webtools.mozilla.org webtools.mozilla.org]
** Bug: -

= Retired Websites =

* [http://guides.mozilla.org guides.mozilla.org]
** Status: COMPLETED
** Decision: Retire, point to WikiMO
** Retirement Date: 2012-01-04
** {{bug|663711}} and {{bug|663712}}

= Retired Websites =

* [http://guides.mozilla.org guides.mozilla.org]
** Status: COMPLETED
** Decision: Retire, point to WikiMO
** Retirement Date: 2012-01-04
** {{bug|663711}} and {{bug|663712}}

* [http://www.mozilla24.com mozilla24.com], [http://www.firefoxccstudio.org firefoxccstudio.org], [http://www.firefoxfestival.com firefoxfestival.com]
** Status: COMPLETED?
** Decision: Redirect to http://www.mozilla.jp/events/2007/mozilla24/
** Retirement Date: Spring/summer 2012
** Bug ?

* [http://events.mozilla-europe.org events.mozilla-europe.org]
** Status: COMPLETED
** Decision: Redirect to WikiMO
** Retirement Date: Spring/summer 2012
** Bug ?

* [http://designchallenges.org/ designchallenges.org]
** Status: COMPLETED
** Decision: Redirect to WikiMO
** Retirement Date: 2012-06-06
** {{bug|760622}}

* [http://build-graphs.mozilla.org/ build-graphs.mozilla.org]
** Status: COMPLETED?
** Decision: Removed from DNS
** Retirement Date: 2011-10-31
** {{bug|698070}}

Websites/Taskforce/Proposals/Abandoned Sites/2012

2012-07-11T21:56:58Z

Nuss:

[[Category:Webdev/Taskforce/Abandoned Sites|2012]]

The following is a list of websites that have been nominated for retirement, have been retired or are in the process of being retired.

= Meetings =

= Nominated Sites =
* http://ankeena.mozilla.org/
* http://artzilla.org/
* http://bb.mozillazine-tr.org/
* http://build-graphs.mozilla.org/ (Laura to check into it)
* http://build.mozillamessaging.com/
* https://despot.mozilla.org/
* http://www.discovershiretoko.org
* http://download-cdnetworks.mozilla.net/
* http://download-speed-test.mozilla.net/
* http://dromaeo.com/
* http://eklentiler.mozillazine-tr.org
* http://extendfirefox.com/
* http://filer.mozilladanmark.dk/
* http://virtualpark.mozilla.org/

= Websites in Process of Retirement =

* [http://doctor.mozilla.org doctor.mozilla.org]
** Bug:

* [http://spark.mozilla.org spark.mozilla.org] - Spark
** {{bug|636785}}

* [http://userpanel.mozilla.com userpanel.mozilla.com]
** Bug: -

* [http://webtools.mozilla.org webtools.mozilla.org]
** Bug: -

= Retired Websites =

* [http://guides.mozilla.org guides.mozilla.org]
** Status: COMPLETED
** Decision: Retire, point to WikiMO
** Retirement Date: 2012-01-04
** {{bug|663711}} and {{bug|663712}}

= Retired Websites =

* [http://guides.mozilla.org guides.mozilla.org]
** Status: COMPLETED
** Decision: Retire, point to WikiMO
** Retirement Date: 2012-01-04
** {{bug|663711}} and {{bug|663712}}

* [http://www.mozilla24.com mozilla24.com], [http://www.firefoxccstudio.org firefoxccstudio.org], [http://www.firefoxfestival.com firefoxfestival.com]
** Status: COMPLETED?
** Decision: Redirect to http://www.mozilla.jp/events/2007/mozilla24/
** Retirement Date: Spring/summer 2012
** Bug ?

* [http://events.mozilla-europe.org events.mozilla-europe.org]
** Status: COMPLETED
** Decision: Redirect to WikiMO
** Retirement Date: Spring/summer 2012
** Bug ?

* [http://designchallenges.org/ designchallenges.org]
** Status: COMPLETED
** Decision: Redirect to WikiMO
** Retirement Date: Spring/summer 2012
** Bug ?

Websites/Taskforce/Proposals/Domain Name Strategy

2012-06-29T10:16:42Z

Nuss: /* mozillalabs.com domains to switch */ Mozilla Labs' switched domains

'''Domain Name Strategy'''

If you have any questions about how this document applies to any work you are doing or if you have feedback or comments or need clarification, please contact david at mozillafoundation dot org and jslater at mozilla dot com.

''This strategy applies only to websites and does not intend to cover anything to do with email addresses.''

=Working Group=

John Slater, Janet Swisher, Laura Forrest and David Boswell

=Status=

This proposal was approved at the [[Websites/Taskforce/2010_10_21|10/21/10 task force meeting]].

=Problem=

We are currently using our organizational structure as a way to set up domain
names and this is presenting irrelevant information to people and diverting our
message away from more important things, such as what we do and why we do it.

For example, the following are some of the organizational domains currently in
use:

* mozilla.com

* mozillamessaging.com

* mozilla-europe.org*

* mozillaonline.com*

* mozilla.jp*

Note that mozilla.org is not an organizational domain -- it is the community's
domain that was set up and used long before there was any Mozilla organization.
It isn't the Foundation's organizational domain -- that is mozillafoundation.org
that was in use briefly but has been retired.

''*Affiliate URLs act as both an organization site and a local site, so there is no need to move away from using those domains. The more important issue with affiliate sites is making the content as relevant as possible by de-emphasizing the organizational information and highlighting the locale specific information.''

=Solution=

To be able to stop using organizations as a basis for our domain name
strategy, we need to develop an alternative that uses something else for its structure. There seem to be two main options:

* Structure a strategy based on product/activity: firefox.com, thunderbird.com, drumbeat.org, etc.

* Structure a strategy based on everything being a part of Mozilla: www.mozilla.org, addons.mozilla.org, foo.mozilla.org

Both options have advantages and disadvantages, but they are mutually exclusive so we need to pick one (although we can certainly maintain redirects for any URLs we want).

=="One Mozilla" Strategy==

To create a "One Mozilla" strategy for domain names, we propose using sub-domains for functional areas and sub-directories for products and programs (programs in the initiative sense) with some exceptions. So:

* service.mozilla.org/sub-category

The following breaks out how this general rule applies to different types of sites.

===Product and Program Sites===

Sites related to the major activities backed by Mozilla organizations should use sub-directories on www.mozilla.org. The service being offered here is delivery of web pages (compared with delivery of a web app providing specific functionality).

Examples:

* www.mozilla.org/firefox

* www.mozilla.org/thunderbird

* www.mozilla.org/drumbeat

Note: Other community-backed projects such as seamonkey-project.org can show affiliation with Mozilla on their site in a number of other ways without having to change their URL structure.

===Web Application Sites===

Sites that exist to host services should have sub-domains based on the service offered and sub-directories based on products or programs. This is the existing addons.mozilla.org model.

Examples:

* addons.mozilla.org/firefox, addons.mozilla.org/mobile, addons.mozilla.org/thunderbird, etc.

* support.mozilla.org/firefox, support.mozilla.org/mobile, support.mozilla.org/thunderbird, etc.

* nightly.mozilla.org/firefox, nightly.mozilla.org/mobile, nightly.mozilla.org/thunderbird, etc.

For sites that provide a service for the community as a whole and not for specific programs or products, there is no need to divide things by sub-directory.

Examples:

* air.mozilla.org

* developer.mozilla.org

* feeds.mozilla.org

===Campaign Sites===

Mini-sites set up for a specific campaign should be able to use whatever URL makes sense. Because these sites are usually relevant to a specific time, an archiving plan should be put in place so this content isn't abandoned.

Examples:

* firefoxflicks.com

* opentochoice.org

* operationfirefox.com

===Local Sites===

There are two main URL styles being used today by local sites.

Examples:

* mozilla.country: mozilla.jp, mozilla.ro, etc.

* mozilla-country.org: mozilla-mexico.org, mozilla-russia.org, etc.

There are also a variety of other URLs in use such as bgzilla.org and mozilla.org.ua. It may make sense to make these more consistent, but there is no plan to do that now. On the other hand, having flexibility with local site URLs allows us to deal with issues relevant to different locales.

===Mobile Sites===

Ideally each site would have one URL which would present its content in a form optimized for any device. For complex sites though, the functionality available on mobile versions may differ greatly and switching style sheets alone may not be sufficient.

When it isn't possible to maintain a single URL for a site, we recommend adding a "m." at the beginning of the domain, such as

* m.foo.mozilla.org.

In the cases when we do choose to go with separate mobile URLs, once we take the time to do things the ideal way we can just redirect mobile URLs to their desktop equivalents for a seamless transition.

===Other Sites===

Mozilla is a big community with many people doing many things and there's no benefit to making every site fit in some structure. It is fine for some sites to have unique URLs as long as they avoid organization specific domains or trademark violations.

Examples of sites with unique URLs that are fine:

* accessfirefox.org

* geckozone.org

* mozillamemory.org

==Proposed URL Changes==

Using the principles of the "One Mozilla" strategy, we suggest the following URL changes (this is just an initial batch and not comprehensive of all possible URL changes).

{| border="1px" cellspacing="0px"
! Existing URL !! Proposed URL !! Comment
|-
| mozilla.com || www.mozilla.org/firefox ||
|-
| mozillamessaging.com || www.mozilla.org/thunderbird ||
|-
| support.mozilla.com || support.mozilla.org ||
|-
| mobile.support.mozilla.com || support.mozilla.org/mobile ||
|-
| support.mozillamessaging.com || support.mozilla.org/thunderbird ||
|-
| air.mozilla.com || air.mozilla.org ||
|-
| feeds.mozilla.com || feeds.mozilla.org ||
|-
| input.mozilla.com || input.mozilla.org ||
|}

== Technical Considerations ==

=== Localization ===

The best practices around how to use locale codes in URLs shouldn't need to be changed due to this proposal. Sites can still use the following scheme (with the example here of Mozilla Europe's German Firefox page):

* www.mozilla-europe.org/de/firefox/

The bigger issue with the l10n process is how will this proposal change how localizers determine what to work on? If sites are aggregated into fewer domains will more content need to be localized or would we create less cohesive experiences with partially localized sites?

=== Security ===

Moving from multiple unique domains to subdomains of a single domain, and in some cases subdirectories within that subdomain, will require changes to the security requirements that are imposed upon these websites. Specifically, all websites that are grouped within the same subdomain will be subject to the highest security requirements of any site within that subdomain.

In some cases this may mean that a site that was previously not hosting or performing critical operations, and thus had more lenient security controls, would be required to significantly enhance the security controls before it could be added as a subdirectory of a more security restrictive subdomain.

In addition, depending upon the criticality of a given group of websites within a subdomain this may result in a more strictly controlled security review process including requirements to review any new code before it is pushed live to the site.

=== Webtrends Tracking ===

From Webtrends - You should be fine changing over from the .com domain to the .org domain, as long as the primary domain designated in the Webtrends JavaScript tag points to what you consider the primary domain. Additionally, if you plan on having both domains concurrently available, you may want to modify the JavaScript tag to include mozilla.com at a value for the this.onsitedoms=""; entry in the JavaScript include. This would then consider all traffic from mozilla.com to be considered part of the traffic on the primary domain and would not prefix entries in reports with "Offsite:"

=== SEO Best Practices ===

SEO Best Practices When Switching Domains

Please take the following into consideration when making these switches to minimize any possible dips in natural search traffic.

Redirect Treatment (Technical Owner)

*The most important thing to avoid is 404 (file not found) errors when searchers click on Mozilla site links that show up on the search engine response page (SERP)
*Use a permanent 301 redirect to redirect the pages on the old site to the new site. This also lets Google know all the pages have officially moved. 
*Change all internal site links to point to the correct domain
*Use link checking software to find any broken links
*Submit a new sitemap to Google Webmaster Tools and Yahoo Site Submit
*Do this in phases if possible, moving one subdirectory over at a time, monitoring the results 

Incoming Links (Business Owner)

*If possible, contact the main owners of our largest incoming traffic and have them change the link (Google Snippets, YouTube, Affiliate Programs, and many more)
*Closely monitor SERP results and incoming organic search traffic for major changes

 

References http://googlewebmastercentral.blogspot.com/2008/04/best-practices-when-moving-your-site.html http://www.clickz.com/clickz/column/1699947/seo-best-practices-when-moving-web-site http://www.seomoz.org/blog/seo-guide-how-to-properly-move-domains 

Also a recent quote from Matt Cutts of Google:  

''When done correctly, a 301 redirect shouldn't cause any drop in traffic, says Matt Cutts, a Google software engineer. He says instead of moving its entire website at once, Evo would have been better off moving the site very slowly, starting with the least-trafficked areas of its website. Changing something like the structure of a site during a move can also cause problems. "If someone changes to a new template, that can affect the rankings," says Cutts. "Sometimes it takes Google a little while to figure out how best to process, index, and rank a page."'' 

And input from Rand Fishkin of SEOmoz on our particular case: 

''On the switch over - I suspect it will be relatively painless, but you might want to do as Google recommends and switch part of the content first, then move over in batches, rather than all at once. You can see Matt Cutts discussing this in an Inc article recently...It's not critical, IMO, but it might save some pain in that "Google's figuring things out" timeframe.'' 

 

 

=== Product Links ===

The following is quoted from [https://bugzilla.mozilla.org/show_bug.cgi?id=606278 bug 606278] as part of a discussion about issues involving switching domains for sites that are linked to from within our products:

Same thing goes for byob.mozilla.com, as I mentioned in bug 607129. Not so much
that it's coded into Fx4, but that the domain name is part of the configuration
distributed with custom browsers.

FWIW, this is not something I see mentioned in the strategy: Existing sites are
linked to by other sites and coded into products / configurations in the wild
(ie. outside our control). Cleanly moving things may not be possible in all
cases, so we'll need some consideration around transitions.

Some sites may need to be served up at both the new and old locations, if only
with a 301 redirect at the legacy URL. However, some URLs may not be amenable
to redirects - ie. sites offering APIs like addons.mozilla.org

It's also possible that there may be some URL namespace collisions where
old/new URLs need to co-exist for an extended period of time. I can't think of
any off the top of my head, though

== Implementation ==

Once we've agreed on the plan we want to roll out these changes incrementally. Doing everything at once would be too big a project and we expect there will be things to learn about the process as we start making changes.

To follow along with the progress of things, see [https://bugzilla.mozilla.org/show_bug.cgi?id=606278 bug 606278]

==== mozilla.com domains to switch ====

The following is the list of mozilla.com domains to switch and the associated bugs.

*<strike>krakenbenchmark.mozilla.com</strike> - [https://bugzilla.mozilla.org/show_bug.cgi?id=613649 bug 613649]

*<strike>feeds.mozilla.com</strike> - [https://bugzilla.mozilla.org/show_bug.cgi?id=613648 bug 613648]

*<strike>air.mozilla.com</strike> - [https://bugzilla.mozilla.org/show_bug.cgi?id=606326 bug 606326]

*<strike>www.mozilla.com</strike> - [https://bugzilla.mozilla.org/show_bug.cgi?id=610724 bug 610724]

*<strike>support.mozilla.com</strike> [https://bugzilla.mozilla.org/show_bug.cgi?id=683674 bug 683674]

*<strike>etherpad.mozilla.com</strike>

*<strike>blog.mozilla.com [https://bugzilla.mozilla.org/show_bug.cgi?id=618095 bug 618095]</strike>

*<strike>input.mozilla.com [https://bugzilla.mozilla.org/show_bug.cgi?id=618157 bug 618157]</strike>

*byob.mozilla.com - [https://bugzilla.mozilla.org/show_bug.cgi?id=607129 bug 607129]

*tools.mozilla.com [https://bugzilla.mozilla.org/show_bug.cgi?id=618147 bug 618147]

*crash-stats.mozilla.com [https://bugzilla.mozilla.org/show_bug.cgi?id=618153 bug 618153]

*browserchoice.mozilla.com [https://bugzilla.mozilla.org/show_bug.cgi?id=618159 bug 618159]

*identity.mozilla.com

*services.mozilla.com

*status.mozilla.com

*brasstacks.mozilla.com

*metrics.mozilla.com

==== mozillalabs.com domains to switch ====

The plan here is for Labs to switch over to mozillalabs.org. They will implement and we can check in as needed.

*<strike>apps.mozillalabs.com</strike>

*<strike>design-challenge.mozillalabs.com</strike>

*<strike>jetpack.mozillalabs.com</strike>

*bespin.mozillalabs.com

*builder.mozillalabs.com

*gaming.mozillalabs.com

*heatmap.mozillalabs.com

*prism.mozillalabs.com

*testpilot.mozillalabs.com

*www.mozillalabs.com

==== mozillamessaging.com domains to switch ====

Mozilla Messaging will switch the domains and we can help as needed.

*<strike>www.mozillamessaging.com</strike> [https://bugzilla.mozilla.org/show_bug.cgi?id=666785 bug 666785]

*<strike>chat.mozillamessaging.com</strike> [https://bugzilla.mozilla.org/show_bug.cgi?id=664049 bug 664049]

*f1.mozillamessaging.com

*ispdb.mozillamessaging.com

*support.mozillamessaging.com

Thunderbird/ISPDB/

2012-05-02T13:39:48Z

Nuss: Redirected page to Thunderbird/ISPDB

#REDIRECT [[Thunderbird/ISPDB]]

Websites/Taskforce/Proposals/Domain Name Strategy

2012-04-13T19:26:13Z

Nuss: /* mozilla.com domains to switch */ added metrics.mozilla.com

'''Domain Name Strategy'''

If you have any questions about how this document applies to any work you are doing or if you have feedback or comments or need clarification, please contact david at mozillafoundation dot org and jslater at mozilla dot com.

''This strategy applies only to websites and does not intend to cover anything to do with email addresses.''

=Working Group=

John Slater, Janet Swisher, Laura Forrest and David Boswell

=Status=

This proposal was approved at the [[Websites/Taskforce/2010_10_21|10/21/10 task force meeting]].

=Problem=

We are currently using our organizational structure as a way to set up domain
names and this is presenting irrelevant information to people and diverting our
message away from more important things, such as what we do and why we do it.

For example, the following are some of the organizational domains currently in
use:

* mozilla.com

* mozillamessaging.com

* mozilla-europe.org*

* mozillaonline.com*

* mozilla.jp*

Note that mozilla.org is not an organizational domain -- it is the community's
domain that was set up and used long before there was any Mozilla organization.
It isn't the Foundation's organizational domain -- that is mozillafoundation.org
that was in use briefly but has been retired.

''*Affiliate URLs act as both an organization site and a local site, so there is no need to move away from using those domains. The more important issue with affiliate sites is making the content as relevant as possible by de-emphasizing the organizational information and highlighting the locale specific information.''

=Solution=

To be able to stop using organizations as a basis for our domain name
strategy, we need to develop an alternative that uses something else for its structure. There seem to be two main options:

* Structure a strategy based on product/activity: firefox.com, thunderbird.com, drumbeat.org, etc.

* Structure a strategy based on everything being a part of Mozilla: www.mozilla.org, addons.mozilla.org, foo.mozilla.org

Both options have advantages and disadvantages, but they are mutually exclusive so we need to pick one (although we can certainly maintain redirects for any URLs we want).

=="One Mozilla" Strategy==

To create a "One Mozilla" strategy for domain names, we propose using sub-domains for functional areas and sub-directories for products and programs (programs in the initiative sense) with some exceptions. So:

* service.mozilla.org/sub-category

The following breaks out how this general rule applies to different types of sites.

===Product and Program Sites===

Sites related to the major activities backed by Mozilla organizations should use sub-directories on www.mozilla.org. The service being offered here is delivery of web pages (compared with delivery of a web app providing specific functionality).

Examples:

* www.mozilla.org/firefox

* www.mozilla.org/thunderbird

* www.mozilla.org/drumbeat

Note: Other community-backed projects such as seamonkey-project.org can show affiliation with Mozilla on their site in a number of other ways without having to change their URL structure.

===Web Application Sites===

Sites that exist to host services should have sub-domains based on the service offered and sub-directories based on products or programs. This is the existing addons.mozilla.org model.

Examples:

* addons.mozilla.org/firefox, addons.mozilla.org/mobile, addons.mozilla.org/thunderbird, etc.

* support.mozilla.org/firefox, support.mozilla.org/mobile, support.mozilla.org/thunderbird, etc.

* nightly.mozilla.org/firefox, nightly.mozilla.org/mobile, nightly.mozilla.org/thunderbird, etc.

For sites that provide a service for the community as a whole and not for specific programs or products, there is no need to divide things by sub-directory.

Examples:

* air.mozilla.org

* developer.mozilla.org

* feeds.mozilla.org

===Campaign Sites===

Mini-sites set up for a specific campaign should be able to use whatever URL makes sense. Because these sites are usually relevant to a specific time, an archiving plan should be put in place so this content isn't abandoned.

Examples:

* firefoxflicks.com

* opentochoice.org

* operationfirefox.com

===Local Sites===

There are two main URL styles being used today by local sites.

Examples:

* mozilla.country: mozilla.jp, mozilla.ro, etc.

* mozilla-country.org: mozilla-mexico.org, mozilla-russia.org, etc.

There are also a variety of other URLs in use such as bgzilla.org and mozilla.org.ua. It may make sense to make these more consistent, but there is no plan to do that now. On the other hand, having flexibility with local site URLs allows us to deal with issues relevant to different locales.

===Mobile Sites===

Ideally each site would have one URL which would present its content in a form optimized for any device. For complex sites though, the functionality available on mobile versions may differ greatly and switching style sheets alone may not be sufficient.

When it isn't possible to maintain a single URL for a site, we recommend adding a "m." at the beginning of the domain, such as

* m.foo.mozilla.org.

In the cases when we do choose to go with separate mobile URLs, once we take the time to do things the ideal way we can just redirect mobile URLs to their desktop equivalents for a seamless transition.

===Other Sites===

Mozilla is a big community with many people doing many things and there's no benefit to making every site fit in some structure. It is fine for some sites to have unique URLs as long as they avoid organization specific domains or trademark violations.

Examples of sites with unique URLs that are fine:

* accessfirefox.org

* geckozone.org

* mozillamemory.org

==Proposed URL Changes==

Using the principles of the "One Mozilla" strategy, we suggest the following URL changes (this is just an initial batch and not comprehensive of all possible URL changes).

{| border="1px" cellspacing="0px"
! Existing URL !! Proposed URL !! Comment
|-
| mozilla.com || www.mozilla.org/firefox ||
|-
| mozillamessaging.com || www.mozilla.org/thunderbird ||
|-
| support.mozilla.com || support.mozilla.org ||
|-
| mobile.support.mozilla.com || support.mozilla.org/mobile ||
|-
| support.mozillamessaging.com || support.mozilla.org/thunderbird ||
|-
| air.mozilla.com || air.mozilla.org ||
|-
| feeds.mozilla.com || feeds.mozilla.org ||
|-
| input.mozilla.com || input.mozilla.org ||
|}

== Technical Considerations ==

=== Localization ===

The best practices around how to use locale codes in URLs shouldn't need to be changed due to this proposal. Sites can still use the following scheme (with the example here of Mozilla Europe's German Firefox page):

* www.mozilla-europe.org/de/firefox/

The bigger issue with the l10n process is how will this proposal change how localizers determine what to work on? If sites are aggregated into fewer domains will more content need to be localized or would we create less cohesive experiences with partially localized sites?

=== Security ===

Moving from multiple unique domains to subdomains of a single domain, and in some cases subdirectories within that subdomain, will require changes to the security requirements that are imposed upon these websites. Specifically, all websites that are grouped within the same subdomain will be subject to the highest security requirements of any site within that subdomain.

In some cases this may mean that a site that was previously not hosting or performing critical operations, and thus had more lenient security controls, would be required to significantly enhance the security controls before it could be added as a subdirectory of a more security restrictive subdomain.

In addition, depending upon the criticality of a given group of websites within a subdomain this may result in a more strictly controlled security review process including requirements to review any new code before it is pushed live to the site.

=== Webtrends Tracking ===

From Webtrends - You should be fine changing over from the .com domain to the .org domain, as long as the primary domain designated in the Webtrends JavaScript tag points to what you consider the primary domain. Additionally, if you plan on having both domains concurrently available, you may want to modify the JavaScript tag to include mozilla.com at a value for the this.onsitedoms=""; entry in the JavaScript include. This would then consider all traffic from mozilla.com to be considered part of the traffic on the primary domain and would not prefix entries in reports with "Offsite:"

=== SEO Best Practices ===

SEO Best Practices When Switching Domains

Please take the following into consideration when making these switches to minimize any possible dips in natural search traffic.

Redirect Treatment (Technical Owner)

*The most important thing to avoid is 404 (file not found) errors when searchers click on Mozilla site links that show up on the search engine response page (SERP)
*Use a permanent 301 redirect to redirect the pages on the old site to the new site. This also lets Google know all the pages have officially moved. 
*Change all internal site links to point to the correct domain
*Use link checking software to find any broken links
*Submit a new sitemap to Google Webmaster Tools and Yahoo Site Submit
*Do this in phases if possible, moving one subdirectory over at a time, monitoring the results 

Incoming Links (Business Owner)

*If possible, contact the main owners of our largest incoming traffic and have them change the link (Google Snippets, YouTube, Affiliate Programs, and many more)
*Closely monitor SERP results and incoming organic search traffic for major changes

 

References http://googlewebmastercentral.blogspot.com/2008/04/best-practices-when-moving-your-site.html http://www.clickz.com/clickz/column/1699947/seo-best-practices-when-moving-web-site http://www.seomoz.org/blog/seo-guide-how-to-properly-move-domains 

Also a recent quote from Matt Cutts of Google:  

''When done correctly, a 301 redirect shouldn't cause any drop in traffic, says Matt Cutts, a Google software engineer. He says instead of moving its entire website at once, Evo would have been better off moving the site very slowly, starting with the least-trafficked areas of its website. Changing something like the structure of a site during a move can also cause problems. "If someone changes to a new template, that can affect the rankings," says Cutts. "Sometimes it takes Google a little while to figure out how best to process, index, and rank a page."'' 

And input from Rand Fishkin of SEOmoz on our particular case: 

''On the switch over - I suspect it will be relatively painless, but you might want to do as Google recommends and switch part of the content first, then move over in batches, rather than all at once. You can see Matt Cutts discussing this in an Inc article recently...It's not critical, IMO, but it might save some pain in that "Google's figuring things out" timeframe.'' 

 

 

=== Product Links ===

The following is quoted from [https://bugzilla.mozilla.org/show_bug.cgi?id=606278 bug 606278] as part of a discussion about issues involving switching domains for sites that are linked to from within our products:

Same thing goes for byob.mozilla.com, as I mentioned in bug 607129. Not so much
that it's coded into Fx4, but that the domain name is part of the configuration
distributed with custom browsers.

FWIW, this is not something I see mentioned in the strategy: Existing sites are
linked to by other sites and coded into products / configurations in the wild
(ie. outside our control). Cleanly moving things may not be possible in all
cases, so we'll need some consideration around transitions.

Some sites may need to be served up at both the new and old locations, if only
with a 301 redirect at the legacy URL. However, some URLs may not be amenable
to redirects - ie. sites offering APIs like addons.mozilla.org

It's also possible that there may be some URL namespace collisions where
old/new URLs need to co-exist for an extended period of time. I can't think of
any off the top of my head, though

== Implementation ==

Once we've agreed on the plan we want to roll out these changes incrementally. Doing everything at once would be too big a project and we expect there will be things to learn about the process as we start making changes.

To follow along with the progress of things, see [https://bugzilla.mozilla.org/show_bug.cgi?id=606278 bug 606278]

==== mozilla.com domains to switch ====

The following is the list of mozilla.com domains to switch and the associated bugs.

*<strike>krakenbenchmark.mozilla.com</strike> - [https://bugzilla.mozilla.org/show_bug.cgi?id=613649 bug 613649]

*<strike>feeds.mozilla.com</strike> - [https://bugzilla.mozilla.org/show_bug.cgi?id=613648 bug 613648]

*<strike>air.mozilla.com</strike> - [https://bugzilla.mozilla.org/show_bug.cgi?id=606326 bug 606326]

*<strike>www.mozilla.com</strike> - [https://bugzilla.mozilla.org/show_bug.cgi?id=610724 bug 610724]

*<strike>support.mozilla.com</strike> [https://bugzilla.mozilla.org/show_bug.cgi?id=683674 bug 683674]

*<strike>etherpad.mozilla.com</strike>

*<strike>blog.mozilla.com [https://bugzilla.mozilla.org/show_bug.cgi?id=618095 bug 618095]</strike>

*byob.mozilla.com - [https://bugzilla.mozilla.org/show_bug.cgi?id=607129 bug 607129]

*tools.mozilla.com [https://bugzilla.mozilla.org/show_bug.cgi?id=618147 bug 618147]

*crash-stats.mozilla.com [https://bugzilla.mozilla.org/show_bug.cgi?id=618153 bug 618153]

*input.mozilla.com [https://bugzilla.mozilla.org/show_bug.cgi?id=618157 bug 618157]

*browserchoice.mozilla.com [https://bugzilla.mozilla.org/show_bug.cgi?id=618159 bug 618159]

*identity.mozilla.com

*services.mozilla.com

*status.mozilla.com

*brasstacks.mozilla.com

*metrics.mozilla.com

==== mozillalabs.com domains to switch ====

The plan here is for Labs to switch over to mozillalabs.org. They will implement and we can check in as needed.

*apps.mozillalabs.com

*bespin.mozillalabs.com

*builder.mozillalabs.com

*design-challenge.mozillalabs.com

*gaming.mozillalabs.com

*heatmap.mozillalabs.com

*jetpack.mozillalabs.com

*prism.mozillalabs.com

*testpilot.mozillalabs.com

*www.mozillalabs.com

==== mozillamessaging.com domains to switch ====

Mozilla Messaging will switch the domains and we can help as needed.

*<strike>www.mozillamessaging.com</strike> [https://bugzilla.mozilla.org/show_bug.cgi?id=666785 bug 666785]

*<strike>chat.mozillamessaging.com</strike> [https://bugzilla.mozilla.org/show_bug.cgi?id=664049 bug 664049]

*f1.mozillamessaging.com

*ispdb.mozillamessaging.com

*support.mozillamessaging.com

Websites/Taskforce/Proposals/Abandoned Sites/2011

2012-02-28T20:25:32Z

Nuss: /* Nominated Sites */

[[Category:Webdev/Taskforce/Abandoned Sites|2011]]

The following is a list of websites that have been nominated for retirement, have been retired or are in the process of being retired.

= Meetings =
* [[Websites/Taskforce/Proposals/Abandoned_Sites/Meetings/2011-09-28|2011-09-28]]
* [[Websites/Taskforce/Proposals/Abandoned_Sites/Meetings/2011-06-09|2011-06-09]]

= Nominated Sites =
* http://build-graphs.mozilla.org/ (Laura to check into it)
* http://designchallenges.org/
* http://www.discovershiretoko.org
* http://download-cdnetworks.mozilla.net/
* http://download-speed-test.mozilla.net/
* http://dromaeo.com/
* http://eklentiler.mozillazine-tr.org
* http://extendfirefox.com/
* http://filer.mozilladanmark.dk/
* http://virtualpark.mozilla.org/

== Stalled/WONTFIX ==
* http://ankeena.mozilla.org/ per {{bug|690949}}
* http://artzilla.org/ per [[Websites/Taskforce/Proposals/Abandoned_Sites/Meetings/2011-09-28|Meeting notes 2011-09-28]]
* https://despot.mozilla.org/ per {{bug|663713}}
* http://bb.mozillazine-tr.org/ per [[Websites/Taskforce/Proposals/Abandoned_Sites/Meetings/2011-09-28|Meeting notes 2011-09-28]]
* http://build.mozillamessaging.com/ per [[Websites/Taskforce/Proposals/Abandoned_Sites/Meetings/2011-09-28|Meeting notes 2011-09-28]]

== Mozilla Japan ==

The Mozilla Japan team will shutdown and archive the following inactive sites during this Q3 2011:

* [http://www.firefoxccstudio.org firefoxccstudio.org] - Firefox CC Studio
* [http://www.firefoxfestival.com firefoxfestival.com] - Firefox ROCK FESTIVAL '07 Supported by mF247
* [http://www.mozilla24.com mozilla24.com] - Mozilla 24

= Websites in Process of Retirement =

* [http://doctor.mozilla.org doctor.mozilla.org]
** Bug:

* [http://events.mozilla-europe.org/ events.mozilla-europe.org]
** Bug: -

* [http://guides.mozilla.org guides.mozilla.org]
** {{bug|663711}} and {{bug|663712}}

* [http://spark.mozilla.org spark.mozilla.org] - Spark
** {{bug|636785}}

* [http://userpanel.mozilla.com userpanel.mozilla.com]
** Bug: -

* [http://webtools.mozilla.org webtools.mozilla.org]
** Bug: -

= Retired Websites =

* [http://chat.mozillamessaging.com chat.mozillamessaging.com]
** {{bug|664049}}
** Retirement date: 2011-09-23

* [http://ostats.mozilla.com/ ostats.mozilla.com]
** {{bug|664262}}
** Status: COMPLETED
** Retirement date: 2011-08-24

* [http://glow.mozilla.org glow.mozilla.org]
** Status: COMPLETED
** Decision: Retire
** Retirement Date: 2011-06-29
** {{bug|668323}}

* [http://hendrix.mozilla.org hendrix.mozilla.org]
** Status: COMPLETED
** Decision: Retire and redirect to input.mozilla.com
** Redirement date: 2011-05-18
** {{bug|622621}}
** See Gerv's [http://weblogs.mozillazine.org/gerv/archives/2010/12/goodbye_hendrix.html blog post] for more

* [http://fashionyourfirefox.com fashionyourfirefox.com] - Fashion your Firefox
** Status: COMPLETED
** Decision: Retire
** Retirement Date: Q1 2011
** {{bug|618366}}

* [http://firefoxlive.mozilla.org/ firefoxlive.mozilla.org] - Firefox Live
** Status: COMPLETED
** Decision: Retire
** Retirement Date: 2011-04-14
** {{bug|644775}}

* [http://irc.mozilla.org irc.mozilla.org]
** Status: COMPLETED
** Decision: Retire; publish as wiki
** Bug: {{bug|650460}}

* [http://www.spreadfirefox.com/ spreadfirefox.com] - Spread Firefox
** Status: COMPLETED
** Decision: Retire
** {{bug|633650}}

* [http://survey.mozilla.com survey.mozilla.com] - Uninstall Survey
** Status: COMPLETED
** Decision: Archive
** {{bug|614475}}

* [http://surveys.mozilla.org surveys.mozilla.org] - Community Surveys
** Status: COMPLETED
** Decision: Retire
** {{bug|615557}}

* [http://firefoxflicks.com/ firefoxflicks.com] - Firefox Flicks
** Status: COMPLETED
** Decision: Retire
** Retirement Date: Dec, 2011
** Bug: {{bug|667719}}

* [http://markup.mozilla.org markup.mozilla.org] - Markup
** Status: COMPLETED
** Decision: Archive
** Retirement Date: 2011-10-10
** {{bug|636781}}

* [http://www.webifyme.org webifyme.org]
** Status: COMPLETED
** Decision: Archive
** Retirement Date: 2011-11-15
** {{bug|641133}}?

* [http://www.webowonder.com/ webowonder.com], [http://demos.mozilla.org/ demos.mozilla.org] - WebOWonder
** Status: COMPLETED
** Decision: Retire, redorect to MDN
** Retirement Date: Q4 2011
** {{bug|642340}}

* [http://banners.mozilla-europe.org banners.mozilla-europe.org]
** Status: COMPLETED
** Decision Retire, redirect to mozilla.org/firefox
** Retirement Date: 2011-12-07
** {{bug|691378}}

* [http://bespin.mozillalabs.com/ bespin.mozillalabs.com]
** Status: COMPLETED
** Decision Retire, redirect to blog post
** Retirement Date: Sept, 2011
** {{bug|692813}}

Websites/Taskforce/Proposals/Abandoned Sites/2012

2012-02-28T20:24:00Z

Nuss: /* Nominated Sites */

[[Category:Webdev/Taskforce/Abandoned Sites|2012]]

The following is a list of websites that have been nominated for retirement, have been retired or are in the process of being retired.

= Meetings =

= Nominated Sites =

* http://ankeena.mozilla.org/
* http://artzilla.org/
* http://bb.mozillazine-tr.org/
* http://build-graphs.mozilla.org/ (Laura to check into it)
* http://build.mozillamessaging.com/
* http://designchallenges.org/
* https://despot.mozilla.org/
* http://www.discovershiretoko.org
* http://download-cdnetworks.mozilla.net/
* http://download-speed-test.mozilla.net/
* http://dromaeo.com/
* http://eklentiler.mozillazine-tr.org
* http://extendfirefox.com/
* http://filer.mozilladanmark.dk/
* http://virtualpark.mozilla.org/

== Mozilla Japan ==

The Mozilla Japan team will shutdown and archive the following inactive sites during this <strike>Q3 2011</strike>:

* [http://www.firefoxccstudio.org firefoxccstudio.org] - Firefox CC Studio
* [http://www.firefoxfestival.com firefoxfestival.com] - Firefox ROCK FESTIVAL '07 Supported by mF247
* [http://www.mozilla24.com mozilla24.com] - Mozilla 24

= Websites in Process of Retirement =

* [http://doctor.mozilla.org doctor.mozilla.org]
** Bug:

* [http://events.mozilla-europe.org/ events.mozilla-europe.org]
** Bug: -

* [http://spark.mozilla.org spark.mozilla.org] - Spark
** {{bug|636785}}

* [http://userpanel.mozilla.com userpanel.mozilla.com]
** Bug: -

* [http://webtools.mozilla.org webtools.mozilla.org]
** Bug: -

= Retired Websites =

* [http://guides.mozilla.org guides.mozilla.org]
** Status: COMPLETED
** Decision: Retire, point to WikiMO
** Retirement Date: 2012-01-04
** {{bug|663711}} and {{bug|663712}}

Websites/Taskforce/Proposals/Abandoned Sites/2011

2012-02-28T20:14:42Z

Nuss: bespin.mozillalabs.com retired

[[Category:Webdev/Taskforce/Abandoned Sites|2011]]

The following is a list of websites that have been nominated for retirement, have been retired or are in the process of being retired.

= Meetings =
* [[Websites/Taskforce/Proposals/Abandoned_Sites/Meetings/2011-09-28|2011-09-28]]
* [[Websites/Taskforce/Proposals/Abandoned_Sites/Meetings/2011-06-09|2011-06-09]]

= Nominated Sites =

* http://ankeena.mozilla.org/
* http://artzilla.org/
* http://bb.mozillazine-tr.org/
* http://build-graphs.mozilla.org/ (Laura to check into it)
* http://build.mozillamessaging.com/
* http://designchallenges.org/
* https://despot.mozilla.org/
* http://www.discovershiretoko.org
* http://download-cdnetworks.mozilla.net/
* http://download-speed-test.mozilla.net/
* http://dromaeo.com/
* http://eklentiler.mozillazine-tr.org
* http://extendfirefox.com/
* http://filer.mozilladanmark.dk/
* http://virtualpark.mozilla.org/

== Mozilla Japan ==

The Mozilla Japan team will shutdown and archive the following inactive sites during this Q3 2011:

* [http://www.firefoxccstudio.org firefoxccstudio.org] - Firefox CC Studio
* [http://www.firefoxfestival.com firefoxfestival.com] - Firefox ROCK FESTIVAL '07 Supported by mF247
* [http://www.mozilla24.com mozilla24.com] - Mozilla 24

= Websites in Process of Retirement =

* [http://doctor.mozilla.org doctor.mozilla.org]
** Bug:

* [http://events.mozilla-europe.org/ events.mozilla-europe.org]
** Bug: -

* [http://guides.mozilla.org guides.mozilla.org]
** {{bug|663711}} and {{bug|663712}}

* [http://spark.mozilla.org spark.mozilla.org] - Spark
** {{bug|636785}}

* [http://userpanel.mozilla.com userpanel.mozilla.com]
** Bug: -

* [http://webtools.mozilla.org webtools.mozilla.org]
** Bug: -

= Retired Websites =

* [http://chat.mozillamessaging.com chat.mozillamessaging.com]
** {{bug|664049}}
** Retirement date: 2011-09-23

* [http://ostats.mozilla.com/ ostats.mozilla.com]
** {{bug|664262}}
** Status: COMPLETED
** Retirement date: 2011-08-24

* [http://glow.mozilla.org glow.mozilla.org]
** Status: COMPLETED
** Decision: Retire
** Retirement Date: 2011-06-29
** {{bug|668323}}

* [http://hendrix.mozilla.org hendrix.mozilla.org]
** Status: COMPLETED
** Decision: Retire and redirect to input.mozilla.com
** Redirement date: 2011-05-18
** {{bug|622621}}
** See Gerv's [http://weblogs.mozillazine.org/gerv/archives/2010/12/goodbye_hendrix.html blog post] for more

* [http://fashionyourfirefox.com fashionyourfirefox.com] - Fashion your Firefox
** Status: COMPLETED
** Decision: Retire
** Retirement Date: Q1 2011
** {{bug|618366}}

* [http://firefoxlive.mozilla.org/ firefoxlive.mozilla.org] - Firefox Live
** Status: COMPLETED
** Decision: Retire
** Retirement Date: 2011-04-14
** {{bug|644775}}

* [http://irc.mozilla.org irc.mozilla.org]
** Status: COMPLETED
** Decision: Retire; publish as wiki
** Bug: {{bug|650460}}

* [http://www.spreadfirefox.com/ spreadfirefox.com] - Spread Firefox
** Status: COMPLETED
** Decision: Retire
** {{bug|633650}}

* [http://survey.mozilla.com survey.mozilla.com] - Uninstall Survey
** Status: COMPLETED
** Decision: Archive
** {{bug|614475}}

* [http://surveys.mozilla.org surveys.mozilla.org] - Community Surveys
** Status: COMPLETED
** Decision: Retire
** {{bug|615557}}

* [http://firefoxflicks.com/ firefoxflicks.com] - Firefox Flicks
** Status: COMPLETED
** Decision: Retire
** Retirement Date: Dec, 2011
** Bug: {{bug|667719}}

* [http://markup.mozilla.org markup.mozilla.org] - Markup
** Status: COMPLETED
** Decision: Archive
** Retirement Date: 2011-10-10
** {{bug|636781}}

* [http://www.webifyme.org webifyme.org]
** Status: COMPLETED
** Decision: Archive
** Retirement Date: 2011-11-15
** {{bug|641133}}?

* [http://www.webowonder.com/ webowonder.com], [http://demos.mozilla.org/ demos.mozilla.org] - WebOWonder
** Status: COMPLETED
** Decision: Retire, redorect to MDN
** Retirement Date: Q4 2011
** {{bug|642340}}

* [http://banners.mozilla-europe.org banners.mozilla-europe.org]
** Status: COMPLETED
** Decision Retire, redirect to mozilla.org/firefox
** Retirement Date: 2011-12-07
** {{bug|691378}}

* [http://bespin.mozillalabs.com/ bespin.mozillalabs.com]
** Status: COMPLETED
** Decision Retire, redirect to blog post
** Retirement Date: Sept, 2011
** {{bug|692813}}

Websites/Taskforce/Proposals/Abandoned Sites/2012

2012-02-28T20:09:39Z

Nuss: /* Nominated Sites */

[[Category:Webdev/Taskforce/Abandoned Sites|2012]]

The following is a list of websites that have been nominated for retirement, have been retired or are in the process of being retired.

= Meetings =

= Nominated Sites =

* http://ankeena.mozilla.org/
* http://artzilla.org/
* http://bb.mozillazine-tr.org/
* http://bespin.mozillalabs.com/ (get DNS redirected)
* http://build-graphs.mozilla.org/ (Laura to check into it)
* http://build.mozillamessaging.com/
* http://designchallenges.org/
* https://despot.mozilla.org/
* http://www.discovershiretoko.org
* http://download-cdnetworks.mozilla.net/
* http://download-speed-test.mozilla.net/
* http://dromaeo.com/
* http://eklentiler.mozillazine-tr.org
* http://extendfirefox.com/
* http://filer.mozilladanmark.dk/
* http://virtualpark.mozilla.org/

== Mozilla Japan ==

The Mozilla Japan team will shutdown and archive the following inactive sites during this <strike>Q3 2011</strike>:

* [http://www.firefoxccstudio.org firefoxccstudio.org] - Firefox CC Studio
* [http://www.firefoxfestival.com firefoxfestival.com] - Firefox ROCK FESTIVAL '07 Supported by mF247
* [http://www.mozilla24.com mozilla24.com] - Mozilla 24

= Websites in Process of Retirement =

* [http://doctor.mozilla.org doctor.mozilla.org]
** Bug:

* [http://events.mozilla-europe.org/ events.mozilla-europe.org]
** Bug: -

* [http://spark.mozilla.org spark.mozilla.org] - Spark
** {{bug|636785}}

* [http://userpanel.mozilla.com userpanel.mozilla.com]
** Bug: -

* [http://webtools.mozilla.org webtools.mozilla.org]
** Bug: -

= Retired Websites =

* [http://guides.mozilla.org guides.mozilla.org]
** Status: COMPLETED
** Decision: Retire, point to WikiMO
** Retirement Date: 2012-01-04
** {{bug|663711}} and {{bug|663712}}

Websites/Taskforce/Proposals/Abandoned Sites/2011

2012-02-28T20:09:10Z

Nuss: /* Nominated Sites */

[[Category:Webdev/Taskforce/Abandoned Sites|2011]]

The following is a list of websites that have been nominated for retirement, have been retired or are in the process of being retired.

= Meetings =
* [[Websites/Taskforce/Proposals/Abandoned_Sites/Meetings/2011-09-28|2011-09-28]]
* [[Websites/Taskforce/Proposals/Abandoned_Sites/Meetings/2011-06-09|2011-06-09]]

= Nominated Sites =

* http://ankeena.mozilla.org/
* http://artzilla.org/
* http://bb.mozillazine-tr.org/
* http://bespin.mozillalabs.com/ (get DNS redirected)
* http://build-graphs.mozilla.org/ (Laura to check into it)
* http://build.mozillamessaging.com/
* http://designchallenges.org/
* https://despot.mozilla.org/
* http://www.discovershiretoko.org
* http://download-cdnetworks.mozilla.net/
* http://download-speed-test.mozilla.net/
* http://dromaeo.com/
* http://eklentiler.mozillazine-tr.org
* http://extendfirefox.com/
* http://filer.mozilladanmark.dk/
* http://virtualpark.mozilla.org/

== Mozilla Japan ==

The Mozilla Japan team will shutdown and archive the following inactive sites during this Q3 2011:

* [http://www.firefoxccstudio.org firefoxccstudio.org] - Firefox CC Studio
* [http://www.firefoxfestival.com firefoxfestival.com] - Firefox ROCK FESTIVAL '07 Supported by mF247
* [http://www.mozilla24.com mozilla24.com] - Mozilla 24

= Websites in Process of Retirement =

* [http://doctor.mozilla.org doctor.mozilla.org]
** Bug:

* [http://events.mozilla-europe.org/ events.mozilla-europe.org]
** Bug: -

* [http://guides.mozilla.org guides.mozilla.org]
** {{bug|663711}} and {{bug|663712}}

* [http://spark.mozilla.org spark.mozilla.org] - Spark
** {{bug|636785}}

* [http://userpanel.mozilla.com userpanel.mozilla.com]
** Bug: -

* [http://webtools.mozilla.org webtools.mozilla.org]
** Bug: -

= Retired Websites =

* [http://chat.mozillamessaging.com chat.mozillamessaging.com]
** {{bug|664049}}
** Retirement date: 2011-09-23

* [http://ostats.mozilla.com/ ostats.mozilla.com]
** {{bug|664262}}
** Status: COMPLETED
** Retirement date: 2011-08-24

* [http://glow.mozilla.org glow.mozilla.org]
** Status: COMPLETED
** Decision: Retire
** Retirement Date: 2011-06-29
** {{bug|668323}}

* [http://hendrix.mozilla.org hendrix.mozilla.org]
** Status: COMPLETED
** Decision: Retire and redirect to input.mozilla.com
** Redirement date: 2011-05-18
** {{bug|622621}}
** See Gerv's [http://weblogs.mozillazine.org/gerv/archives/2010/12/goodbye_hendrix.html blog post] for more

* [http://fashionyourfirefox.com fashionyourfirefox.com] - Fashion your Firefox
** Status: COMPLETED
** Decision: Retire
** Retirement Date: Q1 2011
** {{bug|618366}}

* [http://firefoxlive.mozilla.org/ firefoxlive.mozilla.org] - Firefox Live
** Status: COMPLETED
** Decision: Retire
** Retirement Date: 2011-04-14
** {{bug|644775}}

* [http://irc.mozilla.org irc.mozilla.org]
** Status: COMPLETED
** Decision: Retire; publish as wiki
** Bug: {{bug|650460}}

* [http://www.spreadfirefox.com/ spreadfirefox.com] - Spread Firefox
** Status: COMPLETED
** Decision: Retire
** {{bug|633650}}

* [http://survey.mozilla.com survey.mozilla.com] - Uninstall Survey
** Status: COMPLETED
** Decision: Archive
** {{bug|614475}}

* [http://surveys.mozilla.org surveys.mozilla.org] - Community Surveys
** Status: COMPLETED
** Decision: Retire
** {{bug|615557}}

* [http://firefoxflicks.com/ firefoxflicks.com] - Firefox Flicks
** Status: COMPLETED
** Decision: Retire
** Retirement Date: Dec, 2011
** Bug: {{bug|667719}}

* [http://markup.mozilla.org markup.mozilla.org] - Markup
** Status: COMPLETED
** Decision: Archive
** Retirement Date: 2011-10-10
** {{bug|636781}}

* [http://www.webifyme.org webifyme.org]
** Status: COMPLETED
** Decision: Archive
** Retirement Date: 2011-11-15
** {{bug|641133}}?

* [http://www.webowonder.com/ webowonder.com], [http://demos.mozilla.org/ demos.mozilla.org] - WebOWonder
** Status: COMPLETED
** Decision: Retire, redorect to MDN
** Retirement Date: Q4 2011
** {{bug|642340}}

* [http://banners.mozilla-europe.org banners.mozilla-europe.org]
** Status: COMPLETED
** Decision Retire, redirect to mozilla.org/firefox
** Retirement Date: 2011-12-07
** {{bug|691378}}

Websites/Taskforce/Proposals/Abandoned Sites/2011

2012-02-28T20:08:28Z

Nuss: /* Nominated Sites */

[[Category:Webdev/Taskforce/Abandoned Sites|2011]]

The following is a list of websites that have been nominated for retirement, have been retired or are in the process of being retired.

= Meetings =
* [[Websites/Taskforce/Proposals/Abandoned_Sites/Meetings/2011-09-28|2011-09-28]]
* [[Websites/Taskforce/Proposals/Abandoned_Sites/Meetings/2011-06-09|2011-06-09]]

= Nominated Sites =

* http://ankeena.mozilla.org/
* http://artzilla.org/
* http://bb.mozillazine-tr.org/
* http://bespin.mozillalabs.com/ (get DNS redirected)
* http://build-graphs.mozilla.org/ (Laura to check into it)
* http://build.mozillamessaging.com/
* http://designchallenges.org/
* https://despot.mozilla.org/
* http://www.discovershiretoko.org
* http://download-cdnetworks.mozilla.net/
* http://download-speed-test.mozilla.net/
* http://dromaeo.com/
* http://eklentiler.mozillazine-tr.org
* http://events.mozilla-europe.org/
* http://extendfirefox.com/
* http://filer.mozilladanmark.dk/
* http://virtualpark.mozilla.org/

== Mozilla Japan ==

The Mozilla Japan team will shutdown and archive the following inactive sites during this Q3 2011:

* [http://www.firefoxccstudio.org firefoxccstudio.org] - Firefox CC Studio
* [http://www.firefoxfestival.com firefoxfestival.com] - Firefox ROCK FESTIVAL '07 Supported by mF247
* [http://www.mozilla24.com mozilla24.com] - Mozilla 24

= Websites in Process of Retirement =

* [http://doctor.mozilla.org doctor.mozilla.org]
** Bug:

* [http://events.mozilla-europe.org/ events.mozilla-europe.org]
** Bug: -

* [http://guides.mozilla.org guides.mozilla.org]
** {{bug|663711}} and {{bug|663712}}

* [http://spark.mozilla.org spark.mozilla.org] - Spark
** {{bug|636785}}

* [http://userpanel.mozilla.com userpanel.mozilla.com]
** Bug: -

* [http://webtools.mozilla.org webtools.mozilla.org]
** Bug: -

= Retired Websites =

* [http://chat.mozillamessaging.com chat.mozillamessaging.com]
** {{bug|664049}}
** Retirement date: 2011-09-23

* [http://ostats.mozilla.com/ ostats.mozilla.com]
** {{bug|664262}}
** Status: COMPLETED
** Retirement date: 2011-08-24

* [http://glow.mozilla.org glow.mozilla.org]
** Status: COMPLETED
** Decision: Retire
** Retirement Date: 2011-06-29
** {{bug|668323}}

* [http://hendrix.mozilla.org hendrix.mozilla.org]
** Status: COMPLETED
** Decision: Retire and redirect to input.mozilla.com
** Redirement date: 2011-05-18
** {{bug|622621}}
** See Gerv's [http://weblogs.mozillazine.org/gerv/archives/2010/12/goodbye_hendrix.html blog post] for more

* [http://fashionyourfirefox.com fashionyourfirefox.com] - Fashion your Firefox
** Status: COMPLETED
** Decision: Retire
** Retirement Date: Q1 2011
** {{bug|618366}}

* [http://firefoxlive.mozilla.org/ firefoxlive.mozilla.org] - Firefox Live
** Status: COMPLETED
** Decision: Retire
** Retirement Date: 2011-04-14
** {{bug|644775}}

* [http://irc.mozilla.org irc.mozilla.org]
** Status: COMPLETED
** Decision: Retire; publish as wiki
** Bug: {{bug|650460}}

* [http://www.spreadfirefox.com/ spreadfirefox.com] - Spread Firefox
** Status: COMPLETED
** Decision: Retire
** {{bug|633650}}

* [http://survey.mozilla.com survey.mozilla.com] - Uninstall Survey
** Status: COMPLETED
** Decision: Archive
** {{bug|614475}}

* [http://surveys.mozilla.org surveys.mozilla.org] - Community Surveys
** Status: COMPLETED
** Decision: Retire
** {{bug|615557}}

* [http://firefoxflicks.com/ firefoxflicks.com] - Firefox Flicks
** Status: COMPLETED
** Decision: Retire
** Retirement Date: Dec, 2011
** Bug: {{bug|667719}}

* [http://markup.mozilla.org markup.mozilla.org] - Markup
** Status: COMPLETED
** Decision: Archive
** Retirement Date: 2011-10-10
** {{bug|636781}}

* [http://www.webifyme.org webifyme.org]
** Status: COMPLETED
** Decision: Archive
** Retirement Date: 2011-11-15
** {{bug|641133}}?

* [http://www.webowonder.com/ webowonder.com], [http://demos.mozilla.org/ demos.mozilla.org] - WebOWonder
** Status: COMPLETED
** Decision: Retire, redorect to MDN
** Retirement Date: Q4 2011
** {{bug|642340}}

* [http://banners.mozilla-europe.org banners.mozilla-europe.org]
** Status: COMPLETED
** Decision Retire, redirect to mozilla.org/firefox
** Retirement Date: 2011-12-07
** {{bug|691378}}

Websites/Taskforce/Proposals/Abandoned Sites/2012

2012-02-28T20:04:29Z

Nuss: /* Mozilla Japan */

[[Category:Webdev/Taskforce/Abandoned Sites|2012]]

The following is a list of websites that have been nominated for retirement, have been retired or are in the process of being retired.

= Meetings =

= Nominated Sites =

* http://ankeena.mozilla.org/
* artzilla.org
* bb.mozillazine-tr.org
* bespin.mozillalabs.com (get DNS redirected)
* http://build-graphs.mozilla.org/ (Laura to check into it)
* http://build.mozillamessaging.com/
* designchallenges.org
* despot.mozilla.org
* http://www.discovershiretoko.org
* http://download-cdnetworks.mozilla.net/
* http://download-speed-test.mozilla.net/
* http://dromaeo.com/
* http://eklentiler.mozillazine-tr.org
* http://events.mozilla-europe.org/
* extendfirefox.com
* http://filer.mozilladanmark.dk/
* http://virtualpark.mozilla.org/

== Mozilla Japan ==

The Mozilla Japan team will shutdown and archive the following inactive sites during this <strike>Q3 2011</strike>:

* [http://www.firefoxccstudio.org firefoxccstudio.org] - Firefox CC Studio
* [http://www.firefoxfestival.com firefoxfestival.com] - Firefox ROCK FESTIVAL '07 Supported by mF247
* [http://www.mozilla24.com mozilla24.com] - Mozilla 24

= Websites in Process of Retirement =

* [http://doctor.mozilla.org doctor.mozilla.org]
** Bug:

* [http://events.mozilla-europe.org/ events.mozilla-europe.org]
** Bug: -

* [http://spark.mozilla.org spark.mozilla.org] - Spark
** {{bug|636785}}

* [http://userpanel.mozilla.com userpanel.mozilla.com]
** Bug: -

* [http://webtools.mozilla.org webtools.mozilla.org]
** Bug: -

= Retired Websites =

* [http://guides.mozilla.org guides.mozilla.org]
** Status: COMPLETED
** Decision: Retire, point to WikiMO
** Retirement Date: 2012-01-04
** {{bug|663711}} and {{bug|663712}}

Websites/Taskforce/Proposals/Abandoned Sites/2012

2012-02-28T20:04:04Z

Nuss:

[[Category:Webdev/Taskforce/Abandoned Sites|2012]]

The following is a list of websites that have been nominated for retirement, have been retired or are in the process of being retired.

= Meetings =

= Nominated Sites =

* http://ankeena.mozilla.org/
* artzilla.org
* bb.mozillazine-tr.org
* bespin.mozillalabs.com (get DNS redirected)
* http://build-graphs.mozilla.org/ (Laura to check into it)
* http://build.mozillamessaging.com/
* designchallenges.org
* despot.mozilla.org
* http://www.discovershiretoko.org
* http://download-cdnetworks.mozilla.net/
* http://download-speed-test.mozilla.net/
* http://dromaeo.com/
* http://eklentiler.mozillazine-tr.org
* http://events.mozilla-europe.org/
* extendfirefox.com
* http://filer.mozilladanmark.dk/
* http://virtualpark.mozilla.org/

== Mozilla Japan ==

The Mozilla Japan team will shutdown and archive the following inactive sites during this <dash>Q3 2011</dash>:

* [http://www.firefoxccstudio.org firefoxccstudio.org] - Firefox CC Studio
* [http://www.firefoxfestival.com firefoxfestival.com] - Firefox ROCK FESTIVAL '07 Supported by mF247
* [http://www.mozilla24.com mozilla24.com] - Mozilla 24

= Websites in Process of Retirement =

* [http://doctor.mozilla.org doctor.mozilla.org]
** Bug:

* [http://events.mozilla-europe.org/ events.mozilla-europe.org]
** Bug: -

* [http://spark.mozilla.org spark.mozilla.org] - Spark
** {{bug|636785}}

* [http://userpanel.mozilla.com userpanel.mozilla.com]
** Bug: -

* [http://webtools.mozilla.org webtools.mozilla.org]
** Bug: -

= Retired Websites =

* [http://guides.mozilla.org guides.mozilla.org]
** Status: COMPLETED
** Decision: Retire, point to WikiMO
** Retirement Date: 2012-01-04
** {{bug|663711}} and {{bug|663712}}

Websites/Taskforce/Proposals/Abandoned Sites/2011

2012-02-28T20:03:51Z

Nuss: banners.mozilla-europe.org retired

[[Category:Webdev/Taskforce/Abandoned Sites|2011]]

The following is a list of websites that have been nominated for retirement, have been retired or are in the process of being retired.

= Meetings =
* [[Websites/Taskforce/Proposals/Abandoned_Sites/Meetings/2011-09-28|2011-09-28]]
* [[Websites/Taskforce/Proposals/Abandoned_Sites/Meetings/2011-06-09|2011-06-09]]

= Nominated Sites =

* http://ankeena.mozilla.org/
* artzilla.org
* bb.mozillazine-tr.org
* bespin.mozillalabs.com (get DNS redirected)
* http://build-graphs.mozilla.org/ (Laura to check into it)
* http://build.mozillamessaging.com/
* designchallenges.org
* despot.mozilla.org
* http://www.discovershiretoko.org
* http://download-cdnetworks.mozilla.net/
* http://download-speed-test.mozilla.net/
* http://dromaeo.com/
* http://eklentiler.mozillazine-tr.org
* http://events.mozilla-europe.org/
* extendfirefox.com
* http://filer.mozilladanmark.dk/
* http://virtualpark.mozilla.org/

== Mozilla Japan ==

The Mozilla Japan team will shutdown and archive the following inactive sites during this Q3 2011:

* [http://www.firefoxccstudio.org firefoxccstudio.org] - Firefox CC Studio
* [http://www.firefoxfestival.com firefoxfestival.com] - Firefox ROCK FESTIVAL '07 Supported by mF247
* [http://www.mozilla24.com mozilla24.com] - Mozilla 24

= Websites in Process of Retirement =

* [http://doctor.mozilla.org doctor.mozilla.org]
** Bug:

* [http://events.mozilla-europe.org/ events.mozilla-europe.org]
** Bug: -

* [http://guides.mozilla.org guides.mozilla.org]
** {{bug|663711}} and {{bug|663712}}

* [http://spark.mozilla.org spark.mozilla.org] - Spark
** {{bug|636785}}

* [http://userpanel.mozilla.com userpanel.mozilla.com]
** Bug: -

* [http://webtools.mozilla.org webtools.mozilla.org]
** Bug: -

= Retired Websites =

* [http://chat.mozillamessaging.com chat.mozillamessaging.com]
** {{bug|664049}}
** Retirement date: 2011-09-23

* [http://ostats.mozilla.com/ ostats.mozilla.com]
** {{bug|664262}}
** Status: COMPLETED
** Retirement date: 2011-08-24

* [http://glow.mozilla.org glow.mozilla.org]
** Status: COMPLETED
** Decision: Retire
** Retirement Date: 2011-06-29
** {{bug|668323}}

* [http://hendrix.mozilla.org hendrix.mozilla.org]
** Status: COMPLETED
** Decision: Retire and redirect to input.mozilla.com
** Redirement date: 2011-05-18
** {{bug|622621}}
** See Gerv's [http://weblogs.mozillazine.org/gerv/archives/2010/12/goodbye_hendrix.html blog post] for more

* [http://fashionyourfirefox.com fashionyourfirefox.com] - Fashion your Firefox
** Status: COMPLETED
** Decision: Retire
** Retirement Date: Q1 2011
** {{bug|618366}}

* [http://firefoxlive.mozilla.org/ firefoxlive.mozilla.org] - Firefox Live
** Status: COMPLETED
** Decision: Retire
** Retirement Date: 2011-04-14
** {{bug|644775}}

* [http://irc.mozilla.org irc.mozilla.org]
** Status: COMPLETED
** Decision: Retire; publish as wiki
** Bug: {{bug|650460}}

* [http://www.spreadfirefox.com/ spreadfirefox.com] - Spread Firefox
** Status: COMPLETED
** Decision: Retire
** {{bug|633650}}

* [http://survey.mozilla.com survey.mozilla.com] - Uninstall Survey
** Status: COMPLETED
** Decision: Archive
** {{bug|614475}}

* [http://surveys.mozilla.org surveys.mozilla.org] - Community Surveys
** Status: COMPLETED
** Decision: Retire
** {{bug|615557}}

* [http://firefoxflicks.com/ firefoxflicks.com] - Firefox Flicks
** Status: COMPLETED
** Decision: Retire
** Retirement Date: Dec, 2011
** Bug: {{bug|667719}}

* [http://markup.mozilla.org markup.mozilla.org] - Markup
** Status: COMPLETED
** Decision: Archive
** Retirement Date: 2011-10-10
** {{bug|636781}}

* [http://www.webifyme.org webifyme.org]
** Status: COMPLETED
** Decision: Archive
** Retirement Date: 2011-11-15
** {{bug|641133}}?

* [http://www.webowonder.com/ webowonder.com], [http://demos.mozilla.org/ demos.mozilla.org] - WebOWonder
** Status: COMPLETED
** Decision: Retire, redorect to MDN
** Retirement Date: Q4 2011
** {{bug|642340}}

* [http://banners.mozilla-europe.org banners.mozilla-europe.org]
** Status: COMPLETED
** Decision Retire, redirect to mozilla.org/firefox
** Retirement Date: 2011-12-07
** {{bug|691378}}

Websites/Taskforce/Proposals/Abandoned Sites/2012

2012-02-28T19:54:51Z

Nuss:

[[Category:Webdev/Taskforce/Abandoned Sites|2012]]

The following is a list of websites that have been nominated for retirement, have been retired or are in the process of being retired.

= Meetings =

= Nominated Sites =

* http://ankeena.mozilla.org/
* artzilla.org
* http://banners.mozilla-europe.org
* bb.mozillazine-tr.org
* bespin.mozillalabs.com (get DNS redirected)
* http://build-graphs.mozilla.org/ (Laura to check into it)
* http://build.mozillamessaging.com/
* designchallenges.org
* despot.mozilla.org
* http://www.discovershiretoko.org
* http://download-cdnetworks.mozilla.net/
* http://download-speed-test.mozilla.net/
* http://dromaeo.com/
* http://eklentiler.mozillazine-tr.org
* http://events.mozilla-europe.org/
* extendfirefox.com
* http://filer.mozilladanmark.dk/
* http://virtualpark.mozilla.org/

== Mozilla Japan ==

The Mozilla Japan team will shutdown and archive the following inactive sites during this <dash>Q3 2011</dash>:

* [http://www.firefoxccstudio.org firefoxccstudio.org] - Firefox CC Studio
* [http://www.firefoxfestival.com firefoxfestival.com] - Firefox ROCK FESTIVAL '07 Supported by mF247
* [http://www.mozilla24.com mozilla24.com] - Mozilla 24

= Websites in Process of Retirement =

* [http://doctor.mozilla.org doctor.mozilla.org]
** Bug:

* [http://events.mozilla-europe.org/ events.mozilla-europe.org]
** Bug: -

* [http://spark.mozilla.org spark.mozilla.org] - Spark
** {{bug|636785}}

* [http://userpanel.mozilla.com userpanel.mozilla.com]
** Bug: -

* [http://webtools.mozilla.org webtools.mozilla.org]
** Bug: -

= Retired Websites =

* [http://guides.mozilla.org guides.mozilla.org]
** Status: COMPLETED
** Decision: Retire, point to WikiMO
** Retirement Date: 2012-01-04
** {{bug|663711}} and {{bug|663712}}

Websites/Taskforce/Proposals/Abandoned Sites/2011

2012-02-28T19:53:56Z

Nuss: webifyme.org archived

[[Category:Webdev/Taskforce/Abandoned Sites|2011]]

The following is a list of websites that have been nominated for retirement, have been retired or are in the process of being retired.

= Meetings =
* [[Websites/Taskforce/Proposals/Abandoned_Sites/Meetings/2011-09-28|2011-09-28]]
* [[Websites/Taskforce/Proposals/Abandoned_Sites/Meetings/2011-06-09|2011-06-09]]

= Nominated Sites =

* http://ankeena.mozilla.org/
* artzilla.org
* http://banners.mozilla-europe.org
* bb.mozillazine-tr.org
* bespin.mozillalabs.com (get DNS redirected)
* http://build-graphs.mozilla.org/ (Laura to check into it)
* http://build.mozillamessaging.com/
* designchallenges.org
* despot.mozilla.org
* http://www.discovershiretoko.org
* http://download-cdnetworks.mozilla.net/
* http://download-speed-test.mozilla.net/
* http://dromaeo.com/
* http://eklentiler.mozillazine-tr.org
* http://events.mozilla-europe.org/
* extendfirefox.com
* http://filer.mozilladanmark.dk/
* http://virtualpark.mozilla.org/

== Mozilla Japan ==

The Mozilla Japan team will shutdown and archive the following inactive sites during this Q3 2011:

* [http://www.firefoxccstudio.org firefoxccstudio.org] - Firefox CC Studio
* [http://www.firefoxfestival.com firefoxfestival.com] - Firefox ROCK FESTIVAL '07 Supported by mF247
* [http://www.mozilla24.com mozilla24.com] - Mozilla 24

= Websites in Process of Retirement =

* [http://doctor.mozilla.org doctor.mozilla.org]
** Bug:

* [http://events.mozilla-europe.org/ events.mozilla-europe.org]
** Bug: -

* [http://guides.mozilla.org guides.mozilla.org]
** {{bug|663711}} and {{bug|663712}}

* [http://spark.mozilla.org spark.mozilla.org] - Spark
** {{bug|636785}}

* [http://userpanel.mozilla.com userpanel.mozilla.com]
** Bug: -

* [http://webtools.mozilla.org webtools.mozilla.org]
** Bug: -

= Retired Websites =

* [http://chat.mozillamessaging.com chat.mozillamessaging.com]
** {{bug|664049}}
** Retirement date: 2011-09-23

* [http://ostats.mozilla.com/ ostats.mozilla.com]
** {{bug|664262}}
** Status: COMPLETED
** Retirement date: 2011-08-24

* [http://glow.mozilla.org glow.mozilla.org]
** Status: COMPLETED
** Decision: Retire
** Retirement Date: 2011-06-29
** {{bug|668323}}

* [http://hendrix.mozilla.org hendrix.mozilla.org]
** Status: COMPLETED
** Decision; Retire and redirect to input.mozilla.com
** Redirement date: 2011-05-18
** {{bug|622621}}
** See Gerv's [http://weblogs.mozillazine.org/gerv/archives/2010/12/goodbye_hendrix.html blog post] for more

* [http://fashionyourfirefox.com fashionyourfirefox.com] - Fashion your Firefox
** Status: COMPLETED
** Decision: Retire
** Retirement Date: Q1 2011
** {{bug|618366}}

* [http://firefoxlive.mozilla.org/ firefoxlive.mozilla.org] - Firefox Live
** Status: COMPLETED
** Decision: Retire
** Retirement Date: 2011-04-14
** {{bug|644775}}

* [http://irc.mozilla.org irc.mozilla.org]
** Status: COMPLETED
** Decision: Retire; publish as wiki
** Bug: {{bug|650460}}

* [http://www.spreadfirefox.com/ spreadfirefox.com] - Spread Firefox
** Status: COMPLETED
** Decision: Retire
** {{bug|633650}}

* [http://survey.mozilla.com survey.mozilla.com] - Uninstall Survey
** Status: COMPLETED
** Decision: Archive
** {{bug|614475}}

* [http://surveys.mozilla.org surveys.mozilla.org] - Community Surveys
** Status: COMPLETED
** Decision: Retire
** {{bug|615557}}

* [http://firefoxflicks.com/ firefoxflicks.com] - Firefox Flicks
** Status: COMPLETED
** Decision: Retire
** Retirement Date: Dec, 2011
** Bug: {{bug|667719}}

* [http://markup.mozilla.org markup.mozilla.org] - Markup
** Status: COMPLETED
** Decision: Archive
** Retirement Date: 2011-10-10
** {{bug|636781}}

* [http://www.webifyme.org webifyme.org]
** Status: COMPLETED
** Decision: Archive
** Retirement Date: 2011-11-15
** {{bug|641133}}?

* [http://www.webowonder.com/ webowonder.com], [http://demos.mozilla.org/ demos.mozilla.org] - WebOWonder
** Decision: Retire, point to MDN
** Retirement Date: Q4 2011
** {{bug|642340}}

Websites/Taskforce/Proposals/Abandoned Sites/2011

2012-02-28T19:49:59Z

Nuss:

[[Category:Webdev/Taskforce/Abandoned Sites|2011]]

The following is a list of websites that have been nominated for retirement, have been retired or are in the process of being retired.

= Meetings =
* [[Websites/Taskforce/Proposals/Abandoned_Sites/Meetings/2011-09-28|2011-09-28]]
* [[Websites/Taskforce/Proposals/Abandoned_Sites/Meetings/2011-06-09|2011-06-09]]

= Nominated Sites =

* http://ankeena.mozilla.org/
* artzilla.org
* http://banners.mozilla-europe.org
* bb.mozillazine-tr.org
* bespin.mozillalabs.com (get DNS redirected)
* http://build-graphs.mozilla.org/ (Laura to check into it)
* http://build.mozillamessaging.com/
* designchallenges.org
* despot.mozilla.org
* http://www.discovershiretoko.org
* http://download-cdnetworks.mozilla.net/
* http://download-speed-test.mozilla.net/
* http://dromaeo.com/
* http://eklentiler.mozillazine-tr.org
* http://events.mozilla-europe.org/
* extendfirefox.com
* http://filer.mozilladanmark.dk/
* http://virtualpark.mozilla.org/

== Mozilla Japan ==

The Mozilla Japan team will shutdown and archive the following inactive sites during this Q3 2011:

* [http://www.firefoxccstudio.org firefoxccstudio.org] - Firefox CC Studio
* [http://www.firefoxfestival.com firefoxfestival.com] - Firefox ROCK FESTIVAL '07 Supported by mF247
* [http://www.mozilla24.com mozilla24.com] - Mozilla 24

= Websites in Process of Retirement =

* [https://intranet.mozilla.org/Firefox4All Webify Me]
** Estimated Date: Q3 2011
** {{bug|641133}}

* [http://doctor.mozilla.org doctor.mozilla.org]
** Bug:

* [http://events.mozilla-europe.org/ events.mozilla-europe.org]
** Bug: -

* [http://guides.mozilla.org guides.mozilla.org]
** {{bug|663711}} and {{bug|663712}}

* [http://spark.mozilla.org spark.mozilla.org] - Spark
** {{bug|636785}}

* [http://userpanel.mozilla.com userpanel.mozilla.com]
** Bug: -

* [http://webtools.mozilla.org webtools.mozilla.org]
** Bug: -

= Retired Websites =

* [http://chat.mozillamessaging.com chat.mozillamessaging.com]
** {{bug|664049}}
** Retirement date: 2011-09-23

* [http://ostats.mozilla.com/ ostats.mozilla.com]
** {{bug|664262}}
** Status: COMPLETED
** Retirement date: 2011-08-24

* [http://glow.mozilla.org glow.mozilla.org]
** Status: COMPLETED
** Decision: Retire
** Retirement Date: 2011-06-29
** {{bug|668323}}

* [http://hendrix.mozilla.org hendrix.mozilla.org]
** Status: COMPLETED
** Decision; Retire and redirect to input.mozilla.com
** Redirement date: 2011-05-18
** {{bug|622621}}
** See Gerv's [http://weblogs.mozillazine.org/gerv/archives/2010/12/goodbye_hendrix.html blog post] for more

* [http://fashionyourfirefox.com fashionyourfirefox.com] - Fashion your Firefox
** Status: COMPLETED
** Decision: Retire
** Retirement Date: Q1 2011
** {{bug|618366}}

* [http://firefoxlive.mozilla.org/ firefoxlive.mozilla.org] - Firefox Live
** Status: COMPLETED
** Decision: Retire
** Retirement Date: 2011-04-14
** {{bug|644775}}

* [http://irc.mozilla.org irc.mozilla.org]
** Status: COMPLETED
** Decision: Retire; publish as wiki
** Bug: {{bug|650460}}

* [http://www.spreadfirefox.com/ spreadfirefox.com] - Spread Firefox
** Status: COMPLETED
** Decision: Retire
** {{bug|633650}}

* [http://survey.mozilla.com survey.mozilla.com] - Uninstall Survey
** Status: COMPLETED
** Decision: Archive
** {{bug|614475}}

* [http://surveys.mozilla.org surveys.mozilla.org] - Community Surveys
** Status: COMPLETED
** Decision: Retire
** {{bug|615557}}

* [http://firefoxflicks.com/ firefoxflicks.com] - Firefox Flicks
** Status: COMPLETED
** Decision: Retire
** Retirement Date: Dec, 2011
** Bug: {{bug|667719}}

* [http://markup.mozilla.org markup.mozilla.org] - Markup
** Status: COMPLETED
** Decision: Archive
** Retirement Date: 2011-10-10
** {{bug|636781}}

* [http://www.webowonder.com/ www.webowonder.com], [http://demos.mozilla.org/ demos.mozilla.org] - WebOWonder
** Decision: Retire, point to MDN
** Retirement Date: Q4 2011
** {{bug|642340}}

Websites/Taskforce/Proposals/Abandoned Sites/2012

2012-02-28T19:49:19Z

Nuss: Created page with "2012 The following is a list of websites that have been nominated for retirement, have been retired or are in the process of being ..."

[[Category:Webdev/Taskforce/Abandoned Sites|2012]]

The following is a list of websites that have been nominated for retirement, have been retired or are in the process of being retired.

= Meetings =

= Nominated Sites =

* http://ankeena.mozilla.org/
* artzilla.org
* http://banners.mozilla-europe.org
* bb.mozillazine-tr.org
* bespin.mozillalabs.com (get DNS redirected)
* http://build-graphs.mozilla.org/ (Laura to check into it)
* http://build.mozillamessaging.com/
* designchallenges.org
* despot.mozilla.org
* http://www.discovershiretoko.org
* http://download-cdnetworks.mozilla.net/
* http://download-speed-test.mozilla.net/
* http://dromaeo.com/
* http://eklentiler.mozillazine-tr.org
* http://events.mozilla-europe.org/
* extendfirefox.com
* http://filer.mozilladanmark.dk/
* http://virtualpark.mozilla.org/

== Mozilla Japan ==

The Mozilla Japan team will shutdown and archive the following inactive sites during this <dash>Q3 2011</dash>:

* [http://www.firefoxccstudio.org firefoxccstudio.org] - Firefox CC Studio
* [http://www.firefoxfestival.com firefoxfestival.com] - Firefox ROCK FESTIVAL '07 Supported by mF247
* [http://www.mozilla24.com mozilla24.com] - Mozilla 24

= Websites in Process of Retirement =

* [https://intranet.mozilla.org/Firefox4All Webify Me]
** Estimated Date: Q3 2011
** {{bug|641133}}

* [http://doctor.mozilla.org doctor.mozilla.org]
** Bug:

* [http://events.mozilla-europe.org/ events.mozilla-europe.org]
** Bug: -

* [http://guides.mozilla.org guides.mozilla.org]
** {{bug|663711}} and {{bug|663712}}

* [http://spark.mozilla.org spark.mozilla.org] - Spark
** {{bug|636785}}

* [http://userpanel.mozilla.com userpanel.mozilla.com]
** Bug: -

* [http://webtools.mozilla.org webtools.mozilla.org]
** Bug: -

= Retired Websites =

* [http://guides.mozilla.org guides.mozilla.org]
** Decision: Retire, point to WikiMO
** Retirement Date: 2012-01-04
** {{bug|663711}} and {{bug|663712}}

Websites/Taskforce/Proposals/Abandoned Sites

2012-02-28T19:44:50Z

Nuss: /* Retired Websites */ Added 2012

[[Category:Webdev|Abandoned Sites]]
[[Category:Webdev/Taskforce|Abandoned Sites]]
[[Category:Webdev/Taskforce/Proposals|Abandoned Sites]]
'''Abandoned Sites'''

= Working Group =

Chris More, Frederic Wenzel, Mike Morgan, Chris Lyon, Steve Curbishley, David Boswell and Alex Fowler

= Status =

Accepted Proposal

= Problem =

There are a number of Mozilla sites that are still online but are no longer active or up to date. These sites can make it hard to find more current information and can also create security or privacy concerns when there is functionality that is no longer being maintained or is no longer needed.

Note that this policy deals with abandoned sites and does not touch on abandoned content within otherwise active sites.

= Solution =

To be able to keep the content on our sites up to date and relevant we need a way to archive or turn off abandoned sites.

== Archiving or Turning Off Sites ==

For sites that are no longer active, we propose either archiving them or turning them off. To define these terms more clearly:

Archiving a site involves scraping the content, moving it to a read-only archive site, adding a note about the content being out of date to the top of the pages and setting up redirects (for example, if http://mozillaservice.org was archived someone going to that URL would be taken to http://website-archive.mozilla.org/mozillaservice.org/).

Turning off a site simply involves taking it down from Mozilla's web servers. If there are relevant links, redirects could be set up (for instance, pointing traffic to a blog post about why the site was taken down).

We propose the following steps for determining how to identify abandoned sites and what the best course of action is in a given situation.

=== Identifying Abandoned Sites ===

Because of Mozilla's decentralized structure, there is no easy way to get a list of all sites and their current status. Unless someone comes up with a better way of finding sites and determining their level of activity, we'll just need to manually maintain a site list.

Currently the [http://www.mozilla.org/community/directory.html Community Directory] is the most complete reference we know of. To add new sites to this list, to suggest a site be removed or to propose that a site be moved into the Archive section, please [https://bugzilla.mozilla.org/enter_bug.cgi?product=Websites&component=www.mozilla.org open a www.mozilla.org bug].

=== Processes ===

Once a site has been identified as a candidate for archiving or deletion, the following steps should be followed:

* A bug should be filed in [https://bugzilla.mozilla.org/enter_bug.cgi?product=Websites&component=website-archive.mozilla.org Bugzilla] using the website-archive.mozilla.org component.

* An attempt to identify the owner of the site should be made to confirm the site is no longer active. If no owner can be found, the websites task force will make a decision about the site's status.

* A [http://mxr.mozilla.org/ MXR] search should be performed for the candidate site to ensure that it is not pointed to or used by any of our products. Searches should cover all supported branches of all relevant repositories (mozilla-central, comm-central, mozilla-* and comm-*, labs, chatzilla, etc).

* The Abandoned Sites working group will then take the bug and take the appropriate next steps (closing as wontfix, archiving or turning off site).

=== Guidelines ===

It is important to preserve the community's history, but it is also unnecessary to save every site about Mozilla that's ever existed. To help with the decision making process about what to do with an abandoned site, we offer the following guidelines.

* Is a reasonable alternative version of the content available anywhere else?
** For instance, if all of the firefoxflicks.com videos are on our YouTube channel we could turn off the site and redirect traffic there.

* Is the site a tool used to edit, view or interact with other content?
** For instance, doctor.mozilla.org has no content but allows users to edit content used on CVS-hosted sites and could be turned off.

* Is the site hosted on infrastructure run by the Mozilla Foundation or one of its subsidiaries?
** For instance, a Firefox community site run by a contributor may be archived at our discretion depending on the specific circumstances of that site.

* Are there web analytics for this site?
** For instance, does this site receive a sizeable amount of traffic (e.g. greater than 250 unique visitors per day) that warrants being redirected to an archived copy of the website?

== Implementation ==

The Abandoned Sites working group will meet periodically to discuss the steps for retirement for nominated abandoned sites.

=== Meetings ===

* [[Websites/Taskforce/Proposals/Abandoned_Sites/Meetings/2012-02-01|2012-02-01]]
* [[Websites/Taskforce/Proposals/Abandoned_Sites/Meetings/2011-11-29|2011-11-29]]
* [[Websites/Taskforce/Proposals/Abandoned_Sites/Meetings/2011-09-28|2011-09-28]]
* [[Websites/Taskforce/Proposals/Abandoned_Sites/Meetings/2011-06-09|2011-06-09]]

== Retired Websites ==

* [[Websites/Taskforce/Proposals/Abandoned_Sites/2012|2012 Retired Websites]]
* [[Websites/Taskforce/Proposals/Abandoned_Sites/2011|2011 Retired Websites]]
* [[Websites/Taskforce/Proposals/Abandoned_Sites/2010|2010 Retired Websites]]
* [[Websites/Taskforce/Proposals/Abandoned_Sites/Future|Future Retirements]]

''Note: the items above related to removing a part of a site's functionality are being tracked as part of the archiving process for now, but this really deserves its own policy since these are separate issues.''

=== Process ===

* [[Websites/Taskforce/Proposals/End_of_Life|Document End of Life Strategy Before Launch]]
* [[Websites/Taskforce/Proposals/Abandoned_Sites/Retire|Retire a Website]]
* [[Websites/Taskforce/Proposals/Abandoned_Sites/Archive|Archive a Website]]

Websites/Taskforce/Proposals/Abandoned Sites/2011

2012-02-28T19:42:57Z

Nuss: webowonder.org retired

[[Category:Webdev/Taskforce/Abandoned Sites|2011]]

The following is a list of websites that have been nominated for retirement, have been retired or are in the process of being retired.

= Meetings =
* [[Websites/Taskforce/Proposals/Abandoned_Sites/Meetings/2011-09-28|2011-09-28]]
* [[Websites/Taskforce/Proposals/Abandoned_Sites/Meetings/2011-06-09|2011-06-09]]

= Nominated Sites =

* http://ankeena.mozilla.org/
* artzilla.org
* http://banners.mozilla-europe.org
* bb.mozillazine-tr.org
* bespin.mozillalabs.com (get DNS redirected)
* http://build-graphs.mozilla.org/ (Laura to check into it)
* http://build.mozillamessaging.com/
* designchallenges.org
* despot.mozilla.org
* http://www.discovershiretoko.org
* http://download-cdnetworks.mozilla.net/
* http://download-speed-test.mozilla.net/
* http://dromaeo.com/
* http://eklentiler.mozillazine-tr.org
* http://events.mozilla-europe.org/
* extendfirefox.com
* http://filer.mozilladanmark.dk/
* http://virtualpark.mozilla.org/

== Mozilla Japan ==

The Mozilla Japan team will shutdown and archive the following inactive sites during this Q3 2011:

* [http://www.firefoxccstudio.org firefoxccstudio.org] - Firefox CC Studio
* [http://www.firefoxfestival.com firefoxfestival.com] - Firefox ROCK FESTIVAL '07 Supported by mF247
* [http://www.mozilla24.com mozilla24.com] - Mozilla 24

= Websites in Process of Retirement =

* [https://intranet.mozilla.org/Firefox4All Webify Me]
** Estimated Date: Q3 2011
** {{bug|641133}}

* [http://doctor.mozilla.org doctor.mozilla.org]
** Bug:

* [http://events.mozilla-europe.org/ events.mozilla-europe.org]
** Bug: -

* [http://guides.mozilla.org guides.mozilla.org]
** {{bug|663711}} and {{bug|663712}}

* [http://spark.mozilla.org spark.mozilla.org] - Spark
** {{bug|636785}}

* [http://userpanel.mozilla.com userpanel.mozilla.com]
** Bug: -

* [http://webtools.mozilla.org webtools.mozilla.org]
** Bug: -

= Retired Websites =

* [http://chat.mozillamessaging.com chat.mozillamessaging.com]
** {{bug|664049}}
** Retirement date: 2011-09-23

* [http://ostats.mozilla.com/ ostats.mozilla.com]
** {{bug|664262}}
** Status: COMPLETED
** Retirement date: 2011-08-24

* [http://glow.mozilla.org glow.mozilla.org]
** Status: COMPLETED
** Decision: Retire
** Retirement Date: 2011-06-29
** {{bug|668323}}

* [http://hendrix.mozilla.org hendrix.mozilla.org]
** Status: COMPLETED
** Decision; Retire and redirect to input.mozilla.com
** Redirement date: 2011-05-18
** {{bug|622621}}
** See Gerv's [http://weblogs.mozillazine.org/gerv/archives/2010/12/goodbye_hendrix.html blog post] for more

* [http://fashionyourfirefox.com fashionyourfirefox.com] - Fashion your Firefox
** Status: COMPLETED
** Decision: Retire
** Retirement Date: Q1 2011
** {{bug|618366}}

* [http://firefoxlive.mozilla.org/ firefoxlive.mozilla.org] - Firefox Live
** Status: COMPLETED
** Decision: Retire
** Retirement Date: 2011-04-14
** {{bug|644775}}

* [http://irc.mozilla.org irc.mozilla.org]
** Status: COMPLETED
** Decision: Retire; publish as wiki
** Bug: {{bug|650460}}

* [http://www.spreadfirefox.com/ spreadfirefox.com] - Spread Firefox
** Status: COMPLETED
** Decision: Retire
** {{bug|633650}}

* [http://survey.mozilla.com survey.mozilla.com] - Uninstall Survey
** Status: COMPLETED
** Decision: Archive
** {{bug|614475}}

* [http://surveys.mozilla.org surveys.mozilla.org] - Community Surveys
** Status: COMPLETED
** Decision: Retire
** {{bug|615557}}

* [http://firefoxflicks.com/ firefoxflicks.com] - Firefox Flicks
** Status: COMPLETED
** Decision: Retire
** Retirement Date: Dec, 2011
** Bug: {{bug|667719}}

* [http://markup.mozilla.org markup.mozilla.org] - Markup
** Status: COMPLETED
** Decision: Archive
** Retirement Date: 2011-10-10
** {{bug|636781}}

* [http://www.webowonder.com/ www.webowonder.com], [http://demos.mozilla.org/ demos.mozilla.org] - WebOWonder
** Decision: Retire, point to MDN
** Retirement Date: Q4 2011
** {{bug|642340}}

Websites/Taskforce/Proposals/Abandoned Sites/2011

2012-02-28T19:15:27Z

Nuss: firefoxflicks.com, markup.mozilla.org retired

[[Category:Webdev/Taskforce/Abandoned Sites|2011]]

The following is a list of websites that have been nominated for retirement, have been retired or are in the process of being retired.

= Meetings =
* [[Websites/Taskforce/Proposals/Abandoned_Sites/Meetings/2011-09-28|2011-09-28]]
* [[Websites/Taskforce/Proposals/Abandoned_Sites/Meetings/2011-06-09|2011-06-09]]

= Nominated Sites =

* http://ankeena.mozilla.org/
* artzilla.org
* http://banners.mozilla-europe.org
* bb.mozillazine-tr.org
* bespin.mozillalabs.com (get DNS redirected)
* http://build-graphs.mozilla.org/ (Laura to check into it)
* http://build.mozillamessaging.com/
* designchallenges.org
* despot.mozilla.org
* http://www.discovershiretoko.org
* http://download-cdnetworks.mozilla.net/
* http://download-speed-test.mozilla.net/
* http://dromaeo.com/
* http://eklentiler.mozillazine-tr.org
* http://events.mozilla-europe.org/
* extendfirefox.com
* http://filer.mozilladanmark.dk/
* http://virtualpark.mozilla.org/

== Mozilla Japan ==

The Mozilla Japan team will shutdown and archive the following inactive sites during this Q3 2011:

* [http://www.firefoxccstudio.org firefoxccstudio.org] - Firefox CC Studio
* [http://www.firefoxfestival.com firefoxfestival.com] - Firefox ROCK FESTIVAL '07 Supported by mF247
* [http://www.mozilla24.com mozilla24.com] - Mozilla 24

= Websites in Process of Retirement =

* [https://intranet.mozilla.org/Firefox4All Webify Me]
** Estimated Date: Q3 2011
** {{bug|641133}}

* [http://doctor.mozilla.org doctor.mozilla.org]
** Bug:

* [http://events.mozilla-europe.org/ events.mozilla-europe.org]
** Bug: -

* [http://guides.mozilla.org guides.mozilla.org]
** {{bug|663711}} and {{bug|663712}}

* [http://spark.mozilla.org spark.mozilla.org] - Spark
** {{bug|636785}}

* [http://userpanel.mozilla.com userpanel.mozilla.com]
** Bug: -

* [https://wiki.mozilla.org/Websites/WebOWonder Web of Wonder]
** {{bug|642340}}

* [http://webtools.mozilla.org webtools.mozilla.org]
** Bug: -

= Retired Websites =

* [http://chat.mozillamessaging.com chat.mozillamessaging.com]
** {{bug|664049}}
** Retirement date: 2011-09-23

* [http://ostats.mozilla.com/ ostats.mozilla.com]
** {{bug|664262}}
** Status: COMPLETED
** Retirement date: 2011-08-24

* [http://glow.mozilla.org glow.mozilla.org]
** Status: COMPLETED
** Decision: Retire
** Retirement Date: 2011-06-29
** {{bug|668323}}

* [http://hendrix.mozilla.org hendrix.mozilla.org]
** Status: COMPLETED
** Decision; Retire and redirect to input.mozilla.com
** Redirement date: 2011-05-18
** {{bug|622621}}
** See Gerv's [http://weblogs.mozillazine.org/gerv/archives/2010/12/goodbye_hendrix.html blog post] for more

* [http://fashionyourfirefox.com fashionyourfirefox.com] - Fashion your Firefox
** Status: COMPLETED
** Decision: Retire
** Retirement Date: Q1 2011
** {{bug|618366}}

* [http://firefoxlive.mozilla.org/ firefoxlive.mozilla.org] - Firefox Live
** Status: COMPLETED
** Decision: Retire
** Retirement Date: 2011-04-14
** {{bug|644775}}

* [http://irc.mozilla.org irc.mozilla.org]
** Status: COMPLETED
** Decision: Retire; publish as wiki
** Bug: {{bug|650460}}

* [http://www.spreadfirefox.com/ spreadfirefox.com] - Spread Firefox
** Status: COMPLETED
** Decision: Retire
** {{bug|633650}}

* [http://survey.mozilla.com survey.mozilla.com] - Uninstall Survey
** Status: COMPLETED
** Decision: Archive
** {{bug|614475}}

* [http://surveys.mozilla.org surveys.mozilla.org] - Community Surveys
** Status: COMPLETED
** Decision: Retire
** {{bug|615557}}

* [http://firefoxflicks.com/ firefoxflicks.com] - Firefox Flicks
** Status: COMPLETED
** Decision: Retire
** Retirement Date: Dec, 2011
** Bug: {{bug|667719}}

* [http://markup.mozilla.org markup.mozilla.org] - Markup
** Status: COMPLETED
** Decision: Archive
** Retirement Date: 2011-10-10
** {{bug|636781}}

Websites/Taskforce/Proposals/Domain Name Strategy

2012-02-17T21:37:37Z

Nuss: /* mozilla.com domains to switch */ Etherpad has moved

'''Domain Name Strategy'''

If you have any questions about how this document applies to any work you are doing or if you have feedback or comments or need clarification, please contact david at mozillafoundation dot org and jslater at mozilla dot com.

''This strategy applies only to websites and does not intend to cover anything to do with email addresses.''

=Working Group=

John Slater, Janet Swisher, Laura Forrest and David Boswell

=Status=

This proposal was approved at the [[Websites/Taskforce/2010_10_21|10/21/10 task force meeting]].

=Problem=

We are currently using our organizational structure as a way to set up domain
names and this is presenting irrelevant information to people and diverting our
message away from more important things, such as what we do and why we do it.

For example, the following are some of the organizational domains currently in
use:

* mozilla.com

* mozillamessaging.com

* mozilla-europe.org*

* mozillaonline.com*

* mozilla.jp*

Note that mozilla.org is not an organizational domain -- it is the community's
domain that was set up and used long before there was any Mozilla organization.
It isn't the Foundation's organizational domain -- that is mozillafoundation.org
that was in use briefly but has been retired.

''*Affiliate URLs act as both an organization site and a local site, so there is no need to move away from using those domains. The more important issue with affiliate sites is making the content as relevant as possible by de-emphasizing the organizational information and highlighting the locale specific information.''

=Solution=

To be able to stop using organizations as a basis for our domain name
strategy, we need to develop an alternative that uses something else for its structure. There seem to be two main options:

* Structure a strategy based on product/activity: firefox.com, thunderbird.com, drumbeat.org, etc.

* Structure a strategy based on everything being a part of Mozilla: www.mozilla.org, addons.mozilla.org, foo.mozilla.org

Both options have advantages and disadvantages, but they are mutually exclusive so we need to pick one (although we can certainly maintain redirects for any URLs we want).

=="One Mozilla" Strategy==

To create a "One Mozilla" strategy for domain names, we propose using sub-domains for functional areas and sub-directories for products and programs (programs in the initiative sense) with some exceptions. So:

* service.mozilla.org/sub-category

The following breaks out how this general rule applies to different types of sites.

===Product and Program Sites===

Sites related to the major activities backed by Mozilla organizations should use sub-directories on www.mozilla.org. The service being offered here is delivery of web pages (compared with delivery of a web app providing specific functionality).

Examples:

* www.mozilla.org/firefox

* www.mozilla.org/thunderbird

* www.mozilla.org/drumbeat

Note: Other community-backed projects such as seamonkey-project.org can show affiliation with Mozilla on their site in a number of other ways without having to change their URL structure.

===Web Application Sites===

Sites that exist to host services should have sub-domains based on the service offered and sub-directories based on products or programs. This is the existing addons.mozilla.org model.

Examples:

* addons.mozilla.org/firefox, addons.mozilla.org/mobile, addons.mozilla.org/thunderbird, etc.

* support.mozilla.org/firefox, support.mozilla.org/mobile, support.mozilla.org/thunderbird, etc.

* nightly.mozilla.org/firefox, nightly.mozilla.org/mobile, nightly.mozilla.org/thunderbird, etc.

For sites that provide a service for the community as a whole and not for specific programs or products, there is no need to divide things by sub-directory.

Examples:

* air.mozilla.org

* developer.mozilla.org

* feeds.mozilla.org

===Campaign Sites===

Mini-sites set up for a specific campaign should be able to use whatever URL makes sense. Because these sites are usually relevant to a specific time, an archiving plan should be put in place so this content isn't abandoned.

Examples:

* firefoxflicks.com

* opentochoice.org

* operationfirefox.com

===Local Sites===

There are two main URL styles being used today by local sites.

Examples:

* mozilla.country: mozilla.jp, mozilla.ro, etc.

* mozilla-country.org: mozilla-mexico.org, mozilla-russia.org, etc.

There are also a variety of other URLs in use such as bgzilla.org and mozilla.org.ua. It may make sense to make these more consistent, but there is no plan to do that now. On the other hand, having flexibility with local site URLs allows us to deal with issues relevant to different locales.

===Mobile Sites===

Ideally each site would have one URL which would present its content in a form optimized for any device. For complex sites though, the functionality available on mobile versions may differ greatly and switching style sheets alone may not be sufficient.

When it isn't possible to maintain a single URL for a site, we recommend adding a "m." at the beginning of the domain, such as

* m.foo.mozilla.org.

In the cases when we do choose to go with separate mobile URLs, once we take the time to do things the ideal way we can just redirect mobile URLs to their desktop equivalents for a seamless transition.

===Other Sites===

Mozilla is a big community with many people doing many things and there's no benefit to making every site fit in some structure. It is fine for some sites to have unique URLs as long as they avoid organization specific domains or trademark violations.

Examples of sites with unique URLs that are fine:

* accessfirefox.org

* geckozone.org

* mozillamemory.org

==Proposed URL Changes==

Using the principles of the "One Mozilla" strategy, we suggest the following URL changes (this is just an initial batch and not comprehensive of all possible URL changes).

{| border="1px" cellspacing="0px"
! Existing URL !! Proposed URL !! Comment
|-
| mozilla.com || www.mozilla.org/firefox ||
|-
| mozillamessaging.com || www.mozilla.org/thunderbird ||
|-
| support.mozilla.com || support.mozilla.org ||
|-
| mobile.support.mozilla.com || support.mozilla.org/mobile ||
|-
| support.mozillamessaging.com || support.mozilla.org/thunderbird ||
|-
| air.mozilla.com || air.mozilla.org ||
|-
| feeds.mozilla.com || feeds.mozilla.org ||
|-
| input.mozilla.com || input.mozilla.org ||
|}

== Technical Considerations ==

=== Localization ===

The best practices around how to use locale codes in URLs shouldn't need to be changed due to this proposal. Sites can still use the following scheme (with the example here of Mozilla Europe's German Firefox page):

* www.mozilla-europe.org/de/firefox/

The bigger issue with the l10n process is how will this proposal change how localizers determine what to work on? If sites are aggregated into fewer domains will more content need to be localized or would we create less cohesive experiences with partially localized sites?

=== Security ===

Moving from multiple unique domains to subdomains of a single domain, and in some cases subdirectories within that subdomain, will require changes to the security requirements that are imposed upon these websites. Specifically, all websites that are grouped within the same subdomain will be subject to the highest security requirements of any site within that subdomain.

In some cases this may mean that a site that was previously not hosting or performing critical operations, and thus had more lenient security controls, would be required to significantly enhance the security controls before it could be added as a subdirectory of a more security restrictive subdomain.

In addition, depending upon the criticality of a given group of websites within a subdomain this may result in a more strictly controlled security review process including requirements to review any new code before it is pushed live to the site.

=== Webtrends Tracking ===

From Webtrends - You should be fine changing over from the .com domain to the .org domain, as long as the primary domain designated in the Webtrends JavaScript tag points to what you consider the primary domain. Additionally, if you plan on having both domains concurrently available, you may want to modify the JavaScript tag to include mozilla.com at a value for the this.onsitedoms=""; entry in the JavaScript include. This would then consider all traffic from mozilla.com to be considered part of the traffic on the primary domain and would not prefix entries in reports with "Offsite:"

=== SEO Best Practices ===

SEO Best Practices When Switching Domains

Please take the following into consideration when making these switches to minimize any possible dips in natural search traffic.

Redirect Treatment (Technical Owner)

*The most important thing to avoid is 404 (file not found) errors when searchers click on Mozilla site links that show up on the search engine response page (SERP)
*Use a permanent 301 redirect to redirect the pages on the old site to the new site. This also lets Google know all the pages have officially moved. 
*Change all internal site links to point to the correct domain
*Use link checking software to find any broken links
*Submit a new sitemap to Google Webmaster Tools and Yahoo Site Submit
*Do this in phases if possible, moving one subdirectory over at a time, monitoring the results 

Incoming Links (Business Owner)

*If possible, contact the main owners of our largest incoming traffic and have them change the link (Google Snippets, YouTube, Affiliate Programs, and many more)
*Closely monitor SERP results and incoming organic search traffic for major changes

 

References http://googlewebmastercentral.blogspot.com/2008/04/best-practices-when-moving-your-site.html http://www.clickz.com/clickz/column/1699947/seo-best-practices-when-moving-web-site http://www.seomoz.org/blog/seo-guide-how-to-properly-move-domains 

Also a recent quote from Matt Cutts of Google:  

''When done correctly, a 301 redirect shouldn't cause any drop in traffic, says Matt Cutts, a Google software engineer. He says instead of moving its entire website at once, Evo would have been better off moving the site very slowly, starting with the least-trafficked areas of its website. Changing something like the structure of a site during a move can also cause problems. "If someone changes to a new template, that can affect the rankings," says Cutts. "Sometimes it takes Google a little while to figure out how best to process, index, and rank a page."'' 

And input from Rand Fishkin of SEOmoz on our particular case: 

''On the switch over - I suspect it will be relatively painless, but you might want to do as Google recommends and switch part of the content first, then move over in batches, rather than all at once. You can see Matt Cutts discussing this in an Inc article recently...It's not critical, IMO, but it might save some pain in that "Google's figuring things out" timeframe.'' 

 

 

=== Product Links ===

The following is quoted from [https://bugzilla.mozilla.org/show_bug.cgi?id=606278 bug 606278] as part of a discussion about issues involving switching domains for sites that are linked to from within our products:

Same thing goes for byob.mozilla.com, as I mentioned in bug 607129. Not so much
that it's coded into Fx4, but that the domain name is part of the configuration
distributed with custom browsers.

FWIW, this is not something I see mentioned in the strategy: Existing sites are
linked to by other sites and coded into products / configurations in the wild
(ie. outside our control). Cleanly moving things may not be possible in all
cases, so we'll need some consideration around transitions.

Some sites may need to be served up at both the new and old locations, if only
with a 301 redirect at the legacy URL. However, some URLs may not be amenable
to redirects - ie. sites offering APIs like addons.mozilla.org

It's also possible that there may be some URL namespace collisions where
old/new URLs need to co-exist for an extended period of time. I can't think of
any off the top of my head, though

== Implementation ==

Once we've agreed on the plan we want to roll out these changes incrementally. Doing everything at once would be too big a project and we expect there will be things to learn about the process as we start making changes.

To follow along with the progress of things, see [https://bugzilla.mozilla.org/show_bug.cgi?id=606278 bug 606278]

==== mozilla.com domains to switch ====

The following is the list of mozilla.com domains to switch and the associated bugs.

*<strike>krakenbenchmark.mozilla.com</strike> - [https://bugzilla.mozilla.org/show_bug.cgi?id=613649 bug 613649]

*<strike>feeds.mozilla.com</strike> - [https://bugzilla.mozilla.org/show_bug.cgi?id=613648 bug 613648]

*<strike>air.mozilla.com</strike> - [https://bugzilla.mozilla.org/show_bug.cgi?id=606326 bug 606326]

*<strike>www.mozilla.com</strike> - [https://bugzilla.mozilla.org/show_bug.cgi?id=610724 bug 610724]

*<strike>support.mozilla.com</strike> [https://bugzilla.mozilla.org/show_bug.cgi?id=683674 bug 683674]

*<strike>etherpad.mozilla.com</strike>

*blog.mozilla.com [https://bugzilla.mozilla.org/show_bug.cgi?id=618095 bug 618095]

*byob.mozilla.com - [https://bugzilla.mozilla.org/show_bug.cgi?id=607129 bug 607129]

*tools.mozilla.com [https://bugzilla.mozilla.org/show_bug.cgi?id=618147 bug 618147]

*crash-stats.mozilla.com [https://bugzilla.mozilla.org/show_bug.cgi?id=618153 bug 618153]

*input.mozilla.com [https://bugzilla.mozilla.org/show_bug.cgi?id=618157 bug 618157]

*browserchoice.mozilla.com [https://bugzilla.mozilla.org/show_bug.cgi?id=618159 bug 618159]

*identity.mozilla.com

*services.mozilla.com

*status.mozilla.com

*brasstacks.mozilla.com

==== mozillalabs.com domains to switch ====

The plan here is for Labs to switch over to mozillalabs.org. They will implement and we can check in as needed.

*apps.mozillalabs.com

*bespin.mozillalabs.com

*builder.mozillalabs.com

*design-challenge.mozillalabs.com

*gaming.mozillalabs.com

*heatmap.mozillalabs.com

*jetpack.mozillalabs.com

*prism.mozillalabs.com

*testpilot.mozillalabs.com

*www.mozillalabs.com

==== mozillamessaging.com domains to switch ====

Mozilla Messaging will switch the domains and we can help as needed.

*<strike>www.mozillamessaging.com</strike> [https://bugzilla.mozilla.org/show_bug.cgi?id=666785 bug 666785]

*<strike>chat.mozillamessaging.com</strike> [https://bugzilla.mozilla.org/show_bug.cgi?id=664049 bug 664049]

*f1.mozillamessaging.com

*ispdb.mozillamessaging.com

*support.mozillamessaging.com

Firefox/Features/Chrome migration

2011-05-12T16:19:00Z

Nuss: fixed broken bugzilla links

{| class="fullwidth-table"
|-
| style="font-weight: bold; background: #DDD;" | Feature
| style="font-weight: bold; background: #DDD;" | Status
| style="font-weight: bold; background: #DDD;" | ETA
| style="font-weight: bold; background: #DDD;" | Owner
|-
<section begin="status" />
| [[Firefox/Features/Chrome migration|Migrate Chrome settings and data]]
| Not started.
| YYYY-MM-DD
|
<section end="status" />
|-
|}

== Summary ==
Firefox offers new users migration of settings and data from Internet Explorer, Safari, and Opera. It does not offer users migration from Chrome. It should.

== Team ==
* '''Feature Manager''': ''whoever is responsible for doing the day-to-day work of driving the feature to completion and updating the status on this page''
* '''Lead Developer''':
* '''Product Manager''':
* '''QA''':
* '''UX''':Alex Limi
* '''Security''':
* '''Privacy''':

== Release Requirements ==

== Next Steps & Open Issues ==

== Related Bugs & Dependencies ==
Bugzilla Bug Report: [https://bugzilla.mozilla.org/show_bug.cgi?id=505192 505192 - Chrome profile migration for Import Wizard and Migration Assistant - cookies, history, and bookmarks]

Bugzilla Bug Report: [https://bugzilla.mozilla.org/show_bug.cgi?id=589589 589589 - Chrome profile migration for Import Wizard and Migration Assistant - passwords, form data, and settings]

== Risks ==

== Use Cases ==
A Chrome user wants to try out Firefox so he downloads it and installs it. Unfortunately, for him and the 150 million other Chrome users who might want to try out Firefox, his Chrome settings and data are not migrated so when he goes to log into Facebook and his username and password are not pre-filled, he says "screw it" and returns to Chrome.

== Designs ==

== Test Plans ==

== Goals ==
The goal is to make Firefox a seamless conversion from Chrome.

== Non-Goals ==
The goal is not to keep Firefox in sync with Chrome, just to migrate it one time.

== Other Stuff ==
Other browsers all migrate Firefox settings and data. We are surely losing lots of potential users here.

== Legend (remove if you like) ==
{| class="fullwidth-table"
|-
| {{StatusHealthy|status= }}
| Healthy: feature is progressing as expected.
|-
| {{StatusBlocked|status= }}
| Blocked: feature is currently blocked.
|-
| {{StatusAtRisk|status= }}
| At Risk: feature is at risk of missing its targeted release.
|-
| '''ETA'''
| Estimated date for completion of the current feature task. Overall ETA for the feature is the product release date.
|}

__NOTOC__

[[Category:Features]]
[[Category:Firefox]]

Websites/Taskforce/Proposals/Common Color Palette

2011-02-23T23:43:09Z

Nuss:

'''Color Palette'''

=Problem=
[[File:Collage-of-colors.png|thumb|300px|A collage of blue headers, green buttons, shades of red, yellow, orange, and light blue. All collected at different Mozilla websites (mostly controlled by Mozilla, or believed to be).]]

[[File:Collage-of-clippings.png|thumb|300px|A collage clippings from websites showing the similar but different colors used on a selection of Mozilla websites.]]

Websites in the Mozilla universe often look very different from each other. Granted, these websites all have different goals and purposes. However, by using a common color palette, these different sites could have their unique look, while still be more recognizable as Mozilla sites.

A collage of blue headers, green buttons, shades of red, yellow, orange, and light blue. All collected at different Mozilla controlled websites (or believed to be).

=Solution=
A solution would be to develop a common color palette to be used as a basis for Mozilla's websites. As apparent in the image above, dark blue, red, orange, yellow, light blue, and green are all common colors in the Mozilla universe. Preferably 6 (or more if needed) "Mozilla Colors/Gradients" would be developed and implemented to enhance the connection between the websites in the Mozilla universe, and to strengthen the Mozilla brand.

==Proposal==
Below is a table of proposed colors. These colors are currently (as of February 2011) used in the "Nova" theme of Mozilla.com and [http://support.mozilla.com/army-of-awesome Army of Awesome].

(N.b., the gradients in the table below are only visible in browsers supporting -moz-linear-gradient).

<table cellspacing="2" cellpadding="5" border="0" style="clear: both; width: 100%; empty-cells: show; background: #eee;">
<tr>
<th style="width: 150px;">Name</th>
<th style="width: 80px;">Solid</th>
<th style="width: 80px;">Gradient</th>
<th>Hex values</th>
</tr>

<tr>
<td>Header Blue</td>
<td style="background: #33589f; height: 40px;"></td>
<td style="background: -moz-linear-gradient(270deg, #3b69b1, #2a4187);"></td>
<td>Solid: #33589f Gradient: #3b69b1 to #2a4187</td>
</tr>

<tr>
<td>Aside Blue</td>
<td style="background: #cce2f3; height: 40px;"></td>
<td></td>
<td>Solid: #cce2f3</td>
</tr>

<tr>
<td>Link Blue</td>
<td style="background: #447bc4; height: 40px;"></td>
<td></td>
<td>Solid: #447bc4</td>
</tr>

<tr>
<td>Button Green</td>
<td style="background: #74ba32; height: 40px;"></td>
<td style="background: -moz-linear-gradient(270deg, #84c63c, #57a21f);"></td>
<td>Solid: #74ba32 Gradient: #84c63c to #57a21f</td>
</tr>

<tr>
<td>Accent Red</td>
<td style="background: #b41b00; height: 40px;"></td>
<td></td>
<td>Solid: #b41b00</td>
</tr>

<tr>
<td>Accent Orange</td>
<td style="background: #f66408; height: 40px;"></td>
<td></td>
<td>Solid: #f66408</td>
</tr>

<tr>
<td>Accent Yellow</td>
<td style="background: #ffbc00; height: 40px;"></td>
<td></td>
<td>Solid: #ffbc00</td>
</tr>

</table>

=Scope=
In discussions with David Boswell the initial proposition is to include websites on the mozilla.org domain and [[Websites/Taskforce/Proposals/Domain_Name_Strategy|websites that are planned to be moved to the mozilla.org domain]] as well as *.mozillalabs.com and *.mozillamessaging.com.

In addition, the list excludes [[Websites/Taskforce/Proposals/Abandoned_Sites#Implementation|abandoned websites decided to be retired or archived]].

==Websites that should be included==
''If any of these should not be included for some reason, please move the link to "Websites that should not be included" below. Please add a comment to why this is the case.''

===Sites on *.mozilla.org/*===
* https://addons.mozilla.org/
* http://air.mozilla.com/
* http://blog.mozilla.com/ -- contains various blogs with different themes
* http://bonsai.mozilla.org/
* http://browserchoice.mozilla.com/
* http://build-graphs.mozilla.org/
* http://byob.mozilla.com/
* https://communitystore.mozilla.org/
* http://crash-stats.mozilla.com/
* http://creative.mozilla.org/
* https://developer.mozilla.org/
* https://doctor.mozilla.org/
* http://donate.mozilla.org/
* http://etherpad.mozilla.com/
* http://feeds.mozilla.org/
* http://firefoxlive.mozilla.org/
* http://graphs.mozilla.org/
* http://guides.mozilla.org/
* http://hacks.mozilla.org/
* http://input.mozilla.com/
* http://krakenbenchmark.mozilla.org/
* http://l10n.mozilla.org/
* http://landfill.mozilla.org/
* https://lists.mozilla.org/
* https://litmus.mozilla.org/
* https://localize.mozilla.org/
* https://mail.mozilla.org/
* http://www.mozilla.com/
* http://www.mozilla.org/
* http://www.mozillamessaging.com/
* http://mpl.mozilla.org/
* http://mxr.mozilla.org/
* http://nightly.mozilla.org/
* http://pastebin.mozilla.org/
* http://planet.mozilla.org/
* http://pulse.mozilla.org/
* http://quality.mozilla.org/
* http://releases.mozilla.org/
* http://services.mozilla.com/
* http://status.mozilla.com/
* http://store.mozilla.org/
* http://studentreps.mozilla.org/
* http://summitbook.mozilla.org/
* http://support.mozilla.com/
* http://support.mozillamessaging.com/
* http://tbpl.mozilla.org/
* http://tinderbox.mozilla.org/
* http://tools.mozilla.com/
* http://videos.mozilla.org/
* https://wiki.mozilla.org/

===Sites outside *.mozilla.org/*===
* http://www.drumbeat.org/
* http://www.mozillalabs.com/ and subdomains

===Websites up for discussion for inclusion===
* http://www.bugzilla.org/
* http://www.getfirebug.com/
* http://www.getpersonas.com/
* http://www.rockyourfirefox.com/
* http://www.spreadfirefox.com/
* http://www.spreadthunderbird.org/

===Websites that should not be included===
''Websites from the list above that should not be included should be moved below. Please add a comment to why this is the case as well, e.g. "technical reasons".''
* http://viewvc.svn.mozilla.org/ (code repository browser, third-party tool. --[[User:Wenzel|wenzel]])
* http://bzr.mozilla.org/ (repository browser)
* http://hg.mozilla.org/ (repository browser)
* http://svn.mozilla.org/ (repository browser)

Websites/Taskforce/Proposals/Common Color Palette

2011-02-18T01:19:32Z

Nuss: /* Proposal */

'''Color Palette'''

=Problem=
[[File:Collage-of-colors.png|thumb|300px|A collage of blue headers, green buttons, shades of red, yellow, orange, and light blue. All collected at different Mozilla websites (mostly controlled by Mozilla, or believed to be).]]

[[File:Collage-of-clippings.png|thumb|300px|A collage clippings from websites showing the similar but different colors used on a selection of Mozilla websites.]]

Websites in the Mozilla universe often look very different from each other. Granted, these websites all have different goals and purposes. However, by using a common color palette, these different sites could have their unique look, while still be more recognizable as Mozilla sites.

A collage of blue headers, green buttons, shades of red, yellow, orange, and light blue. All collected at different Mozilla controlled websites (or believed to be).

=Solution=
A solution would be to develop a common color palette to be used as a basis for Mozilla's websites. As apparent in the image above, dark blue, red, orange, yellow, light blue, and green are all common colors in the Mozilla universe. Preferably 6 (or more if needed) "Mozilla Colors/Gradients" would be developed and implemented to enhance the connection between the websites in the Mozilla universe, and to strengthen the Mozilla brand.

==Proposal==
Below is a table of proposed colors. These colors are currently (as of February 2011) used in the "Nova" theme of Mozilla.com and [http://support.mozilla.com/army-of-awesome Army of Awesome].

<table cellspacing="2" cellpadding="5" border="0" style="clear: both; width: 100%; empty-cells: show; background: #eee;">
<tr>
<th style="width: 150px;">Name</th>
<th style="width: 80px;">Solid</th>
<th style="width: 80px;">Gradient</th>
<th>Hex values</th>
</tr>

<tr>
<td>Header Blue</td>
<td style="background: #33589f; height: 40px;"></td>
<td style="background: -moz-linear-gradient(270deg, #3b69b1, #2a4187);"></td>
<td>Solid: #33589f Gradient: #3b69b1 to #2a4187</td>
</tr>

<tr>
<td>Aside Blue</td>
<td style="background: #cce2f3; height: 40px;"></td>
<td></td>
<td>Solid: #cce2f3</td>
</tr>

<tr>
<td>Link Blue</td>
<td style="background: #447bc4; height: 40px;"></td>
<td></td>
<td>Solid: #447bc4</td>
</tr>

<tr>
<td>Button Green</td>
<td style="background: #74ba32; height: 40px;"></td>
<td style="background: -moz-linear-gradient(270deg, #84c63c, #57a21f);"></td>
<td>Solid: #74ba32 Gradient: #84c63c to #57a21f</td>
</tr>

<tr>
<td>Accent Red</td>
<td style="background: #b41b00; height: 40px;"></td>
<td></td>
<td>Solid: #b41b00</td>
</tr>

<tr>
<td>Accent Orange</td>
<td style="background: #f66408; height: 40px;"></td>
<td></td>
<td>Solid: #f66408</td>
</tr>

<tr>
<td>Accent Yellow</td>
<td style="background: #ffbc00; height: 40px;"></td>
<td></td>
<td>Solid: #ffbc00</td>
</tr>

</table>

=Scope=
In discussions with David Boswell the initial proposition is to include websites on the mozilla.org domain and [[Websites/Taskforce/Proposals/Domain_Name_Strategy|websites that are planned to be moved to the mozilla.org domain]] as well as *.mozillalabs.com and *.mozillamessaging.com.

In addition, the list excludes [[Websites/Taskforce/Proposals/Abandoned_Sites#Implementation|abandoned websites decided to be retired or archived]].

==Websites that should be included==
''If any of these should not be included for some reason, please move the link to "Websites that should not be included" below. Please add a comment to why this is the case.''

===Sites on *.mozilla.org/*===
* https://addons.mozilla.org/
* http://air.mozilla.com/
* http://blog.mozilla.com/ -- contains various blogs with different themes
* http://bonsai.mozilla.org/
* http://browserchoice.mozilla.com/
* http://build-graphs.mozilla.org/
* http://byob.mozilla.com/
* https://communitystore.mozilla.org/
* http://crash-stats.mozilla.com/
* http://creative.mozilla.org/
* https://developer.mozilla.org/
* https://doctor.mozilla.org/
* http://donate.mozilla.org/
* http://etherpad.mozilla.com/
* http://feeds.mozilla.org/
* http://firefoxlive.mozilla.org/
* http://graphs.mozilla.org/
* http://guides.mozilla.org/
* http://hacks.mozilla.org/
* http://input.mozilla.com/
* http://krakenbenchmark.mozilla.org/
* http://l10n.mozilla.org/
* http://landfill.mozilla.org/
* https://lists.mozilla.org/
* https://litmus.mozilla.org/
* https://localize.mozilla.org/
* https://mail.mozilla.org/
* http://www.mozilla.com/
* http://www.mozilla.org/
* http://www.mozillamessaging.com/
* http://mpl.mozilla.org/
* http://mxr.mozilla.org/
* http://nightly.mozilla.org/
* http://pastebin.mozilla.org/
* http://planet.mozilla.org/
* http://pulse.mozilla.org/
* http://quality.mozilla.org/
* http://releases.mozilla.org/
* http://services.mozilla.com/
* http://status.mozilla.com/
* http://store.mozilla.org/
* http://studentreps.mozilla.org/
* http://summitbook.mozilla.org/
* http://support.mozilla.com/
* http://support.mozillamessaging.com/
* http://tbpl.mozilla.org/
* http://tinderbox.mozilla.org/
* http://tools.mozilla.com/
* http://videos.mozilla.org/
* https://wiki.mozilla.org/

===Sites outside *.mozilla.org/*===
* http://www.drumbeat.org/
* http://www.mozillalabs.com/ and subdomains

===Websites up for discussion for inclusion===
* http://www.bugzilla.org/
* http://www.getfirebug.com/
* http://www.getpersonas.com/
* http://www.rockyourfirefox.com/
* http://www.spreadfirefox.com/
* http://www.spreadthunderbird.org/

===Websites that should not be included===
''Websites from the list above that should not be included should be moved below. Please add a comment to why this is the case as well, e.g. "technical reasons".''
* http://viewvc.svn.mozilla.org/ (code repository browser, third-party tool. --[[User:Wenzel|wenzel]])
* http://bzr.mozilla.org/ (repository browser)
* http://hg.mozilla.org/ (repository browser)
* http://svn.mozilla.org/ (repository browser)

Websites/Taskforce/Proposals/Common Color Palette

2011-02-18T01:05:42Z

Nuss: /* Proposal */

'''Color Palette'''

=Problem=
[[File:Collage-of-colors.png|thumb|300px|A collage of blue headers, green buttons, shades of red, yellow, orange, and light blue. All collected at different Mozilla websites (mostly controlled by Mozilla, or believed to be).]]

[[File:Collage-of-clippings.png|thumb|300px|A collage clippings from websites showing the similar but different colors used on a selection of Mozilla websites.]]

Websites in the Mozilla universe often look very different from each other. Granted, these websites all have different goals and purposes. However, by using a common color palette, these different sites could have their unique look, while still be more recognizable as Mozilla sites.

A collage of blue headers, green buttons, shades of red, yellow, orange, and light blue. All collected at different Mozilla controlled websites (or believed to be).

=Solution=
A solution would be to develop a common color palette to be used as a basis for Mozilla's websites. As apparent in the image above, dark blue, red, orange, yellow, light blue, and green are all common colors in the Mozilla universe. Preferably 6 (or more if needed) "Mozilla Colors/Gradients" would be developed and implemented to enhance the connection between the websites in the Mozilla universe, and to strengthen the Mozilla brand.

==Proposal==
Below is a table of proposed colors. These colors are currently (as of February 2011) used in the "Nova" theme of Mozilla.com and [http://support.mozilla.com/army-of-awesome Army of Awesome].

<table cellspacing="2" cellpadding="5" border="0" style="clear: both; width: 100%; empty-cells: show; background: #eee;">
<tr>
<th style="width: 150px;">Name</th>
<th style="width: 80px;">Solid</th>
<th style="width: 80px;">Gradient</th>
<th>Hex values</th>
</tr>

<tr>
<td>Header Blue</td>
<td style="background: #33589f; height: 40px;"></td>
<td style="background: -moz-linear-gradient(270deg, #3b69b1, #2a4187);"></td>
<td>Solid: #33589f Gradient: #3b69b1 to #2a4187</td>
</tr>

<tr>
<td>Aside Blue</td>
<td style="background: #cce2f3; height: 40px;"></td>
<td></td>
<td>Solid: #cce2f3</td>
</tr>

<tr>
<td>Button Green</td>
<td style="background: #74ba32; height: 40px;"></td>
<td style="background: -moz-linear-gradient(270deg, #84c63c, #57a21f);"></td>
<td>Solid: #74ba32 Gradient: #84c63c to #57a21f</td>
</tr>

<tr>
<td>Accent Red</td>
<td style="background: #b41b00; height: 40px;"></td>
<td></td>
<td>Solid: #b41b00</td>
</tr>

<tr>
<td>Accent Orange</td>
<td style="background: #f66408; height: 40px;"></td>
<td></td>
<td>Solid: #f66408</td>
</tr>

<tr>
<td>Accent Yellow</td>
<td style="background: #ffbc00; height: 40px;"></td>
<td></td>
<td>Solid: #ffbc00</td>
</tr>

</table>

=Scope=
In discussions with David Boswell the initial proposition is to include websites on the mozilla.org domain and [[Websites/Taskforce/Proposals/Domain_Name_Strategy|websites that are planned to be moved to the mozilla.org domain]] as well as *.mozillalabs.com and *.mozillamessaging.com.

In addition, the list excludes [[Websites/Taskforce/Proposals/Abandoned_Sites#Implementation|abandoned websites decided to be retired or archived]].

==Websites that should be included==
''If any of these should not be included for some reason, please move the link to "Websites that should not be included" below. Please add a comment to why this is the case.''

===Sites on *.mozilla.org/*===
* https://addons.mozilla.org/
* http://air.mozilla.com/
* http://blog.mozilla.com/ -- contains various blogs with different themes
* http://bonsai.mozilla.org/
* http://browserchoice.mozilla.com/
* http://build-graphs.mozilla.org/
* http://byob.mozilla.com/
* https://communitystore.mozilla.org/
* http://crash-stats.mozilla.com/
* http://creative.mozilla.org/
* https://developer.mozilla.org/
* https://doctor.mozilla.org/
* http://donate.mozilla.org/
* http://etherpad.mozilla.com/
* http://feeds.mozilla.org/
* http://firefoxlive.mozilla.org/
* http://graphs.mozilla.org/
* http://guides.mozilla.org/
* http://hacks.mozilla.org/
* http://input.mozilla.com/
* http://krakenbenchmark.mozilla.org/
* http://l10n.mozilla.org/
* http://landfill.mozilla.org/
* https://lists.mozilla.org/
* https://litmus.mozilla.org/
* https://localize.mozilla.org/
* https://mail.mozilla.org/
* http://www.mozilla.com/
* http://www.mozilla.org/
* http://www.mozillamessaging.com/
* http://mpl.mozilla.org/
* http://mxr.mozilla.org/
* http://nightly.mozilla.org/
* http://pastebin.mozilla.org/
* http://planet.mozilla.org/
* http://pulse.mozilla.org/
* http://quality.mozilla.org/
* http://releases.mozilla.org/
* http://services.mozilla.com/
* http://status.mozilla.com/
* http://store.mozilla.org/
* http://studentreps.mozilla.org/
* http://summitbook.mozilla.org/
* http://support.mozilla.com/
* http://support.mozillamessaging.com/
* http://tbpl.mozilla.org/
* http://tinderbox.mozilla.org/
* http://tools.mozilla.com/
* http://videos.mozilla.org/
* https://wiki.mozilla.org/

===Sites outside *.mozilla.org/*===
* http://www.drumbeat.org/
* http://www.mozillalabs.com/ and subdomains

===Websites up for discussion for inclusion===
* http://www.bugzilla.org/
* http://www.getfirebug.com/
* http://www.getpersonas.com/
* http://www.rockyourfirefox.com/
* http://www.spreadfirefox.com/
* http://www.spreadthunderbird.org/

===Websites that should not be included===
''Websites from the list above that should not be included should be moved below. Please add a comment to why this is the case as well, e.g. "technical reasons".''
* http://viewvc.svn.mozilla.org/ (code repository browser, third-party tool. --[[User:Wenzel|wenzel]])
* http://bzr.mozilla.org/ (repository browser)
* http://hg.mozilla.org/ (repository browser)
* http://svn.mozilla.org/ (repository browser)

Websites/Taskforce/Proposals/Common Color Palette

2011-02-18T00:45:07Z

Nuss: /* Proposal */

'''Color Palette'''

=Problem=
[[File:Collage-of-colors.png|thumb|300px|A collage of blue headers, green buttons, shades of red, yellow, orange, and light blue. All collected at different Mozilla websites (mostly controlled by Mozilla, or believed to be).]]

[[File:Collage-of-clippings.png|thumb|300px|A collage clippings from websites showing the similar but different colors used on a selection of Mozilla websites.]]

Websites in the Mozilla universe often look very different from each other. Granted, these websites all have different goals and purposes. However, by using a common color palette, these different sites could have their unique look, while still be more recognizable as Mozilla sites.

A collage of blue headers, green buttons, shades of red, yellow, orange, and light blue. All collected at different Mozilla controlled websites (or believed to be).

=Solution=
A solution would be to develop a common color palette to be used as a basis for Mozilla's websites. As apparent in the image above, dark blue, red, orange, yellow, light blue, and green are all common colors in the Mozilla universe. Preferably 6 (or more if needed) "Mozilla Colors/Gradients" would be developed and implemented to enhance the connection between the websites in the Mozilla universe, and to strengthen the Mozilla brand.

==Proposal==
Below is a table of proposed colors. These colors are currently (as of February 2011) used in the "Nova" theme of Mozilla.com, on Mozilla.org ("Foundation"), and in the [http://www.mozilla.org/foundation/identity-guidelines/mozilla-foundation.html Mozilla Foundation Visual Identity Guidelines]. Since no single (or "official") Mascot orange was found, the color from Air Mozilla was used.

<table cellspacing="2" cellpadding="5" border="0" style="clear: both; width: 100%; empty-cells: show; background: #eee;">
<tr>
<th style="width: 150px;">Name</th>
<th style="width: 80px;">Solid</th>
<th style="width: 80px;">Gradient</th>
<th>Hex values</th>
</tr>

<tr>
<td>Header Blue</td>
<td style="background: #33589f; height: 40px;"></td>
<td style="background: -moz-linear-gradient(270deg, #3b69b1, #2a4187);"></td>
<td>Solid: #33589f Gradient: #3b69b1 to #2a4187</td>
</tr>

<tr>
<td>Aside Blue</td>
<td style="background: #cce2f3; height: 40px;"></td>
<td></td>
<td>Solid: #cce2f3</td>
</tr>

<tr>
<td>Button Green</td>
<td style="background: #74ba32; height: 40px;"></td>
<td style="background: -moz-linear-gradient(270deg, #84c63c, #57a21f);"></td>
<td>Solid: #74ba32 Gradient: #84c63c to #57a21f</td>
</tr>

<tr>
<td>Foundation Gray</td>
<td style="background: #262626; height: 40px;"></td>
<td></td>
<td>Solid: #262626</td>
</tr>

<tr>
<td>Foundation Red</td>
<td style="background: #a5151e; height: 40px;"></td>
<td></td>
<td>Solid: #a5151e</td>
</tr>

<tr>
<td>Foundation Link Blue</td>
<td style="background: #148cb5; height: 40px;"></td>
<td></td>
<td>Solid: #148cb5</td>
</tr>

<tr>
<td>Mascot Red</td>
<td style="background: #ff1a00; height: 40px;"></td>
<td></td>
<td>Solid: #ff1a00</td>
</tr>

<tr>
<td>Mascot Orange</td>
<td style="background: #fcaa00; height: 40px;"></td>
<td></td>
<td>Solid: #fcaa00</td>
</tr>

</table>

=Scope=
In discussions with David Boswell the initial proposition is to include websites on the mozilla.org domain and [[Websites/Taskforce/Proposals/Domain_Name_Strategy|websites that are planned to be moved to the mozilla.org domain]] as well as *.mozillalabs.com and *.mozillamessaging.com.

In addition, the list excludes [[Websites/Taskforce/Proposals/Abandoned_Sites#Implementation|abandoned websites decided to be retired or archived]].

==Websites that should be included==
''If any of these should not be included for some reason, please move the link to "Websites that should not be included" below. Please add a comment to why this is the case.''

===Sites on *.mozilla.org/*===
* https://addons.mozilla.org/
* http://air.mozilla.com/
* http://blog.mozilla.com/ -- contains various blogs with different themes
* http://bonsai.mozilla.org/
* http://browserchoice.mozilla.com/
* http://build-graphs.mozilla.org/
* http://byob.mozilla.com/
* https://communitystore.mozilla.org/
* http://crash-stats.mozilla.com/
* http://creative.mozilla.org/
* https://developer.mozilla.org/
* https://doctor.mozilla.org/
* http://donate.mozilla.org/
* http://etherpad.mozilla.com/
* http://feeds.mozilla.org/
* http://firefoxlive.mozilla.org/
* http://graphs.mozilla.org/
* http://guides.mozilla.org/
* http://hacks.mozilla.org/
* http://input.mozilla.com/
* http://krakenbenchmark.mozilla.org/
* http://l10n.mozilla.org/
* http://landfill.mozilla.org/
* https://lists.mozilla.org/
* https://litmus.mozilla.org/
* https://localize.mozilla.org/
* https://mail.mozilla.org/
* http://www.mozilla.com/
* http://www.mozilla.org/
* http://www.mozillamessaging.com/
* http://mpl.mozilla.org/
* http://mxr.mozilla.org/
* http://nightly.mozilla.org/
* http://pastebin.mozilla.org/
* http://planet.mozilla.org/
* http://pulse.mozilla.org/
* http://quality.mozilla.org/
* http://releases.mozilla.org/
* http://services.mozilla.com/
* http://status.mozilla.com/
* http://store.mozilla.org/
* http://studentreps.mozilla.org/
* http://summitbook.mozilla.org/
* http://support.mozilla.com/
* http://support.mozillamessaging.com/
* http://tbpl.mozilla.org/
* http://tinderbox.mozilla.org/
* http://tools.mozilla.com/
* http://videos.mozilla.org/
* https://wiki.mozilla.org/

===Sites outside *.mozilla.org/*===
* http://www.drumbeat.org/
* http://www.mozillalabs.com/ and subdomains

===Websites up for discussion for inclusion===
* http://www.bugzilla.org/
* http://www.getfirebug.com/
* http://www.getpersonas.com/
* http://www.rockyourfirefox.com/
* http://www.spreadfirefox.com/
* http://www.spreadthunderbird.org/

===Websites that should not be included===
''Websites from the list above that should not be included should be moved below. Please add a comment to why this is the case as well, e.g. "technical reasons".''
* http://viewvc.svn.mozilla.org/ (code repository browser, third-party tool. --[[User:Wenzel|wenzel]])
* http://bzr.mozilla.org/ (repository browser)
* http://hg.mozilla.org/ (repository browser)
* http://svn.mozilla.org/ (repository browser)

Websites/Taskforce/Proposals/Common Color Palette

2011-02-18T00:37:26Z

Nuss:

'''Color Palette'''

=Problem=
[[File:Collage-of-colors.png|thumb|300px|A collage of blue headers, green buttons, shades of red, yellow, orange, and light blue. All collected at different Mozilla websites (mostly controlled by Mozilla, or believed to be).]]

[[File:Collage-of-clippings.png|thumb|300px|A collage clippings from websites showing the similar but different colors used on a selection of Mozilla websites.]]

Websites in the Mozilla universe often look very different from each other. Granted, these websites all have different goals and purposes. However, by using a common color palette, these different sites could have their unique look, while still be more recognizable as Mozilla sites.

A collage of blue headers, green buttons, shades of red, yellow, orange, and light blue. All collected at different Mozilla controlled websites (or believed to be).

=Solution=
A solution would be to develop a common color palette to be used as a basis for Mozilla's websites. As apparent in the image above, dark blue, red, orange, yellow, light blue, and green are all common colors in the Mozilla universe. Preferably 6 (or more if needed) "Mozilla Colors/Gradients" would be developed and implemented to enhance the connection between the websites in the Mozilla universe, and to strengthen the Mozilla brand.

==Proposal==
<table cellspacing="2" cellpadding="5" border="0" style="clear: both; width: 100%; empty-cells: show; background: #eee;">
<tr>
<th style="width: 150px;">Name</th>
<th style="width: 80px;">Solid</th>
<th style="width: 80px;">Gradient</th>
<th>Hex values</th>
</tr>

<tr>
<td>Header Blue</td>
<td style="background: #33589f; height: 40px;"></td>
<td style="background: -moz-linear-gradient(270deg, #3b69b1, #2a4187);"></td>
<td>Solid: #33589f Gradient: #3b69b1 to #2a4187</td>
</tr>

<tr>
<td>Aside Blue</td>
<td style="background: #cce2f3; height: 40px;"></td>
<td></td>
<td>Solid: #cce2f3</td>
</tr>

<tr>
<td>Button Green</td>
<td style="background: #74ba32; height: 40px;"></td>
<td style="background: -moz-linear-gradient(270deg, #84c63c, #57a21f);"></td>
<td>Solid: #74ba32 Gradient: #84c63c to #57a21f</td>
</tr>

<tr>
<td>Foundation Gray</td>
<td style="background: #262626; height: 40px;"></td>
<td></td>
<td>Solid: #262626</td>
</tr>

<tr>
<td>Foundation Red</td>
<td style="background: #a5151e; height: 40px;"></td>
<td></td>
<td>Solid: #a5151e</td>
</tr>

<tr>
<td>Foundation Link Blue</td>
<td style="background: #148cb5; height: 40px;"></td>
<td></td>
<td>Solid: #148cb5</td>
</tr>

<tr>
<td>Mascot Red</td>
<td style="background: #ff1a00; height: 40px;"></td>
<td></td>
<td>Solid: #ff1a00</td>
</tr>

<tr>
<td>Mascot Orange</td>
<td style="background: #fcaa00; height: 40px;"></td>
<td></td>
<td>Solid: #fcaa00</td>
</tr>

</table>

=Scope=
In discussions with David Boswell the initial proposition is to include websites on the mozilla.org domain and [[Websites/Taskforce/Proposals/Domain_Name_Strategy|websites that are planned to be moved to the mozilla.org domain]] as well as *.mozillalabs.com and *.mozillamessaging.com.

In addition, the list excludes [[Websites/Taskforce/Proposals/Abandoned_Sites#Implementation|abandoned websites decided to be retired or archived]].

==Websites that should be included==
''If any of these should not be included for some reason, please move the link to "Websites that should not be included" below. Please add a comment to why this is the case.''

===Sites on *.mozilla.org/*===
* https://addons.mozilla.org/
* http://air.mozilla.com/
* http://blog.mozilla.com/ -- contains various blogs with different themes
* http://bonsai.mozilla.org/
* http://browserchoice.mozilla.com/
* http://build-graphs.mozilla.org/
* http://byob.mozilla.com/
* https://communitystore.mozilla.org/
* http://crash-stats.mozilla.com/
* http://creative.mozilla.org/
* https://developer.mozilla.org/
* https://doctor.mozilla.org/
* http://donate.mozilla.org/
* http://etherpad.mozilla.com/
* http://feeds.mozilla.org/
* http://firefoxlive.mozilla.org/
* http://graphs.mozilla.org/
* http://guides.mozilla.org/
* http://hacks.mozilla.org/
* http://input.mozilla.com/
* http://krakenbenchmark.mozilla.org/
* http://l10n.mozilla.org/
* http://landfill.mozilla.org/
* https://lists.mozilla.org/
* https://litmus.mozilla.org/
* https://localize.mozilla.org/
* https://mail.mozilla.org/
* http://www.mozilla.com/
* http://www.mozilla.org/
* http://www.mozillamessaging.com/
* http://mpl.mozilla.org/
* http://mxr.mozilla.org/
* http://nightly.mozilla.org/
* http://pastebin.mozilla.org/
* http://planet.mozilla.org/
* http://pulse.mozilla.org/
* http://quality.mozilla.org/
* http://releases.mozilla.org/
* http://services.mozilla.com/
* http://status.mozilla.com/
* http://store.mozilla.org/
* http://studentreps.mozilla.org/
* http://summitbook.mozilla.org/
* http://support.mozilla.com/
* http://support.mozillamessaging.com/
* http://tbpl.mozilla.org/
* http://tinderbox.mozilla.org/
* http://tools.mozilla.com/
* http://videos.mozilla.org/
* https://wiki.mozilla.org/

===Sites outside *.mozilla.org/*===
* http://www.drumbeat.org/
* http://www.mozillalabs.com/ and subdomains

===Websites up for discussion for inclusion===
* http://www.bugzilla.org/
* http://www.getfirebug.com/
* http://www.getpersonas.com/
* http://www.rockyourfirefox.com/
* http://www.spreadfirefox.com/
* http://www.spreadthunderbird.org/

===Websites that should not be included===
''Websites from the list above that should not be included should be moved below. Please add a comment to why this is the case as well, e.g. "technical reasons".''
* http://viewvc.svn.mozilla.org/ (code repository browser, third-party tool. --[[User:Wenzel|wenzel]])
* http://bzr.mozilla.org/ (repository browser)
* http://hg.mozilla.org/ (repository browser)
* http://svn.mozilla.org/ (repository browser)

Websites/Taskforce/Proposals/Common Color Palette

2011-02-03T18:15:03Z

Nuss: removed weeklyupdates.mozillacloud.org

Websites/Taskforce/Proposals/Common Color Palette

2011-02-03T17:49:41Z

Nuss: Added collage of clippings

File:Collage-of-clippings.png

2011-02-03T17:46:44Z

Nuss:

Websites/Taskforce/Proposals/Common Color Palette

2011-02-03T17:46:02Z

Nuss: added scope

Websites/Taskforce/Proposals

2011-01-31T23:49:30Z

Nuss:

This page lists the various proposals made to the web site task force and their current status.

''Note: Please feel free to add additional proposals for discussion at future meetings. You can copy the [[Websites/Taskforce/Proposals/Template|Proposal Template]] as a starting place.''

{| cellspacing="0" cellpadding="3" border="1"
|-
! Proposal
! Proposed by
! Status
|-
| [[Websites/Taskforce/Proposals/Domain Name Strategy|Domain Name Strategy]]
| John, Janet and David
| Approved at [[Websites/Taskforce/2010 10 21|10/21/10 meeting]]
|-
| [[Websites/Taskforce/Proposals/Abandoned Sites|Abandoned Sites]]
| Ryan, David, Frederic, Mike, Chris and Steve
| Approved at [[Websites/Taskforce/2010_11_18|11/18/10 meeting]]
|-
| [[Websites/Taskforce/Proposals/Web Fonts|Web Fonts]]
| Ned, John, Sean and David
| Draft
|-
| [[Websites/Taskforce/Proposals/Universal tab|Universal Tab]]
| Sean Martell, David, John, Potch
| Draft
|-
| [[Websites/Taskforce/Proposals/Common Footer|Common Footer]]
| Julie, Liz, FuzzyFox and David
| Draft
|-
| [[Websites/Taskforce/Proposals/Site_Checklist|Site Checklist]]
| FuzzyFox, David, Stephen Donner
| Draft
|-
| [[Websites/Taskforce/Proposals/CSS Framework|CSS Framework]]
| [[User:Theinterned|Ned Schwartz]], David
| Concept
|-
| [[Websites/Taskforce/Proposals/Official communities badges|Official community badges]]
| Milos, David
| Concept
|-
| [[Websites/Taskforce/Proposals/Documenting Ownership|Documenting Ownership]]
|
| Need owner
|-
| [[Websites/Taskforce/Proposals/Common Color Palette|Common Color Palette]]
| [[User:Nuss|Nuss]]
|

|-
| [[Websites/Taskforce/Proposals/Typefaces for Body Text|Typefaces for Body Text]]
| [[User:Nuss|Nuss]]
|
|}

Websites/Taskforce/Proposals/Typefaces for Body Text

2011-01-31T23:48:40Z

Nuss: Created page with "'''Typefaces for Body Text''' ''This proposal is an extension of the Web Fonts proposal, instead focusing on typefaces used in body te..."

'''Typefaces for Body Text'''

''This proposal is an extension of the [[Websites/Taskforce/Proposals/Web_Fonts|Web Fonts]] proposal, instead focusing on typefaces used in body texts.''

=Problem=
Websites in the Mozilla universe often look very different from each other. Granted, these websites all have different goals and purposes. However, by using common typefaces, these different sites could have their unique look, while still be more recognizable as Mozilla sites.

A quick look at the font-family used in various Mozilla controlled websites' CSS files shows that the following typefaces are used: ''Verdana, Trebuchet MS, Georgia, Arial, Lucida (different families), Cambria, Times New Roman''. This list is presumably incomplete, as @font-face defined, and monospaced typefaces were excluded in the sample.

=Solution=
Agree upon a smaller set of first choice typefaces for body text. Preferably one sans serif, one serif, and one monospace (in addition, one "accent typeface" might be included in the list). By the look of it, the majority of websites that were recently updated visually use Arial as sans serif and Georgia as serif. Monospace typefaces is somewhat different, since only Courier are available on the two major platforms; in this case perhaps the first choices could be Consolas followed by Menlo. In all cases, backup typefaces should be provided, for Linux and for older operating systems that do not include the first choice typefaces.

===Proposed font-family series for body text===
* '''Sans serif''': Arial, Liberation Sans, Helvetica, sans-serif
* '''Serif''': Georgia, Liberation Serif, Times New Roman, Times, serif
* '''Monospace''': Consolas, Menlo, Liberation Mono, Monaco, Courier, monospace

Websites/Taskforce/Proposals/Common Color Palette

2011-01-31T23:18:50Z

Nuss:

Websites/Taskforce/Proposals/Common Color Palette

2011-01-31T23:13:44Z

Nuss:

Websites/Taskforce/Proposals

2011-01-31T22:57:55Z

Nuss:

Websites/Taskforce/Proposals

2011-01-31T22:55:20Z

Nuss: