View source for Websites/Mozilla.org/One Mozilla

== Goals ==

<b>Phase 1. The Merge (March 2011 - August 2011)</b> 

Bring mozilla.com (Firefox product site), mozilla-messaging.org (Thunderbird product site), mozilla-europe.org, and mozilla.org (community site) together into a single codebase: 
*until August 24, 2011, marketing materials directed users to mozilla.org/firefox, which then redirects users to a .com page)
*In this phase we united codebases and rebranded URLs from major Firefox-focused product pages as .org, an effort to bring clarity to the user experience and overall understanding of Mozilla as a non-profit 

<b>Phase II. Build Bedrock & Redesign mozilla.org (September 2011 - current)</b>
<br>
*build a real One Mozilla, a single platform where Mozilla.org and Mozilla product sites (Firefox, Thunderbirds, Apps, etc.)&nbsp;can co-exist and share code
*refresh the mozilla.org design to better express mobile-first techniques, updated brand messaging, usability improvements

== Overview  ==

<br> '''Why Build a New Platform?''' 

Mozilla.org is a pretty simple static content site (though, we have a lot of it!), but working on the site has become increasingly hard over the past few years. Here are some of our pain points (some might sound all too familiar to you in your job): 

<br> 

*'''Mobile,''' we currently don't have framework for handling mobile pages 
*'''Templates,''' we currently don't have clear separation of templates and code, which is messy, hard to understand 
*'''SVN, '''we currently use SVN instead of GIT and SVN doesn't excel when it comes to tracking features and managing rollouts quickly 
**(Here's more on our SVN pains: [http://jlongster.com/s/git-transition/ http://jlongster.com/s/git-transition/]) 
*'''Libraries, '''we currently can't leverage popular libraries of optimizations that other mozilla sites use

<br> '''Why Bedrock''' 

*Mobile, we will have libraries to handle mobile views of pages with a lot of nice features (keeps track of user's preference, uses templates to reuse code, etc) 
*Templates, we will have a powerful templating system: jinja2 ([http://jinja.pocoo.org/docs/ http://jinja.pocoo.org/docs/]) 
*GIT, we will build on top of git instead of SVN, which allows for easy branching and merging for rolling out (until we create a new workflow that the community weighs in on, localizations will still be kept in SVN - eventually though, Bedrock would take the need to know how to code out of the l10n process, which would be glorious!) 
*Libraries, we'll be able to benefit from a number of awesome Python libraries: 
**django-mobility, mobile detection/redirection, [https://github.com/jbalogh/django-mobilit https://github.com/jbalogh/django-mobility] 
**jingo, jinja2 template integration with django,[https://github.com/jbalogh/jingo jingo-minify https://github.com/jbalogh/jingo jingo-minify] 
**JS/CSS minifier, [https://github.com/jsocol/jingo-minify/ https://github.com/jsocol/jingo-minify/ ] 
**django-waffle, feature flipper for continuous deployment, [https://github.com/jsocol/django-waffle https://github.com/jsocol/django-waffle] 
**django-celery, celery (async task manager) integration with django, [https://github.com/ask/django-celery https://github.com/ask/django-celery] 
**django-qunit, quint testing integration, [https://github.com/kumar303/django-qunit https://github.com/kumar303/django-qunit] 
**django-nose, nose test runner, [https://github.com/jbalogh/django-nose https://github.com/jbalogh/django-nose]

These libraries are currently being used and actively developed on other Mozilla sites. 

<br> Most of this and more can be found at "Current Pain Points with Mozilla.com's Architecture/Platform": [http://jlongster.com/s/moz-com-dev/ http://jlongster.com/s/moz-com-dev/] 

*Why bedrock: http://etherpad.mozilla.com:9000/why-bedrock 
*Hacking todo list: http://etherpad.mozilla.com:9000/bedrock-hacking 
*Docs (scarce right now): https://github.com/mozilla/bedrock

== Goals  ==

To create and maintain a true "One Mozilla" web universe, where our many diverse product sites are connected by common navigational elements, URL structure and visual identity. 

The One Mozilla project should feature nothing less than world class design and content on the front end and be built on the very best code and open technology on the back end. It should be a showcase for the modern web, while never deviating from its mission of serving the Mozilla community. 

It should be fully accessible across platforms and devices, and inclusive of the many languages and cultures we support. Our process should be disciplined, transparent and open to anyone who wants to participate, and our methods should be a careful mix of data-driven decision making and expert intuition. 

Our web universe should reflect the best of Mozilla, and we never stop trying to make it even better. 

== Phases  ==

'''Q4 2011''' 

*[https://wiki.mozilla.org/One-Mozilla-Project/Visual-Design '''One Mozilla Visual Design (wiki):'''] 
**Design and code a new mozilla.org responsive visual theme 
**Implement and test a functional universal tab for /firefox [https://bugzilla.mozilla.org/show_bug.cgi?id=629699 Bug 629699] 
**Update mozilla.org/about section to better reflect who we are 
*'''One Mozilla Platform, Bedrock: ''' 
**Build first version of platform, focus on l10n workflow 
**Prioritize content for ongoing migration conducted by webdev (page-by-page):<br> 
***/firefox<br> 
***Mozilla Europe 
***Mozilla.org<br> 
*[https://etherpad.mozilla.org/one-mozilla-communications-q4 '''Communications&nbsp;Plan''']
**[http://onemozilla.org '''Blog''']

== People  ==

'''Negotiate''' - these are the project owners, responsible for going to all the meetings and making the final decisions on things 

*James 
*John 
*Sean Martell 
*Stephanie Schipper

'''Consult''' - the folks will be very involved in the review &amp; feedback process, but aren't considered 'owners' of the project 

*Fred 
*CB 
*David Boswell 
*Asa Dotzler 
*Matej Novak

'''Inform''' - these people will be directly informed of project updates (design reviews, etc) and their opinions will be sought, but are less involved than the people on the consult level 

*Ragavan 
*Thunder 
*Pascal Finette 
*Pascal Chevrel 
*Mike Morgan 
*Jason Grlicky 
*Ryan Merkley 
*Jane Finette 
*Jay Patel 
*Gervase Markham 
*fantasai 
*Eric Shepherd
== Planning ==

*Complete Content Inventories for: 
**[http://bit.ly/jyC0rL Mozilla-Europe] 
**[http://bit.ly/jyC0rL Mozilla Messaging] 
**[http://bit.ly/jyC0rL Mozilla.org] 
**[http://bit.ly/jyC0rL Mozilla.com]

*Complete Content Stakeholder Interviews for: 
**Mozilla-Europe, Pascal, June 7 
**Mozilla Messaging, Rafael, June 8 
**Mozilla.org, David Boswell, June 9 
**Mozilla.com, John Slater 
**L10N Team, Stas, June 9

*Complete Technical Specification/Plan for Rebranding 
**[https://wiki.mozilla.org/Mozilla.com/2011-Rebranding-Project#Phase_1:_Rebrand_Mozilla_Europe Mozilla-Europe], James Long, June 16 
**[https://wiki.mozilla.org/Mozilla.com/2011-Rebranding-Project#Phase_2:_Rebrand_Mozilla_Messaging Mozilla Messaging,] Rafeal Lebron, June 23 
**Mozilla.org, No rebranding required<br>
**[https://wiki.mozilla.org/Mozilla.com/2011-Rebranding-Project#Phase_3:_Rebrand_Mozilla.com Mozilla.com,] James Long, June 23

== Meetings & Notes  ==
*[https://etherpad.mozilla.org/one-mozilla-120811 December 8, 2011]
*[https://etherpad.mozilla.org/one-mozilla-120111 December 1, 2011]
*[https://etherpad.mozilla.org/one-mozilla-111711 November 17, 2011]
*[https://etherpad.mozilla.org/one-mozilla-111011 November 10, 2011]
*[https://etherpad.mozilla.org/one-mozilla-110311 November 3, 2011]
*[https://etherpad.mozilla.org/one-mozilla-102711 October 27, 2011]
*[https://etherpad.mozilla.org/one-mozilla-102011 October 20, 2011] 
*[https://etherpad.mozilla.org/one-mozilla-101311 October 13, 2011]
*Phase I. Launch day, August 24, 2011
*[http://etherpad.mozilla.org:9000/08182011 Meeting Notes, August 18, 2011] (code freeze!)
*[http://etherpad.mozilla.org:9000/08112011 Meeting Notes, August 11, 2011] 
*<strike>Meeting Notes, August 4, 2011</strike> 
*[http://etherpad.mozilla.org:9000/07282011 Meeting Notes, July 28, 2011] 
*[http://etherpad.mozilla.org:9000/07212011 Meeting Notes, July 21, 2011] 
*[http://etherpad.mozilla.org:9000/07142011 Meeting Notes, July 14, 2011] 
*[http://etherpad.mozilla.org:9000/07072011 Meeting Notes, July 7, 2011] 
*<strike>Meeting, June 30. 2011</strike>(cancelled) 
*[http://etherpad.mozilla.org:9000/rebrand-project-062311 Meeting Notes, June 23, 2011] 
*<strike>Meeting, June 16, 2011</strike> (cancelled) 
*[https://docs.google.com/document/d/1AiqziSi9Yxt-XB38yHRA-itQZIjaZ1BmKLuF8Lat2lc/edit?hl=en_US&authkey=COf5ldQE "What is Bedrock" meeting, June 15, 2011] 
*[http://etherpad.mozilla.org:9000/rebrand-project-060911 Meeting Notes, June 9, 2011] 
*[http://etherpad.mozilla.org:9000/7r7AcxinH2 Meeting Notes, June 2, 2011]

== Bugs  ==
[https://bugzilla.mozilla.org/show_bug.cgi?id=610724 Tracking Bug 610724]

Backend:
*[https://bugzilla.mozilla.org/show_bug.cgi?id=652292 652292] - [Bedrock Dev Site] Up and Running<br>
*[https://bugzilla.mozilla.org/show_bug.cgi?id=706836 706836] - [Bedrock Dev Site] Doesn't seem to be serving<br>

Frontend:
*[https://bugzilla.mozilla.org/show_bug.cgi?id=630964 630964] - [One Mozilla] Integrate designs of www.mozilla.com and www.mozilla.org <br> 
*[https://bugzilla.mozilla.org/show_bug.cgi?id=629699 629699] - [Universal Header] Phase 2 <br>
for merged mozilla.org site - https://bugzilla.mozilla.org/show_bug.cgi?id=677305

== Feature Requests ==

*Bedrock: https://wiki.mozilla.org/Mozilla.com/Bedrock#Roadmap_.26_Features

== Follow Along With Blogs &amp; More  ==
* [http://onemozilla.org onemozilla.org]
* Other blogs etc. go here :-)