Websites/Mozilla.org/One Mozilla/Initial-Hack

From MozillaWiki
Jump to: navigation, search

Merge Mozilla Europe into mozilla.com/firefox

This phase involves PascalC heavily, as lead of mozilla-europe.org.

There are a few things to note about mozilla-europe.org where it stands today (June 16, 2011):

  • All of the content we need from mozilla-europe.org has already been ported to mozilla.com (product pages, release notes, etc)
  • mozilla-europe.org is moving to europe.mozilla.org and will become a community-focused site.

What needs to happen next:

  1. Pascal will remove the product pages and make new landing pages for all the locales on europe.mozilla.org -a few locales done in July, due date TBD
    1. Add links on europe.mozilla.com landing pages to moz.com product pages (and download buttons?)
    2. https://bugzilla.mozilla.org/show_bug.cgi?id=669915
  2. The domain mozilla-europe.org should retain it's community status, and will redirect to europe.mozilla.org - due date TBD
    1. https://bugzilla.mozilla.org/show_bug.cgi?id=664393

Merge Mozilla Messaging into mozilla.org

Project Complete: Wednesday, June 29, 2011, Mozilla Messaging relaunched as Thunderbird at mozilla.org/thunderbird

Merge mozilla.com into mozilla.org = mozilla.org/firefox

Mozilla.com will be rebranded as mozilla.org. The current mozilla.org content will still be served under mozilla.org. There are many potential problems with this, from conflicting URLs to the drastically different workflows for the sites. First, let's take note of a few things:

  • Most of mozilla.org's content doesn't need to live there. A lot of it is wiki-like pages that is already being ported to MDN (or something wiki-like).
  • The few pages that do need to live on are static content pages

Eventually, the few important pages on mozilla.org can be re-created in the mozilla.com codebase, and the existing mozilla.org codebase will go away. However, due to the amount of work that needs to be done to transition devs off of mozilla.org, and the minimal gains from waiting to do so, we will not wait to move content off of moz.org, merge mozilla.org pages, change devs workflows, and fix other details to achieve a true merge.

To keep this simple and to achieve the goal of rebranding mozilla.com as .org, we will run the current mozilla.com and mozilla.org codebases side-by-side and tweak how the sites are served.

Idea #1

Use Apache rewrites:

  • Move mozilla.org into a subfolder of mozilla.com
  • Create a list of top-level folders on mozilla.org
  • Use Apache magic to continue serving these folders at the top-level, internally from the mozilla.org subfolder
  • Run combined codebase as mozilla.com

You could also simply use proxied rewrites and serve the .org URLs from another domain, rather than a subfolder.

Idea #2

  • Create a list of top-level folders on mozilla.org
  • Implement rewrites in Zeus to serve the appropriate codebase depending on URL (i.e. anything under /community)

This is even easier then idea #1 and more transparent. This looks like the best solution so far.

Captain's Log, July 8, 2011

I have a prototype of this merge working: http://etherpad.mozilla.com:9000/mozmerge

This implements the above plan. We need to resolve some conflicting URLs and fix a few bugs, but the two sites a running together almost perfectly.

Captain's Log, July 12, 2011

I have a new idea of how to implement the rewrites. Use Zeus instead of Apache, which sits in front of all of our servers and handles caching, load balancing, etc. You can write "site scripts" which is code executed in Zeus per request. Write a site-script which looks at the top-level URL part and serve from the appropriate codebase.

Future

Setup a stage version of the merged mozilla.com/.org using Zeus - https://bugzilla.mozilla.org/show_bug.cgi?id=670115

We really need to start thinking about these bugs too:

Phase II: Build Bedrock & Redesign mozilla.org

wiki

1.) Conduct and produce a  technical inventory of the current moz.com

2.) Read mozilla.com - assimilating mozilla.org http://etherpad.mozilla.com:9000/mozmerge

3.) Why Bedrock