MozillaWiki - User contributions [en]

Firefox OS

2015-05-21T20:57:50Z

Cbeard: formatting for clarity

<div style="float: right; margin: 0px 0px 10px 25px;">[[File:Fxos.png|link=]]</div>
=Firefox OS Design Principles=

# '''We will build phones and connected devices that people want to buy because of the experience, not simply the price.'''
# '''We will focus on depth first vs. breadth first'''. Our goal will be to on achieve real meaningful success and significant traction within our target market segments. We won’t allow ourselves to be distracted, and we won’t expand to new segments until significant traction is demonstrated. (It’s important that we establish a beachhead to build from, and that we’re following through all the way from delivering the initial product to achieving real market success and end-user delight and advocacy.)
# '''We will build products that feel like Mozilla.''' We must define, build and own the product experience to ensure it delivers upon our brand promise and principles. This is critical to ensure that we’re building product expertise and that we’re able to deliver ever more value to our end-users and activate other distribution partnerships to reach even more people.
# '''We will deliver compelling content and app experiences that exceed consumer expectations.''' We will continue to invest in Web platform capabilities and programs to incentivize developers to build for the Web. And to bridge this app gap between user expectations and the readiness of the ecosystem, we will explore implementing limited Android app compatibility for key apps, within a framework that keeps our long-term focus on the Web as the platform across desktop, mobile and connected devices. This mirrors our earlier strategy with Firefox in the face of Internet Explorer market dominance, and we believe this is a necessary step to the web flourishing as a mobile ecosystem.
# '''We will ensure that when you buy a Firefox OS-powered phone you’re joining our global community.''' Empowering people with technology, know-how and opportunity is key to our success, and we must provide product experiences that invite users into our community from enabling people to hack and customize their phone experience to providing local engagement for support, education and more.
# '''We will ensure that the products we build are timely, technically excellent and high quality.''' In order for our products to be great and loved by people they be available when and where they expect them, and they must meet or exceed their expectations in terms of performance and reliability, at all price points. We must aim to build products that we’re proud of.

These principles come out of discussions with many of you and the learnings from the v3 iteration process, as well as our understanding of the industry. We want to spend some time reviewing these together and then declare them part of our official working plan. We can use these to align our strategy and approach with the Mozilla mission and to evaluate product opportunities.

=Firefox OS Functional Team Information=
Everything you need to know about the functional teams working on Firefox OS is [[Firefox OS/functionalteams|here]] (Meeting times, Leadership teams, and Individual Backlogs)

* [[Firefox OS/functionalteams|Firefox OS Org Chart]]
* [[Firefox OS/functionalteams#Devices|B2G Certification]]
* [[Firefox OS/functionalteams#Comms|Communications]]
* [[Firefox OS/functionalteams#Devices|Devices]]
* [[Firefox OS/functionalteams#Media|Media]]
* [[Firefox OS/functionalteams#Multimedia Platform|Multimedia Platform]]
* [[Firefox OS/functionalteams#Networking_.2F_Connectivity|Networking / Connectivity]]
* [[Firefox OS/functionalteams#Performance|Performance]]
* [[Firefox OS/functionalteams#Productivity|Productivity]]
* [[Firefox OS/functionalteams#Systems-Frontend|Systems-Frontend]]
* [[Firefox OS/functionalteams#Systems-Platform|Systems-Platform]]
* [[Gaia/UXTeam|User Experience]]

----

=Firefox OS Release Management & Triage=
Tracking Features and Blocking Bugs across all FXOS functional teams

===Release Management===
* [https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AmStZDZgJbV7dDhtMDZlQmRtdDB4a1plZXRwNXIzYWc&usp=sharing#gid=0 B2G Train Schedule]
* [[Release_Management/B2G_Landing|Release Management - B2G Landing Info]]

===Triage===
* [[B2G/Triage#Triage_for_1.3.0|Nominated and Blocking Bugs]]

----

=Firefox OS Development Process and Release Lifecycle=

* [[Firefox OS/devlifecycle|Development Lifecycle and Release Timeline]]
* [[Firefox OS/devlifecycle#Bugzilla_.22Done.22_Criteria_and_Workflow|Bugzilla Done Criteria & Workflow]]
----

=Firefox OS UX=
* '''All specs''': https://mozilla.app.box.com/s/44utizl9oz4eupyu3fuu
* '''v3.0''' [https://wiki.mozilla.org/Firefox_OS/v3_ideation Participate in Brainstorming & Ideation]
* '''v2.1''': https://mozilla.app.box.com/s/44utizl9oz4eupyu3fuu/1/1759289051
*'''v2.0''': https://mozilla.app.box.com/s/44utizl9oz4eupyu3fuu/1/1732424767
* '''v1.4''': https://mozilla.app.box.com/s/44utizl9oz4eupyu3fuu/1/1226137087
* '''v1.3''': https://mozilla.app.box.com/s/44utizl9oz4eupyu3fuu/1/1147153091
* '''v1.2''': https://mozilla.app.box.com/s/44utizl9oz4eupyu3fuu/1/1030015572

=Firefox OS Sprint Status=

===1.4 Sprint Schedule - [[Firefox OS/devlifecycle#1.4_Release_Calendar Calendar View]]===

{| border="1" cellpadding="2" width ="500"
|-
! !! Start !! End
|-
! Firefox 1
| 2/3 || 2/14
|-
! Firefox 2
| 2/17 || 2/28
|-
! Firefox 3
| 3/3 || 3/14
|-
! Firefox 4
| 3/17 || 3/28
|-
! Firefox 5
| 3/31 || 4/11
|-
! Firefox 6
| 4/14 || 4/25
|}

----
--Ahmedalkabir 09:52, 26 February 2014 (PST)

=Sprint Tracking=
Real-time dashboard view of each functional team's progress sprint-to-sprint. You are able to see all current open user stories and bugs in current sprint. (Dashboards are queried directly from bugzilla and pull based on target milestone and team product components and/or whiteboard tags)

* [[Firefox OS/sprintstatus|All FxOS Functional Team Dashboard]]
* [[Firefox OS/Comms|Communications]]
* [[Firefox OS/RIL|Networking / Connectivity]]
* [[Firefox OS/devices|Devices]]
* [[Platform/GFX|Graphic]] / [[TPEGFX/Bugs|Graphic@Taipei]]
* [[Firefox OS/media|Media]]
* [[Firefox OS/MultimediaPlatform|Multimedia Platform]]
* [https://scrumbu.gs/p/fxos-perf/ Performance] / [[Firefox OS/Performance|Performance]]
* [[Firefox OS/productivity|Productivity]]
* [[Firefox OS/systemsfe|Systems Frontend]]
* [[Firefox OS/systemplatform|System Platform]]
* [[Firefox OS/services|Services]]
* [[Firefox OS/UX|User Experience]]

----

=Firefox OS Product Management=

===Product Backlog===
User stories, acceptance criteria, assumptions, and dependencies for all FXOS functional teams are maintained in the backlog below. (listed by tab)

* [[B2G/Roadmap|Firefox OS Product Roadmap Wiki]]
* [https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AtVT90hlMtdSdEd4TVVjWXNfU3ctMlVhWFRrWkpweVE#gid=39 Firefox OS All-Functional Team Backlog]
* [[Firefox OS/Haida|Haida Concept]]

----

=Firefox OS Security Team=

More information on the [[Security/B2G|team page]].

* [[Security/B2G/Reviews|Security Reviews]]

=Other Resources=
other references, very useful catch all category for existing links and text when cleaning up existing project pages

* [[Firefox OS/Research|Technical Research]]

MozWeek/2014 Portland

2014-11-26T00:00:11Z

Cbeard: Added section on the Friday night party

'''What is it?''' -- multiple work weeks, happening in the same city, at the same time, all within a few city blocks of each other + some opportunity to get together as one big group as well as with other teams as it makes sense. Then, on the last day, we have a giant party, Mozilla-style!

=='''Dates, Location and Weather'''==
Monday, December 1st - Friday, December 5th, 2014 (travel days Monday & Saturday*) in Portland, Oregon, USA (various venues): https://mapsengine.google.com/map/u/0/viewer?mid=zGDglM1VcNwI.khD1s_r2QdO0

''*For those countries where rest time is required on weekends (vs. work travel), Mozilla will cover a return on Monday the 8th if you choose.''

* Weather Forecast: [http://forecast.weather.gov/MapClick.php?lat=45.517&lon=-122.683&unit=1 °C] or [http://forecast.weather.gov/MapClick.php?lat=45.517&lon=-122.683 °F]

=== Invitation letter (non-US) ===
''*For non US travelers, please download the attached invitation to bring with you. The letter is formatted in Microsoft Word so you can insert your personal details. If you need personal assistance please email immigration@mozilla.com. https://docs.google.com/a/mozilla.com/document/d/1kYW-L4mXsrigRDosxAJY-FfZGYwLiySKPIea7lt_f7c/edit?usp=sharing .''

== '''Hotels & Meeting Space''' ==
The idea is that teams will stay in the same hotel. Won't be perfect, but we'll get as close as we can. All of the hotels are within walking distance from each other and from the Portland Art Museum. One (Marriot Waterfront) is a bit farther out (where we have a big chunk of rooms) so we'll likely have transportation to/from the PAM from there. You can see all hotels here: https://mapsengine.google.com/map/u/0/viewer?mid=zGDglM1VcNwI.khD1s_r2QdO0.

=== floorplans ===
* [http://events.portlandartmuseum.org/venues/capacities Portland Art Museum]
* [https://wiki.mozilla.org/images/e/e9/Portland_Marriott_Downtown_Waterfront_Floor_Plans.pdf Marriott Waterfront]
* [https://wiki.mozilla.org/images/0/0f/Hilton_Floor_Plan.pdf Hilton]
* [http://portland.heathmanhotel.com/meetings/room-floor-plans.aspx Heathman]

=== wifi ===
'''PORTLAND ART MUSEUM'''

'''SSID: MozillaPDXww -- No password'''
** 100MB bandwidth (5 MB down/2 MB up per user)
** 26 access points (dualband 802.11ac)
** Ethernet switches and router
** Custom network.

'''MARRIOTT WATERFRONT'''

'''SSID: Mozilla Conference (this may change) -- Password: Mozilla2014'''
** 100Mb bandwidth dedicated to the meeting space + extra 100MB dedicated (for 200 MB total)
** 18 Ruckus 7962 Zoneflex G access points each capable of carrying up to 500 users. The Ruckus Zone director 3000 series prevents dropping from AP to AP.

'''HILTON'''

'''SSID: MozillaPDXWW -- Passcode: December2014'''
** 71 Mbps of bandwidth dedicated to the meeting space exclusively.
** 35 access points (Cisco 1130G) with dynamic Allocation (roughly one+ per space)

'''HEATHMAN'''

'''SSID: TBD -- Passcode: TBD'''
** Total Bandwidth is 100 mb(down) x 20mb (up) - this is shared between all guests at the hotel.
** Free access is 3X1 with a 5x2 5 second burst.

=== white boards, projectors, access to central printer, etc.===
Will be available in all spaces. Process TBD.

=== Mother's Rooms ===

*'''PAM''' - 4th floor women's restroom. It is a private and secluded space with a chair.
** Back up would be walking to Heathman, if you don't like the bathroom. There isn't another space available all days.

*'''Marriott''' - guestroom. Need to check in with Lisa Carlson at the registration desk on the Ballroom level for a key

*'''Hilton''' - guestroom - need to check in with Cheryl Barnet at the registration desk on the 2nd floor, outside Broadway rooms for a key.

*'''Heathman''' - guestroom. Need to check in with Cheryl Barnet. She'll be at Hilton, but can run over to provide keys (or set up a time to pass them on)

MozMamas can keep the guestroom keys for the week, but if they become demagnetized, you'll have to go back to the contact to get a new one.

=== parking ===

This site <http://portland.bestparking.com/> will help you find garages that allow overnight parking and show the accumulated cost.

Smartpark has five 24/7 downtown garages, you can see their rates here -> <http://www.portlandoregon.gov/transportation/article/254736>
Do double check that they allow overnight parking.

SW 1st and Jefferson - 123 SW Jefferson St
Open 24/7

SW 3rd and Alder - 621 SW 3rd Ave
Open 24/7

SW 4th and Yamhill - 818 SW 4th Ave
Open 24/7

SW 10th and Yamhill - 730 SW 10th Ave
Open 24/7

NW Naito and Davis - 33 NW Davis St
Open 24/7

== '''Airport Transportation''' ==

Once you arrive at your hotel, you will be able to check in. Some rooms might not be ready earlier in the day, but we will do our best. If you have questions or concerns with your reservation, please call Cheryl at 206-255-2926 or Nolan at 206-255-2844. They can assist you in sorting everything out.

=== Arrivals ===
There will be Mozilla airport shuttles from the Portland airport ("PDX") to hotels for arrivals between 8:00 am and 11:00 pm on December 1. Upon arrival at the airport on December 1, please proceed to baggage claim (even if you didn't check bags) and look for friendly faces holding signs that say Mozilla! They will help you find and board the shuttles. You will need to know what hotel you're staying in...If you need assistance, please call +01 (206)255-2929.

=== Departures ===
There will be return Mozilla airport shuttles from hotels to PDX between 5:00 am and 2:00 pm on December 6 (there will be shuttles starting at Marriott Waterfront at 4:00 am for the 6:40 am flight to SFO). We recommend leaving two hours or more before your flight.

==== Shuttle Routes ====

Shuttles will operate on routes (both for arrivals and departures -- there are very few places where we can park out buses):

'''Route 1 – NINES-BENSON'''
* Pick up location: The Nines - Morrison between 5th and 6th
* Those at Benson, walk to Nines for Shuttle (and/or are dropped off there)

'''Route 2 – HILTON-MARRIOTT CITY-PARAMOUNT-HEATHMAN'''
* Pick up location: The Hilton - Taylor between 5th & 6th
* Those at Marriott City Center, Paramount and Heathman, walk to Hilton for Shuttle (and/or are dropped off there)

'''Routes 3 – MARRIOTT WATERFRONT-MODERA'''

* Pick up Location: Marriott – Clay St between Naito & 1st; Modera – Clay St between 5th & 6th
* Stops at both hotels.

=== Travel or Hotel Help?===
If your flight changes and you are at the airport, approach the airline for assistance. If you need additional help, you can call Nancy at +01 (206)255-2929.

=== Shuttle Alternatives (for those arriving at odd times/dates) ===

These are transportation options for those arriving ''outside'' of the shuttle hours. '''If you are arriving during shuttle hours, please take the shuttle; we are saving a spot for you!'''

* '''Light rail ("MAX")'''
** The MAX light rail Red Line is the easiest way to travel to and from the airport.
** The trip between the airport and downtown Portland takes about 38 minutes.
** An adult ticket costs $2.50 (Youth $1.65, Honored Citizen $1). MAX ticket machines return change in coins, so small bills are recommended.
** You can roll your luggage on board.
** The first train of the day arrives at PDX at 4:45 a.m. The last train departs PDX at 11:50 p.m.
** The MAX station and ticket machines are located on the lower level, next to the south baggage claim area (turn right at the base of the escalator).
** For complete schedules and more information, visit www.trimet.org/schedules/maxredline.htm
** If you're planning to use TriMet for 2 or more trips, the TriMet Tickets app for [https://play.google.com/store/apps/details?id=org.trimet.mt.mobiletickets Android] or [https://itunes.apple.com/us/app/trimet-tickets/id687943985?mt=8&ign-mpt=uo%3D4 iOS] is highly recommended.

* '''[http://www.bluestarbus.com/downtown-express.php Blue Star Bus Downtown Shuttle]'''
** Book online in advance
** $14 one way
** When leaving the airport, you can find the Downtown Airport Express and other hotel shuttle buses on the terminal’s lower roadway.

* '''Taxi'''
** Should be used when two above options are not available
** $35 one way + tip ($3 - $5 is reasonable)
** The one-way trip takes 20-40 minutes.
** Taxis will be waiting in the center section of the airport terminal’s lower roadway outside of baggage claim.
** To get back to the airport from the city center, you can order a cab through the city’s main operators or from a hotel with a dedicated taxi stand.

=='''Work week schedule''' ==

Work week schedule (will be updated): https://docs.google.com/a/mozilla.com/spreadsheets/d/12K2OIUKAURjtQOcOMcPCOi4qeB1i80UWCA4EZLX94b4/edit#gid=0

'''Monday''':
* 6:00pm - 8:00pm (cocktails, informal)

'''Tuesday + Wednesday''':
* All-hands block: 9:00am - 11:00am PT
* Work week blocks:
** 11:00am - 2:00pm
** 2:00pm - 5:00pm (some spaces are available until 4:00pm only)
** 5:00pm - 8:00pm (dinner - see dine arounds)

'''Thursday'''
* Work week blocks
** 8:00am - 11:00am
** 11:00am - 2:00pm
** 2:00pm - 5:00pm (some spaces are available until 4:00pm only)
** 5:00pm - 8:00pm (dinner reservations will likely start at 6:30pm)

'''Friday'''
* Work week blocks
** 8:00am - 11:00am
** 11:00am - 2:00pm
** 2:00pm - 4:00pm
** 6:00pm - 12:00am Wrap Up (closing talks, food, drinks, live music, dancing and more - dress up for a night on the town)

=== Shuttles to/from the Marriott Waterfront ===

'''December 2 and 3'''
* Marriott Waterfront to PAM (7-9 am), return to Marriott (11 am - 1 pm), Hilton-Marriott Waterfront Loop (1 pm – 5 pm)
* Shuttle Hours – 7 am – 5 pm

'''December 4 and 5'''
* Hilton-Marriott Waterfront Loop (7 am – 5 pm)
* Shuttle Hours – 7 am – 5 pm

=='''Expenses'''==
We're managing the budget for the event carefully and centrally. And we are crafting an experience that doesn’t just give each team their own space for a work week, but also promotes teamwork and coming together.

There is no other budget for this so the use of corporate cards for this event, should you have one, needs to be cleared ahead of time, by your VP.

Almost all meals are covered by the event, including [https://wiki.mozilla.org/Portland_coincidental_work_week#Tuesday.2C_Wednesday.2C_Thursday dine-arounds] on Tuesday, Wednesday and Thursday evening. If you choose to do something different, the budget for dinner is in the $30 - $40 USD range per person per night.

For other items, please rely on our travel and expense guidelines.

===Volunteer Reimbursement via Reps===
Volunteers attending this event may submit for visa and U.S. travel/health insurance- related costs (and other incidentals) via Mozilla Reps:
* Mozilla Reps attending this event may submit for reimbursement through the [https://bugzilla.mozilla.org/form.reps.budget standard process].
* Mozillians who are not Mozilla Reps should contact a local Rep and the Rep will help them get reimbursed. The process is as follows:
** '''Step 1:''' contact a Rep [https://reps.mozilla.org/people/ in your country]*
** '''Step 2:''' once the Rep has accepted to process your reimbursement, give them an estimate of what your costs will be. If you need the funds beforehand, be sure to say that
** '''Step 3:''' after the event, send him/her all your scanned receipts and bank details/paypal account
** '''Step 4:''' inform the Rep once you have successfully received the funds

== '''Food''' ==
Portland has an amazing [http://en.wikipedia.org/wiki/Foodie foodie] culture and some of the coolest [http://www.foodcartsportland.com/ food carts] around. Rather than serve up standard conference fare for the whole week we're going to mix it up a bit. Some of our meals will be catered (hard to get out of that entirely), some won't. Some will be paid for centrally (meaning no cash/credit card needed), some won't (meaning you'll need to pay and submit for reimbursement). If paying up front for a meal that is not provided is not something you can reasonably do, please contact your manager OR, if you're a volunteer, the person that invited you to their work week.

'''Any of our leftover food, through our own catering, will be donated to: http://blanchethouse.org/'''.

==== Breakfast ====
* '''Tuesday/Wednesday''', breakfast will be catered and provided at the PAM (our all-hands session starts there at 9:00am, so breakfast will be available by 7:30am).
* '''Thursday/Friday''', breakfast will be catered and provided within each of the hotels where we have work week breakout space (Hilton, Marriott Waterfront, and Heathman).
* You may want to try coffee from [http://stumptowncoffee.com/location/portland/ Stumptown] at some point, and a donut or two from [http://voodoodoughnut.com VooDoo] both of which are distinctly Portland.
<blockquote>If you want donuts, you're much better off with [http://www.bluestardonuts.com/ Blue Star]. If you want coffee, Stumptown is OK, but try Coffeehouse Northwest, or Courier, or Public Domain, or Sterling, or Water Avenue, or any number of more interesting, small cafes.

Sincerely,
Portland.</blockquote>

==== Lunch ====
Mozillians are encouraged to head to the food cart center for lunch (although you'll need to pay for this on your own and submit for reimbursement). It's walking distance from most of our work week hotels and from the PAM. You can find it on this map (or ask a native): https://mapsengine.google.com/map/u/0/viewer?mid=zGDglM1VcNwI.khD1s_r2QdO0.

For those folks working out of the Marriott Waterfront, the food cart center is a bit of a walk. So, we're going to bring the carts to you.

In some cases (TBD) on some days, we'll provide catered lunches. More on this soon.

==== Dinner ====

===== '''Monday'''=====
There will be a cocktail party reception at the Portland Art Museum that starts at 6:00pm. There will be lots of great appetizers there as well as, well, cocktails (we'll have juice and sparkly water too). While it's not a formal dinner, it's likely enough to get you started. We have no other dinner plans for Monday evening so if you need more food, you'll need to head to a nearby restaurant (the range of expense expected for dinner is between $30 - $40 USD per person).

===== '''Tuesday, Wednesday, Thursday'''=====
So we can experience a bit of Portland, and still stay within our budget, we've arranged for three-evenings of Portland dine-arounds. Dine-arounds are a collection of local restaurants that have agreed to feed us a pre-set menu for a fixed price (includes one drink, the rest is up to you). In each case, depending on which restaurant you choose, your meal is pre-paid by Mozilla (you don't need to bring cash unless you want extras). We have enough seats each evening to cover about 75% of us, understanding there will be folks with other plans.

* Most of the restaurants are within walking distance of the Portland Art Museum and where they aren't, you can cab it or take public transit. Our reservations times vary but generally start after 6:00pm. Specific times will be noted on the Dine-Around sign-up sheet.

* Dietary restrictions can be accommodated. We have listed these under each restaurant and will update as we have more information. The only exceptions would be the restaurants doing buffets. There may be options, but no modifications. Let us know if you have specific accommodations needed and we can suggest some options.

* In some cases, menus have not been posted. Many restaurants use fresh, local, in season ingredients and won't know what they will feature until mid-month. We'll update the document as we get more information.

* If a restaurant is at its max and you'd still like to dine there, please add your name anyway. In lots of cases, restaurants can accommodate more than they've indicated. We wanted to start with a conservative estimate.

'''SIGN-UPS''': http://mzl.la/signups (pro tip: this link will take you to an un-editable version if you try to access it from a non-Mozilla Google account OR if you have a non-Mozilla and a Mozilla account open in the same browser session).

'''MENUS/RESTAURANT DETAIL''': http://mzl.la/menus

===== '''Friday''' =====
Closing talks / food / drinks / live music / dancing and more. Dress up for a night on the town. From 6pm until late. More details to follow.

==== Snacks ====
These will be provide at each of the work week sites (other than our office, where there are snacks already) at stations throughout the space.

== <big>Your Old Phones Needed in Portland</big> ==
Did you know that the estimated 500,000 mobile devices discarded daily can have another life improving someone's life?

[http://medicmobile.org/ Medic Mobile], a not-for-profit that seeks to advance healthcare in 16 countries with mobile technology (their app in the Firefox Marketplace here: https://marketplace.firefox.com/app/medic-mobile) recycles any type of mobile device through their Hope Phones program (https://hopephones.org/) to fund public health program around the world.

They need your help. '''Let's collect 1,000 old phones to the Mozilla offsite''' to empower health workers and improve the lives of many more. Bring your old Blackberry, StarTac, Chocolate, Galaxy or anonymous device to Portland and help us show that Mozilla cares. We'll have collections points around the offsite for easy drop-off.

If you plan to bring and donate a device that you received from Mozilla, please complete this form to help our IT group track our assets:
(https://docs.google.com/a/mozilla.com/forms/d/1ASIB1HWh3SGIHFG9pO8qX6LLka9ZgMMt8EDeRUf_QaQ/viewform)

Note that if you are [http://www.tsa.gov/press/releases/2014/07/06/enhanced-security-measures-certain-airports-overseas traveling internationally with phones in carry-on baggage], the phones must be charged and able to power-on. If security screeners ask you to power-on a phone, and it fails to do so, it may be confiscated.

Many thanks. Questions: Pete Scanlon (pscanlon@mozilla.com)

==Sessions==
If you have one to propose, add it here with a sign up link.

*[https://etherpad.mozilla.org/web-media-mozlandia-2014 Teach us how to do web media on Air Mozilla] Possible super-team for all people who know about media and how to best put it on the web. Hosted by the Air Mozilla team who are eager to learn.
*[https://etherpad.mozilla.org/project-foxeye-mozlandia-2014 Project FoxEye: Bring modern computer vision and image processing technology to the Web], Target audience: JavaScript developer, multimedia team and people who are interested in computer vision field. Hosted by Taipei Multimedia team.
* [https://etherpad.mozilla.org/ArabicRTL-Sessions Arabic RTL sessions] There will be multiple Arabic RTL sessions in Portland. From talks to hands-on workshop, check out the etherpad for more info!
* [https://etherpad.mozilla.org/MQM-PDX-TrainingSession MQM Translation Quality Testing]: Are you fluent in another language? Want to learn how you can easily get involved in testing the quality of the translations on Firefox OS? Come join us and we'll teach you! Let's start training the next generation of trainers!
*[https://etherpad.mozilla.org/servo-mozlandia-2014 Your first Servo contribution!] Members of the new browser engine project, Servo, will be mentoring all those interested in landing fixes to a slew of good first bugs. Free [http://imgur.com/CLnfQnO dino sticker] to the first 100 who open a PR!
* [https://etherpad.mozilla.org/ateam-pdx-performance-sheriffing Performance data sheriffing]: We're developing a system that allows push-based performance data (ala Talos) to be visualized and sheriffed within Treeherder. This project is called Perfherder. We'd like discuss plans for Perfherder, and get some input from potential users of it.
* [https://etherpad.mozilla.org/ateam-pdx-intermittent-oranges The War on Orange: improving the way we deal with intermittents]: Join the A-Team for a discussion about better ways to handle intermittent oranges, including fixing them, preventing them, hiding them, and reporting them.
* [https://etherpad.mozilla.org/ateam-pdx-treeherder Treeherder Brainstorming and Q&A]: Join the Treeherder developers for Q&A, brainstorming of future enhancements, and providing general feedback on Treeherder features.

==Friday night in Portland==
'''On Friday night in Portland we invite you to travel back to the Prohibition Era, a time of outlaws, innovators and those who found their own way of doing things.'''

We’ll come together to wrap up our week in style with closing talks, food, drink, music, dancing and more.

Transportation from & to the hotels will start around 6pm and run until midnight.

Dress code? That’s up to you. Think of this like you would a big night out on the town — including great food, company and ending up at a night club with a live band and music to dance to, or perhaps a karaoke bar, or at a late night restaurant chatting into the wee hours with friends. Or all of the above. Above all else be yourself and bring your own personal style.

There will be a little something for everyone — from live music to karaoke, dancing to lounging — with multiple themed rooms, music and experiences to suit different tastes.

* More details to follow in email.
* Karaoke Song List: [[File:Portland-karaoke.pdf]]

==Extra Curriculars==
If you have one to propose, add it here with a sign up link.

* '''Hockey!!!''' (ice, shinny style) - 8-9:15am on Thursday, Dec 4th - [https://etherpad.mozilla.org/mozlandia-hockey sign up] -- feel free to come cheer/photograph
* '''SNOW Summit outing to Mount Hood''' (tentative) - [https://etherpad.mozilla.org/snow-summit-2014 Sign up + Information Here]
* '''Zumba! With our very own Rowe Hoffer''' (We will do it if there is interest) - [https://etherpad.mozilla.org/PDXZumba Sign up + Information Here]
* '''Find running partners!''' - [http://goo.gl/forms/ouh00YmVIt Sign up Here]
* '''Ping Pong!!!''' - There are loads of great places where Mozillians can play ping pong. And if we have enough signed up, we'll organize a tournament! [https://etherpad.mozilla.org/PDX-pingpong-extravaganza Sign up + Information Here]
* '''Indoor Kart Racing''' - Evenings Monday-Thursday (tentative) [https://etherpad.mozilla.org/portland-indoor-karting-2014-12 Interested? SIGN UP!]
* '''Homozilla''' (LGBTQ Mozillians and allies) will be doing a couple of [https://etherpad.mozilla.org/homozilla-night-out social things]
* '''Scotch, Whiskey, Bourbon!''' - Evening pub crawls to taste the best of Portland's brown. [https://etherpad.mozilla.org/pdx-brown-tour Sign up + Information here] [http://bit.ly/1tuj04H Portland Fun Map]
* '''Beer!''' - Evening pub crawls to taste the best of Portland's beer. [https://etherpad.mozilla.org/pdx-beer-tour Sign up + Information here] [http://bit.ly/1tuj04H Portland Fun Map]
* '''Crossfit''' - After a night of drinking, come work out and try not to puke :) [https://etherpad.mozilla.org/pdx-crossfit Sign up + Information here] [http://bit.ly/1tuj04H Portland Fun Map]
* '''Christians''' - Early morning [https://etherpad.mozilla.org/christians-in-portland prayer and fellowship]
* '''Board/Card Games''' - [https://etherpad.mozilla.org/portland-board-games organize here]
* '''UI/UX <3''' - Calling all UI and UX Mozillians. Let's carve out a hour or more to get together during Mozlandia for free hugs, good conversation and all the things that make our minds tick. [http://goo.gl/forms/y7LYr4MRuO Signup open to all]
* '''Birding''' - Hey birders and bird lovers, let's go for a walk at the Portland Audubon and check out who's overwintering near Portland. [http://etherpad.mozilla.org/birding-in-pdx Signup open to all]
*'''Crafty Mozilla''' - we will try to have in place a crafty corner/table and some stuff ready to make some awesome things! [https://etherpad.mozilla.org/crafty-mozilla-portland Sign up here!]
*'''Pozilla Poker Evening''' - Texas Hold'em. We have a set of chips! [https://etherpad.mozilla.org/pozilla Sign up here!]
*'''Playing Ingress''' - A cool cross-faction field-art of our favorite Dino-head, appleseed Mozilla PDX office space area & of course regular AP hunts, dog-fights, (for foreign agents a huge amount of) unique portal visits/captures etc. [https://etherpad.mozilla.org/ingress-portland-workweek Planning & Sign up]
*'''Gamers''' - We're not going to actually play games, just drink about them. Wednesday @ 9:30 Driftwood Room. Dress classy. (So, t-shirt and jeans, then? Sounds good.) [http://www.hoteldeluxeportland.com/eat-drink/driftwood-room/].
*'''Shootin' Range''' - Portland has several high-quality indoor ranges scattered around the city. Let's head out and plink on some targets! [https://etherpad.mozilla.org/mozrangeia Sign up here!]
*'''[http://groundkontrol.com/ Ground Kontrol]''' - Portland classic arcade open for max. 130 people from 8:00pm - 12:00am PT on Tuesday, December 2nd only. Minors welcome. Includes free play on all machines, as well as sodas. This is Mozilla sponsored. [https://etherpad.mozilla.org/ground-kontrol Sign up here].
*'''MozillaWiki Hackathon''' -- Wednesday and Thursday 6pm-10pm at Mozilla Portland office. We'll order food and work on MozillaWiki tasks. Other Mozilla projects welcome! If you're interested, put your name [https://wiki.etherpad.mozilla.org/december-pdx-hackathon here!]
*'''MozWomen Lunch''' -- Let's coincidentally get lunch one day (not restricted to women, of course - any welcome!). Etherpad [https://etherpad.mozilla.org/moz-women-lunch here!]
* '''[http://portlandartmuseum.org/ Portland Art Museum]''' - they are offering us full access to all of the galleries for $5.00 (standard ticketed entry is $15.00). Additionally, the museum gift shop will be offering a 10% discount to all participants, which, I might add, is doubly appealing, given that Oregon has no sales tax! The gift shop has an extensive collection of fine art books, gifts, and a variety of unique, locally-inspired merchandise, cards, and gift wrap.

== FAQ ==
Please add your questions to this document: https://docs.google.com/a/mozilla.com/document/d/1g-KqjCWwjJtgYHJYuFXgWYW9i0MY234_tMRPbXxq5Jc/edit

== Links ==
* Guest speaker suggestions: https://etherpad.mozilla.org/workweekspeakers
* Fun things to do suggestions: https://etherpad.mozilla.org/hogwarts

File:Portland-karaoke.pdf

2014-11-25T23:57:28Z

Cbeard: Song list for Friday night Karaoke at the Portland Coincidental Work Week

Song list for Friday night Karaoke at the Portland Coincidental Work Week

MozWeek/2014 Portland

2014-11-25T23:53:28Z

Cbeard: /* Work week schedule */

'''What is it?''' -- multiple work weeks, happening in the same city, at the same time, all within a few city blocks of each other + some opportunity to get together as one big group as well as with other teams as it makes sense. Then, on the last day, we have a giant party, Mozilla-style!

=='''Dates, Location and Weather'''==
Monday, December 1st - Friday, December 5th, 2014 (travel days Monday & Saturday*) in Portland, Oregon, USA (various venues): https://mapsengine.google.com/map/u/0/viewer?mid=zGDglM1VcNwI.khD1s_r2QdO0

''*For those countries where rest time is required on weekends (vs. work travel), Mozilla will cover a return on Monday the 8th if you choose.''

* Weather Forecast: [http://forecast.weather.gov/MapClick.php?lat=45.517&lon=-122.683&unit=1 °C] or [http://forecast.weather.gov/MapClick.php?lat=45.517&lon=-122.683 °F]

=== Invitation letter (non-US) ===
''*For non US travelers, please download the attached invitation to bring with you. The letter is formatted in Microsoft Word so you can insert your personal details. If you need personal assistance please email immigration@mozilla.com. https://docs.google.com/a/mozilla.com/document/d/1kYW-L4mXsrigRDosxAJY-FfZGYwLiySKPIea7lt_f7c/edit?usp=sharing .''

== '''Hotels & Meeting Space''' ==
The idea is that teams will stay in the same hotel. Won't be perfect, but we'll get as close as we can. All of the hotels are within walking distance from each other and from the Portland Art Museum. One (Marriot Waterfront) is a bit farther out (where we have a big chunk of rooms) so we'll likely have transportation to/from the PAM from there. You can see all hotels here: https://mapsengine.google.com/map/u/0/viewer?mid=zGDglM1VcNwI.khD1s_r2QdO0.

=== floorplans ===
* [http://events.portlandartmuseum.org/venues/capacities Portland Art Museum]
* [https://wiki.mozilla.org/images/e/e9/Portland_Marriott_Downtown_Waterfront_Floor_Plans.pdf Marriott Waterfront]
* [https://wiki.mozilla.org/images/0/0f/Hilton_Floor_Plan.pdf Hilton]
* [http://portland.heathmanhotel.com/meetings/room-floor-plans.aspx Heathman]

=== wifi ===
'''PORTLAND ART MUSEUM'''

'''SSID: MozillaPDXww -- No password'''
** 100MB bandwidth (5 MB down/2 MB up per user)
** 26 access points (dualband 802.11ac)
** Ethernet switches and router
** Custom network.

'''MARRIOTT WATERFRONT'''

'''SSID: Mozilla Conference (this may change) -- Password: Mozilla2014'''
** 100Mb bandwidth dedicated to the meeting space + extra 100MB dedicated (for 200 MB total)
** 18 Ruckus 7962 Zoneflex G access points each capable of carrying up to 500 users. The Ruckus Zone director 3000 series prevents dropping from AP to AP.

'''HILTON'''

'''SSID: MozillaPDXWW -- Passcode: December2014'''
** 71 Mbps of bandwidth dedicated to the meeting space exclusively.
** 35 access points (Cisco 1130G) with dynamic Allocation (roughly one+ per space)

'''HEATHMAN'''

'''SSID: TBD -- Passcode: TBD'''
** Total Bandwidth is 100 mb(down) x 20mb (up) - this is shared between all guests at the hotel.
** Free access is 3X1 with a 5x2 5 second burst.

=== white boards, projectors, access to central printer, etc.===
Will be available in all spaces. Process TBD.

=== Mother's Rooms ===

*'''PAM''' - 4th floor women's restroom. It is a private and secluded space with a chair.
** Back up would be walking to Heathman, if you don't like the bathroom. There isn't another space available all days.

*'''Marriott''' - guestroom. Need to check in with Lisa Carlson at the registration desk on the Ballroom level for a key

*'''Hilton''' - guestroom - need to check in with Cheryl Barnet at the registration desk on the 2nd floor, outside Broadway rooms for a key.

*'''Heathman''' - guestroom. Need to check in with Cheryl Barnet. She'll be at Hilton, but can run over to provide keys (or set up a time to pass them on)

MozMamas can keep the guestroom keys for the week, but if they become demagnetized, you'll have to go back to the contact to get a new one.

=== parking ===

This site <http://portland.bestparking.com/> will help you find garages that allow overnight parking and show the accumulated cost.

Smartpark has five 24/7 downtown garages, you can see their rates here -> <http://www.portlandoregon.gov/transportation/article/254736>
Do double check that they allow overnight parking.

SW 1st and Jefferson - 123 SW Jefferson St
Open 24/7

SW 3rd and Alder - 621 SW 3rd Ave
Open 24/7

SW 4th and Yamhill - 818 SW 4th Ave
Open 24/7

SW 10th and Yamhill - 730 SW 10th Ave
Open 24/7

NW Naito and Davis - 33 NW Davis St
Open 24/7

== '''Airport Transportation''' ==

Once you arrive at your hotel, you will be able to check in. Some rooms might not be ready earlier in the day, but we will do our best. If you have questions or concerns with your reservation, please call Cheryl at 206-255-2926 or Nolan at 206-255-2844. They can assist you in sorting everything out.

=== Arrivals ===
There will be Mozilla airport shuttles from the Portland airport ("PDX") to hotels for arrivals between 8:00 am and 11:00 pm on December 1. Upon arrival at the airport on December 1, please proceed to baggage claim (even if you didn't check bags) and look for friendly faces holding signs that say Mozilla! They will help you find and board the shuttles. You will need to know what hotel you're staying in...If you need assistance, please call +01 (206)255-2929.

=== Departures ===
There will be return Mozilla airport shuttles from hotels to PDX between 5:00 am and 2:00 pm on December 6 (there will be shuttles starting at Marriott Waterfront at 4:00 am for the 6:40 am flight to SFO). We recommend leaving two hours or more before your flight.

==== Shuttle Routes ====

Shuttles will operate on routes (both for arrivals and departures -- there are very few places where we can park out buses):

'''Route 1 – NINES-BENSON'''
* Pick up location: The Nines - Morrison between 5th and 6th
* Those at Benson, walk to Nines for Shuttle (and/or are dropped off there)

'''Route 2 – HILTON-MARRIOTT CITY-PARAMOUNT-HEATHMAN'''
* Pick up location: The Hilton - Taylor between 5th & 6th
* Those at Marriott City Center, Paramount and Heathman, walk to Hilton for Shuttle (and/or are dropped off there)

'''Routes 3 – MARRIOTT WATERFRONT-MODERA'''

* Pick up Location: Marriott – Clay St between Naito & 1st; Modera – Clay St between 5th & 6th
* Stops at both hotels.

=== Travel or Hotel Help?===
If your flight changes and you are at the airport, approach the airline for assistance. If you need additional help, you can call Nancy at +01 (206)255-2929.

=== Shuttle Alternatives (for those arriving at odd times/dates) ===

These are transportation options for those arriving ''outside'' of the shuttle hours. '''If you are arriving during shuttle hours, please take the shuttle; we are saving a spot for you!'''

* '''Light rail ("MAX")'''
** The MAX light rail Red Line is the easiest way to travel to and from the airport.
** The trip between the airport and downtown Portland takes about 38 minutes.
** An adult ticket costs $2.50 (Youth $1.65, Honored Citizen $1). MAX ticket machines return change in coins, so small bills are recommended.
** You can roll your luggage on board.
** The first train of the day arrives at PDX at 4:45 a.m. The last train departs PDX at 11:50 p.m.
** The MAX station and ticket machines are located on the lower level, next to the south baggage claim area (turn right at the base of the escalator).
** For complete schedules and more information, visit www.trimet.org/schedules/maxredline.htm
** If you're planning to use TriMet for 2 or more trips, the TriMet Tickets app for [https://play.google.com/store/apps/details?id=org.trimet.mt.mobiletickets Android] or [https://itunes.apple.com/us/app/trimet-tickets/id687943985?mt=8&ign-mpt=uo%3D4 iOS] is highly recommended.

* '''[http://www.bluestarbus.com/downtown-express.php Blue Star Bus Downtown Shuttle]'''
** Book online in advance
** $14 one way
** When leaving the airport, you can find the Downtown Airport Express and other hotel shuttle buses on the terminal’s lower roadway.

* '''Taxi'''
** Should be used when two above options are not available
** $35 one way + tip ($3 - $5 is reasonable)
** The one-way trip takes 20-40 minutes.
** Taxis will be waiting in the center section of the airport terminal’s lower roadway outside of baggage claim.
** To get back to the airport from the city center, you can order a cab through the city’s main operators or from a hotel with a dedicated taxi stand.

=='''Work week schedule''' ==

Work week schedule (will be updated): https://docs.google.com/a/mozilla.com/spreadsheets/d/12K2OIUKAURjtQOcOMcPCOi4qeB1i80UWCA4EZLX94b4/edit#gid=0

'''Monday''':
* 6:00pm - 8:00pm (cocktails, informal)

'''Tuesday + Wednesday''':
* All-hands block: 9:00am - 11:00am PT
* Work week blocks:
** 11:00am - 2:00pm
** 2:00pm - 5:00pm (some spaces are available until 4:00pm only)
** 5:00pm - 8:00pm (dinner - see dine arounds)

'''Thursday'''
* Work week blocks
** 8:00am - 11:00am
** 11:00am - 2:00pm
** 2:00pm - 5:00pm (some spaces are available until 4:00pm only)
** 5:00pm - 8:00pm (dinner reservations will likely start at 6:30pm)

'''Friday'''
* Work week blocks
** 8:00am - 11:00am
** 11:00am - 2:00pm
** 2:00pm - 4:00pm
** 6:00pm - 12:00am Wrap Up (closing talks, food, drinks, live music, dancing and more - dress up for a night on the town)

=== Shuttles to/from the Marriott Waterfront ===

'''December 2 and 3'''
* Marriott Waterfront to PAM (7-9 am), return to Marriott (11 am - 1 pm), Hilton-Marriott Waterfront Loop (1 pm – 5 pm)
* Shuttle Hours – 7 am – 5 pm

'''December 4 and 5'''
* Hilton-Marriott Waterfront Loop (7 am – 5 pm)
* Shuttle Hours – 7 am – 5 pm

=='''Expenses'''==
We're managing the budget for the event carefully and centrally. And we are crafting an experience that doesn’t just give each team their own space for a work week, but also promotes teamwork and coming together.

There is no other budget for this so the use of corporate cards for this event, should you have one, needs to be cleared ahead of time, by your VP.

Almost all meals are covered by the event, including [https://wiki.mozilla.org/Portland_coincidental_work_week#Tuesday.2C_Wednesday.2C_Thursday dine-arounds] on Tuesday, Wednesday and Thursday evening. If you choose to do something different, the budget for dinner is in the $30 - $40 USD range per person per night.

For other items, please rely on our travel and expense guidelines.

===Volunteer Reimbursement via Reps===
Volunteers attending this event may submit for visa and U.S. travel/health insurance- related costs (and other incidentals) via Mozilla Reps:
* Mozilla Reps attending this event may submit for reimbursement through the [https://bugzilla.mozilla.org/form.reps.budget standard process].
* Mozillians who are not Mozilla Reps should contact a local Rep and the Rep will help them get reimbursed. The process is as follows:
** '''Step 1:''' contact a Rep [https://reps.mozilla.org/people/ in your country]*
** '''Step 2:''' once the Rep has accepted to process your reimbursement, give them an estimate of what your costs will be. If you need the funds beforehand, be sure to say that
** '''Step 3:''' after the event, send him/her all your scanned receipts and bank details/paypal account
** '''Step 4:''' inform the Rep once you have successfully received the funds

== '''Food''' ==
Portland has an amazing [http://en.wikipedia.org/wiki/Foodie foodie] culture and some of the coolest [http://www.foodcartsportland.com/ food carts] around. Rather than serve up standard conference fare for the whole week we're going to mix it up a bit. Some of our meals will be catered (hard to get out of that entirely), some won't. Some will be paid for centrally (meaning no cash/credit card needed), some won't (meaning you'll need to pay and submit for reimbursement). If paying up front for a meal that is not provided is not something you can reasonably do, please contact your manager OR, if you're a volunteer, the person that invited you to their work week.

'''Any of our leftover food, through our own catering, will be donated to: http://blanchethouse.org/'''.

==== Breakfast ====
* '''Tuesday/Wednesday''', breakfast will be catered and provided at the PAM (our all-hands session starts there at 9:00am, so breakfast will be available by 7:30am).
* '''Thursday/Friday''', breakfast will be catered and provided within each of the hotels where we have work week breakout space (Hilton, Marriott Waterfront, and Heathman).
* You may want to try coffee from [http://stumptowncoffee.com/location/portland/ Stumptown] at some point, and a donut or two from [http://voodoodoughnut.com VooDoo] both of which are distinctly Portland.
<blockquote>If you want donuts, you're much better off with [http://www.bluestardonuts.com/ Blue Star]. If you want coffee, Stumptown is OK, but try Coffeehouse Northwest, or Courier, or Public Domain, or Sterling, or Water Avenue, or any number of more interesting, small cafes.

Sincerely,
Portland.</blockquote>

==== Lunch ====
Mozillians are encouraged to head to the food cart center for lunch (although you'll need to pay for this on your own and submit for reimbursement). It's walking distance from most of our work week hotels and from the PAM. You can find it on this map (or ask a native): https://mapsengine.google.com/map/u/0/viewer?mid=zGDglM1VcNwI.khD1s_r2QdO0.

For those folks working out of the Marriott Waterfront, the food cart center is a bit of a walk. So, we're going to bring the carts to you.

In some cases (TBD) on some days, we'll provide catered lunches. More on this soon.

==== Dinner ====

===== '''Monday'''=====
There will be a cocktail party reception at the Portland Art Museum that starts at 6:00pm. There will be lots of great appetizers there as well as, well, cocktails (we'll have juice and sparkly water too). While it's not a formal dinner, it's likely enough to get you started. We have no other dinner plans for Monday evening so if you need more food, you'll need to head to a nearby restaurant (the range of expense expected for dinner is between $30 - $40 USD per person).

===== '''Tuesday, Wednesday, Thursday'''=====
So we can experience a bit of Portland, and still stay within our budget, we've arranged for three-evenings of Portland dine-arounds. Dine-arounds are a collection of local restaurants that have agreed to feed us a pre-set menu for a fixed price (includes one drink, the rest is up to you). In each case, depending on which restaurant you choose, your meal is pre-paid by Mozilla (you don't need to bring cash unless you want extras). We have enough seats each evening to cover about 75% of us, understanding there will be folks with other plans.

* Most of the restaurants are within walking distance of the Portland Art Museum and where they aren't, you can cab it or take public transit. Our reservations times vary but generally start after 6:00pm. Specific times will be noted on the Dine-Around sign-up sheet.

* Dietary restrictions can be accommodated. We have listed these under each restaurant and will update as we have more information. The only exceptions would be the restaurants doing buffets. There may be options, but no modifications. Let us know if you have specific accommodations needed and we can suggest some options.

* In some cases, menus have not been posted. Many restaurants use fresh, local, in season ingredients and won't know what they will feature until mid-month. We'll update the document as we get more information.

* If a restaurant is at its max and you'd still like to dine there, please add your name anyway. In lots of cases, restaurants can accommodate more than they've indicated. We wanted to start with a conservative estimate.

'''SIGN-UPS''': http://mzl.la/signups (pro tip: this link will take you to an un-editable version if you try to access it from a non-Mozilla Google account OR if you have a non-Mozilla and a Mozilla account open in the same browser session).

'''MENUS/RESTAURANT DETAIL''': http://mzl.la/menus

===== '''Friday''' =====
Closing talks / food / drinks / live music / dancing and more. Dress up for a night on the town. From 6pm until late. More details to follow.

==== Snacks ====
These will be provide at each of the work week sites (other than our office, where there are snacks already) at stations throughout the space.

== <big>Your Old Phones Needed in Portland</big> ==
Did you know that the estimated 500,000 mobile devices discarded daily can have another life improving someone's life?

[http://medicmobile.org/ Medic Mobile], a not-for-profit that seeks to advance healthcare in 16 countries with mobile technology (their app in the Firefox Marketplace here: https://marketplace.firefox.com/app/medic-mobile) recycles any type of mobile device through their Hope Phones program (https://hopephones.org/) to fund public health program around the world.

They need your help. '''Let's collect 1,000 old phones to the Mozilla offsite''' to empower health workers and improve the lives of many more. Bring your old Blackberry, StarTac, Chocolate, Galaxy or anonymous device to Portland and help us show that Mozilla cares. We'll have collections points around the offsite for easy drop-off.

If you plan to bring and donate a device that you received from Mozilla, please complete this form to help our IT group track our assets:
(https://docs.google.com/a/mozilla.com/forms/d/1ASIB1HWh3SGIHFG9pO8qX6LLka9ZgMMt8EDeRUf_QaQ/viewform)

Note that if you are [http://www.tsa.gov/press/releases/2014/07/06/enhanced-security-measures-certain-airports-overseas traveling internationally with phones in carry-on baggage], the phones must be charged and able to power-on. If security screeners ask you to power-on a phone, and it fails to do so, it may be confiscated.

Many thanks. Questions: Pete Scanlon (pscanlon@mozilla.com)

==Sessions==
If you have one to propose, add it here with a sign up link.

*[https://etherpad.mozilla.org/web-media-mozlandia-2014 Teach us how to do web media on Air Mozilla] Possible super-team for all people who know about media and how to best put it on the web. Hosted by the Air Mozilla team who are eager to learn.
*[https://etherpad.mozilla.org/project-foxeye-mozlandia-2014 Project FoxEye: Bring modern computer vision and image processing technology to the Web], Target audience: JavaScript developer, multimedia team and people who are interested in computer vision field. Hosted by Taipei Multimedia team.
* [https://etherpad.mozilla.org/ArabicRTL-Sessions Arabic RTL sessions] There will be multiple Arabic RTL sessions in Portland. From talks to hands-on workshop, check out the etherpad for more info!
* [https://etherpad.mozilla.org/MQM-PDX-TrainingSession MQM Translation Quality Testing]: Are you fluent in another language? Want to learn how you can easily get involved in testing the quality of the translations on Firefox OS? Come join us and we'll teach you! Let's start training the next generation of trainers!
*[https://etherpad.mozilla.org/servo-mozlandia-2014 Your first Servo contribution!] Members of the new browser engine project, Servo, will be mentoring all those interested in landing fixes to a slew of good first bugs. Free [http://imgur.com/CLnfQnO dino sticker] to the first 100 who open a PR!
* [https://etherpad.mozilla.org/ateam-pdx-performance-sheriffing Performance data sheriffing]: We're developing a system that allows push-based performance data (ala Talos) to be visualized and sheriffed within Treeherder. This project is called Perfherder. We'd like discuss plans for Perfherder, and get some input from potential users of it.
* [https://etherpad.mozilla.org/ateam-pdx-intermittent-oranges The War on Orange: improving the way we deal with intermittents]: Join the A-Team for a discussion about better ways to handle intermittent oranges, including fixing them, preventing them, hiding them, and reporting them.
* [https://etherpad.mozilla.org/ateam-pdx-treeherder Treeherder Brainstorming and Q&A]: Join the Treeherder developers for Q&A, brainstorming of future enhancements, and providing general feedback on Treeherder features.

==Extra Curriculars==
If you have one to propose, add it here with a sign up link.

* '''Hockey!!!''' (ice, shinny style) - 8-9:15am on Thursday, Dec 4th - [https://etherpad.mozilla.org/mozlandia-hockey sign up] -- feel free to come cheer/photograph
* '''SNOW Summit outing to Mount Hood''' (tentative) - [https://etherpad.mozilla.org/snow-summit-2014 Sign up + Information Here]
* '''Zumba! With our very own Rowe Hoffer''' (We will do it if there is interest) - [https://etherpad.mozilla.org/PDXZumba Sign up + Information Here]
* '''Find running partners!''' - [http://goo.gl/forms/ouh00YmVIt Sign up Here]
* '''Ping Pong!!!''' - There are loads of great places where Mozillians can play ping pong. And if we have enough signed up, we'll organize a tournament! [https://etherpad.mozilla.org/PDX-pingpong-extravaganza Sign up + Information Here]
* '''Indoor Kart Racing''' - Evenings Monday-Thursday (tentative) [https://etherpad.mozilla.org/portland-indoor-karting-2014-12 Interested? SIGN UP!]
* '''Homozilla''' (LGBTQ Mozillians and allies) will be doing a couple of [https://etherpad.mozilla.org/homozilla-night-out social things]
* '''Scotch, Whiskey, Bourbon!''' - Evening pub crawls to taste the best of Portland's brown. [https://etherpad.mozilla.org/pdx-brown-tour Sign up + Information here] [http://bit.ly/1tuj04H Portland Fun Map]
* '''Beer!''' - Evening pub crawls to taste the best of Portland's beer. [https://etherpad.mozilla.org/pdx-beer-tour Sign up + Information here] [http://bit.ly/1tuj04H Portland Fun Map]
* '''Crossfit''' - After a night of drinking, come work out and try not to puke :) [https://etherpad.mozilla.org/pdx-crossfit Sign up + Information here] [http://bit.ly/1tuj04H Portland Fun Map]
* '''Christians''' - Early morning [https://etherpad.mozilla.org/christians-in-portland prayer and fellowship]
* '''Board/Card Games''' - [https://etherpad.mozilla.org/portland-board-games organize here]
* '''UI/UX <3''' - Calling all UI and UX Mozillians. Let's carve out a hour or more to get together during Mozlandia for free hugs, good conversation and all the things that make our minds tick. [http://goo.gl/forms/y7LYr4MRuO Signup open to all]
* '''Birding''' - Hey birders and bird lovers, let's go for a walk at the Portland Audubon and check out who's overwintering near Portland. [http://etherpad.mozilla.org/birding-in-pdx Signup open to all]
*'''Crafty Mozilla''' - we will try to have in place a crafty corner/table and some stuff ready to make some awesome things! [https://etherpad.mozilla.org/crafty-mozilla-portland Sign up here!]
*'''Pozilla Poker Evening''' - Texas Hold'em. We have a set of chips! [https://etherpad.mozilla.org/pozilla Sign up here!]
*'''Playing Ingress''' - A cool cross-faction field-art of our favorite Dino-head, appleseed Mozilla PDX office space area & of course regular AP hunts, dog-fights, (for foreign agents a huge amount of) unique portal visits/captures etc. [https://etherpad.mozilla.org/ingress-portland-workweek Planning & Sign up]
*'''Gamers''' - We're not going to actually play games, just drink about them. Wednesday @ 9:30 Driftwood Room. Dress classy. (So, t-shirt and jeans, then? Sounds good.) [http://www.hoteldeluxeportland.com/eat-drink/driftwood-room/].
*'''Shootin' Range''' - Portland has several high-quality indoor ranges scattered around the city. Let's head out and plink on some targets! [https://etherpad.mozilla.org/mozrangeia Sign up here!]
*'''[http://groundkontrol.com/ Ground Kontrol]''' - Portland classic arcade open for max. 130 people from 8:00pm - 12:00am PT on Tuesday, December 2nd only. Minors welcome. Includes free play on all machines, as well as sodas. This is Mozilla sponsored. [https://etherpad.mozilla.org/ground-kontrol Sign up here].
*'''MozillaWiki Hackathon''' -- Wednesday and Thursday 6pm-10pm at Mozilla Portland office. We'll order food and work on MozillaWiki tasks. Other Mozilla projects welcome! If you're interested, put your name [https://wiki.etherpad.mozilla.org/december-pdx-hackathon here!]
*'''MozWomen Lunch''' -- Let's coincidentally get lunch one day (not restricted to women, of course - any welcome!). Etherpad [https://etherpad.mozilla.org/moz-women-lunch here!]
* '''[http://portlandartmuseum.org/ Portland Art Museum]''' - they are offering us full access to all of the galleries for $5.00 (standard ticketed entry is $15.00). Additionally, the museum gift shop will be offering a 10% discount to all participants, which, I might add, is doubly appealing, given that Oregon has no sales tax! The gift shop has an extensive collection of fine art books, gifts, and a variety of unique, locally-inspired merchandise, cards, and gift wrap.

== FAQ ==
Please add your questions to this document: https://docs.google.com/a/mozilla.com/document/d/1g-KqjCWwjJtgYHJYuFXgWYW9i0MY234_tMRPbXxq5Jc/edit

== Links ==
* Guest speaker suggestions: https://etherpad.mozilla.org/workweekspeakers
* Fun things to do suggestions: https://etherpad.mozilla.org/hogwarts

MozWeek/2014 Portland

2014-11-22T01:04:47Z

Cbeard: /* Time Blocks (subject to change) */

'''What is it?''' -- multiple work weeks, happening in the same city, at the same time, all within a few city blocks of each other + some opportunity to get together as one big group as well as with other teams as it makes sense. Then, on the last day, we have a giant party, Mozilla-style!

=='''Dates and Location'''==
Monday, December 1st - Friday, December 5th, 2014 (travel days Monday & Saturday*) in Portland, Oregon, USA (various venues): https://mapsengine.google.com/map/u/0/viewer?mid=zGDglM1VcNwI.khD1s_r2QdO0

''*For those countries where rest time is required on weekends (vs. work travel), Mozilla will cover a return on Monday the 8th if you choose.''

''*For non US travellers, please download the attached invitation to bring with you. The letter is formatted in Microsoft Word so you can insert your personal details. If you need personal assistance please email immigration@mozilla.com. https://docs.google.com/a/mozilla.com/document/d/1kYW-L4mXsrigRDosxAJY-FfZGYwLiySKPIea7lt_f7c/edit?usp=sharing .''

* Weather Forecast: [http://forecast.weather.gov/MapClick.php?lat=45.517&lon=-122.683&unit=1 °C] or [http://forecast.weather.gov/MapClick.php?lat=45.517&lon=-122.683 °F]

== '''Hotels & Meeting Space''' ==
The idea is that teams will stay in the same hotel. Won't be perfect, but we'll get as close as we can. All of the hotels are within walking distance from each other and from the Portland Art Museum. One (Marriot Waterfront) is a bit farther out (where we have a big chunk of rooms) so we'll likely have transportation to/from the PAM from there. You can see all hotels here: https://mapsengine.google.com/map/u/0/viewer?mid=zGDglM1VcNwI.khD1s_r2QdO0.

=== wifi ===
* '''Portland Art Museum (all-hands space, mofo, engagement, IT, WPR)'''
** 100MB bandwidth (5 MB down/2 MB up per user)
** 26 access points (dualband 802.11ac)
** Ethernet switches and router
** Custom network.

* '''Marriott Waterfront (engineering hub)'''
** 100Mb bandwidth dedicated to the meeting space + extra 100MB dedicated (for 200 MB total)
** 18 Ruckus 7962 Zoneflex G access points each capable of carrying up to 500 users. The Ruckus Zone director 3000 series prevents dropping from AP to AP.

* '''Hilton (apps day, some engineering breakouts, content services, legal/bd/privacy)'''
** 71 Mbps of bandwidth dedicated to the meeting space exclusively.
** 35 access points (Cisco 1130G) with dynamic Allocation (roughly one+ per space)

*'''Heathman (HR/Finance, small number of breakouts)'''
** Total Bandwidth is 100 mb(down) x 20mb (up) - this is shared between all guests at the hotel.
** Free access is 3X1 with a 5x2 5 second burst.
=== white boards, projectors, access to central printer, etc.===
Will be available in all spaces. Process TBD.

=== Mother's Rooms ===

*'''PAM''' - 4th floor women's restroom. It is a private and secluded space with a chair.
** Back up would be walking to Heathman, if you don't like the bathroom. There isn't another space available all days.

*'''Marriott''' - guestroom. Need to check in with Lisa Carlson at the registration desk on the Ballroom level for a key

*'''Hilton''' - guestroom - need to check in with Cheryl Barnet at the registration desk on the 2nd floor, outside Broadway rooms for a key.

*'''Heathman''' - guestroom. Need to check in with Cheryl Barnet. She'll be at Hilton, but can run over to provide keys (or set up a time to pass them on)

MozMamas can keep the guestroom keys for the week, but if they become demagnetized, you'll have to go back to the contact to get a new one.

the shuttles and get you on your way to your hotels. You will need to know what hotel you are staying at. If you need assistance, please call +01 (206)255-2929.

== '''Airport Transportation''' ==

Once you arrive at your hotel, you will be able to check in. Some rooms might not be ready earlier in the day, but we will do our best. If you have questions or concerns with your reservation, please call Cheryl at 206-255-2926 or Nolan at 206-255-2844. They can assist you in sorting everything out.

=== Arrivals ===
There will be Mozilla airport shuttles from the Portland airport ("PDX") to hotels for arrivals between 8:00 am and 10:00 pm on December 1. Upon arrival at the airport on December 1, please proceed to baggage claim (even if you didn't check bags) and look for friendly faces holding signs that say Mozilla! They will help you find and board the shuttles.

==== Shuttle Routes ====

Shuttles will operate on routes (both for arrivals and departures -- there are very few places where we can park out buses):

'''Route 1 – NINES-BENSON'''
* Pick up location: The Nines - Morrison between 5th and 6th
* Those at Benson, walk to Nines for Shuttle (and/or are dropped off there)

'''Route 2 – HILTON-MARRIOTT CITY-PARAMOUNT-HEATHMAN'''
* Pick up location: The Hilton - Taylor between 5th & 6th
* Those at Marriott City Center, Paramount and Heathman, walk to Hilton for Shuttle (and/or are dropped off there)

'''Routes 3 – MARRIOTT WATERFRONT-MODERA'''

* Pick up Location: Marriott – Clay St between Naito & 1st; Modera – Clay St between 5th & 6th
* Stops at both hotels.

=== Departures ===
There will be return Mozilla airport shuttles from hotels to PDX between 5:00 am and 2:00 pm on December 6 (there will be shuttles starting at Marriott Waterfront at 4:00 am for the 6:40 am flight to SFO). We recommend leaving two hours or more before your flight.

=== Travel Help?===
If your flight changes and you are at the airport, approach the airline for assistance. If you need additional help, you can call Nancy at +01 (206)255-2929.

=== Shuttle Alternatives (for those arriving at odd times/dates) ===
These are transportation options for those arriving ''outside'' of the shuttle hours. '''If you are arriving during shuttle hours, please take the shuttle; we are saving a spot for you!'''

* '''Light rail ("MAX")'''
** The MAX light rail Red Line is the easiest way to travel to and from the airport.
** The trip between the airport and downtown Portland takes about 38 minutes.
** An adult ticket costs $2.50 (Youth $1.65, Honored Citizen $1). MAX ticket machines return change in coins, so small bills are recommended.
** You can roll your luggage on board.
** The first train of the day arrives at PDX at 4:45 a.m. The last train departs PDX at 11:50 p.m.
** The MAX station and ticket machines are located on the lower level, next to the south baggage claim area (turn right at the base of the escalator).
** For complete schedules and more information, visit www.trimet.org/schedules/maxredline.htm
** If you're planning to use TriMet for 2 or more trips, the TriMet Tickets app for [https://play.google.com/store/apps/details?id=org.trimet.mt.mobiletickets Android] or [https://itunes.apple.com/us/app/trimet-tickets/id687943985?mt=8&ign-mpt=uo%3D4 iOS] is highly recommended.

* '''[http://www.bluestarbus.com/downtown-express.php Blue Star Bus Downtown Shuttle]'''
** Book online in advance
** $14 one way
** When leaving the airport, you can find the Downtown Airport Express and other hotel shuttle buses on the terminal’s lower roadway.

* '''Taxi'''
** Should be used when two above options are not available
** $35 one way + tip ($3 - $5 is reasonable)
** The one-way trip takes 20-40 minutes.
** Taxis will be waiting in the center section of the airport terminal’s lower roadway outside of baggage claim.
** To get back to the airport from the city center, you can order a cab through the city’s main operators or from a hotel with a dedicated taxi stand.

=='''Time Blocks''' (subject to change)==

Work week schedule (will be updated): https://docs.google.com/a/mozilla.com/spreadsheets/d/12K2OIUKAURjtQOcOMcPCOi4qeB1i80UWCA4EZLX94b4/edit#gid=0

'''Monday''':
* 6:00pm - 8:00pm (cocktails, informal)

'''Tuesday + Wednesday''':
* All-hands block: 9:00am - 11:00am PT
* Work week blocks:
** 11:00am - 2:00pm
** 2:00pm - 5:00pm (some spaces are available until 4:00pm only)
** 5:00pm - 8:00pm (dinner - see dine arounds)

'''Thursday'''
* Work week blocks
** 8:00am - 11:00am
** 11:00am - 2:00pm
** 2:00pm - 5:00pm (some spaces are available until 4:00pm only)
** 5:00pm - 8:00pm (dinner reservations will likely start at 6:30pm)

'''Friday'''
* Work week blocks
** 8:00am - 11:00am
** 11:00am - 2:00pm
** 2:00pm - 4:00pm
** 6:00pm - 12:00am (closing talks, food, drinks, live music, dancing and more - dress up for a night on the town)

=='''Expenses'''==
We're managing the budget for the event carefully and centrally. And we are crafting an experience that doesn’t just give each team their own space for a work week, but also promotes teamwork and coming together.

There is no other budget for this so the use of corporate cards for this event, should you have one, needs to be cleared ahead of time, by your VP.

Almost all meals are covered by the event, including [https://wiki.mozilla.org/Portland_coincidental_work_week#Tuesday.2C_Wednesday.2C_Thursday dine-arounds] on Tuesday, Wednesday and Thursday evening. If you choose to do something different, the budget for dinner is in the $30 - $40 USD range per person per night.

For other items, please rely on our travel and expense guidelines.

===Volunteer Reimbursement via Reps===
Volunteers attending this event may submit for visa and U.S. travel/health insurance- related costs (and other incidentals) via Mozilla Reps:
* Mozilla Reps attending this event may submit for reimbursement through the [https://bugzilla.mozilla.org/form.reps.budget standard process].
* Mozillians who are not Mozilla Reps should contact a local Rep and the Rep will help them get reimbursed. The process is as follows:
** '''Step 1:''' contact a Rep [https://reps.mozilla.org/people/ in your country]*
** '''Step 2:''' once the Rep has accepted to process your reimbursement, give them an estimate of what your costs will be. If you need the funds beforehand, be sure to say that
** '''Step 3:''' after the event, send him/her all your scanned receipts and bank details/paypal account
** '''Step 4:''' inform the Rep once you have successfully received the funds

== '''Food''' ==
Portland has an amazing [http://en.wikipedia.org/wiki/Foodie foodie] culture and some of the coolest [http://www.foodcartsportland.com/ food carts] around. Rather than serve up standard conference fare for the whole week we're going to mix it up a bit. Some of our meals will be catered (hard to get out of that entirely), some won't. Some will be paid for centrally (meaning no cash/credit card needed), some won't (meaning you'll need to pay and submit for reimbursement). If paying up front for a meal that is not provided is not something you can reasonably do, please contact your manager OR, if you're a volunteer, the person that invited you to their work week.

'''Any of our leftover food, through our own catering, will be donated to: http://blanchethouse.org/'''.

==== Breakfast ====
* '''Tuesday/Wednesday''', breakfast will be catered and provided at the PAM (our all-hands session starts there at 9:00am, so breakfast will be available by 7:30am).
* '''Thursday/Friday''', breakfast will be catered and provided within each of the hotels where we have work week breakout space (Hilton, Marriott Waterfront, and Heathman).
* You may want to try coffee from [http://stumptowncoffee.com/location/portland/ Stumptown] at some point, and a donut or two from [http://voodoodoughnut.com VooDoo] both of which are distinctly Portland.
<blockquote>If you want donuts, you're much better off with [http://www.bluestardonuts.com/ Blue Star]. If you want coffee, Stumptown is OK, but try Coffeehouse Northwest, or Courier, or Public Domain, or Sterling, or Water Avenue, or any number of more interesting, small cafes.

Sincerely,
Portland.</blockquote>

==== Lunch ====
Mozillians are encouraged to head to the food cart center for lunch (although you'll need to pay for this on your own and submit for reimbursement). It's walking distance from most of our work week hotels and from the PAM. You can find it on this map (or ask a native): https://mapsengine.google.com/map/u/0/viewer?mid=zGDglM1VcNwI.khD1s_r2QdO0.

For those folks working out of the Marriott Waterfront, the food cart center is a bit of a walk. So, we're going to bring the carts to you.

In some cases (TBD) on some days, we'll provide catered lunches. More on this soon.

==== Dinner ====

===== '''Monday'''=====
There will be a cocktail party reception at the Portland Art Museum that starts at 6:00pm. There will be lots of great appetizers there as well as, well, cocktails (we'll have juice and sparkly water too). While it's not a formal dinner, it's likely enough to get you started. We have no other dinner plans for Monday evening so if you need more food, you'll need to head to a nearby restaurant (the range of expense expected for dinner is between $30 - $40 USD per person).

===== '''Tuesday, Wednesday, Thursday'''=====
So we can experience a bit of Portland, and still stay within our budget, we've arranged for three-evenings of Portland dine-arounds. Dine-arounds are a collection of local restaurants that have agreed to feed us a pre-set menu for a fixed price (includes one drink, the rest is up to you). In each case, depending on which restaurant you choose, your meal is pre-paid by Mozilla (you don't need to bring cash unless you want extras). We have enough seats each evening to cover about 75% of us, understanding there will be folks with other plans.

* Most of the restaurants are within walking distance of the Portland Art Museum and where they aren't, you can cab it or take public transit. Our reservations times vary but generally start after 6:00pm. Specific times will be noted on the Dine-Around sign-up sheet.

* Dietary restrictions can be accommodated. We have listed these under each restaurant and will update as we have more information. The only exceptions would be the restaurants doing buffets. There may be options, but no modifications. Let us know if you have specific accommodations needed and we can suggest some options.

* In some cases, menus have not been posted. Many restaurants use fresh, local, in season ingredients and won't know what they will feature until mid-month. We'll update the document as we get more information.

* If a restaurant is at its max and you'd still like to dine there, please add your name anyway. In lots of cases, restaurants can accommodate more than they've indicated. We wanted to start with a conservative estimate.

'''SIGN-UPS''': http://mzl.la/signups (pro tip: this link will take you to an un-editable version if you try to access it from a non-Mozilla Google account OR if you have a non-Mozilla and a Mozilla account open in the same browser session).

'''MENUS/RESTAURANT DETAIL''': http://mzl.la/menus

===== '''Friday''' =====
Closing talks / food / drinks / live music / dancing and more. Dress up for a night on the town. From 6pm until late. More details to follow.

==== Snacks ====
These will be provide at each of the work week sites (other than our office, where there are snacks already) at stations throughout the space.

== <big>Your Old Phones Needed in Portland</big> ==
Did you know that the estimated 500,000 mobile devices discarded daily can have another life improving someone's life?

[http://medicmobile.org/ Medic Mobile], a not-for-profit that seeks to advance healthcare in 16 countries with mobile technology (their app in the Firefox Marketplace here: https://marketplace.firefox.com/app/medic-mobile) recycles any type of mobile device through their Hope Phones program (https://hopephones.org/) to fund public health program around the world.

They need your help. '''Let's collect 1,000 old phones to the Mozilla offsite''' to empower health workers and improve the lives of many more. Bring your old Blackberry, StarTac, Chocolate, Galaxy or anonymous device to Portland and help us show that Mozilla cares. We'll have collections points around the offsite for easy drop-off.

If you plan to bring and donate a device that you received from Mozilla, please complete this form to help our IT group track our assets:
(https://docs.google.com/a/mozilla.com/forms/d/1ASIB1HWh3SGIHFG9pO8qX6LLka9ZgMMt8EDeRUf_QaQ/viewform)

Note that if you are [http://www.tsa.gov/press/releases/2014/07/06/enhanced-security-measures-certain-airports-overseas traveling internationally with phones in carry-on baggage], the phones must be charged and able to power-on. If security screeners ask you to power-on a phone, and it fails to do so, it may be confiscated.

Many thanks. Questions: Pete Scanlon (pscanlon@mozilla.com)

==Sessions==
If you have one to propose, add it here with a sign up link.

*[https://etherpad.mozilla.org/web-media-mozlandia-2014 Teach us how to do web media on Air Mozilla] Possible super-team for all people who know about media and how to best put it on the web. Hosted by the Air Mozilla team who are eager to learn.
*[https://etherpad.mozilla.org/project-foxeye-mozlandia-2014 Project FoxEye: Bring modern computer vision and image processing technology to the Web], Target audience: JavaScript developer, multimedia team and people who are interested in computer vision field. Hosted by Taipei Multimedia team.
* [https://etherpad.mozilla.org/ArabicRTL-Sessions Arabic RTL sessions] There will be multiple Arabic RTL sessions in Portland. From talks to hands-on workshop, check out the etherpad for more info!
* [https://etherpad.mozilla.org/MQM-PDX-TrainingSession MQM Translation Quality Testing]: Are you fluent in another language? Want to learn how you can easily get involved in testing the quality of the translations on Firefox OS? Come join us and we'll teach you! Let's start training the next generation of trainers!

==Extra Curriculars==
If you have one to propose, add it here with a sign up link.

* '''Hockey!!!''' (ice, shinny style) - 8-9:15am on Thursday, Dec 4th - [https://etherpad.mozilla.org/mozlandia-hockey sign ups are full, waitlist available] -- feel free to come cheer/photograph
* '''SNOW Summit outing to Mount Hood''' (tentative) - [https://etherpad.mozilla.org/snow-summit-2014 Sign up + Information Here]
* '''Zumba! With our very own Rowe Hoffer''' (We will do it if there is interest) - [https://etherpad.mozilla.org/PDXZumba Sign up + Information Here]
* '''Find running partners!''' - [http://goo.gl/forms/ouh00YmVIt Sign up Here]
* '''Ping Pong!!!''' - There are loads of great places where Mozillians can play ping pong. And if we have enough signed up, we'll organize a tournament! [https://etherpad.mozilla.org/PDX-pingpong-extravaganza Sign up + Information Here]
* '''Indoor Kart Racing''' - Evenings Monday-Thursday (tentative) [https://etherpad.mozilla.org/portland-indoor-karting-2014-12 Interested? SIGN UP!]
* '''Homozilla''' (LGBTQ Mozillians and allies) will be doing a couple of [https://etherpad.mozilla.org/homozilla-night-out social things]
* '''Scotch, Whiskey, Bourbon!''' - Evening pub crawls to taste the best of Portland's brown. [https://etherpad.mozilla.org/pdx-brown-tour Sign up + Information here] [http://bit.ly/1tuj04H Portland Fun Map]
* '''Beer!''' - Evening pub crawls to taste the best of Portland's beer. [https://etherpad.mozilla.org/pdx-beer-tour Sign up + Information here] [http://bit.ly/1tuj04H Portland Fun Map]
* '''Crossfit''' - After a night of drinking, come work out and try not to puke :) [https://etherpad.mozilla.org/pdx-crossfit Sign up + Information here] [http://bit.ly/1tuj04H Portland Fun Map]
* '''Christians''' - Early morning [https://etherpad.mozilla.org/christians-in-portland prayer and fellowship]
* '''Board/Card Games''' - [https://etherpad.mozilla.org/portland-board-games organize here]
* '''UI/UX <3''' - Calling all UI and UX Mozillians. Let's carve out a hour or more to get together during Mozlandia for free hugs, good conversation and all the things that make our minds tick. [http://goo.gl/forms/y7LYr4MRuO Signup open to all]
* '''Birding''' - Hey birders and bird lovers, let's go for a walk at the Portland Audubon and check out who's overwintering near Portland. [http://etherpad.mozilla.org/birding-in-pdx Signup open to all]
*'''Crafty Mozilla''' - we will try to have in place a crafty corner/table and some stuff ready to make some awesome things! [https://etherpad.mozilla.org/crafty-mozilla-portland Sign up here!]
*'''Pozilla Poker Evening''' - Texas Hold'em. We have a set of chips! [https://etherpad.mozilla.org/pozilla Sign up here!]
*'''Playing Ingress''' - A cool cross-faction field-art of our favorite Dino-head, appleseed Mozilla PDX office space area & of course regular AP hunts, dog-fights, (for foreign agents a huge amount of) unique portal visits/captures etc. [https://etherpad.mozilla.org/ingress-portland-workweek Planning & Sign up]
*'''Gamers''' - We're not going to actually play games, just drink about them. Wednesday @ 9:30 Driftwood Room [http://www.hoteldeluxeportland.com/eat-drink/driftwood-room/].
*'''Shootin' Range''' - Portland has several high-quality indoor ranges scattered around the city. Let's head out and plink on some targets! [https://etherpad.mozilla.org/mozrangeia Sign up here!]
*'''[http://groundkontrol.com/ Ground Kontrol]''' - Portland classic arcade open for max. 130 people from 8:00pm - 12:00am PT on Tuesday, December 2nd only. Minors welcome. Includes free play on all machines, as well as sodas. This is Mozilla sponsored. [https://etherpad.mozilla.org/ground-kontrol Sign up here].
*'''MozillaWiki Hackathon''' -- Details to come. If you're interested, put your name [https://wiki.etherpad.mozilla.org/december-pdx-hackathon here!]
*'''MozWomen Lunch''' -- Let's coincidentally get lunch one day (not restricted to women, of course - any welcome!). Etherpad [https://etherpad.mozilla.org/moz-women-lunch here!]

== FAQ ==
Please add your questions to this document: https://docs.google.com/a/mozilla.com/document/d/1g-KqjCWwjJtgYHJYuFXgWYW9i0MY234_tMRPbXxq5Jc/edit

== Links ==
* Guest speaker suggestions: https://etherpad.mozilla.org/workweekspeakers
* Fun things to do suggestions: https://etherpad.mozilla.org/hogwarts

MozWeek/2014 Portland

2014-11-22T01:03:59Z

Cbeard: /* Friday */

'''What is it?''' -- multiple work weeks, happening in the same city, at the same time, all within a few city blocks of each other + some opportunity to get together as one big group as well as with other teams as it makes sense. Then, on the last day, we have a giant party, Mozilla-style!

=='''Dates and Location'''==
Monday, December 1st - Friday, December 5th, 2014 (travel days Monday & Saturday*) in Portland, Oregon, USA (various venues): https://mapsengine.google.com/map/u/0/viewer?mid=zGDglM1VcNwI.khD1s_r2QdO0

''*For those countries where rest time is required on weekends (vs. work travel), Mozilla will cover a return on Monday the 8th if you choose.''

''*For non US travellers, please download the attached invitation to bring with you. The letter is formatted in Microsoft Word so you can insert your personal details. If you need personal assistance please email immigration@mozilla.com. https://docs.google.com/a/mozilla.com/document/d/1kYW-L4mXsrigRDosxAJY-FfZGYwLiySKPIea7lt_f7c/edit?usp=sharing .''

* Weather Forecast: [http://forecast.weather.gov/MapClick.php?lat=45.517&lon=-122.683&unit=1 °C] or [http://forecast.weather.gov/MapClick.php?lat=45.517&lon=-122.683 °F]

== '''Hotels & Meeting Space''' ==
The idea is that teams will stay in the same hotel. Won't be perfect, but we'll get as close as we can. All of the hotels are within walking distance from each other and from the Portland Art Museum. One (Marriot Waterfront) is a bit farther out (where we have a big chunk of rooms) so we'll likely have transportation to/from the PAM from there. You can see all hotels here: https://mapsengine.google.com/map/u/0/viewer?mid=zGDglM1VcNwI.khD1s_r2QdO0.

=== wifi ===
* '''Portland Art Museum (all-hands space, mofo, engagement, IT, WPR)'''
** 100MB bandwidth (5 MB down/2 MB up per user)
** 26 access points (dualband 802.11ac)
** Ethernet switches and router
** Custom network.

* '''Marriott Waterfront (engineering hub)'''
** 100Mb bandwidth dedicated to the meeting space + extra 100MB dedicated (for 200 MB total)
** 18 Ruckus 7962 Zoneflex G access points each capable of carrying up to 500 users. The Ruckus Zone director 3000 series prevents dropping from AP to AP.

* '''Hilton (apps day, some engineering breakouts, content services, legal/bd/privacy)'''
** 71 Mbps of bandwidth dedicated to the meeting space exclusively.
** 35 access points (Cisco 1130G) with dynamic Allocation (roughly one+ per space)

*'''Heathman (HR/Finance, small number of breakouts)'''
** Total Bandwidth is 100 mb(down) x 20mb (up) - this is shared between all guests at the hotel.
** Free access is 3X1 with a 5x2 5 second burst.
=== white boards, projectors, access to central printer, etc.===
Will be available in all spaces. Process TBD.

=== Mother's Rooms ===

*'''PAM''' - 4th floor women's restroom. It is a private and secluded space with a chair.
** Back up would be walking to Heathman, if you don't like the bathroom. There isn't another space available all days.

*'''Marriott''' - guestroom. Need to check in with Lisa Carlson at the registration desk on the Ballroom level for a key

*'''Hilton''' - guestroom - need to check in with Cheryl Barnet at the registration desk on the 2nd floor, outside Broadway rooms for a key.

*'''Heathman''' - guestroom. Need to check in with Cheryl Barnet. She'll be at Hilton, but can run over to provide keys (or set up a time to pass them on)

MozMamas can keep the guestroom keys for the week, but if they become demagnetized, you'll have to go back to the contact to get a new one.

the shuttles and get you on your way to your hotels. You will need to know what hotel you are staying at. If you need assistance, please call +01 (206)255-2929.

== '''Airport Transportation''' ==

Once you arrive at your hotel, you will be able to check in. Some rooms might not be ready earlier in the day, but we will do our best. If you have questions or concerns with your reservation, please call Cheryl at 206-255-2926 or Nolan at 206-255-2844. They can assist you in sorting everything out.

=== Arrivals ===
There will be Mozilla airport shuttles from the Portland airport ("PDX") to hotels for arrivals between 8:00 am and 10:00 pm on December 1. Upon arrival at the airport on December 1, please proceed to baggage claim (even if you didn't check bags) and look for friendly faces holding signs that say Mozilla! They will help you find and board the shuttles.

==== Shuttle Routes ====

Shuttles will operate on routes (both for arrivals and departures -- there are very few places where we can park out buses):

'''Route 1 – NINES-BENSON'''
* Pick up location: The Nines - Morrison between 5th and 6th
* Those at Benson, walk to Nines for Shuttle (and/or are dropped off there)

'''Route 2 – HILTON-MARRIOTT CITY-PARAMOUNT-HEATHMAN'''
* Pick up location: The Hilton - Taylor between 5th & 6th
* Those at Marriott City Center, Paramount and Heathman, walk to Hilton for Shuttle (and/or are dropped off there)

'''Routes 3 – MARRIOTT WATERFRONT-MODERA'''

* Pick up Location: Marriott – Clay St between Naito & 1st; Modera – Clay St between 5th & 6th
* Stops at both hotels.

=== Departures ===
There will be return Mozilla airport shuttles from hotels to PDX between 5:00 am and 2:00 pm on December 6 (there will be shuttles starting at Marriott Waterfront at 4:00 am for the 6:40 am flight to SFO). We recommend leaving two hours or more before your flight.

=== Travel Help?===
If your flight changes and you are at the airport, approach the airline for assistance. If you need additional help, you can call Nancy at +01 (206)255-2929.

=== Shuttle Alternatives (for those arriving at odd times/dates) ===
These are transportation options for those arriving ''outside'' of the shuttle hours. '''If you are arriving during shuttle hours, please take the shuttle; we are saving a spot for you!'''

* '''Light rail ("MAX")'''
** The MAX light rail Red Line is the easiest way to travel to and from the airport.
** The trip between the airport and downtown Portland takes about 38 minutes.
** An adult ticket costs $2.50 (Youth $1.65, Honored Citizen $1). MAX ticket machines return change in coins, so small bills are recommended.
** You can roll your luggage on board.
** The first train of the day arrives at PDX at 4:45 a.m. The last train departs PDX at 11:50 p.m.
** The MAX station and ticket machines are located on the lower level, next to the south baggage claim area (turn right at the base of the escalator).
** For complete schedules and more information, visit www.trimet.org/schedules/maxredline.htm
** If you're planning to use TriMet for 2 or more trips, the TriMet Tickets app for [https://play.google.com/store/apps/details?id=org.trimet.mt.mobiletickets Android] or [https://itunes.apple.com/us/app/trimet-tickets/id687943985?mt=8&ign-mpt=uo%3D4 iOS] is highly recommended.

* '''[http://www.bluestarbus.com/downtown-express.php Blue Star Bus Downtown Shuttle]'''
** Book online in advance
** $14 one way
** When leaving the airport, you can find the Downtown Airport Express and other hotel shuttle buses on the terminal’s lower roadway.

* '''Taxi'''
** Should be used when two above options are not available
** $35 one way + tip ($3 - $5 is reasonable)
** The one-way trip takes 20-40 minutes.
** Taxis will be waiting in the center section of the airport terminal’s lower roadway outside of baggage claim.
** To get back to the airport from the city center, you can order a cab through the city’s main operators or from a hotel with a dedicated taxi stand.

=='''Time Blocks''' (subject to change)==

Work week schedule (will be updated): https://docs.google.com/a/mozilla.com/spreadsheets/d/12K2OIUKAURjtQOcOMcPCOi4qeB1i80UWCA4EZLX94b4/edit#gid=0

'''Monday''':
* 6:00pm - 8:00pm (cocktails, informal)

'''Tuesday + Wednesday''':
* All-hands block: 9:00am - 11:00am PT
* Work week blocks:
** 11:00am - 2:00pm
** 2:00pm - 5:00pm (some spaces are available until 4:00pm only)
** 5:00pm - 8:00pm (dinner - see dine arounds)

'''Thursday'''
* Work week blocks
** 8:00am - 11:00am
** 11:00am - 2:00pm
** 2:00pm - 5:00pm (some spaces are available until 4:00pm only)
** 5:00pm - 8:00pm (dinner reservations will likely start at 6:30pm)

'''Friday'''
* Work week blocks
** 8:00am - 11:00am
** 11:00am - 2:00pm
** 2:00pm - 4:00pm
** 6:00pm - 12:00am (dinner + party)

=='''Expenses'''==
We're managing the budget for the event carefully and centrally. And we are crafting an experience that doesn’t just give each team their own space for a work week, but also promotes teamwork and coming together.

There is no other budget for this so the use of corporate cards for this event, should you have one, needs to be cleared ahead of time, by your VP.

Almost all meals are covered by the event, including [https://wiki.mozilla.org/Portland_coincidental_work_week#Tuesday.2C_Wednesday.2C_Thursday dine-arounds] on Tuesday, Wednesday and Thursday evening. If you choose to do something different, the budget for dinner is in the $30 - $40 USD range per person per night.

For other items, please rely on our travel and expense guidelines.

===Volunteer Reimbursement via Reps===
Volunteers attending this event may submit for visa and U.S. travel/health insurance- related costs (and other incidentals) via Mozilla Reps:
* Mozilla Reps attending this event may submit for reimbursement through the [https://bugzilla.mozilla.org/form.reps.budget standard process].
* Mozillians who are not Mozilla Reps should contact a local Rep and the Rep will help them get reimbursed. The process is as follows:
** '''Step 1:''' contact a Rep [https://reps.mozilla.org/people/ in your country]*
** '''Step 2:''' once the Rep has accepted to process your reimbursement, give them an estimate of what your costs will be. If you need the funds beforehand, be sure to say that
** '''Step 3:''' after the event, send him/her all your scanned receipts and bank details/paypal account
** '''Step 4:''' inform the Rep once you have successfully received the funds

== '''Food''' ==
Portland has an amazing [http://en.wikipedia.org/wiki/Foodie foodie] culture and some of the coolest [http://www.foodcartsportland.com/ food carts] around. Rather than serve up standard conference fare for the whole week we're going to mix it up a bit. Some of our meals will be catered (hard to get out of that entirely), some won't. Some will be paid for centrally (meaning no cash/credit card needed), some won't (meaning you'll need to pay and submit for reimbursement). If paying up front for a meal that is not provided is not something you can reasonably do, please contact your manager OR, if you're a volunteer, the person that invited you to their work week.

'''Any of our leftover food, through our own catering, will be donated to: http://blanchethouse.org/'''.

==== Breakfast ====
* '''Tuesday/Wednesday''', breakfast will be catered and provided at the PAM (our all-hands session starts there at 9:00am, so breakfast will be available by 7:30am).
* '''Thursday/Friday''', breakfast will be catered and provided within each of the hotels where we have work week breakout space (Hilton, Marriott Waterfront, and Heathman).
* You may want to try coffee from [http://stumptowncoffee.com/location/portland/ Stumptown] at some point, and a donut or two from [http://voodoodoughnut.com VooDoo] both of which are distinctly Portland.
<blockquote>If you want donuts, you're much better off with [http://www.bluestardonuts.com/ Blue Star]. If you want coffee, Stumptown is OK, but try Coffeehouse Northwest, or Courier, or Public Domain, or Sterling, or Water Avenue, or any number of more interesting, small cafes.

Sincerely,
Portland.</blockquote>

==== Lunch ====
Mozillians are encouraged to head to the food cart center for lunch (although you'll need to pay for this on your own and submit for reimbursement). It's walking distance from most of our work week hotels and from the PAM. You can find it on this map (or ask a native): https://mapsengine.google.com/map/u/0/viewer?mid=zGDglM1VcNwI.khD1s_r2QdO0.

For those folks working out of the Marriott Waterfront, the food cart center is a bit of a walk. So, we're going to bring the carts to you.

In some cases (TBD) on some days, we'll provide catered lunches. More on this soon.

==== Dinner ====

===== '''Monday'''=====
There will be a cocktail party reception at the Portland Art Museum that starts at 6:00pm. There will be lots of great appetizers there as well as, well, cocktails (we'll have juice and sparkly water too). While it's not a formal dinner, it's likely enough to get you started. We have no other dinner plans for Monday evening so if you need more food, you'll need to head to a nearby restaurant (the range of expense expected for dinner is between $30 - $40 USD per person).

===== '''Tuesday, Wednesday, Thursday'''=====
So we can experience a bit of Portland, and still stay within our budget, we've arranged for three-evenings of Portland dine-arounds. Dine-arounds are a collection of local restaurants that have agreed to feed us a pre-set menu for a fixed price (includes one drink, the rest is up to you). In each case, depending on which restaurant you choose, your meal is pre-paid by Mozilla (you don't need to bring cash unless you want extras). We have enough seats each evening to cover about 75% of us, understanding there will be folks with other plans.

* Most of the restaurants are within walking distance of the Portland Art Museum and where they aren't, you can cab it or take public transit. Our reservations times vary but generally start after 6:00pm. Specific times will be noted on the Dine-Around sign-up sheet.

* Dietary restrictions can be accommodated. We have listed these under each restaurant and will update as we have more information. The only exceptions would be the restaurants doing buffets. There may be options, but no modifications. Let us know if you have specific accommodations needed and we can suggest some options.

* In some cases, menus have not been posted. Many restaurants use fresh, local, in season ingredients and won't know what they will feature until mid-month. We'll update the document as we get more information.

* If a restaurant is at its max and you'd still like to dine there, please add your name anyway. In lots of cases, restaurants can accommodate more than they've indicated. We wanted to start with a conservative estimate.

'''SIGN-UPS''': http://mzl.la/signups (pro tip: this link will take you to an un-editable version if you try to access it from a non-Mozilla Google account OR if you have a non-Mozilla and a Mozilla account open in the same browser session).

'''MENUS/RESTAURANT DETAIL''': http://mzl.la/menus

===== '''Friday''' =====
Closing talks / food / drinks / live music / dancing and more. Dress up for a night on the town. From 6pm until late. More details to follow.

==== Snacks ====
These will be provide at each of the work week sites (other than our office, where there are snacks already) at stations throughout the space.

== <big>Your Old Phones Needed in Portland</big> ==
Did you know that the estimated 500,000 mobile devices discarded daily can have another life improving someone's life?

[http://medicmobile.org/ Medic Mobile], a not-for-profit that seeks to advance healthcare in 16 countries with mobile technology (their app in the Firefox Marketplace here: https://marketplace.firefox.com/app/medic-mobile) recycles any type of mobile device through their Hope Phones program (https://hopephones.org/) to fund public health program around the world.

They need your help. '''Let's collect 1,000 old phones to the Mozilla offsite''' to empower health workers and improve the lives of many more. Bring your old Blackberry, StarTac, Chocolate, Galaxy or anonymous device to Portland and help us show that Mozilla cares. We'll have collections points around the offsite for easy drop-off.

If you plan to bring and donate a device that you received from Mozilla, please complete this form to help our IT group track our assets:
(https://docs.google.com/a/mozilla.com/forms/d/1ASIB1HWh3SGIHFG9pO8qX6LLka9ZgMMt8EDeRUf_QaQ/viewform)

Note that if you are [http://www.tsa.gov/press/releases/2014/07/06/enhanced-security-measures-certain-airports-overseas traveling internationally with phones in carry-on baggage], the phones must be charged and able to power-on. If security screeners ask you to power-on a phone, and it fails to do so, it may be confiscated.

Many thanks. Questions: Pete Scanlon (pscanlon@mozilla.com)

==Sessions==
If you have one to propose, add it here with a sign up link.

*[https://etherpad.mozilla.org/web-media-mozlandia-2014 Teach us how to do web media on Air Mozilla] Possible super-team for all people who know about media and how to best put it on the web. Hosted by the Air Mozilla team who are eager to learn.
*[https://etherpad.mozilla.org/project-foxeye-mozlandia-2014 Project FoxEye: Bring modern computer vision and image processing technology to the Web], Target audience: JavaScript developer, multimedia team and people who are interested in computer vision field. Hosted by Taipei Multimedia team.
* [https://etherpad.mozilla.org/ArabicRTL-Sessions Arabic RTL sessions] There will be multiple Arabic RTL sessions in Portland. From talks to hands-on workshop, check out the etherpad for more info!
* [https://etherpad.mozilla.org/MQM-PDX-TrainingSession MQM Translation Quality Testing]: Are you fluent in another language? Want to learn how you can easily get involved in testing the quality of the translations on Firefox OS? Come join us and we'll teach you! Let's start training the next generation of trainers!

==Extra Curriculars==
If you have one to propose, add it here with a sign up link.

* '''Hockey!!!''' (ice, shinny style) - 8-9:15am on Thursday, Dec 4th - [https://etherpad.mozilla.org/mozlandia-hockey sign ups are full, waitlist available] -- feel free to come cheer/photograph
* '''SNOW Summit outing to Mount Hood''' (tentative) - [https://etherpad.mozilla.org/snow-summit-2014 Sign up + Information Here]
* '''Zumba! With our very own Rowe Hoffer''' (We will do it if there is interest) - [https://etherpad.mozilla.org/PDXZumba Sign up + Information Here]
* '''Find running partners!''' - [http://goo.gl/forms/ouh00YmVIt Sign up Here]
* '''Ping Pong!!!''' - There are loads of great places where Mozillians can play ping pong. And if we have enough signed up, we'll organize a tournament! [https://etherpad.mozilla.org/PDX-pingpong-extravaganza Sign up + Information Here]
* '''Indoor Kart Racing''' - Evenings Monday-Thursday (tentative) [https://etherpad.mozilla.org/portland-indoor-karting-2014-12 Interested? SIGN UP!]
* '''Homozilla''' (LGBTQ Mozillians and allies) will be doing a couple of [https://etherpad.mozilla.org/homozilla-night-out social things]
* '''Scotch, Whiskey, Bourbon!''' - Evening pub crawls to taste the best of Portland's brown. [https://etherpad.mozilla.org/pdx-brown-tour Sign up + Information here] [http://bit.ly/1tuj04H Portland Fun Map]
* '''Beer!''' - Evening pub crawls to taste the best of Portland's beer. [https://etherpad.mozilla.org/pdx-beer-tour Sign up + Information here] [http://bit.ly/1tuj04H Portland Fun Map]
* '''Crossfit''' - After a night of drinking, come work out and try not to puke :) [https://etherpad.mozilla.org/pdx-crossfit Sign up + Information here] [http://bit.ly/1tuj04H Portland Fun Map]
* '''Christians''' - Early morning [https://etherpad.mozilla.org/christians-in-portland prayer and fellowship]
* '''Board/Card Games''' - [https://etherpad.mozilla.org/portland-board-games organize here]
* '''UI/UX <3''' - Calling all UI and UX Mozillians. Let's carve out a hour or more to get together during Mozlandia for free hugs, good conversation and all the things that make our minds tick. [http://goo.gl/forms/y7LYr4MRuO Signup open to all]
* '''Birding''' - Hey birders and bird lovers, let's go for a walk at the Portland Audubon and check out who's overwintering near Portland. [http://etherpad.mozilla.org/birding-in-pdx Signup open to all]
*'''Crafty Mozilla''' - we will try to have in place a crafty corner/table and some stuff ready to make some awesome things! [https://etherpad.mozilla.org/crafty-mozilla-portland Sign up here!]
*'''Pozilla Poker Evening''' - Texas Hold'em. We have a set of chips! [https://etherpad.mozilla.org/pozilla Sign up here!]
*'''Playing Ingress''' - A cool cross-faction field-art of our favorite Dino-head, appleseed Mozilla PDX office space area & of course regular AP hunts, dog-fights, (for foreign agents a huge amount of) unique portal visits/captures etc. [https://etherpad.mozilla.org/ingress-portland-workweek Planning & Sign up]
*'''Gamers''' - We're not going to actually play games, just drink about them. Wednesday @ 9:30 Driftwood Room [http://www.hoteldeluxeportland.com/eat-drink/driftwood-room/].
*'''Shootin' Range''' - Portland has several high-quality indoor ranges scattered around the city. Let's head out and plink on some targets! [https://etherpad.mozilla.org/mozrangeia Sign up here!]
*'''[http://groundkontrol.com/ Ground Kontrol]''' - Portland classic arcade open for max. 130 people from 8:00pm - 12:00am PT on Tuesday, December 2nd only. Minors welcome. Includes free play on all machines, as well as sodas. This is Mozilla sponsored. [https://etherpad.mozilla.org/ground-kontrol Sign up here].
*'''MozillaWiki Hackathon''' -- Details to come. If you're interested, put your name [https://wiki.etherpad.mozilla.org/december-pdx-hackathon here!]
*'''MozWomen Lunch''' -- Let's coincidentally get lunch one day (not restricted to women, of course - any welcome!). Etherpad [https://etherpad.mozilla.org/moz-women-lunch here!]

== FAQ ==
Please add your questions to this document: https://docs.google.com/a/mozilla.com/document/d/1g-KqjCWwjJtgYHJYuFXgWYW9i0MY234_tMRPbXxq5Jc/edit

== Links ==
* Guest speaker suggestions: https://etherpad.mozilla.org/workweekspeakers
* Fun things to do suggestions: https://etherpad.mozilla.org/hogwarts

Engagement

2011-10-26T23:04:19Z

Cbeard:

__TOC__

= Who We Are =
The Engagement team works with our passionate volunteers, guiding Mozilla's product marketing, competitive insights, creative, design, community, and PR efforts. Just as our community grows each day, we're looking to increase the ways people can learn about our efforts and help contribute to promoting Mozilla. This page highlights our teams, what they do and how to get into contact with them.

= Where can you find us? =
The easiest way to send a message to Engagement is in one our community mailing lists.

Otherwise, join us on IRC in either of our channels:
* [irc://irc.mozilla.org/%23marketing #marketing]: General discussion about Mozilla marketing efforts
* [irc://irc.mozilla.org/%23webgagement #webgagement]: Communication/collaboration/cooperation between the Engagement and WebDev teams

= How to get involved? =

Check out each of the teams below to learn more about the different groups and projects, and how to get involved.

= Teams =

{{#lst:Engagement/User_Engagement|summary}} 
{{#lst:Engagement/Contributor_Engagement|summary}} 
{{#lst:Engagement/Developer_Engagement|summary}} 
{{#lst:Engagement/Product_Marketing|summary}} 
{{#lst:Engagement/Insights|summary}} 
{{#lst:Engagement/Creative|summary}} 
{{#lst:Engagement/Communications|summary}}

WeeklyUpdates/2011-03-28

2011-03-28T17:17:44Z

Cbeard: /* Speakers */

[[WeeklyUpdates/2011-03-21|« previous week]] | [[WeeklyUpdates|index]] | [[WeeklyUpdates/2011-04-04|next week »]]

= Video for today's meeting =

<video controls="controls"><source src="http://videos.mozilla.org/serv/air_mozilla/monday_meetings/status-2011-03-28.ogg" type="video/ogg; codecs="theora, vorbis"" /></video>

= Friends of the Tree [[Image:Tree.gif|Friends of the Tree]] =
* philor and jag for diagnosing and fixing the ridiculously slow Tinderbox tree admin page.
* Aleksej, Anders, lcamacho, and our own Henrik Skupin for making the Mozmill Crowd Testing testday a success
* GeorgeF(George Fiotakis), Greek web localizer and community superstar, for being very helpful in the L10n field in the last week. He's currently the only one who created localized screenshots for Linux and Mac for Firefox 4 features page on mozilla-europe.org. Also, he's been pretty active in the mailing-lists discussion on how to get more people involved. - Milos(milos@mozilla.com).

= Upcoming Events =

'''This Week'''

'''Monday, 28 March'''

'''Tuesday, 29 March'''

'''Wednesday, 30 March'''

'''Thursday, 31 March'''

'''Friday, 1 April'''

'''Next Week'''

= Product Status Updates =

== Firefox 4 ==

== Firefox 3.6 ==

== Mobile Firefox ==

== Thunderbird ==

== Older Branch Work ==

== Drumbeat ==

= Speakers =

The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation.

{| class="fullwidth-table"
|-
! Title
! Presenter
! Topic
! Media
! More Details
|-
| Your Title Here
| Your Name Here
| What are you going to talk about?
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
| Getting the word out
| Chris Beard
| Brand campaign
|
| Pilot campaign starting this week targeting digerati in Bay Area to reinforce our differentiation & advocacy position
|}

= Status Updates By Team =

== Firefox ==

== Platform ==

== Messaging ==

== Mobile ==

== IT ==

== Release Engineering ==

== QA ==
; General
* [http://seleniumhq.wordpress.com/2011/03/21/selenium-2-0b3-the-next-gen-browser-release/ Selenium 2.0b3] released with Firefox 4 support

;Test Execution

;Test Automation
* [http://www.hskupin.info/2011/03/24/mozmill-crowd-0-1-2-released/ MozMill Crowd 0.1.2] has been released

;WebQA

;QA Community

;Test Dev

== Automation & Tools ==

== Security ==

== Engagement ==

'''PR'''

'''Events'''

'''Creative Team'''

'''Community Marketing'''

== Support ==

== Metrics ==

== Evangelism ==

== Labs ==

== Developer Tools ==

== Add-ons ==

== Webdev ==

== L10n ==

= Introducing New Hires =

*[http://ben.adida.net/ Ben Adida], Staff Engineer for the Apps Group

= Foundation Updates =

= Roundtable =

Brand/Firefox

2011-03-24T15:22:29Z

Cbeard: /* Materials */

=Background=

The Firefox brand is one of Mozilla's greatest assets, and one of the top Engagement team goals for 2011 is making sure that we communicate what the it stands for as crisply and effectively as possible. To that end, we've created v1 of a brand book that will help guide the way we talk about Firefox and what it means for users around the world.

Over the coming months, this will be expanded into a complete guide with more detailed reference materials and communications info. In the spirit of "release early, release often", though, we're posting this initial version here.

For more info, we definitely recommend downloading [https://wiki.mozilla.org/File:Firefox_Brand_Book.pdf the pdf version] of the brand book and watching [http://videos.mozilla.org/serv/brand/Mozilla_Firefox_Manifesto_v0.1.webm the "Mozilla Firefox: A Different Kind of Browser" video]. Stay tuned for more!

=Brand Book: Introduction=

Whether you’re new to Firefox or you’ve been around for a while, you know there is something very special about this brand.

What this guide attempts to do is to define what makes Firefox special and give us some tools to help us articulate, express and evaluate the brand in our daily work.

This foundation (brand promise, position and voice) is a great beginning, a tool that allows us to speak with one voice.

=Brand Promise=

Our brand promise is a single statement that captures the essence of our experience. This is the internal compass we use to guide the development of our brand.

This is not an ad. This is not a tagline. This is our promise to our users. It’s that simple.

'''Firefox answers to no one but you'''

=Brand Positioning=

Positioning provides detail around the benefits we offer our users.
This level of detail is important when developing ideas, communications or making decisions that reflect on the brand.

'''Firefox prioritizes principles over profits to put individuals in control and shape the future of the web for the public good.'''

=Five Pillars of the Brand=

* Nonprofit: Firefox is fundamentally driven by the Mozilla mission rather than business concerns.
* Track record: Firefox has a long history of doing the right thing for both individuals and the web as a whole.
* Empowering innovation: Firefox enables individuals to create and build without permission or restriction.
* Community driven: At its core, Firefox is about people and is powered by a global community of individuals working together for the public good.
* Challenger spirit: Firefox starts races, and isn’t afraid to compete with the world’s biggest companies.

=Brand Voice=

When we create communications, how do we ensure we are making this promise and positioning real?

We hold up these expressions of the brand to help evaluate the work. This is the language that is fluid and generative.

This is the language that is influenced by the world in which we live. This is the language that embodies the promise of “Firefox answers to no one but you.”

*Unconventional
*Engaging
*Honest
*Human
*Smart
*Confident

=Brand Manifesto=

We’re quite content to be the odd browser out.

We don’t have a fancy stock abbreviation to go alongside our name in the press. We don’t have a profit margin. We don’t have sacred rock stars that we put above others. We don’t make the same deals, sign the same contracts or shake the same hands as everyone else.

And all of this is fine by us.

We’re a pack of independently spirited, fiercely unconventional people who do things a little differently. Where others may value the bottom line, we value—well—values. When a competitor considers making something proprietary,we strive to set it free.

And while most products and technologies are developed behind closed doors, ours are cultivated out in the open for everyone to see. We’re not beholden to stake, share or power holders—we answer to no one but you. And we don’t operate this way for the fun of it, even though it is incredibly fun. We operate this way because we believe it’s the right thing to do.

We believe in principle over profit.

We believe that secrecy is trumped by honesty.

And corporate interest by community.

We believe that the web is more cared for than owned.

More of a resource to be tended to than a mere commodity to be sold.

And we strongly believe in innovation that puts users front, center, and squarely in the driver’s seat.

But most importantly, we believe in you.

We believe that the world’s best browser is made possible by engineers, programmers, designers and people just like you who give their time, talents, energy and support to the cause. And we believe that together, with this cause in mind, we can continue to innovate for the benefit of the individual and the betterment of the web, so that it always and forever serves the greater good.

We are all Mozilla Firefox. And we’re not just a different kind of browser.

We’re a browser that is making a difference.

=Materials=

[https://wiki.mozilla.org/File:Firefox_Brand_Book.pdf Brand book, version 1] (Dec 2010)

[http://videos-cdn.mozilla.net/serv/brand/Mozilla_Firefox_Manifesto_v0.1.webm "Mozilla Firefox: A Different Kind of Browser" video - .webm]

[http://videos-cdn.mozilla.net/serv/brand/Mozilla_Firefox_Manifesto_v0.1.ogv "Mozilla Firefox: A Different Kind of Browser" video - .ogv]

Brand/Firefox

2011-03-24T15:22:07Z

Cbeard: /* Materials */

=Background=

The Firefox brand is one of Mozilla's greatest assets, and one of the top Engagement team goals for 2011 is making sure that we communicate what the it stands for as crisply and effectively as possible. To that end, we've created v1 of a brand book that will help guide the way we talk about Firefox and what it means for users around the world.

Over the coming months, this will be expanded into a complete guide with more detailed reference materials and communications info. In the spirit of "release early, release often", though, we're posting this initial version here.

For more info, we definitely recommend downloading [https://wiki.mozilla.org/File:Firefox_Brand_Book.pdf the pdf version] of the brand book and watching [http://videos.mozilla.org/serv/brand/Mozilla_Firefox_Manifesto_v0.1.webm the "Mozilla Firefox: A Different Kind of Browser" video]. Stay tuned for more!

=Brand Book: Introduction=

Whether you’re new to Firefox or you’ve been around for a while, you know there is something very special about this brand.

What this guide attempts to do is to define what makes Firefox special and give us some tools to help us articulate, express and evaluate the brand in our daily work.

This foundation (brand promise, position and voice) is a great beginning, a tool that allows us to speak with one voice.

=Brand Promise=

Our brand promise is a single statement that captures the essence of our experience. This is the internal compass we use to guide the development of our brand.

This is not an ad. This is not a tagline. This is our promise to our users. It’s that simple.

'''Firefox answers to no one but you'''

=Brand Positioning=

Positioning provides detail around the benefits we offer our users.
This level of detail is important when developing ideas, communications or making decisions that reflect on the brand.

'''Firefox prioritizes principles over profits to put individuals in control and shape the future of the web for the public good.'''

=Five Pillars of the Brand=

* Nonprofit: Firefox is fundamentally driven by the Mozilla mission rather than business concerns.
* Track record: Firefox has a long history of doing the right thing for both individuals and the web as a whole.
* Empowering innovation: Firefox enables individuals to create and build without permission or restriction.
* Community driven: At its core, Firefox is about people and is powered by a global community of individuals working together for the public good.
* Challenger spirit: Firefox starts races, and isn’t afraid to compete with the world’s biggest companies.

=Brand Voice=

When we create communications, how do we ensure we are making this promise and positioning real?

We hold up these expressions of the brand to help evaluate the work. This is the language that is fluid and generative.

This is the language that is influenced by the world in which we live. This is the language that embodies the promise of “Firefox answers to no one but you.”

*Unconventional
*Engaging
*Honest
*Human
*Smart
*Confident

=Brand Manifesto=

We’re quite content to be the odd browser out.

We don’t have a fancy stock abbreviation to go alongside our name in the press. We don’t have a profit margin. We don’t have sacred rock stars that we put above others. We don’t make the same deals, sign the same contracts or shake the same hands as everyone else.

And all of this is fine by us.

We’re a pack of independently spirited, fiercely unconventional people who do things a little differently. Where others may value the bottom line, we value—well—values. When a competitor considers making something proprietary,we strive to set it free.

And while most products and technologies are developed behind closed doors, ours are cultivated out in the open for everyone to see. We’re not beholden to stake, share or power holders—we answer to no one but you. And we don’t operate this way for the fun of it, even though it is incredibly fun. We operate this way because we believe it’s the right thing to do.

We believe in principle over profit.

We believe that secrecy is trumped by honesty.

And corporate interest by community.

We believe that the web is more cared for than owned.

More of a resource to be tended to than a mere commodity to be sold.

And we strongly believe in innovation that puts users front, center, and squarely in the driver’s seat.

But most importantly, we believe in you.

We believe that the world’s best browser is made possible by engineers, programmers, designers and people just like you who give their time, talents, energy and support to the cause. And we believe that together, with this cause in mind, we can continue to innovate for the benefit of the individual and the betterment of the web, so that it always and forever serves the greater good.

We are all Mozilla Firefox. And we’re not just a different kind of browser.

We’re a browser that is making a difference.

=Materials=

[https://wiki.mozilla.org/File:Firefox_Brand_Book.pdf Brand book, version 1] (Dec 2010)

[http://videos-cdn.mozilla.net/serv/brand/Mozilla_Firefox_Manifesto_v0.1.webm
"Mozilla Firefox: A Different Kind of Browser" video - .webm]

[http://videos-cdn.mozilla.net/serv/brand/Mozilla_Firefox_Manifesto_v0.1.ogv "Mozilla Firefox: A Different Kind of Browser" video - .ogv]

Ask Mitchell

2010-10-14T18:01:39Z

Cbeard:

:''These calls are an opportunity for the whole of the Mozilla community to discuss topical issues with Mitchell Baker, Chair of the Mozilla Foundation.''

'''Meeting Details'''

*Friday, October 15th @ 10:00am Pacific Time (18:00 UTC through November 6)
*Mozilla HQ, Ten Forward commons area
*+1 650 903 0800 x92 Conf# 8600 (US/International)
*+1 416 848 3114 x92 Conf# 8600 (Canada)
*+1 800 707 2533 (pin 369) Conf# 8600 (US Toll Free)
*sip:weeklystatus@mozilla.com from generic SIP clients
*http://air.mozilla.com/ to watch and listen
*join irc.mozilla.org #staffmeeting for backchannel discussion

When you call in, you'll be muted by default, to keep phone noise down. Use "*1" (including the star) to unmute yourself if you want to say something.

Full notes below. 

'''Meeting Notes'''
*[[Ask_Mitchell/2010-10-15|October 15, 2010]] - Topic: Q&A on new CEO Appointment

Ask Mitchell

2010-10-14T16:55:32Z

Cbeard:

:''These calls are an opportunity for the whole of the Mozilla community to discuss topical issues with Mitchell Baker.''

'''Meeting Details'''

*Friday, October 15th @ 10:00am Pacific Time (18:00 UTC through November 6)
*Mozilla HQ, Ten Forward commons area
*+1 650 903 0800 x92 Conf# 8600 (US/International)
*+1 416 848 3114 x92 Conf# 8600 (Canada)
*+1 800 707 2533 (pin 369) Conf# 8600 (US Toll Free)
*sip:weeklystatus@mozilla.com from generic SIP clients
*http://air.mozilla.com/ to watch and listen
*join irc.mozilla.org #staffmeeting for backchannel discussion

When you call in, you'll be muted by default, to keep phone noise down. Use "*1" (including the star) to unmute yourself if you want to say something.

Full notes below. 

'''Meeting Notes'''
*[[Ask_Mitchell/2010-10-15|October 15, 2010]] - Topic: Q&A on new CEO Appointment

Ask Mitchell

2010-10-14T16:55:14Z

Cbeard:

Ask Mitchell

2010-10-14T16:54:32Z

Cbeard: Created page with ":''These calls are an opportunity for the whole of the Mozilla community to discuss topical issues with Mitchell Baker.'' '''Meeting Details''' *Friday, October 15th @ 10:00am..."

Summit2010/Schedule

2010-07-07T18:21:35Z

Cbeard:

[[File:Mozilla-summit-wiki-banner.png]]

<div style="margin: 1em 0px; border: 2px solid orange; padding: 1em; background-color: #FFC; text-align: center;">'''Schedule is still in flux: this is not final.'''</div>

All times listed are Pacific.

'''[http://bit.ly/SummitBreakoutSessions Breakout Session Descriptions!]'''

{| cellpadding="5" cellspacing="0" border-collapse="collapse" border="1" width="1090px"

|-
{{Summit2010DateRow
|date=Tuesday - July 6, 2010
}}

|-
{{Summit2010HeaderRow}}

|-
{{Summit2010FullRow
|color=#F2F5A9
|time=07:00 - 18:00
|all= Registration & MozCafé Open 
}}

|-
{{Summit2010FullRow
|color=#58FAF4
|time=18:00 - 20:00
|all= Reception on Woodland Terrace 
}}

|}

{| cellpadding="5" cellspacing="0" border-collapse="collapse" border="1" width="1090px"

|-
{{Summit2010DateRow
|date=Wednesday - July 7, 2010
}}

|-
{{Summit2010HeaderRow}}

|-
{{Summit2010FullRow
|color=#58FAF4
|time=07:00 - 08:15
|all= Breakfast 
}}

|-
{{Summit2010FullRow
|color=#F2F5A9
|time=08:15 - 08:30
|all=Everyone moves to Keynotes room
}}

|-
{{Summit2010FullRow
|color=#FFFF00
|time=08:30 - 10:00
|all= Welcome & Keynotes 
}}

|-
{{Summit2010FullRow
|color=#FFF
|time=10:00 - 10:30
|all=Break
}}

|-
{{Summit2010FullRow
|color=#FFFF00
|time=10:30 - 12:00
|all= Keynotes (con't) 
}}

|-
{{Summit2010FullRow
|color=#58FAF4
|time=12:00 - 14:30
|all= Lunch 
}}

|-
{{Summit2010Row
|time=14:30-15:15
|macAcolor=#FFFFFF | macA=EMPTY
|macBCcolor=#CEF6CE | macBC=B112 - Mobile Roadmap
|macEcolor=#E3CEF6 | macE=B136 - Supporting Enterprise Deployments
|macFcolor=#F6E3CE | macF=B035 - Addon Compatibility: Towards Firefox 4
|empAcolor=#CEE3F6 | empA=B054 - Moving from Local Events to Strong Local Communities
|empBcolor=#CEF6CE | empB=B063 - Messaging (e.g. email, twitter, etc.) with Mozilla Values
|empCcolor=#CEF6CE | empC=B094 - The Future of Gecko Embedding
|froAcolor=#D8D8D8 | froA=Unavailable
|froBcolor=#D8D8D8 | froB=Unavailable
}}

|-
{{Summit2010FullRow
|color=#FFF
|time=15:15 - 15:45
|all=Break
}}

|-
{{Summit2010Row
|time=15:45 - 16:30
|macAcolor=#CEF6CE | macA=B093 - Servo Project
|macBCcolor=#CEE3F6 | macBC=B045 - Privacy Principles & Brand Attributes at Mozilla
|macEcolor=#F5F6CE | macE=B005 - Mozilla's L10N Information Architecture
|macFcolor=#CEE3F6 | macF=B050 - Keeping Firefox Sexy: How product marketing can help
|empAcolor=#F5F6CE | empA=B009 - Bug Days & You
|empBcolor=#CEF6CE | empB=B125 - How to Prototype and Influence People
|empCcolor=#F6E3CE | empC=B024 - AMO Editors: Present & Future
|froAcolor=#F5F6CE | froA=B003 - How to Write Awesome Documentation
|froBcolor=#CEE3F6 | froB=B049 - Mozilla Drumbeat in 2100 Seconds
}}

|-
{{Summit2010FullRow
|color=#FFF
|time=16:30 - 17:00
|all=Break
}}

|-
{{Summit2010Row
|time=17:00 - 17:45
|macAcolor=#CEE3F6 | macA=B046 - The Mozilla Web Universe
|macBCcolor=#CEF6CE | macBC=B300 - Shaver's Performance Talk
|macEcolor=#F5F6CE | macE=B020 - QA on a Global Scale
|macFcolor=#F6E3CE | macF=B042 - Mozilla's Participation in Standards
|empAcolor=#E3CEF6 | empA=B132 - Revising the MPL
|empBcolor=#F5F6CE | empB=B012 - The Future of Verbatim & Using Translation Memory
|empCcolor=#FFFFFF | empC=EMPTY
|froAcolor=#F5F6CE | froA=B001 - Leveraging Support's User Base
|froBcolor=#CEF6CE | froB=B104 - Bugzilla Branch Management
}}

|-
{{Summit2010FullRow
|color=#FFF
|time=17:45-18:30
|all=Break
}}

|-
{{Summit2010FullRow
|color=#58FAF4
|time=18:30 - 20:00
|all= Dine Around the Village 
}}

|-
{{Summit2010FullRow
|color=#01DF01
|time=20:15 - 22:30
|all= BOF Sessions (Empress & Frontenac only!) 
}}

|}

{| cellpadding="5" cellspacing="0" border-collapse="collapse" border="1" width="1090px"

|-
{{Summit2010DateRow
|date=Thursday - July 8, 2010
}}

|-
{{Summit2010HeaderRow}}

|-
{{Summit2010FullRow
|color=#58FAF4
|time=07:00 - 08:45
|all= Breakfast 
}}

|-
{{Summit2010FullRow
|color=#F2F5A9
|time=08:45 - 09:00
|all=Everyone moves to Keynotes room
}}

|-
{{Summit2010FullRow
|color=#FFFF00
|time=09:00 - 10:15
|all= Keynotes (Mitchell & Shaver) 
}}

|-
{{Summit2010FullRow
|color=#FFF
|time=10:15 - 10:30
|all=Break
}}

|-
{{Summit2010Row
|time=10:30 - 11:15
|macAcolor=#F6E3CE | macA=B029 - Mozilla Add-ons Marketplace
|macBCcolor=#CEE3F6 | macBC=B055 - Staying Open for Business: Fostering Transparency in a 24 Internet News Cycle
|macEcolor=#CEF6CE | macE=B082 - Modules for JavaScript
|macFcolor=#FFFFFF | macF=EMPTY
|empAcolor=#CEF6CE | empA=B085 - Beyond HTML5 Video: RTC and Adaptive Bandwidth
|empBcolor=#CEF6CE | empB=B088 - Firefox Sync: What's Coming?
|empCcolor=#CEF6CE | empC=B111 - Content Team Planning
|froAcolor=#CEE3F6 | froA=B057 - What Can Mozilla Learn From Other Movements?
|froBcolor=#CEF6CE | froB=B099 - Hardware Acceleration: Where We Are & Where We Are Going
}}

|-
{{Summit2010FullRow
|color=#FFF
|time=11:15 - 11:30
|all=Break
}}

|-
{{Summit2010FullRow
|color=#FF8000
|time=11:30 - 12:45
|all= Lightning Talks (11 @ 5mins ea) 
}}

|-
{{Summit2010FullRow
|color=#58FAF4
|time=12:45 - 13:45
|all= Lunch 
}}

|-
{{Summit2010FullRow
|color=#FFF
|time=13:45 - 14:15
|all=Break / Science Fair set up
}}

|-
{{Summit2010FullRow
|color=#58ACFA
|time=14:15 - 15:45
|all= Science Fair 
}}

|-
{{Summit2010FullRow
|color=#FFF
|time=15:45 - 16:15
|all=Break / Science Fair tear down
}}

|-
{{Summit2010Row
|time=16:15 - 17:00
|macAcolor=#F6E3CE | macA=B027 - Account Manager & Online Identity
|macBCcolor=#CEF6CE | macBC=B069 - Web Platform for Firefox 5
|macEcolor=#CEF6CE | macE=B071 - HTML5 Audio and Video Accessibility
|macFcolor=#CEE3F6 | macF=B060 - Acting Locally
|empAcolor=#E3CEF6 | empA=B144 - Build Your Own Browser in the Wild
|empBcolor=#CEE3F6 | empB=B051 - Telling the Mozilla Story: Mission, Branding & More
|empCcolor=#CEF6CE | empC=B083 - NPAPI & Binary Plugins in Gecko
|froAcolor=#CEF6CE | froA=B091 - Getting to Confirmed: Improving Bug Triage
|froBcolor=#CEF6CE | froB=B115 - Future of JS/DOM Bindings
}}

|-
{{Summit2010FullRow
|color=#FFF
|time=17:00 - 18:00
|all=Break / World Expo set up
}}

|-
{{Summit2010FullRow
|color=#A9A9F5
|time=18:00 - 19:00
|all= World Expo Reception 
}}

|-
{{Summit2010FullRow
|color=#E3CEF6
|time=19:00 - 20:30
|all= International Dinner & World Expo 
}}

|-
{{Summit2010FullRow
|color=#A9A9F5
|time=20:30 - 21:00
|all=World Expo tear down
}}

|-
{{Summit2010FullRow
|color=#01DF01
|time=21:00 - 22:30
|all= BOF Sessions (Empress & Frontenac Only) 
}}

|}

{| cellpadding="5" cellspacing="0" border-collapse="collapse" border="1" width="1090px"

|-
{{Summit2010DateRow
|date=Friday - July 9, 2010
}}

|-
{{Summit2010HeaderRow}}

|-
{{Summit2010FullRow
|color=#58FAF4
|time=07:00 - 08:45
|all= Breakfast 
}}

|-
{{Summit2010FullRow
|color=#F2F5A9
|time=08:45 - 09:00
|all=Everyone moves to Keynotes room
}}

|-
{{Summit2010FullRow
|color=#FF8000
|time=09:00 - 10:30
|all= Lightning Talks (14 @ 5mins ea) 
}}

|-
{{Summit2010FullRow
|color=#FFF
|time=10:30 - 10:45
|all=Break
}}

|-
{{Summit2010Row
|time=10:45 - 11:30
|macAcolor=#F6E3CE | macA=B030 - Addons: Past, Present & Future
|macBCcolor=#CEF6CE | macBC=B092 - Tools, the Future & You
|macEcolor=#CEF6CE | macE=B107 - Giving Firefox Users Control over Their Data
|macFcolor=#CEE3F6 | macF=B064 - User Participation 2.0
|empAcolor=#F5F6CE | empA=B017 - Localization 2.0
|empBcolor=#F6E3CE | empB=B037 - Gaming on the Web
|empCcolor=#CEF6CE | empC=B089 - Contacts in the Browser
|froAcolor=#CEF6CE | froA=B122 - Fuzz Testing: Meet the robotic monkeys who keep Firefox safe
|froBcolor=#CEF6CE | froB=B098 - The Future of Client-side Web Debugging
}}

|-
{{Summit2010FullRow
|color=#FFF
|time=11:30 - 12:00
|all=Break
}}

|-
{{Summit2010FullRow
|color=#FF8000
|time=12:00 - 12:45
|all= Lightning Talks (7 @ 5mins ea) 
}}

|-
{{Summit2010FullRow
|color=#58FAF4
|time=12:45 - 13:45
|all= Lunch 
}}

|-
{{Summit2010FullRow
|color=#FFF
|time=13:45 - 14:00
|all=Break
}}

|-
{{Summit2010Row
|time=14:00-14:45
|macAcolor=#F6E3CE | macA=B026 - Jetpack & the Future of Addon Development
|macBCcolor=#CEF6CE | macBC=B081 - Browser Security Trends
|macEcolor=#CEF6CE | macE=B097 - Inside SpiderMonkey: JavaScript Speedups in Firefox 4
|macFcolor=#CEE3F6 | macF=B011 - "Get Involved" Page and the Contributor Funnel
|empAcolor=#CEF6CE | empA=B105 - Socorro.next
|empBcolor=#F5F6CE | empB=B002 - Introduction to the Firefox 4 Beta Program for Localizers
|empCcolor=#F5F6CE | empC=B032 - MozMill Crowd - The birth of global automated testing
|froAcolor=#D8D8D8 | froA=Unavailable
|froBcolor=#D8D8D8 | froB=Unavailable
}}

|-
{{Summit2010FullRow
|color=#FFF
|time=14:45 - 15:15
|all=Break
}}

|-
{{Summit2010Row
|time=15:15 - 16:00
|macAcolor=#FFFFFF | macA=EMPTY
|macBCcolor=#CEF6CE | macBC=B095 - Mozilla 2 & API Stability
|macEcolor=#CEF6CE | macE=B101 - Bringing the Firefox UI to New Platforms and Devices
|macFcolor=#F6E3CE | macF=B033 - The Future of Web Audio
|empAcolor=#CEF6CE | empA=B109 - Mozilla Networking Discussion
|empBcolor=#CEE3F6 | empB=B048 - Message in a Bottle: Spreading the Mozilla Story
|empCcolor=#F6E3CE | empC=B031 - Mozilla Developer Network (MDN) Sessions
|froAcolor=#CEF6CE | froA=B080 - Browser Privacy and Anonymity
|froBcolor=#CEE3F6 | froB=B056 - Drumbeat & P2PU School of Webcraft
}}

|-
{{Summit2010FullRow
|color=#FFF
|time=16:00 - 16:30
|all=Break
}}

|-
{{Summit2010Row
|time=16:30 - 17:15
|macAcolor=#E3CEF6 | macA=B134 - How Should We Visualize Mozilla's Information
|macBCcolor=#F6E3CE | macBC=B301 - An Open Web App Store
|macEcolor=#CEF6CE | macE=B084 - Mobile, Addons & Electrolysis
|macFcolor=#FFFFFF | macF=EMPTY
|empAcolor=#CEF6CE | empA=B120 - Mozilla & Research
|empBcolor=#FFFFFF | empB=EMPTY
|empCcolor=#F5F6CE | empC=B010 - Plans for Firefox Input (Feedback)
|froAcolor=#CEE3F6 | froA=B058 - Belonging to Mozilla: Exploring Supporter & Membership Models
|froBcolor=#CEF6CE | froB=B068 - Web & Browser User Experience Beer Hall
}}

|-
{{Summit2010FullRow
|color=#F2F5A9
|time=17:15 - 17:30
|all=Back into the Keynotes room!
}}

|-
{{Summit2010FullRow
|color=#FFFF00
|time=17:30 - 18:00
|all= Closing Remarks 
}}

|-
{{Summit2010FullRow
|color=#FFF
|time=18:00 - 18:30
|all=Break
}}

|-
{{Summit2010FullRow
|color=#F2F5A9
|time= 18:30 - 20:00 
|all=Gondola ferries everyone up the mountain
}}

|-
{{Summit2010FullRow
|color=#58FAF4
|time=18:00 -
|all= Summit Wrap-up Party at the Roundhouse Restaurant 
}}

|-
{{Summit2010HeaderRow}}

|}

Labs/Weave/Developer

2010-02-06T15:41:33Z

Cbeard: removing depracated (and insecure) PHP client

= Weave Services: Developer Home =

Weave Services are server-based, always-on services to enhance Firefox users' experience of the web. Our goal is to enable a consistent user experience of the web, whenever our users use the web, while protecting user privacy and choice.

Mozilla Labs has launched these services to Firefox users through the [http://mozillalabs.com/weave Weave addon]. We encourage the developer community to write new applications that work with these services to bring better experiences to their users!

Our services are open-source and have open APIs. Developers are welcome to integrate their software with our services, and anyone is welcome to download the source code for the server software and run their own services if they wish.

= Available Services =

* The Weave Identity service maintains an account for users that acts as an identifier for the other Weave services.

* The Weave Sync service maintains an indexed, encrypted data store that provides server storage for history, passwords, bookmarks, form history, preferences, and tabs exported from a web browser. Add-on developers can use a browser-level API to synchronize add-on data between browser instances. By using the Sync Server API, developers can write client software to access the sync data on any platform.

The Weave Sync service is not intended to be a mechanism to share your browser history with other services. To learn more about the plans to enable secure private sharing of personal data, read our [[Labs/Weave/Developer/SecureDataSharing|Secure Data Sharing]] plans.

= Services Developer FAQ =

What sort of applications can I build with Weave Services?

As an add-on developer, you can use the Weave Identity and Sync services to create a consistent experience for your users. Read about [[Labs/Weave/Developer/HowToSynchronizeAddOnPrefs|how to synchronize add-on preferences here.]]

As a client software developer, you can use the Weave Identity and Sync services to access users' web experience data to create a consistent user experience between your software and Firefox. Read about [[Labs/Weave/Developer/HowToWriteClient|how to access browser data in client software here]].

As a web developer, you can get the source code for the pure HTML implementation of the Weave client and explore new ways of letting the user interact with their history and bookmarks. (Note that the current Weave services are not appropriate for use in server software: our goal is to make sure servers do not receive information unnecessarily)

What sort of applications shouldn't I build with these services?

Mozilla has made a strong effort to provide a user data storage system that protects our users' privacy. The current system does not store any decrypted data about the user on the server, besides the minimal set of data we need to log the user in and contact them if they lose their password.

Developers should not write applications that erode this privacy guarantee lightly. In particular, we believe that the users' password and passphrase, and the cryptographic resources accessed through those values, should never leave their personal computer or device. This means that you shouldn't write a server that stores these values and accesses the user's personal data from another server.

Also, the Weave Services web services are designed to support a relatively small amount of high-value user data. Users are restricted to a fairly small data quota. Applications should respect this restriction by using the Weave Services web services for relatively small amounts of data (in the neighborhood of tens of kilobytes).

What are the platform features you are planning to offer in the future?

Add-on and search engine sync is under development now.

We have a plan to support [[Labs/Weave/Developer/SecureDataSharing|Secure Data Sharing]] that empowers both users and service developers. Your input is welcome!

We are enhancing the Weave Identity service, to be a full-featured OpenID provider and to support profile-exchange and service-discovery features.

Can I write commercial applications or closed-source software that uses these services?

Yes, you may. You must make certain that your terms of service and privacy policy are compatible with the [http://mozillalabs.com/projects-2/weave10/tos/ Weave Terms of Service] and [http://mozillalabs.com/weave/weave-privacy-policy/ Weave Privacy Policy]. Note that crawling or otherwise attempting to bulk-extract data from the services is explicitly forbidden, as is trading or reselling any of the Weave Services. The terms of service also have some restrictions on trademarks, which mean that you'll need to name your service in a way that respects those restrictions.

{{:Labs/Weave/Includes/Documentation}}
= Libraries =

* Javascript: http://hg.mozilla.org/labs/weaveweb/file/tip/weave.js#l163
* Python: http://hg.mozilla.org/labs/weaveclient-python


{{:Labs/Weave/Experimental_Clients}}

= Release Notes for 2010-02-05 =

* Please do not start adding your own custom data types or storing large quantities of data on our servers. We don't yet have the capacity to handle that and will be monitoring our servers for unusual activity. If you have any doubts or questions as to what is appropriate, contact us on the [https://groups.google.com/mozilla-labs-weave-dev mailing lists] or #labs on irc.mozilla.org and we'll be happy to chat about the best approach.
* We '''strongly''' recommend doing your development with your own [http://tobyelliott.wordpress.com/2009/09/11/weave-minimal-server/ self-hosted server]. Please do not point your prototype code at the production Weave servers, as you will find your API calls failing as we throttle or disable your access. '

Labs/Weave/Developer/FAQ

2010-02-06T00:33:33Z

Cbeard: /* Can I take Weave and submit it to the App Store myself? */

= 2010-02-05 Weave API Release =

== What is Weave ==
Weave is a Mozilla Labs project exploring opportunities for the Web browser to broker richer experiences while increasing user control over their data and personal information. The Weave platform will ultimately include services and APIs for managing your identity and personal data across the Web.

== What is Weave Sync? ==
Weave Sync is the first component of the Weave platform. Using this free browser add-on from Mozilla Labs, you can use security mechanisms to access all of your personal data across all of your supported devices, making your Web experience instantly more personal and useful. Weave Sync synchronizes your bookmarks, saved passwords, browsing history and open browser tabs. And all of your data is encrypted end-to-end to help protect your privacy.

== What are the other components of the Weave platform? ==
The Weave platform will ultimately include services and APIs for managing your identity and personal data across the Web. In terms of the roadmap, the next components will focus on identity, sharing and notifications.

== What personal data is stored ==
Weave stores personal data from Firefox including your bookmarks, browsing history, saved password, open browser tabs and certain preferences. All of your data is transmitted over SSL and is encrypted end-to-end as a way to help your privacy.

== How do users know their data is secure? ==
Weave strongly encrypts all of your data locally before transmitting over SSL to Mozilla (or your own server), using a secret phrase that is created by you, and designed to not leave your hard drive. Mozilla does not have access to this secret phrase. Also, The Mozilla Foundation, our parent company, is an international non-profit organization and our business model is not based upon accessing your personal data.
(Read more about Weave cryptography here: https://wiki.mozilla.org/Labs/Weave/Crypto)

== Where is the personal data stored? ==
By default, you can use the Mozilla-hosted Weave service to store you data. You can also optionally setup your own server (with an open source server implementation that we provide for free) or point to another service provider that has implemented the Weave APIs.

== How can I use Weave today? What platforms does it support? ==
We currently support Weave Sync for Firefox on Windows, Mac and Linux on the desktop, and Maemo on mobile devices.

== How many people are using Weave today? ==
In the first week since Weave has been generally available, we're seeing hundreds of thousands of users actively using the add-on and service to seamlessly bridge their desktop and mobile experences.

== What are you announcing today? ==
Last week we announced that the Weave Sync add-on for Firefox is generally available to seamlessly bridge your desktop and mobile Firefox experiences. Today, we are launching the Weave Developer Resources site with APIs, documentation, libraries, tools, design and early prototypes.

== What prompted you to launch the developer resources site? ==
This is part of a broader call for participation to increase the number of places where you can access your personal data through Weave.

== What do you hope to see from developers? What devices and platforms do you expect developers to create Weave clients for? ==
We're working to get Firefox with full Weave support onto as many connected devices as possible. Firefox is available today on Nokia's Maemo platform, and we're actively working on Android and Windows Mobile versions. Independent of the full Firefox experience, with the Weave APIs we're excited to see where developers can provide users with access to their personal data through Weave to provide richer, more personalized experiences across the Web.

== Does Weave integrate with iPhone features or Safari? ==
The Weave client for the iPhone is a standalone application that providers users with secure access to the bookmarks, history, open tabs, etc. It allows you to quickly find and preview your favorite sites, open tabs, etc. and then provides you the ability to open them in the native browser or share with friends via email.

== Is Weave being developed for other platforms? e.g. Android, Blackberry, Palm, etc. ==
We're working to get Firefox with full Weave support onto as many connected devices as possible. Firefox is available today on Nokia's Maemo platform, and we're actively working on Android and Windows Mobile versions. Independent of the full Firefox experience, with the Weave APIs we're excited to see where developers can provide users with access to their personal data through Weave to provide richer, more personalized experiences across the Web.

== Will Mozilla be submitting the Weave client to the App Store? When? ==
We haven't made a final decision as to whether or not we'll submit a Weave iPhone client to the App Store. But if we do it will be offered as a free download, and we would want to ensure that we could continue to provide the source code under an open source license. Stay tuned.

== Is this a preview of Firefox coming to the iPhone? ==
No. We don't have any plans to develop Firefox for the iPhone. We're working to get Firefox with full Weave support onto as many connected devices as possible. Firefox is available today on Nokia's Maemo platform, and we're actively working on Android and Windows Mobile versions.

The Weave client for the iPhone is independent of the browser. It is a standalone application that providers users with secure access to the bookmarks, history, open tabs, etc. It allows you to quickly find and preview your favorite sites, open tabs, etc. and then provides you the ability to open them in the native browser or share with friends via email.

== What are the plans for future development? ==
Future releases of Weave Sync will add support for synchronizing your browser add-ons, search plugins and other customizations and ultimately everything that makes your Firefox and Web experience personal.

As we begin to roll out other components of the Weave platform (e.g. identity, sharing, etc.), additional APIs and services will be made available.

Jetpack/Roadmap-2011

2009-06-02T16:07:58Z

Cbeard:

{{draft}}

= Jetpack 1.0 Goals =

* '''A seamless install process''': It defeats the purpose of Jetpack to first require users to install Jetpack, then install a particular Jetpack, before using its features. Instead, we need a solution which allows a seamless install process.
* '''Seamless debugging''': No pointless error messages, and all relevant warnings, line numbers, and tracebacks, are displayed.
* '''Enabling API''': An API deep enough to support a large range of add-ons. It is a non-goal in 1.0 to support everything, instead it is to support 80% of the long-tail of add-ons. The exact feature set of the API will be determined by a set of target add-ons (TBD) and feedback from Jetpack authors.
** '''Frozen API''': Although the API may be versioned, we the API will be backwards compatible from 1.0 on.
* '''Beautiful by default''': A set of OS-specific icons, as well as a beautiful look for Jetpacks.
* '''Security-sensitive Import mechanism''': The strength of any API is measured in how easily 3rd parties can extend it. The 1.0 release will have a strong import mechanism, replete with security provisions.
* '''Security''': A functioning security system that mixes code with social protections.
** An AMO-like service with social code-review
* '''Localization story'''
* '''Works on Fennec'''

=== Milestone 1 ===

Functional prototype API that follows the Guiding Principles and provides enough capability to implement these target add-ons:

[[Target Add-ons]]

=== Milestone 2 ===

Get to a point where we can start implementing something like social bookmarking (e.g. Delicious Bookmarks) via the API:

* Access to prefs
* Access to cookie jar or alternatively the ability to have its own sandboxed cookie jar
* Web service calls via Firefox network prefs (i.e. proxy settings)
* mozStorage
* Ability to modify menus/keyboard shortcuts
* New Sidebar, new toolbar, and adding/removing buttons from Fx toolbar
* Ability to add search plugins (but not remove unrelated plugins)

Labs/Jetpack

2009-06-02T16:07:26Z

Cbeard:

__NOTOC__

= Mozilla Labs - Jetpack =
Jetpack is a newly formed experiment in using open Web technologies to enhance the browser, with the goal of allowing anyone who can build a Web site to participate in making the Web a better place to work, communicate and play.

In short, Jetpack is an API for allowing you to write Firefox add-ons using the web technologies you already know.

As with all Labs experiments, Jetpack is an open source project and everyone is welcome to participate in its design, development and testing.

== Project News & Information ==
* [https://labs.mozilla.com/2009/05/introducing-jetpack-call-for-participation/ Introducing Jetpack, Call for Participation] (May 20, 2009)

== Resources for Building a Jetpack ==
* [https://jetpack.mozillalabs.com Jetpack API Documentation, Tutorial & Demos]
* [[Labs/Jetpack/In_The_Wild|Jetpacks in the Wild]].

== Resources for Jetpack Platform Development ==

* [[Labs/Jetpack/Roadmap|Jetpack Roadmap]] (Under Development)

* [[Labs/Jetpack/JEPs|Jetpack Proposed Extensions (JEPs)]] is the place to propose language and API extensions to Jetpack.

* Initial investigation into the capabilities used by top add-ons today, and in particular, which de facto API calls they rely upon.
** [[Labs/Extensions2/Notes]]
** [[Labs/Extensions2/Target_Add-ons]]

== Getting Involved ==

* Discuss, debate and add to the design in the [http://groups.google.com/group/mozilla-labs-jetpack/topics Jetpack discussion group]
* [https://hg.mozilla.org/labs/jetpack Grab the source code] and fix a bug or add a feature
* Join us in #jetpack on irc.mozilla.org
* [https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Labs&component=Jetpack Report a bug]

Labs/Jetpack

2009-06-02T16:06:25Z

Cbeard:

{{draft}}

= Overview =
Jetpack is a newly formed experiment in using open Web technologies to enhance the browser, with the goal of allowing anyone who can build a Web site to participate in making the Web a better place to work, communicate and play.

In short, Jetpack is an API for allowing you to write Firefox add-ons using the web technologies you already know.

As with all Labs experiments, Jetpack is an open source project and everyone is welcome to participate in its design, development and testing.

== Project News & Information ==
* [https://labs.mozilla.com/2009/05/introducing-jetpack-call-for-participation/ Introducing Jetpack, Call for Participation] (May 20, 2009)

== Resources for Building a Jetpack ==
* [https://jetpack.mozillalabs.com Jetpack API Documentation, Tutorial & Demos]
* [[Labs/Jetpack/In_The_Wild|Jetpacks in the Wild]].

== Resources for Jetpack Platform Development ==

* [[Labs/Jetpack/Roadmap|Jetpack Roadmap]]

* [[Labs/Jetpack/JEPs|Jetpack Proposed Extensions (JEPs)]] is the place to propose language and API extensions to Jetpack.

* Initial investigation into the capabilities used by top add-ons today, and in particular, which de facto API calls they rely upon.
** [[Labs/Extensions2/Notes]]
** [[Labs/Extensions2/Target_Add-ons]]

== Getting Involved ==

* Discuss, debate and add to the design in the [http://groups.google.com/group/mozilla-labs-jetpack/topics Jetpack discussion group]
* [https://hg.mozilla.org/labs/jetpack Grab the source code] and fix a bug or add a feature
* Join us in #jetpack on irc.mozilla.org
* [https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Labs&component=Jetpack Report a bug]

Labs/Extensions2/Target Add-ons

2009-04-16T22:54:30Z

Cbeard:

Back to [[Labs/Jetpack]].

These are a set of target add-ons that we would like to think about for [[Labs/Jetpack|Jetpack]]. These add-ons:

* are useful
* do not require write access to the file system
* do not require Places access
* are simple enough in most cases to be developed and designed by a single developer
* cover a range of browser integrations that are broadly useful to developers

In general these extensions strike a balance between complexity and utility, hence their consideration for an early version of Jetpack.

=== [https://addons.mozilla.org/en-US/firefox/addon/26 Download Statusbar] ===
This add-on modifies the status bar to monitor downloads.

Required features:

* Status bar integration
* HTML overlays for mouseovers
* Access to Download Manager
* Custom prefs window in Add-on manager
* First-run experience

=== [https://addons.mozilla.org/en-US/firefox/addon/4925 AutoPager] ===
This add-on has no visible UI but adds infinite scroll capability to a paginated web page.

Required features:

* access/modify DOM

=== [https://addons.mozilla.org/en-US/firefox/addon/4810 Speed Dial] ===
Speed Dial is an add-on that brings up a grid of saved pages (not bookmarks) marked for quick access on a keystroke. There is also a toolbar button that invokes this screen.

Required features:

* Add toolbar button
* Add Context Menu option (right click on link to add to quick dial)
* Custom prefs pane
* mozStorage
* Add Menu option to Bookmarks menu to 'Save to Speed Dial'

=== [https://addons.mozilla.org/en-US/firefox/addon/398 Forecastfox] ===
Forecastfox inserts weather channel data in the status bar.

* Insert icons and text into status bar
* Access network resources (poll web service)
* rich tooltips (images)
* insert images into toolbar (not clickable)

=== [https://addons.mozilla.org/en-US/firefox/addon/2677 Morning Coffee] ===
This extension allows the user to set a default set of pages based on rules determined by the day of week.

* Access current location
* context menu
* Load one or more pages on firefox startup

=== [https://addons.mozilla.org/en-US/firefox/addon/77 Sage] ===
Sage is a sidebar based RSS newsreader. It does have bookmarks integration but I don't believe that it's something that is critical to the add-on.

* Custom sidebar implementation, something that can probably be implemented without chrome access.
* Network access
* mozStorage (store subscriptions)
* File read access
* Add 'Sage' as option for subscribing to RSS via awesomebar or subscriptions page

=== [https://addons.mozilla.org/en-US/firefox/addon/590 ShowIP] ===
This is a very simple extension that is similar to what a hobbyist might want to create. It shows the current IP of the page being viewed in the status bar and offers a few options like whois, etc.

* Poll current location
* Network access (look up IP, whois)
* Status bar text
* Status bar context menu

=== [https://addons.mozilla.org/en-US/firefox/addon/3982 allmusic.com toolbar] ===
In addition to being a simple search bar for allmusic.com, this toolbar also allows the user to highlight text and use a context menu to trigger searches.

* DOM read access
* Custom toolbar
* Open a URL (search)

Labs/Vapour

2009-04-16T22:53:25Z

Cbeard:

See [[Labs/Jetpack|Labs/Jetpack]]

Labs/Jetpack

2009-04-16T22:52:51Z

Cbeard: Created page with '{{draft}} = Overview = Jetpack is a project to explore new & innovative approaches to extensibility of the browser. == Background == TBD == Guiding Principles == Enhancing t...'

{{draft}}

= Overview =
Jetpack is a project to explore new & innovative approaches to extensibility of the browser.

== Background ==
TBD

== Guiding Principles ==

Enhancing the browser should be as easy as it is to write a web page. The time between having an idea, and an implementation should be as short as possible: Programming the "hello world" add-on for each of the major add-on types should take less than 5 minutes from start to running in the browser.

# '''Use Web Technology'''
#*HTML, Javascript, and CSS should be the only tools required to create an add-on. If you are already a web developer, you know all you need to be comfortable writing an add-on.
# '''Develop Once, Run Anywhere, Any Version'''.
#* Writing an add-on for Firefox should run in Firefox Mobile, Thunderbird, and anywhere else that's apropos. Programming should be by intent: You should be able to say, "My add-on should expose UI in a toolbar-like thing", and it will. Whatever a toolbar-like thing happens to be on Fennec, Firefox, etc.
#* As a developer, you shouldn't have to worry about some detail-of-Firefox internals changing breaking your extension. Add-ons will work through a version'ed facade-pattern so that you won't be in a constant struggle to keep your extension working with the latest FF edition.
#'''Secure'''
#* Add-ons should have access to only the privileges they need. They should be as safe and secure as Firefox proper.
#* Add-ons should be easy to code review -- making security problems much more shallow.
#* Add-ons should not interfere with each other.
#* Security models should be easy to innovate. Security is ripe for improvement, and we should be enabling easy experimentation and deployment, letting security researchers mix social trust models, object component models, and as-of-yet unthought-of models.
#* Security should always be presented in human-terms, not technical-terms.
#* More secure add-ons should enjoy a more streamlined user experience for installation.
# '''Easy to code'''
#* The API should be small, short, concise.
#* Great design patterns should be easy to follow with good supporting APIs
#* Should allow open innovation in APIs via easy inclusion of 3rd party libraries.
#* Changes made during development should be reflected in real-time in the browser
#* Great documentation. Tutorials, snippets, examples.
# '''Easy to install, easy to use, easy to keep up-to-dates'''
#* Add-ons should feel light-weight: they should be installable without restart and in two clicks or less
#* Add-ons should automatically up-date securely. This process should be easy for users and developers alike.

= Design Constraints =
[...]

= Proposed Roadmap =

=== Milestone 1 ===

Functional prototype API that follows the Guiding Principles and provides enough capability to implement these target add-ons:

[[Target Add-ons]]

=== Milestone 2 ===

Get to a point where we can start implementing something like social bookmarking (e.g. Delicious Bookmarks) via the API:

* Access to prefs
* Access to cookie jar or alternatively the ability to have its own sandboxed cookie jar
* Web service calls via Firefox network prefs (i.e. proxy settings)
* mozStorage
* Ability to modify menus/keyboard shortcuts
* New Sidebar, new toolbar, and adding/removing buttons from Fx toolbar
* Ability to add search plugins (but not remove unrelated plugins)

= Resources =

* Initial investigation into the capabilities used by top add-ons today, and in particular, which de facto API calls they rely upon.
** [[Labs/Extensions2/Notes]]
** [[Labs/Extensions2/Target_Add-ons]]

* Rough notes on potential API structure
** [[User:Aza/VapourExamples|Code Snippets]]
** [[User:Mconnor/Extensions2.0|Specs]]

Labs/Vapour

2009-04-16T22:51:33Z

Cbeard: Blanked the page

Firefox/Projects/About:newtab

2009-03-04T22:45:45Z

Cbeard: /* Overview */

= Overview =
'''Drivers:''' Dan Mills (thunder), Aza Razkin (aza), Edward Lee (Mardak) 
'''Get involved:''' by hopping onto #labs on irc.mozilla.org or clicking on [[Talk:About:newtab|Discussion]] and leaving your comments

;Description
:Instead of a blank page, the new tab page should present useful task-centric navigation options based on the user's history.

= Goals / Use Cases =
* be perceptibly as fast as about:blank to load
* allow user to re-open previously closed tabs
* offer navigation targets that are likely to be of use to the user
* do not break the user's mental "flow" or otherwise interrupt a user task

= Non Goals =
* act as a content aggregator for "new" material

= Design =
'''v0.0.1'''
* provide thumbnail links to commonly visited pages along the bottom of the page
* put links to recently closed tabs along the side of the page
* if there is content in the clipboard, provide a button to search for that content in the upper left of the page
* if there are RSS feeds on the commonly visited pages, show the most recent 3 stories for those above their thumbnails

= Bugs =

= Test Builds / Add-Ons =

Labs/Personas/PersonasListUpdate

2009-02-28T01:55:18Z

Cbeard: /* Format of Update Request */

{{draft}}
= Personas Update Service =

== Requirements ==

* Every 24 hours the client will request an update to the directory by requesting the latest list from the Personas sever using the URL scheme provided below.
* The update request will return a JSON file that provides the current list of available Personas.
* No personally identifiable or potentially personally identifiable information shall be tracked or recorded in any way.

== Format of Update Request ==

<blockquote>
<table border="1" cellspacing="0" cellpadding="3">
<tr><td>'''https://getpersonas.com/update/PersonasDirectoryUpdate?reqVersion=%REQ_VERSION%&id=%ITEM_ID%&version=%ITEM_VERSION%&duration=%ITEM_DURATION%&appID=%APP_ID%&appVersion=%APP_VERSION%&appLocale=%APP_LOCALE%&appOS=%APP_OS%&appABI=%APP_ABI%'''</td></tr>
<tr><td>
* %REQ_VERSION% is the version of the request;
* %ITEM_ID% is the UUID of the selected persona (e.g. 22);
* %ITEM_VERSION% is the version of the selected persona (e.g. 1);
* %ITEM_DURATION% is the timestamp the persona was selected;
* %APP_ID% is the UUID of the application;
* %APP_VERSION% is the version of the application (e.g. 3.0.6);
* %APP_LOCALE% is the locale of the application (e.g. en-US);
* %APP_OS% is the target OS;
* %APP_ABI% is the target architecture</td></tr>
</table>
</blockquote>

Labs/Personas/PersonasListUpdate

2009-02-28T01:54:07Z

Cbeard: /* Requirements */

{{draft}}
= Personas Update Service =

== Requirements ==

* Every 24 hours the client will request an update to the directory by requesting the latest list from the Personas sever using the URL scheme provided below.
* The update request will return a JSON file that provides the current list of available Personas.
* No personally identifiable or potentially personally identifiable information shall be tracked or recorded in any way.

== Format of Update Request ==

<blockquote>
<table border="1" cellspacing="0" cellpadding="3">
<tr><td>'''https://getpersonas.com/update/PersonasDirectoryUpdate.php?reqVersion=%REQ_VERSION%&id=%ITEM_ID%&version=%ITEM_VERSION%&duration=%ITEM_DURATION%&appID=%APP_ID%&appVersion=%APP_VERSION%&appLocale=%APP_LOCALE%&appOS=%APP_OS%&appABI=%APP_ABI%'''</td></tr>
<tr><td>
* %REQ_VERSION% is the version of the request;
* %ITEM_ID% is the UUID of the selected persona (e.g. 22);
* %ITEM_VERSION% is the version of the selected persona (e.g. 1);
* %ITEM_DURATION% is the timestamp the persona was selected;
* %APP_ID% is the UUID of the application;
* %APP_VERSION% is the version of the application (e.g. 3.0.6);
* %APP_LOCALE% is the locale of the application (e.g. en-US);
* %APP_OS% is the target OS;
* %APP_ABI% is the target architecture</td></tr>
</table>
</blockquote>

Labs/Personas/PersonasListUpdate

2009-02-28T00:12:33Z

Cbeard: /* Format of Update Request */

{{draft}}
= Personas Update Service =

== Requirements ==

* Every 24 hours the client will request an update to the directory by requesting the latest list from the Personas sever using the URL scheme provided below.
* The update request will return a JSON file that provides the current list of available Personas.
* The list of available Personas will include the currently selected Persona even if that Persona is no longer in the directory due to a decline in popularity. Minimally, it should be included as the last item in its appropriate category.
* No personally identifiable or potentially personally identifiable information shall be tracked or recorded in any way.

== Format of Update Request ==

<blockquote>
<table border="1" cellspacing="0" cellpadding="3">
<tr><td>'''https://getpersonas.com/update/PersonasDirectoryUpdate.php?reqVersion=%REQ_VERSION%&id=%ITEM_ID%&version=%ITEM_VERSION%&duration=%ITEM_DURATION%&appID=%APP_ID%&appVersion=%APP_VERSION%&appLocale=%APP_LOCALE%&appOS=%APP_OS%&appABI=%APP_ABI%'''</td></tr>
<tr><td>
* %REQ_VERSION% is the version of the request;
* %ITEM_ID% is the UUID of the selected persona (e.g. 22);
* %ITEM_VERSION% is the version of the selected persona (e.g. 1);
* %ITEM_DURATION% is the timestamp the persona was selected;
* %APP_ID% is the UUID of the application;
* %APP_VERSION% is the version of the application (e.g. 3.0.6);
* %APP_LOCALE% is the locale of the application (e.g. en-US);
* %APP_OS% is the target OS;
* %APP_ABI% is the target architecture</td></tr>
</table>
</blockquote>

Labs/Personas/PersonasListUpdate

2009-02-28T00:10:20Z

Cbeard: New page: {{draft}} = Personas Update Service = == Requirements == * Every 24 hours the client will request an update to the directory by requesting the latest list from the Personas sever using t...

{{draft}}
= Personas Update Service =

== Requirements ==

* Every 24 hours the client will request an update to the directory by requesting the latest list from the Personas sever using the URL scheme provided below.
* The update request will return a JSON file that provides the current list of available Personas.
* The list of available Personas will include the currently selected Persona even if that Persona is no longer in the directory due to a decline in popularity. Minimally, it should be included as the last item in its appropriate category.
* No personally identifiable or potentially personally identifiable information shall be tracked or recorded in any way.

== Format of Update Request ==

<blockquote>
<table border="1" cellspacing="0" cellpadding="3">
<tr><td>'''https://getpersonas.com/update/PersonasDirectoryUpdate.php?reqVersion=%REQ_VERSION%&id=%ITEM_ID%&version=%ITEM_VERSION%&duration=%ITEM_DURATION%&appID=%APP_ID%&appVersion=%APP_VERSION%&appLocale=%APP_LOCALE%&appOS=%APP_OS%&appABI=%APP_ABI%'''</td></tr>
<tr><td>
* %REQ_VERSION% is the version of the request;
* %ITEM_ID% is the UUID of the selected persona (e.g. 22);
* %ITEM_VERSION% is the version of the selected persona (e.g. 1);
* %ITEM_DURATION% is the number of seconds the selected personas has been active (e.g. 3600);
* %APP_ID% is the UUID of the application;
* %APP_VERSION% is the version of the application (e.g. 3.0.6);
* %APP_LOCALE% is the locale of the application (e.g. en-US);
* %APP_OS% is the target OS;
* %APP_ABI% is the target architecture</td></tr>
</table>
</blockquote>

Labs/Bespin

2009-02-19T20:42:26Z

Cbeard:

<table><tr><td>__TOC__</td><td>
http://people.mozilla.com/~cbeard/Bespin_Logo.png</td></tr></table>
[http://labs.mozilla.com/projects/bespin/ Bespin] is a [http://labs.mozilla.com Mozilla Labs] project and place for the wider community to discuss what a Web based code editor could be like.

== Find out more ==

* [http://labs.mozilla.com/projects/bespin Bespin]: Our home page
* [http://labs.mozilla.com/2009/02/introducing-bespin Initial Announcement]: Our first blog post
* [[Labs/Bespin/Roadmap|Roadmap]]: This is where we will try to keep a high level roadmap

== User Guide ==

* [[Labs/Bespin/UserGuide|User Guide]]: Don't expect much right now - we're just getting started.
* [[Labs/Bespin/FAQ|Frequently Asked Questions]]: We will try to answer as many question as possible here.
* [[Labs/Bespin/Tips|Tips and Tricks]]: Here we will place tips for users of Bespin
* [[Labs/Bespin/KnownIssues|Known Issues]]: Bugzilla is the right place to look for up to date information, but this will tell you which big items are very much known and on our plate.

== Source Code ==

* [http://hg.mozilla.org/labs/bespin/ The Bespin Source Code]: It all starts here
* [[Labs/Bespin/Contributing|Contributing to Bespin]]: How to contribute code
* [https://bespin.mozilla.com/docs/ Bespin Code Documentation]: Thanks to code illumination
* [[Labs/Bespin/ServerAPI|Server API]]: Fancy implementing a Bespin server?
* [[Labs/Bespin/Architecture|Architecture]]: What are the parts and pieces of Bespin
* [[Labs/Bespin/ReleaseNotes|Release Notes]]: This is where we will update each release with info on what is in there.
* [[Labs/Bespin/CodingStyle|Coding Style]]: A (brief) guide to sharing code

== We know that you have something to contribute, join us! ==

* [[Labs/Bespin/BugzillaUsage|Bugzilla Usage]]: Reporting a bug / enhancement request
* [http://groups.google.com/group/bespin Google Group]: Participate on our Google Group
* [irc://irc.mozilla.org/bespin IRC #bespin]: Join our irc channel
* [[Labs/Bespin/ProjectsUsingBespin|Related Projects]]: If you are using Bespin somewhere, please let us know!

Labs/Vapour

2009-02-05T15:50:40Z

Cbeard:

{{draft}}
''[Note that the name "Vapour" is a placeholder while we work to make this project real. ;-)]''

= Overview =
Vapour is a project to explore new & innovative approaches to extensibility of the browser.

== Background ==
TBD

== Guiding Principles ==

Enhancing the browser should be as easy as it is to write a web page. The time between having an idea, and an implementation should be as short as possible: Programming the "hello world" add-on for each of the major add-on types should take less than 5 minutes from start to running in the browser.

# '''Use Web Technology'''
#*HTML, Javascript, and CSS should be the only tools required to create an add-on. If you are already a web developer, you know all you need to be comfortable writing an add-on.
# '''Develop Once, Run Anywhere, Any Version'''.
#* Writing an add-on for Firefox should run in Firefox Mobile, Thunderbird, and anywhere else that's apropos. Programming should be by intent: You should be able to say, "My add-on should expose UI in a toolbar-like thing", and it will. Whatever a toolbar-like thing happens to be on Fennec, Firefox, etc.
#* As a developer, you shouldn't have to worry about some detail-of-Firefox internals changing breaking your extension. Add-ons will work through a version'ed facade-pattern so that you won't be in a constant struggle to keep your extension working with the latest FF edition.
#'''Secure'''
#* Add-ons should have access to only the privileges they need. They should be as safe and secure as Firefox proper.
#* Add-ons should be easy to code review -- making security problems much more shallow.
#* Add-ons should not interfere with each other.
#* Security models should be easy to innovate. Security is ripe for improvement, and we should be enabling easy experimentation and deployment, letting security researchers mix social trust models, object component models, and as-of-yet unthought-of models.
#* Security should always be presented in human-terms, not technical-terms.
#* More secure add-ons should enjoy a more streamlined user experience for installation.
# '''Easy to code'''
#* The API should be small, short, concise.
#* Great design patterns should be easy to follow with good supporting APIs
#* Should allow open innovation in APIs via easy inclusion of 3rd party libraries.
#* Changes made during development should be reflected in real-time in the browser
#* Great documentation. Tutorials, snippets, examples.
# '''Easy to install, easy to use, easy to keep up-to-dates'''
#* Add-ons should feel light-weight: they should be installable without restart and in two clicks or less
#* Add-ons should automatically up-date securely. This process should be easy for users and developers alike.

= Design Constraints =
* Must support (or have a clear migration path to support) the vast majority of existing add-ons in short order.
* ...

= Proposed Roadmap =

=== Milestone 1 ===

Functional prototype API that follows the Guiding Principles and provides enough capability to implement these target add-ons:

[[Target Add-ons]]

=== Milestone 2 ===

Get to a point where we can start implementing something like Delicious Bookmarks via the API:

* Access to prefs
* Access to cookie jar or alternatively the ability to have its own sandboxed cookie jar
* Web service calls via Firefox network prefs (i.e. proxy settings)
* mozStorage
* Ability to modify menus/keyboard shortcuts
* New Sidebar, new toolbar, and adding/removing buttons from Fx toolbar
* Ability to add search plugins (but not remove unrelated plugins)

= Resources =

* Initial investigation into the capabilities used by top add-ons today, and in particular, which de facto API calls they rely upon.
** [[Labs/Extensions2/Notes]]
** [[Labs/Extensions2/Target_Add-ons]]

* Rough notes on potential API structure
** [[User:Aza/VapourExamples]]
** [[User:Mconnor/Extensions2.0]]

Labs/Vapour

2009-02-05T05:31:21Z

Cbeard:

= Vapour: A project to explore new & innovative approaches to extensibility of the browser. =

== Background ==
TBD

== Guiding Principles ==

Enhancing the browser should be as easy as it is to write a web page. The time between having an idea, and an implementation should be as short as possible: Programming the "hello world" add-on for each of the major add-on types should take less than 5 minutes from start to running in the browser.

# '''Use Web Technology'''
#*HTML, Javascript, and CSS should be the only tools required to create an add-on. If you are already a web developer, you know all you need to be comfortable writing an add-on.
# '''Develop Once, Run Anywhere, Any Version'''.
#* Writing an add-on for Firefox should run in Firefox Mobile, Thunderbird, and anywhere else that's apropos. Programming should be by intent: You should be able to say, "My add-on should expose UI in a toolbar-like thing", and it will. Whatever a toolbar-like thing happens to be on Fennec, Firefox, etc.
#* As a developer, you shouldn't have to worry about some detail-of-Firefox internals changing breaking your extension. Add-ons will work through a version'ed facade-pattern so that you won't be in a constant struggle to keep your extension working with the latest FF edition.
#'''Secure'''
#* Add-ons should have access to only the privileges they need. They should be as safe and secure as Firefox proper.
#* Add-ons should be easy to code review -- making security problems much more shallow.
#* Add-ons should not interfere with each other.
#* Security models should be easy to innovate. Security is ripe for improvement, and we should be enabling easy experimentation and deployment, letting security researchers mix social trust models, object component models, and as-of-yet unthought-of models.
#* Security should always be presented in human-terms, not technical-terms.
#* More secure add-ons should enjoy a more streamlined user experience for installation.
# '''Easy to code'''
#* The API should be small, short, concise.
#* Great design patterns should be easy to follow with good supporting APIs
#* Should allow open innovation in APIs via easy inclusion of 3rd party libraries.
#* Changes made during development should be reflected in real-time in the browser
#* Great documentation. Tutorials, snippets, examples.
# '''Easy to install, easy to use, easy to keep up-to-dates'''
#* Add-ons should feel light-weight: they should be installable without restart and in two clicks or less
#* Add-ons should automatically up-date securely. This process should be easy for users and developers alike.

= Design Constraints =

e.g. Support for existing add-ons.

TBD

= Proposed Roadmap =

=== Milestone 1 ===

Functional prototype API that follows the Guiding Principles and provides enough capability to implement these target add-ons:

[[Target Add-ons]]

=== Milestone 2 ===

Get to a point where we can start implementing something like Delicious Bookmarks via the API:

* Access to prefs
* Access to cookie jar or alternatively the ability to have its own sandboxed cookie jar
* Web service calls via Firefox network prefs (i.e. proxy settings)
* mozStorage
* Ability to modify menus/keyboard shortcuts
* New Sidebar, new toolbar, and adding/removing buttons from Fx toolbar
* Ability to add search plugins (but not remove unrelated plugins)

= Examples =

[[User:Aza/VapourExamples]]

[[User:Mconnor/Extensions2.0]]

= Notes on Current Use =

[[Labs/Extensions2/Notes]]

[[Labs/Extensions2/Target_Add-ons]]

WeeklyUpdates/2008-12-22

2008-12-22T21:09:25Z

Cbeard: /* Webdev, Add-ons, AMO */

[[WeeklyUpdates/2008-12-15| « previous week]] | [[WeeklyUpdates|index]] | [[WeeklyUpdates/2008-12-29|next week »]]

'''Meeting Details'''
* 1:00pm Pacific time (21:00 UTC until March 8, 2009)
* Mozilla HQ, 1st floor conference table
* +1 650 903 0800 x92 Conf# 8600 (US/International)
* +1 416 848 3114 x92 Conf# 8600 (Canada)
* +1 800 707 2533 (pin 369) Conf# 8600 (US Toll Free)
* sip:weeklystatus@mozilla.com from generic SIP clients
* http://air.mozilla.com/ to watch and listen
* join irc.mozilla.org #staffmeeting for backchannel

'''note:''' all participants are muted automatically; if you want to talk, press *1 to un-mute yourself

'''WeeklyUpdate Live''': You can watch the weekly meetings live at [http://air.mozilla.com Air Mozilla] You can also view previous meetings from the "on-demand" button on the Air Mozilla player. Meetings will be posted for on-demand consumption shortly after the meeting conclusion.

= Friends of the Tree [[Image:Tree.gif|Friends of the Tree]] =

*Alix writes in to nominate "Bruno Magrani, Koichi Kameda, and Ronaldo Lemos at FGV for their hard work in organizing and moderating Mozilla's first [http://blog.mozilla.com/brasil/2008/12/13/mozilla-lanca-projeto-para-lan-houses/ LAN House workshop in Rio, Brazil] last week.

*Simon Montague nominated Serge Gautherie, Robert O'Callahan, and Vladimir Vukicevic for making reftesting faster and friendlier.

Please send FotT nominations to [mailto:asa@mozilla.org asa@mozilla.org]. This is a great opportunity for the community to recognize those who go above and beyond, so please tell me when you see that happening. Thanks.

= Development Updates =

== Branch work: Firefox 2.0.0.19 / 3.0.5 / Major Update ==
* '''Firefox [[Releases/Firefox_2.0.0.19|2.0.0.19]] / [[Releases/Firefox_3.0.5|3.0.5]] / [[Releases/Firefox_2.0.0.20|2.0.0.20]]'''
** Shipped Firefox 2.0.0.19 and 3.0.5 on Tuesday
** Noticed that the 2.0.0.19 release was incomplete
** Shipped 2.0.0.20 release on Thursday
* '''[[Releases/Thunderbird_2.0.0.19|Thunderbird 2.0.0.19]]'''
** Shipped Thunderbird 2.0.0.19 to beta users on Thursday
** Aiming for final release in early January
* '''[[Releases/Firefox_3.0.6|Firefox 3.0.6]]'''
** Code freeze is January 6
** Aiming for ship date in early February

== Gecko 1.9.1 ==
* 39 Bugs blocking beta 3, 24 of those have patches.
* Beta 3 code freeze is Jan 13.
* For weekly engineering meeting notes and other info see the [https://wiki.mozilla.org/Platform Platform page].
* [http://wiki.mozilla.org/Platform/1.9.1 Interesting queries related to Gecko 1.9.1]
* [http://tinyurl.com/3jsumu 167 1.9.1 blockers].
** [http://tinyurl.com/4ombdf 39 Blocking 1.9.1 P1s]
** [http://tinyurl.com/4lt8ah 65 Blocking 1.9.1 P2s]
** [http://tinyurl.com/5x59y5 26 Blocking 1.9.1 P3s]
** [http://tinyurl.com/47df5d 37 Blocking 1.9.1 w/ no priority.]

== Firefox 3.1 ==

== TB 3 ==

== Mobile ==
<strike>[https://bugzilla.mozilla.org/show_bug.cgi?id=468729 Two]</strike> [https://bugzilla.mozilla.org/show_bug.cgi?id=453470 bugs] remaining before A2 release.

== IT ==
* Handled three releases & a SUMO update:
** Funnelcake - 12/15
** Firefox 2.0.0.19/3.0.5 - 12/16
** Firefox 2.0.0.20 - 12/18
** [http://support.mozilla.com/ support.mozilla.com] - 12/18

== Release Engineering ==
* another busy week of releases:
** FF2.0.0.19
** FF2.0.0.20
** FF3.0.5
** TB2.0.0.19
** partner major updates
** funnelcake
** major update (ff2.0.0.20->ff3.0.5)
* a11y turned on in production {{bug|424195}}
* consolidated pool of build-and-unittest slaves

== QA ==

'''Test Execution'''
* Shipped Fx2.0.0.19 & Fx3.0.5 on 12/16
* Then shipped a quick Fx2.0.0.20 in < 1 1/2 days
** Testplan [https://wiki.mozilla.org/Firefox:2.0.0.20:Test_Plan results]
** Fx3.1 feature tracking [http://spreadsheets.google.com/ccc?key=pnyCb4cp33faqpi709iEhcA&hl=en spreadsheet]
*** Testplan completion: 89%
*** Testcase completion: 73%

'''Web Dev testing, Metrics, Accessibility, Localization, Crash Reports'''
* Re-released [http://quality.mozilla.org/ QMO2] - our community testing portal.
* We are looking for [http://quality.mozilla.org/blogs/nightly-testers-needed-mozilla-central more nightly testers on mozilla-central]!
* Web Dev testing- Tested [http://tinyurl.com/99g2l7 bug fixes for the Community Store and Support]
* Accessibility- The tests are finally running on mozilla-central and mozilla-1.9.1 production Tinderbox unit test machines. Lukas switched them on on Thursday morning, and so far, they are looking good.
* Metrics- Generated new code coverage data from the Firefox 3.2Alpha1 trunk. Modified the Lcov and geninfo tools that come with gcov to work with Mozilla builds to generated file source line level link for CodeCov [http://ultra5.office.mozilla.org/~mnandigama/nativeCovReport/ report].
* Crash Reporting- Helped with some new reports that are finally starting to go live. See alpha versions of: [http://crash-stats.mozilla.com/mtbf/of/Firefox/major MTBF], [http://crash-stats.mozilla.com/topcrasher/bydomain/Firefox/3.0.5 By Domain], [http://crash-stats.mozilla.com/topcrasher/byurl/Firefox/3.0.5 By URL].

''' Test Development'''
* Working on an extension with locale testing of Major Updates (MUs). See {{bug|452327}}
* Testing mobile in preparation for Alpha 2
* Test of 100,000 Topsites is running (so far around 22,000 Pages are done!)
* Investigating Mochitest failures on Fennec. See [http://people.mozilla.com/~jmaher/mochitest.htm details]

'''Misc'''
* Attending [http://events.ccc.de/congress/2008/ 25c3] Security Conference in Berlin next week

== Security ==

No updates.

== Marketing/PR ==

'''PR'''
* John Lilly reflects on the competition in [http://www.computerworld.com/action/article.do?command=viewArticleBasic&articleId=9124141&intsrc=news_ts_head ComputerWorld]
* Read/Write Web announces Weave as a [http://www.readwriteweb.com/archives/top_10_web_platforms_of_2008.php Top 10 Web Platform of 2008]
* Firefox 3 honored in “Best Browser Peoples Choice Award” in [http://www.crunchgear.com/2008/12/19/crunchgears-best-of-2008-plus-the-peoples-choice/ Crunch Gear]
* Firefox security updates released: [http://news.cnet.com/8301-1009_3-10126106-83.html CNEt], [http://www.crn.com/security/212501064 CRN], [http://arstechnica.com/journals/linux.ars/2008/12/17/firefox-security-updates-ready-for-download Ars Technica]
* Firefox 2.0.0.20 released: [http://www.pcworld.com/article/155831/mozilla_revamps_firefox_20_update.html PCWorld], [http://blogs.pcmag.com/securitywatch/2008/12/the_absolutely_last_and_final.php PC Mag], [http://blog.internetnews.com/skerner/2008/12/missing-mozilla-firefox-flaw-r.html InternetNews]

'''Impact Mozilla'''

'''Other'''

* [http://www.spreadfirefox.com/holiday Firefox for the Holidays] on Sfx
* New [http://www.mozilla.com/en-US/firefox/video/ video page] live on mozilla.com
* Round 2 of the [http://blogmag.net/blog/read/115/Firefox_in_your_country_survey_round_2 Firefox in your country survey] open until Dec 26th. [http://blogmag.net/blog/alix/insights Round 1] results.
* [http://blog.mozilla.com/brasil/2008/12/13/mozilla-lanca-projeto-para-lan-houses/ LAN House workshop] took place last week in Rio, Brazil

== Support ==
* With 0.8 we now have support for detecting and showing Firefox 3.1 specific information for people running that (beta) version. Going to start adding content for these users on the most common issues articles shortly.
* Thanks to Wil Clouser, we now have SUMO support in Verbatim, meaning localizers can translate the site UI using this interface, which is a lot more straightforward than the built-in SUMO UI. I'll be blogging about this tomorrow with more info on how to log in.

== Metrics ==

== Evangelism ==

* We need demos - please add if you have some: https://wiki.mozilla.org/Firefox3.1/Demos

== Labs ==

== Developer Tools ==
== Add-ons ==
== Webdev ==
* SUMO [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Other&product=support.mozilla.com&component=Chat&component=Forum&component=General&component=Knowledge+Base+Articles&component=Knowledge+Base+Software&component=Localization&target_milestone=0.8&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&;emailreporter2=1&emailqa_contact2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit 0.8] shipped with some issues on Thursday, so we pushed out 0.8.0.1 on Friday to fix. New search not yet turned on as we're trying to solve an issue with the indexing [[https://bugzilla.mozilla.org/show_bug.cgi?id=405028#c10]] [[https://bugzilla.mozilla.org/show_bug.cgi?id=460213]] for more info.
* Verbatim support for SUMO
* Community Store 2.0 released, now has galleries for contributors, search and various other [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Websites&component=communitystore.mozilla.org&target_milestone=2.0&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=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&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= bug fixes]
* Most of webdev on vacation this week, or trapped in the snowpocalypse. laura, rdoherty, lars, lorchard are on deck.

== L10n ==
* Firefox 3.1 beta 3 correspondence and schedule has been sent to all localizers

= Foundation Updates =

* David created a '''draft survey for the Powered by Mozilla program'''; for more information see [http://davidwboswell.wordpress.com/2008/12/17/learning-more-about-mozilla-based-applications/ David's blog post].
* Mark worked on the '''2009 Foundation budget''' and related tasks.
* Eitan Isaacson completed his Foundation-funded project to create a '''test framework for non-interactive inspection of the accessibility APIs provided by web browsers'''; among other things, this allows comparison of Firefox's accessibility support with that of IE, Safari, Opera, etc. For more information see [http://monotonous.org/2008/12/21/go-use-it/ Eitan's blog post] and related [http://monotonous.org/tag/specular/ progress reports], as well as his [http://monotonous.org/specular/scriptingenabled/ slide presentation].
* Frank started [http://groups.google.com/group/mozilla.dev.tech.crypto/browse_thread/thread/2dd9e4e1fa4c1716# public discussion] for the '''CA inclusion request from S-TRUST'''.

= Roundtable =

= Other Business =

Labs/PrismFeature

2008-12-10T20:23:40Z

Cbeard:

= Prism-like Feature for Firefox =
Based upon the success and interest in the Prism experiment, we believe that there is an opportunity to uplift a Prism-like feature into a future version of Firefox.

The Prism experiment and platform itself should continue in its exploration, and we'll continually look for opportunities for uplift.

= The Split =

The proposal is that we consider a Prism-like feature in two parts. JS APIs (code name Reach?), and "turn this page into a desktop app" (Appify?).

= Appify =

If we do not want Prism to go the way of the every-so-geeky implementations done by Safari and Chrome, we need to focus on helping users discover when they might want to make an web-app into a desktop app.

When the user is found (by examining the places database) to visit a site frequently and stay on it (i.e., uses it like an application), we can show a suggestion that the user might want to turn it into a desktop application. We can whitelist a number of high-profile known sites that can be appified, others can advertise their ability to be hosted using a link rel tag.

http://img.skitch.com/20081210-mu6783bt3jy13adcik1wfrsfcn.jpg

The message animates into the site identity button indicating the feature can be accessed there. Some heuristic is used to decide how many times the suggestion should be shown. Clicking on the link causes a beautiful animation (the page scales down to the thumbnail seen below, everything else fades in):

http://img.skitch.com/20081210-k6jxkbtx1f7fgxpptefx4usmit.jpg

= JS API (Reach) =

== Use Cases ==

All require being able to be used when offline.

== Flickr Uploader ==

* '''Offline use'''
* '''Drag and drop file handling'''
* '''Generic XHTTP for communication'''

== Zoho Docs ==

* '''File association'''
* '''File access'''
* '''Persistent storage'''
* Offline use
* Drag and drop file handling
* Generic XHTTP for communication

== Task Manager/TO-DO List ==

* '''Listen for system-level keystrokes -- i.e., global heyhook'''
* '''Display + animate windows (transparent and shaped)'''
* '''Run at startup'''
* Offline use
* Generic XHTTP for communication
* Persistent storage

== A Cross Platform Growl ==

* '''Daemon tasks'''
* '''Listen on a port for IPC'''
* '''Install an icon in the menu bar/dock/quick tray/etc.'''
* '''Access to system services (like Text To Speech)'''
* Offline use
* Display + animate windows (transparent and shaped)
* Persistent storage

== Twitter/Social Feed Client ==

* '''Device access (Audio, Camera/Video, GPS)'''
* All of the above

== Adium/Chat Program ==

* '''Ability to interoperate with various chat protocols'''
* All of the above

== Ubiquity ==

* '''Access to the clipboard, and ability to issue copy and paste'''
* All of the above

Labs/PrismFeature

2008-12-10T20:22:49Z

Cbeard: /* The Split */

= Prism-like Feature for Firefox =
Based upon the success and interest in the Prism experiment, we believe that there is an opportunity to uplift a Prism-like feature into a future version of Firefox.

= The Split =

The proposal is that we consider a Prism-like feature in two parts. JS APIs (code name Reach?), and "turn this page into a desktop app" (Appify?).

= Appify =

If we do not want Prism to go the way of the every-so-geeky implementations done by Safari and Chrome, we need to focus on helping users discover when they might want to make an web-app into a desktop app.

When the user is found (by examining the places database) to visit a site frequently and stay on it (i.e., uses it like an application), we can show a suggestion that the user might want to turn it into a desktop application. We can whitelist a number of high-profile known sites that can be appified, others can advertise their ability to be hosted using a link rel tag.

http://img.skitch.com/20081210-mu6783bt3jy13adcik1wfrsfcn.jpg

The message animates into the site identity button indicating the feature can be accessed there. Some heuristic is used to decide how many times the suggestion should be shown. Clicking on the link causes a beautiful animation (the page scales down to the thumbnail seen below, everything else fades in):

http://img.skitch.com/20081210-k6jxkbtx1f7fgxpptefx4usmit.jpg

= JS API (Reach) =

== Use Cases ==

All require being able to be used when offline.

== Flickr Uploader ==

* '''Offline use'''
* '''Drag and drop file handling'''
* '''Generic XHTTP for communication'''

== Zoho Docs ==

* '''File association'''
* '''File access'''
* '''Persistent storage'''
* Offline use
* Drag and drop file handling
* Generic XHTTP for communication

== Task Manager/TO-DO List ==

* '''Listen for system-level keystrokes -- i.e., global heyhook'''
* '''Display + animate windows (transparent and shaped)'''
* '''Run at startup'''
* Offline use
* Generic XHTTP for communication
* Persistent storage

== A Cross Platform Growl ==

* '''Daemon tasks'''
* '''Listen on a port for IPC'''
* '''Install an icon in the menu bar/dock/quick tray/etc.'''
* '''Access to system services (like Text To Speech)'''
* Offline use
* Display + animate windows (transparent and shaped)
* Persistent storage

== Twitter/Social Feed Client ==

* '''Device access (Audio, Camera/Video, GPS)'''
* All of the above

== Adium/Chat Program ==

* '''Ability to interoperate with various chat protocols'''
* All of the above

== Ubiquity ==

* '''Access to the clipboard, and ability to issue copy and paste'''
* All of the above

Project/2010 Goals/MozCampEU Discussions/Data

2008-10-28T17:05:28Z

Cbeard: /* Detailed Notes */

==MozCamp Europe Discussions==

===Summary===

* '''We should help people to better understand and have more control over the privacy of their various online activities & contexts'''

* '''We should provide leadership in the development, promotion and use of open standards for data representation & interoperability'''

* '''If we use data to enhance the online experience we should ensure that we're doing so in ways that promote and ''raise'' expectations for data protection, control and transparency practices on the Web as a whole'''

===Detailed Notes===

* '''We should help people to better understand and have more control over the privacy of various online activities & contexts''' ''[knowledge, visibility, selectivity, control]''

** users should be able to change their mind at any time about what they are sharing as situations change (e.g. companies change ownership)
** it should be clearer to users when there is data being collected about them, both explicitly (by submitting a form) and through use (by using a web site)
** should be possible [to clearly and visibly] differentiate between public and private spaces & activities
** flexibility and control to selectively share data
** how do you know if your activity online is public or private, e.g. the browser tells you now if the session is encrypted, could it also tell you how the data submitted from a form may be used
** ability to see the data that you're sharing with anyone
** all decisions (and rights) on your data should be revocable

* '''We should provide leadership in the development, promotion and use of open standards for data representation & interoperability''' ''[interoperability, standards, openness]''

** increasing prevalence of proprietary data formats, opportunities to enable adoption of open formats?
** lots of duplication of metadata (e.g. CD/DVD titles, etc.), opportunities to aggregate and consolidate into shared commons
** customer can't leverage own data
** blog comments are hard for people to keep track of
** we've solved some of the data privacy and interoperability problems before and new web services are reinventing components of these technologies but not adopting the practices and policies that were developed over years, i.e. data retention policies, access controls, interoperability, data portability, etc.
** should be possible to combine data feeds from various public and/or proprietary sources and do something useful with them, e.g. visualizations, mashups, etc.
** there should be common formats and/or open standards to represent data and data policies
** files and media in proprietary formats are at risk of being useless if and when companies that back them fail.
** should focus on developing and promoting open standards & interoperability
** should evangelize and protect against dangers inherent in RFC-based Internet communication and data interchange formats/protocols (e.g. IMAP, SMTP, NNTP, etc.) being replaced with proprietary Web technologies (e.g. Facebook, Twitter, etc.)
** should define "open"-ness for data & related services and ensure that it means more than just publishing the API to a set of proprietary hosted services

* '''If we use data to enhance the online experience we should ensure that we're doing so in ways that promote and ''raise'' expectations for data protection, control and transparency practices on the Web as a whole''' ''[user experience, data protection, policies, control, transparency]''

** data being stored locally and on servers of companies that you interact with is valuable [and presently outside of your ability to view, edit or control]
** should be possible to combine data feeds from various public and/or proprietary sources and do something useful with them, e.g. visualizations, mashups, etc.
** data sharing could increase efficiency (e.g. not having to fill out forms with the same data on multiple web sites)
** we should lead the way in opening data and setting example
** open source tools & libraries for handling data could be created that set the example and make it easy for people to do the right thing, i.e. so companies and developers don't need to invest in development of infrastructure
** make it easier for people to do the right thing, right now it's easier to be less secure and with no data protection
** many countries laws protect their citizens
** legal coverage to protect people (e.g. outside the EU) is questionable
** what access does the US gov't have to user data for users outside of their jurisdiction?
** privacy policies could be standardized to be easier to read and understand
** all decisions (and rights) on your data should be revocable
** are there legal jurisdiction considerations in the location of any data that we collect?
** should be possible to combine data feeds from various public and/or proprietary sources and do something useful with them, e.g. visualizations, mashups, etc.
** there should be common formats and/or open standards to represent data and data policies

Project/2010 Goals/MozCampEU Discussions/Data

2008-10-28T17:00:18Z

Cbeard: /* Detailed Notes */

==MozCamp Europe Discussions==

===Summary===

* '''We should help people to better understand and have more control over the privacy of their various online activities & contexts'''

* '''We should provide leadership in the development, promotion and use of open standards for data representation & interoperability'''

* '''If we use data to enhance the online experience we should ensure that we're doing so in ways that promote and ''raise'' expectations for data protection, control and transparency practices on the Web as a whole'''

===Detailed Notes===

* '''We should help people to better understand and have more control over the privacy of various online activities & contexts''' ''[knowledge, visibility, selectivity, control]''

** users should be able to change their mind at any time about what they are sharing as situations change (e.g. companies change ownership)
** it should be clearer to users when there is data being collected about them, both explicitly (by submitting a form) and through use (by using a web site)
** should be possible [to clearly and visibly] differentiate between public and private spaces & activities
** flexibility and control to selectively share data
** data sharing could increase efficiency (e.g. not having to fill out forms with the same data on multiple web sites)
** how do you know if your activity online is public or private, e.g. the browser tells you now if the session is encrypted, could it also tell you how the data submitted from a form may be used
** ability to see the data that you're sharing with anyone
** all decisions (and rights) on your data should be revocable

* '''We should provide leadership in the development, promotion and use of open standards for data representation & interoperability''' ''[interoperability, standards, openness]''

** increasing prevalence of proprietary data formats, opportunities to enable adoption of open formats?
** lots of duplication of metadata (e.g. CD/DVD titles, etc.), opportunities to aggregate and consolidate into shared commons
** customer can't leverage own data
** blog comments are hard for people to keep track of
** we've solved some of the data privacy and interoperability problems before and new web services are reinventing components of these technologies but not adopting the practices and policies that were developed over years, i.e. data retention policies, access controls, interoperability, data portability, etc.
** should be possible to combine data feeds from various public and/or proprietary sources and do something useful with them, e.g. visualizations, mashups, etc.
** there should be common formats and/or open standards to represent data and data policies
** files and media in proprietary formats are at risk of being useless if and when companies that back them fail.
** should focus on developing and promoting open standards & interoperability
** should evangelize and protect against dangers inherent in RFC-based Internet communication and data interchange formats/protocols (e.g. IMAP, SMTP, NNTP, etc.) being replaced with proprietary Web technologies (e.g. Facebook, Twitter, etc.)
** should define "open"-ness for data & related services and ensure that it means more than just publishing the API to a set of proprietary hosted services

* '''If we use data to enhance the online experience we should ensure that we're doing so in ways that promote and ''raise'' expectations for data protection, control and transparency practices on the Web as a whole''' ''[user experience, data protection, policies, control, transparency]''

** data being stored locally and on servers of companies that you interact with is valuable [and presently outside of your ability to view, edit or control]
** should be possible to combine data feeds from various public and/or proprietary sources and do something useful with them, e.g. visualizations, mashups, etc.
** we should lead the way in opening data and setting example
** open source tools & libraries for handling data could be created that set the example and make it easy for people to do the right thing, i.e. so companies and developers don't need to invest in development of infrastructure
** make it easier for people to do the right thing, right now it's easier to be less secure and with no data protection
** many countries laws protect their citizens
** legal coverage to protect people (e.g. outside the EU) is questionable
** what access does the US gov't have to user data for users outside of their jurisdiction?
** privacy policies could be standardized to be easier to read and understand
** all decisions (and rights) on your data should be revocable
** are there legal jurisdiction considerations in the location of any data that we collect?
** should be possible to combine data feeds from various public and/or proprietary sources and do something useful with them, e.g. visualizations, mashups, etc.
** there should be common formats and/or open standards to represent data and data policies

Project/2010 Goals/MozCampEU Discussions/Data

2008-10-28T16:58:44Z

Cbeard:

==MozCamp Europe Discussions==

===Summary===

* '''We should help people to better understand and have more control over the privacy of their various online activities & contexts'''

* '''We should provide leadership in the development, promotion and use of open standards for data representation & interoperability'''

* '''If we use data to enhance the online experience we should ensure that we're doing so in ways that promote and ''raise'' expectations for data protection, control and transparency practices on the Web as a whole'''

===Detailed Notes===

* '''We should help people to better understand and have more control over the privacy of various online activities & contexts''' ''[knowledge, visibility, selectivity, control]''

** users should be able to change their mind at any time about what they are sharing as situations change (e.g. companies change ownership)
** it should be clearer to users when there is data being collected about them, both explicitly (by submitting a form) and through use (by using a web site)
** differentiated between public and private spaces & activities
** flexibility and control to selectively share data
** data sharing could increase efficiency (e.g. not having to fill out forms with the same data on multiple web sites)
** how do you know if your activity online is public or private, e.g. the browser tells you now if the session is encrypted, could it also tell you how the data submitted from a form may be used
** ability to see the data that you're sharing with anyone
** all decisions (and rights) on your data should be revocable

* '''We should provide leadership in the development, promotion and use of open standards for data representation & interoperability''' ''[interoperability, standards, openness]''

** increasing prevalence of proprietary data formats, opportunities to enable adoption of open formats?
** lots of duplication of metadata (e.g. CD/DVD titles, etc.), opportunities to aggregate and consolidate into shared commons
** customer can't leverage own data
** blog comments are hard for people to keep track of
** we've solved some of the data privacy and interoperability problems before and new web services are reinventing components of these technologies but not adopting the practices and policies that were developed over years, i.e. data retention policies, access controls, interoperability, data portability, etc.
** should be possible to combine data feeds from various public and/or proprietary sources and do something useful with them, e.g. visualizations, mashups, etc.
** there should be common formats and/or open standards to represent data and data policies
** files and media in proprietary formats are at risk of being useless if and when companies that back them fail.
** should focus on developing and promoting open standards & interoperability
** should evangelize and protect against dangers inherent in RFC-based Internet communication and data interchange formats/protocols (e.g. IMAP, SMTP, NNTP, etc.) being replaced with proprietary Web technologies (e.g. Facebook, Twitter, etc.)
** should define "open"-ness for data & related services and ensure that it means more than just publishing the API to a set of proprietary hosted services

* '''If we use data to enhance the online experience we should ensure that we're doing so in ways that promote and ''raise'' expectations for data protection, control and transparency practices on the Web as a whole''' ''[user experience, data protection, policies, control, transparency]''

** data being stored locally and on servers of companies that you interact with is valuable [and presently outside of your ability to view, edit or control]
** should be possible to combine data feeds from various public and/or proprietary sources and do something useful with them, e.g. visualizations, mashups, etc.
** we should lead the way in opening data and setting example
** open source tools & libraries for handling data could be created that set the example and make it easy for people to do the right thing, i.e. so companies and developers don't need to invest in development of infrastructure
** make it easier for people to do the right thing, right now it's easier to be less secure and with no data protection
** many countries laws protect their citizens
** legal coverage to protect people (e.g. outside the EU) is questionable
** what access does the US gov't have to user data for users outside of their jurisdiction?
** privacy policies could be standardized to be easier to read and understand
** all decisions (and rights) on your data should be revocable
** are there legal jurisdiction considerations in the location of any data that we collect?
** should be possible to combine data feeds from various public and/or proprietary sources and do something useful with them, e.g. visualizations, mashups, etc.
** there should be common formats and/or open standards to represent data and data policies

Project/2010 Goals/MozCampEU Discussions/Data

2008-10-28T16:51:44Z

Cbeard:

==MozCamp Europe Discussions==

===Summary===

* '''We should help people to better understand and have more control over the privacy of their various online activities & contexts''' ''[knowledge, visibility, selectivity, control]''

* '''We should provide leadership in the development, promotion and use of open standards for data representation & interoperability''' ''[interoperability, standards, openness]''

* '''If we use data to enhance the online experience we should ensure that we're doing so in ways that promote and ''raise'' expectations for data protection, control and transparency practices on the Web as a whole''' ''[user experience, data protection, policies, control, transparency]''

===Detailed Notes===

* '''We should help people to better understand and have more control over the privacy of various online activities & contexts'''
** users should be able to change their mind at any time about what they are sharing as situations change (e.g. companies change ownership)
** it should be clearer to users when there is data being collected about them, both explicitly (by submitting a form) and through use (by using a web site)
** differentiated between public and private spaces & activities
** flexibility and control to selectively share data
** data sharing could increase efficiency (e.g. not having to fill out forms with the same data on multiple web sites)
** how do you know if your activity online is public or private, e.g. the browser tells you now if the session is encrypted, could it also tell you how the data submitted from a form may be used
** ability to see the data that you're sharing with anyone
** all decisions (and rights) on your data should be revocable

* '''We should provide leadership in the development, promotion and use of open standards for data representation & interoperability'''
** increasing prevalence of proprietary data formats, opportunities to enable adoption of open formats?
** lots of duplication of metadata (e.g. CD/DVD titles, etc.), opportunities to aggregate and consolidate into shared commons
** customer can't leverage own data
** blog comments are hard for people to keep track of
** we've solved some of the data privacy and interoperability problems before and new web services are reinventing components of these technologies but not adopting the practices and policies that were developed over years, i.e. data retention policies, access controls, interoperability, data portability, etc.
** should be possible to combine data feeds from various public and/or proprietary sources and do something useful with them, e.g. visualizations, mashups, etc.
** there should be common formats and/or open standards to represent data and data policies
** files and media in proprietary formats are at risk of being useless if and when companies that back them fail.
** should focus on developing and promoting open standards & interoperability
** should evangelize and protect against dangers inherent in RFC-based Internet communication and data interchange formats/protocols (e.g. IMAP, SMTP, NNTP, etc.) being replaced with proprietary Web technologies (e.g. Facebook, Twitter, etc.)
** should define "open"-ness for data & related services and ensure that it means more than just publishing the API to a set of proprietary hosted services

* '''If we use data to enhance the online experience we should ensure that we're doing so in ways that promote and ''raise'' expectations for data protection, control and transparency practices on the Web as a whole'''
** data being stored locally and on servers of companies that you interact with is valuable [and presently outside of your ability to view, edit or control]
** should be possible to combine data feeds from various public and/or proprietary sources and do something useful with them, e.g. visualizations, mashups, etc.
** we should lead the way in opening data and setting example
** open source tools & libraries for handling data could be created that set the example and make it easy for people to do the right thing, i.e. so companies and developers don't need to invest in development of infrastructure
** make it easier for people to do the right thing, right now it's easier to be less secure and with no data protection
** many countries laws protect their citizens
** legal coverage to protect people (e.g. outside the EU) is questionable
** what access does the US gov't have to user data for users outside of their jurisdiction?
** privacy policies could be standardized to be easier to read and understand
** all decisions (and rights) on your data should be revocable
** are there legal jurisdiction considerations in the location of any data that we collect?
** should be possible to combine data feeds from various public and/or proprietary sources and do something useful with them, e.g. visualizations, mashups, etc.
** there should be common formats and/or open standards to represent data and data policies

Project/2010 Goals/MozCampEU Discussions/Data

2008-10-26T11:19:28Z

Cbeard: /* Detailed Notes */

==MozCamp Europe Discussions==

===Summary===

* x
* y
* z

===Detailed Notes===

* increasing prevalence of proprietary data formats, opportunities to enable adoption of open formats?
* lots of duplication of metadata (e.g. CD/DVD titles, etc.), opportunities to aggregate and consolidate into shared commons
* customer can't leverage own data
* blog comments are hard for people to keep track of
* data being stored locally and on servers of companies that you interact with is valuable
* users should be able to change their mind at any time about what they are sharing as situations change (e.g. companies change ownership)
* we've solved some of the data privacy and interoperability problems before (e.g. usenet, email, etc.) and new web technologies and reinventing components of these technologies but not adopting the practices and policies that were developed over years (e.g. data retention policies, access controls, interoperability, data portability, etc.)
* should be possible to combine data feeds from various public and/or proprietary sources and do something useful with them, e.g. visualizations, mashups, etc.
* there should be common formats and/or open standards to represent data and data policies
* files and media in proprietary formats are at risk of being useless if and when companies that back them fail.
* should focus on developing and promoting open standards & interopability
* it should be clearer to users when there is data being collected about them, both explicitly (by submitting a form) and through use (by using a web site)
* differentiated between public and private spaces & activities
* flexibility and control to selectively share data
* data sharing could increase efficiency (e.g. not having to fill out forms with the same data on multiple web sites)
* we should lead the way in opening data and setting example
* many countries laws protect their citizens
* legal coverage to protect people (e.g. outside the EU) is questionable
* what access does the US gov't have to user data for users outside of their jurisdiction?
* privacy policies could be standardized to be easier to read and understand
* open source tools & libraries for handling data could be created that set the example and make it easy for people to do the right thing, i.e. so companies and developers don't need to invest in development of infrastructure
* make it easier for people to do the right thing, right now it's easier to be less secure and with no data protection
* all decisions (and rights) on your data should be revocable
* are there legal jurisdiction considerations in the location of any data that we collect?
* how do you know if your activity online is public or private, e.g. the browser tells you now if the session is encrypted, could it also tell you how the data submitted from a form may be used
* ability to see the data that you're sharing with anyone

Project/2010 Goals/MozCampEU Discussions/Data

2008-10-26T11:17:51Z

Cbeard: /* Detailed Notes */

==MozCamp Europe Discussions==

===Summary===

* x
* y
* z

===Detailed Notes===

* increasing prevalence of proprietary data formats, opportunities to enable adoption of open formats?
* lots of duplication of metadata (e.g. CD/DVD titles, etc.), opportunities to aggregate and consolidate into shared commons
* customer can't leverage own data
* blog comments are hard for people to keep track of
* data being stored localled and on servers of companies that you interact with is valuable
* users should be able to change their mind at any time about what they are sharing as situations change (e.g. companies change ownership)
* we've solved some of the data privacy and interoperability problems before (e.g. usenet, email, etc.) and new web technologies and reinventing components of these technologies but not adopting the practices and policies that were developed over years (e.g. data retention policies, access controls, interoperability, data portability, etc.)
* should be possible to combine data feeds from various public and/or proprietary sources and do something useful with them, e.g. visualizations, mashups, etc.
* there should be common formats and/or open standards to represent data and data policies
* files and media in proprietary formats are at risk of being useless if and when companies that back them fail.
* should focus on developing and promoting open standards & interopability
* it should be clearer to users when there is data being collected about them, both explicitly (by submitting a form) and through use (by using a web site)
* differentiated between public and private spaces & activities
* flexibility and control to selectively share data
* data sharing could increase efficiency (e.g. not having to fill out forms with the same data on multiple web sites)
* we should lead the way in opening data and setting example
* many countries laws protect their citizens
* legal coverage to protect people (e.g. outside the EU) is questionable
* what access does the US gov't have to user data for users outside of their jurisdiction?
* privay policies could be standardized to be easier to read and understand
* open source tools & libraries for handling data could be created that set the example and make it easy for people to do the right thing, i.e. so companies and developers don't need to invest in development of infrastructure
* make it easier for people to do the right thing, right now it's easier to be less secure and with no data protection
* all decisions (and rights) on your data should be revocable
* are there legal jurisdiction considerations in the location of any data that we collect?
* how do you know if your activity online is public or private, e.g. the browser tells you now if the session is encrypted, could it also tell you how the data submitted from a form may be used
* ability to see the data that you're sharing with anyone

EU MozCamp 2008/Programme

2008-10-24T16:36:07Z

Cbeard: /* Saturday 25 October, 2008 */

==Saturday 25 October, 2008==

{| border=1 |
|-
{{EUCamp08HeaderRow}}
|-
{{EUCamp08FullRow
|time=9:00 - 10:00
|all=Welcome coffee
}}
|-
{{EUCamp08Row
|time=10:00 - 11:00
|Auditori=Welcome introduction - Tristan Nitot and John Lilly
|SalaA=
|SalaB=
|SalaC=
|Pods=
|Floor=
}}
|-
{{EUCamp08Row
|time=11:00 - 11:30
|Auditori= Keynote by Aza Raskin (Mozilla Labs)
|SalaA=
|SalaB=
|SalaC=
|Pods=
|Floor=
}}
|-
{{EUCamp08Row
|time=11:30 - 12:15
|Auditori=Keynote by David Ascher (Mozilla Messaging)
|SalaA=
|SalaB=
|SalaC=
|Pods=
|Floor=
}}
|-
{{EUCamp08Row
|time=12:15 - 13:00
|Auditori=Keynote by Christian Sejersen (Firefox Mobile)
|SalaA=
|SalaB=
|SalaC=
|Pods=
|Floor=
}}
|-
{{EUCamp08FullRow
|time=13:00 - 14:00
|all=Lunch
}}
|-
{{EUCamp08Row
|time=14:00 - 14:50
|Auditori=Introduction to Firefox (in Spanish)
|SalaA=[[EU_MozCamp_2008/Programme/Prism|Prism]]
|SalaB=[[EU_MozCamp_2008/Programme/L10n-drivers_Team_Presentation|L10n-drivers Team Presentation]]
|SalaC=[[EU_MozCamp_2008/Programme/Intro_MozQA|Introduction to Mozilla QA]]
|Pods=
|Floor=
}}
|-
{{EUCamp08Row
|time=15:00 - 15:50
|Auditori=Introduction to Thunderbird (in Spanish)
|SalaA=Thunderbird and Calendar
|SalaB=[[EU_MozCamp_2008/Programme/Testing|Testing session with Pike]]
|SalaC=[[EU_MozCamp_2008/Programme/Leak_Testing|Leak Testing Demo/Open source testing tools in practice]]
|Pods=
|Floor=
}}
|-
{{EUCamp08FullRow
|time=16:00 - 16:15
|all=Coffee break
}}
|-
{{EUCamp08Row
|time=16:15 - 17:05
|Auditori=
|SalaA=Thunderbird as a platform
|SalaB=[[EU_MozCamp_2008/Programme/QA_and_l10n_roundtable|QA and l10n roundtable]]
|SalaC=Automated Testing
|Pods=
|Floor=
}}
|-
{{EUCamp08Row
|time=17:15 - 18:05
|Auditori=
|SalaA=[http://labs.mozilla.com/2007/12/introducing-weave/ Weave]
|SalaB=[[EU_MozCamp_2008/Programme/Localizing_SUMO|Localizing SUMO]]
|SalaC=[[EU_MozCamp_2008/Programme/Embedding_Gecko|How to embed Gecko]]
|Pods=
|Floor=
}}
|-
{{EUCamp08Row
|time=18:15 - 19:05
|Auditori=
|SalaA=[http://labs.mozilla.com/2008/08/introducing-ubiquity/ Ubiquity]
|SalaB=[[EU_MozCamp_2008/Programme/Firefox_Extensions_and_Start-ups|Choosing Firefox as a platform for a Start-up]]
|SalaC=[[EU_MozCamp_2008/Programme/Silme|L10n toolkit - Silme demo/workshop]]
|Pods=
|Floor=
}}
|-
|}

==Sunday 26 October, 2008==

{| border=1 |
|-
{{EUCamp08HeaderRow}}
|-
{{EUCamp08FullRow
|time=9:00 - 10:00
|all=Welcome coffee
}}
|-
{{EUCamp08Row
|time=10:00 - 10:20
|Auditori=Keynote by Juantomas Garcia
|SalaA=
|SalaB=
|SalaC=
|Pods=
|Floor=
}}
|-
{{EUCamp08Row
|time=10:20 - 10:40
|Auditori= Keynote by Mike Connor (Firefox)
|SalaA=
|SalaB=
|SalaC=
|Pods=
|Floor=
}}
|-
{{EUCamp08Row
|time=10:40 - 11:30
|Auditori=[[Mozilla_2010_Goals_Discussion|Mozilla 2010 Goals Discussion]]
|SalaA=
|SalaB=
|SalaC=
|Pods=
|Floor=
}}
|-
{{EUCamp08Row
|time=11:30 - 12:30
|Auditori=
|SalaA=l10n tools : Babelzilla/mini-litmus/Glossary script/localizing extensions
|SalaB=Mobile Firefox UX
|SalaC=Ref Test/Mochitest
|Pods=
|Floor=
}}
|-
{{EUCamp08Row
|time=12:30 - 13:30
|Auditori=
|SalaA=Thunderbird User Experience
|SalaB=[[EU_MozCamp_2008/Programme/AMO_Overview|State of the Add-ons universe / AMO overview]]
|SalaC=Writing a minimized test case
|Pods=
|Floor=
}}
|-
{{EUCamp08FullRow
|time=13:30 - 14:30
|all=Lunch
}}
|-
{{EUCamp08Row
|time=14:30 - 15:00
|Auditori=Goals 2010 - Round-up
|SalaA=
|SalaB=
|SalaC=
|Pods=
|Floor=
}}
|-
{{EUCamp08Row
|time=15:00 - 15:45
|Auditori=
|SalaA=[[EU_MozCamp_2008/Programme/Fennec_Addons|Fennec Add-ons]]
|SalaB=[[EU_MozCamp_2008/Programme/Firebug_And_Chromebug|Development with Firebug and Chromebug]]
|SalaC=Community building / Mozilla Hispano / MozFR / Aviary / Mozilla.cat
|Pods=
|Floor=
}}
|-
{{EUCamp08Row
|time=15:45 - 16:30
|Auditori=
|SalaA=[[EU_MozCamp_2008/Programme/XULRunner|XUL Runner]]
|SalaB=
|SalaC=[[EU_MozCamp_2008/Programme/CommunityMarketing|Community Marketing Discussion: What should Mozilla do to help?]] (30 mins) [[EU_MozCamp_2008/Programme/StartCommunity|How to start a community website and develop it]] (30 mins)
|Pods=
|Floor=
}}
|-
{{EUCamp08Row
|time=16:30 - 17:15
|Auditori=
|SalaA=
|SalaB=XUL Dark Matter
|SalaC=Spanish locales roundtable
|Pods=
|Floor=
}}
|-
{{EUCamp08FullRow
|time=17:15 - 18:15
|all=Good bye coffee break
}}
|-
|}

WeeklyUpdates/2008-10-13

2008-10-13T20:08:07Z

Cbeard: /* Labs */

[[WeeklyUpdates/2008-10-06| « previous week]] | [[WeeklyUpdates|index]] | [[WeeklyUpdates/2008-10-20|next week »]]

'''Meeting Details'''
* 1:00pm Pacific time (20:00 UTC until November 2, 2008)
* Mozilla HQ, 1st floor conference table
* +1 650 903 0800 x91 Conf# 8600 (US/International)
* +1 416 848 3114 x91 Conf# 8600 (Canada)
* +1 800 707 2533 (pin 369) Conf# 8600 (US Toll Free)
* http://air.mozilla.com/ to watch and listen
* join irc.mozilla.org #staffmeeting for backchannel

'''note:''' all participants are muted automatically; if you want to talk, press *1 to un-mute yourself

'''WeeklyUpdate Live''': You can watch the weekly meetings live at [http://air.mozilla.com Air Mozilla] You can also view previous meetings from the "on-demand" button on the Air Mozilla player. Meetings will be posted for on-demand consumption shortly after the meeting conclusion.

= Friends of the Tree [[Image:Tree.gif|Friends of the Tree]] =

* Ted writes in, "I'd like to nominate Ben Hearsum for his hard work on reinventing release automation to work with Mercurial, and making the 3.1 beta 1 release happen."

* Seth joins Ted in nominating Ben. "I'd like to nominate Ben Hearsum for friends of the tree for re-spinning zh-CN by hand so the locale could participate in the FF 3.1 Beta 1 release."

Ben Hearsum, this weeks build/release hero and Fried of the Tree!!

Please send FotT nominations to [mailto:asa@mozilla.org asa@mozilla.org]. This is a great opportunity for the community to recognize those who go above and beyond, so please tell me when you see that happening. Thanks.

= Development Updates =

== Branch work: Firefox 2.0.0.18 / 3.0.4 ==
* Code freeze is October 24, a week from this Friday
* Please land any approved patches
* Please work on any blocking bugs
* Reminders will be sent quite often
* Now triaging approvals with [[User:Mconnor/SecurityUpdates|new criteria]]
* Intend on changing release scheduling per proposal

== Gecko 1.9.1 ==
* Cranking on Beta 2.
* Major items of interest this week:
** About to land nanojit2. Edwin Smith from Adobe is helping Graydon Hoare iron out issues so we can land their nanojit. A BIG thanks to Adobe for all their collaborative efforts here! For lots of technical details see [https://bugzilla.mozilla.org/show_bug.cgi?id=457786 the bug.]
*** Will get us closer to JIT'ing regex in the future.
*** Will enable more perf wins specifically related to tracing.
** mrbkap is working on [https://bugzilla.mozilla.org/show_bug.cgi?id=364315#c38 optimistic script loading]
*** For slow networks, this gives solid perf improvements with numbers being report as about a 19% win.
*** This is very important for mobile networks which are high-latency.
* For always interesting notes on new features and tech on platform, be sure to read the [http://developer.mozilla.org/web-tech/ Web Tech Blog]. Roc has a [http://developer.mozilla.org/web-tech/2008/10/13/mozafterpaint/ great post on MozAfterPaint], Boris [http://developer.mozilla.org/web-tech/2008/10/10/svg-external-document-references/ talks about SVG External Document References] which landed for the first beta.
* See freeze dates below in Firefox 3.1 section.
* [http://wiki.mozilla.org/Platform/1.9.1 Interesting queries related to Gecko 1.9.1]
* [http://tinyurl.com/3jsumu 80 1.9.1 blockers].
** [http://tinyurl.com/4ombdf 1 Blocking 1.9.1 P1s]
** [http://tinyurl.com/4lt8ah 37 Blocking 1.9.1 P2s]
** [http://tinyurl.com/5x59y5 35 Blocking 1.9.1 P3s]
** [http://tinyurl.com/47df5d 7 Blocking 1.9.1 Other priority] (Need to fix the priorities here!)
* [http://tinyurl.com/3uzqh6 284 wanted bugs (also up)] NOTE: Work on blockers, not wanted bugs, if you can!

== Firefox 3.1 ==
* Aiming for a beta 1 release this week (tomorrow if all goes well)

== TB 3 ==
* 3.0Alpha3 to release this week
* Hard at work on Beta 1 stuff

== Mobile ==

== IT ==
Last week's maintenance:
* More Netscaler OS upgrades
* kernel upgrades
* mailman upgrades (<tt>lists.mozilla.org</tt>)
* phone system upgrades in all Mozilla offices except Beijing
** will upgrade Beijing sometime this week (will coordinate with them on an outage time)
** major changes to the way extensions in Toronto are set up
** backend changes to the way calls are delivered between all of the offices
** If anyone runs into anything strange (things that used to work that don't anymore, etc) track down justdave or file a bug in Server Ops
** New user-visible features with this upgrade, mostly around conference rooms. Will be rolling that out sometime this week after we get the new config set up.
* Final MySQL 4 -> 5 migration

Upcoming Maintenance
* mailman upgrades (<tt>mail.mozilla.org, bugzilla.org, mozilla.org</tt>)
* Zimbra upgrade

== Release Engineering ==
* FF3.1b1 tomorrow
* Welcome Chris AtLee ("catlee" on irc)
* RelEng all in Toronto this week

== QA ==

Firefox 3.0.x
* tested a patch for Norton 360 issue
* Updated the [[QA/Topcrashes#Current_topcrashes_being_tracked_3.0.3|top crash report for 3.0.3]]. Contacted an extension developer which appears to be causing our #1 and #4 topcrashes. [ss]
* Completed 1.9.0.x blocking triage and half way through 1.9.0.x approval triage [ss]

Firefox 3.1
* The team is [[QA/Firefox3.1/TestPlan/Beta1|testing Beta1]]. Running smoke tests, BFTs, bug fix verifications, etc. Blocker found: {{bug|459156}} - :zhCN beta 1 builds show different search plugins per OS filed. A respin of zhCN only will be made on 3 platforms. Found [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=459082%2C+458968%2C+459399%2C+459111%2C+459157%2C+459256%2C+459406%2C+459282%2C+459289%2C+459108&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= 10 other new bugs].
* Feature testing:
** Worker Threads - Waiting for API to be solidified before adding more tests [adam]
** Acid3 - Started to write [[QA/Firefox3.1/Acid3|Test plan]] [tomcat]
** Got review comments on border radius patch [ctalbert]
** Got Review on CSS Transforms patch, need to address those comments [ctalbert]
** Completed analysis on XHR. See [[QA/Firefox3.1/XHR_TestPlan|test plan]] [ctalbert]
** Ran Private Browsing Tryserver builds [marcia]
** Added litmus test cases for location bar [stephend]
* Progressing with Global 500 TopSite Testing for leaks, assertions and crashed [tomcat]
* Litmus- Hand corrected 15 test cases. Worked with coop to fix {{bug|454248}}. That fixed 45 unclear test case!

Test Dev
* [[QA/TDAI/MozMillTestTool|MozMill]] (AKA GristMill):
** Beta 2 released on Oct 8th!
** Working on functionality for inspecting and building keypress automation, debugging some event listener problems with drop downs and local event listeners interfering with the inspector. [adam]
** Landed new framework code [mikeal]
* Generated i-Bench Benchmarks for Safari, FFx 3.1, FFx 3.0.3, IE 8 B2 [tomcat]

JavaScript Testing - Triaged bugs, reducing backlog of un-reviewed bugs from over 170, to approximately 90, with 30 bugs queued for test addition. Added tests to [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=418314%2C+421621%2C+432075%2C+435497%2C+450176%2C+450199%2C+450529%2C+451580%2C+451588%2C+451787%2C+451806%2C+452476%2C+452563%2C+453024%2C+453462%2C+454682%2C+455413%2C+455605%2C+455691%2C+455748%2C+455757%2C+455775%2C+455982%2C+456370%2C+456477%2C+456540%2C+456826%2C+457351%2C+457456%2C+457580%2C+457778%2C+457795%2C+457824%2C+458076%2C+458959%2C+459077%2C+459085%2C+459185%2C+459186%2C+459233&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= 40 bugs].[bc]

Localization - Worked with SethB, choffman to improve our strategy for connecting with localization testers and maximize the L10n testing discussions at the EU Camp at the end of October. [marcia, tomcat, tchung, timr]

Mobile - Worked on mobile mochitests. Ran into hurdle with tests restarting device, or not launching xpcshell/fennec.

WebDev testing:
* AMO- Worked on [https://wiki.mozilla.org/Update:Remora_Meeting_Notepad 4.0.2], which code-freezes tonight and ships on Oct. 16.
** Verified [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Server+Software&product=addons.mozilla.org&target_milestone=4.0.2&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=VERIFIED&resolution=FIXED&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-10-05&chfieldto=2008-10-12&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=bug_status&type0-0-0=changedby&value0-0-0=stephen.donner%40gmail.com 6 bugs]
** Worked with Wil Clouser on a test plan for revising our [https://bugzilla.mozilla.org/show_bug.cgi?id=435129 Add to Firefox detection mechanism].
* SUMO- Verified [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Other&product=support.mozilla.com&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=VERIFIED&resolution=FIXED&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-10-05&chfieldto=2008-10-12&chfield=bug_status&chfieldvalue=Verified&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=bug_status&type0-0-0=changedby&value0-0-0=stephen.donner%40gmail.com 7 bugs]. Graph Server- Verified [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Webtools&component=Graph+Server&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=VERIFIED&resolution=FIXED&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-10-05&chfieldto=2008-10-12&chfield=bug_status&chfieldvalue=Verified&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=bug_status&type0-0-0=changedby&value0-0-0=stephen.donner%40gmail.com 2 bugs]
* Spread Firefox- Rewrote the Selenium BFT to accommodate the changes to the [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Server+Software&product=addons.mozilla.org&target_milestone=4.0.2&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=VERIFIED&resolution=FIXED&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-10-05&chfieldto=2008-10-12&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=bug_status&type0-0-0=changedby&value0-0-0=stephen.donner%40gmail.com Affiliates] page

== Security ==
*No update

== Marketing/PR ==

'''PR'''
* Mobile
** [http://www.networkworld.com/news/2008/100908-firefox-mobile.html NWW interview with Jay]
** [http://arstechnica.com/journals/linux.ars/2008/10/11/mozillas-fennec-browser-ported-to-windows-mobile Screenshots of Windows Mobile]
* Labs
** [http://tech.blorge.com/Structure:%20/2008/10/09/mozilla-firefox-goes-local-with-new-geode-location-plugin/ Geode]
** [http://ajaxian.com/archives/ajaxians-join-mozilla-creating-developer-tools&ct=ga&cd=oWsBc4wA8mg&usg=AFQjCNHkOeFwoRQi9x-09SiZKCBK5iPwSQ Developer Tools Lab]
* [http://blog.mozilla.com/news/ Above the Fold up and running]

'''Events'''

Europe:
* [http://www.jdll.org/ JDLL], Lyon, France, Oct 17 - 18: Tristan and the Mozilla FR community to attend.
* [http://www.opensourceworldconference.com/oswc/presenta Open Source World Conference, Malaga, Spain, Oct. 20 - 21: Tristan keynoting.
* [http://en.oreilly.com/webexberlin2008/ Web 2.0 Berlin], Oct 21 - 23: John Lilly is keynoting.
* Moz Camp, Barcelona, Spain, Oct. 25 - 26
* Mozilla Labs EU Innovation Tour: Aza Raskin & Dan Mills will be in Europe from Oct 20-26 for both press meetings and labs meetups.
* Internet CEE Conference, Warsaw, Poland Oct 28: Seth Bindernagel will hold a session on the Importance of Localization in Open Source

U.S. and more:

* ICMC/USP Computer Science Week, Oct. 13, San Carlos, Brazil: Remote presentation for students at San Carlos University today at 3:30.
* [http://legionoftech.org/blog/?p=34 WhereCamp PDX], Oct. 17 - 19, Portland, OR - Dietrich Ayala demo'ing Geode.
* [http://fsoss.senecac.on.ca/2008/ FSOSS], Oct. 24 - 24, Seneca College, Toronto - Several Mozilla speakers!
* [http://www.aspirationtech.org/events/devsummit08 Nonprofit Software Development Summit], Nov. 17 - 19, Oakland, CA: Please check it out if you are local!
* [http://www.greenfestivals.org/ Green Festival], San Francisco, Nov. 14 - 16: Mozilla will have passes for 200 people. Please let Mary or Julie know if you want to attend.
* [http://www.fosscamp.org/ FOSSCamp], Mountain View, Dec. 5 - 6: Organized by Ubuntu folks. Please check it out if you are local!

'''Impact Mozilla'''
* since launch: 80,000 unique visitors to [http://impactmozilla.com impactmozilla.com]
* discussion forum: 90 members have joined
* submissions: approx. 100 emails received
* Please help us spread the word among student groups and marketing professionals... initial deadline is two weeks away!

== Support ==
* Time for a new Support Firefox Day!
** Friday, November 21st
** Focus will be on localization, so the event will be split up into more than one time slot to allow people to participate around the globe.
** More info about the event to follow shortly.

== Metrics ==

== Evangelism ==
* Mozilla Developer Center
** [http://developer.mozilla.org/En/CSS/Using_CSS_transforms CSS transforms] documentation is now complete.
** [http://developer.mozilla.org/En/CSS/Media_queries CSS media queries] documentation is now complete.
** The [http://developer.mozilla.org/En/HTML/Element/Audio HTML 5 <code>audio</code> element] is now documented.
** The [http://developer.mozilla.org/En/HTML/Element/Video HTML 5 <code>video</code> element] is now documented.
** [http://developer.mozilla.org/En/Using_geolocation Geolocation] is now documented.
** The [http://developer.mozilla.org/en/Gecko-Specific_DOM_Events#MozAfterPaint <code>MozAfterPaint</code>] event is now documented.
** Documentation of worker threads has been pushed back to beta 2, since we're still working on matching the spec.
** Planning to deploy the Deki 8.08.1 update this Thursday, which picks up a few bug fixes and a couple of security improvements.
** Continuing to engage with MindTouch on plans for the next major release of Deki, which is shaping up to have a lot of big wins for MDC. We're a major factor in their design process for this release, once again. MindTouch is very eager to make us happy. See [http://wiki.developer.mindtouch.com/MindToucH_Deki/Release/Lyons "Lyons" release's roadmap] for details.

* 3.1b1 updates:
** [https://wiki.mozilla.org/Firefox3.1/Messaging#Beta_1 Beta 1 outline]
** devnews blog post with overview of developer features underway
** Please add comments if you have any

== Labs ==
* [http://labs.mozilla.com/2008/10/introducing-geode/ Geode] was released!
* Myk conducted [http://www.melez.com/mykzilla/2008/10/easier-access-to-sidebars.html experiment in easier access to sidebars in Firefox] and would like feedback

* welcoming dion almaer & ben galbraith to mozilla full-time to lead a new [http://labs.mozilla.com/2008/10/developer-tools-and-the-open-web/ developer tools lab]

* Dan and Aza will be visiting Europe next week, more detailed schedule with events coming soon. Rough schedule:
** Sunday 19 - Monday 20: London
** Tuesday 21 - Thursday 23: Berlin
** Friday 24 - Sunday 26: Barcelona

== Webdev, Add-ons, AMO ==
* AMO 4.0.2 [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=addons.mozilla.org&target_milestone=4.0.2&long_desc_type=allwordssubstr&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=---&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&known_name=AMO-3.5&query_based_on=AMO-4.0.2&field0-0-0=noop&type0-0-0=noop&value0-0-0= open bugs] & [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=addons.mozilla.org&target_milestone=4.0.2&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&resolution=FIXED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&known_name=AMO4.0.2&query_based_on=AMO4.0.2-fixed&field0-0-0=noop&type0-0-0=noop&value0-0-0= fixed bugs] -- Code freeze Monday night, midnight
* Lars Lohn and Frank Griswold are in the final stages of re-engineering the Socorro filesystem -- [http://blog.mozilla.com/webdev/2008/10/10/socorros-file-system-storage/ read Lars' post about it] or the [http://code.google.com/p/socorro/wiki/SocorroFileSystem SocorroFileSystem wiki page]
* Austin King [https://bugzilla.mozilla.org/show_bug.cgi?id=426389 posted a patch] for the Socorro topcrashers cron job (woot)
* Les Orchard worked on an activity feed for all '''public''' Mozilla activity -- looking at fleshing this out over the next few weeks, but [http://people.mozilla.org/~lorchard/lizardfeeder/ here is a demo of his work]
* [http://article.gmane.org/gmane.comp.misc.translate.pootle/1844 pootle 1.2.0] and [http://micropipes.com/blog/2008/10/08/verbatim-alpha-release/ verbatim alpha] released
* SUMO release schedule for the rest of 2008 [https://wiki.mozilla.org/Support/SUMOdev_Meeting_Notepad#October_9_2008], 0.7.1 in progress with freeze Thursday.

== L10n ==
* L10n-drivers is working to create a testing strategy for the localization community. We are working on long-term testing that will carry over from release to release as well as developing release-specific testing plans. Mail [mailto:sethb@mozilla.com sethb] to learn more.

* L10n-drivers, l10n community and Mozilla marketing are creating and will slowly begin rolling out localized FF3 landing pages for 37 locales with the aim of fostering community and the visibility of all of FF3 language tools. Mail [mailto:lmesa@mozilla.com Laura Mesa] or [mailto:sethb@mozilla.com sethb] to learn more.

* Firefox 3.1 beta 2, working on remaining locales to participate. We are shooting for a fully localized build.

= Foundation Updates =

=== Highlights ===

* Mark was in Mountain View for the Mozilla Foundation board meeting and various other meetings with Foundation and Corporation folks, including discussions on Foundation plans and budgets for 2008Q4 and 2009, possible new Foundation initiatives, Foundation/Corporation interactions, the Mozilla Store, and other topics.
* The Mozilla Foundation is making a $5K grant to the [http://www.tug.org/ TeX Users Group] to support the [http://www.openfontlibrary.org/ Open Font Library] initiative to make high-quality free fonts available for use with the [http://www.css3.info/preview/web-fonts-with-font-face/ @font-face font downloading feature] implemented in Firefox 3.1 (bug [https://bugzilla.mozilla.org/show_bug.cgi?id=70132 70132]) and other browsers.

=== Program activities ===

* Education
** Zak worked to research who is doing what in open source education, to help in planning and making decisions about our own program efforts.
* Grants
** [http://www.paciellogroup.com/ The Paciello Group] is making good progress on their Foundation-funded project to develop a Firefox/Mozilla accessibility reporting panel and ARIA QA extension. [http://juicystudio.com/index.php Gez Lemon] of TPG has produced a set of blog posts describing use of [https://addons.mozilla.org/en-US/firefox/addon/9108 the extension] for examining WAI ARIA [http://juicystudio.com/article/examining-wai-aria-live-regions.php live regions], [http://juicystudio.com/article/examining-wai-aria-document-andmark-roles.php document landmark roles], [http://juicystudio.com/article/examining-wai-aria-roles.php roles], and [http://juicystudio.com/article/examining-wai-aria-properties.php properties].
* CAs
** [http://groups.google.com/group/mozilla.dev.tech.crypto/browse_thread/thread/416427a350db11a9/ Public discussion] of the CA inclusion request from [http://www.mozilla.org/projects/security/certs/pending/#Microsec Microsec Ltd] is ongoing, but Frank wasn't able to do the preliminary decision on schedule, so now will need to push the overall CA schedule out.
** Frank worked with Kathleen Wilson to get her CVS access so that she can update the [http://www.mozilla.org/projects/security/certs/pending/ CA pending list] herself.

=== Public communications and community outreach ===

* Powered by Mozilla
** David worked on the "Powered by Mozilla" design guidelines page with John Slater and Tara, and worked on a Bugzilla template for "Powered by Mozilla" logo requests
* www.mozilla.org
** David continued with archiving, redirect and bug triage work, posted new [http://www.mozilla.org/projects/technologies.html Mozilla Technologies] and [http://www.mozilla.org/projects/specifications.html Mozilla Specifications] pages, and archived the [http://www-archive.mozilla.org/projects/list.html old Projects page].

=== Upcoming activities ===

* Gerv will be representing the Mozilla Foundation at the mySociety fifth birthday event (October 14, London).
* Mark and Frank will attend and participate in the [http://fsoss.senecac.on.ca/ FSOSS 2008 conference] at Seneca College (October 23-24, Toronto).
* Mark will attend [https://wiki.mozilla.org/EU_MozCamp_2008 EU Mozilla Camp] (October 25-26, Barcelona).
* We have a Mozilla Foundation staff retreat planned for late October (October 28-30, Mountain View).
* Zak will deliver the opening keynote for the [http://afup.org AFUP] (French PHP User Group) [http://afup.org/pages/forumphp2008/sessions.php Forum PHP conference] (December 8, Paris)

= Roundtable =

= Other Business =

WeeklyUpdates/2008-10-13

2008-10-13T19:33:28Z

Cbeard: /* Mozilla Labs */

[[WeeklyUpdates/2008-10-06| « previous week]] | [[WeeklyUpdates|index]] | [[WeeklyUpdates/2008-10-20|next week »]]

'''Meeting Details'''
* 1:00pm Pacific time (20:00 UTC until November 2, 2008)
* Mozilla HQ, 1st floor conference table
* +1 650 903 0800 x91 Conf# 8600 (US/International)
* +1 416 848 3114 x91 Conf# 8600 (Canada)
* +1 800 707 2533 (pin 369) Conf# 8600 (US Toll Free)
* http://air.mozilla.com/ to watch and listen
* join irc.mozilla.org #staffmeeting for backchannel

'''note:''' all participants are muted automatically; if you want to talk, press *1 to un-mute yourself

'''WeeklyUpdate Live''': You can watch the weekly meetings live at [http://air.mozilla.com Air Mozilla] You can also view previous meetings from the "on-demand" button on the Air Mozilla player. Meetings will be posted for on-demand consumption shortly after the meeting conclusion.

= Friends of the Tree [[Image:Tree.gif|Friends of the Tree]] =

* Ted writes in, "I'd like to nominate Ben Hearsum for his hard work on reinventing release automation to work with Mercurial, and making the 3.1 beta 1 release happen."

* Seth joins Ted in nominating Ben. "I'd like to nominate Ben Hearsum for friends of the tree for re-spinning zh-CN by hand so the locale could participate in the FF 3.1 Beta 1 release."

Ben Hearsum, this weeks build/release hero and Fried of the Tree!!

Please send FotT nominations to [mailto:asa@mozilla.org asa@mozilla.org]. This is a great opportunity for the community to recognize those who go above and beyond, so please tell me when you see that happening. Thanks.

= Development Updates =

== Branch work: Firefox 2.0.0.18 / 3.0.4 ==
* Code freeze is October 24, a week from this Friday
* Please land any approved patches
* Please work on any blocking bugs
* Reminders will be sent quite often
* Now triaging approvals with [[User:Mconnor/SecurityUpdates|new criteria]]
* Intend on changing release scheduling per proposal

== Gecko 1.9.1 ==
* Cranking on Beta 2.
* Major items of interest this week:
** About to land nanojit2. Edwin Smith from Adobe is helping Graydon Hoare iron out issues so we can land their nanojit. A BIG thanks to Adobe for all their collaborative efforts here! For lots of technical details see [https://bugzilla.mozilla.org/show_bug.cgi?id=457786 the bug.]
*** Will get us closer to JIT'ing regex in the future.
*** Will enable more perf wins specifically related to tracing.
** mrbkap is working on [https://bugzilla.mozilla.org/show_bug.cgi?id=364315#c38 optimistic script loading]
*** For slow networks, this gives solid perf improvements with numbers being report as about a 19% win.
*** This is very important for mobile networks which are high-latency.
* For always interesting notes on new features and tech on platform, be sure to read the [http://developer.mozilla.org/web-tech/ Web Tech Blog]. Roc has a [http://developer.mozilla.org/web-tech/2008/10/13/mozafterpaint/ great post on MozAfterPaint], Boris [http://developer.mozilla.org/web-tech/2008/10/10/svg-external-document-references/ talks about SVG External Document References] which landed for the first beta.
* See freeze dates below in Firefox 3.1 section.
* [http://wiki.mozilla.org/Platform/1.9.1 Interesting queries related to Gecko 1.9.1]
* [http://tinyurl.com/3jsumu 80 1.9.1 blockers].
** [http://tinyurl.com/4ombdf 1 Blocking 1.9.1 P1s]
** [http://tinyurl.com/4lt8ah 37 Blocking 1.9.1 P2s]
** [http://tinyurl.com/5x59y5 35 Blocking 1.9.1 P3s]
** [http://tinyurl.com/47df5d 7 Blocking 1.9.1 Other priority] (Need to fix the priorities here!)
* [http://tinyurl.com/3uzqh6 284 wanted bugs (also up)] NOTE: Work on blockers, not wanted bugs, if you can!

== Firefox 3.1 ==
* Aiming for a beta 1 release this week (tomorrow if all goes well)

== TB 3 ==
* 3.0Alpha3 to release this week
* Hard at work on Beta 1 stuff

== Mobile ==

== IT ==
Last week's maintenance:
* More Netscaler OS upgrades
* kernel upgrades
* mailman upgrades (<tt>lists.mozilla.org</tt>)
* phone system upgrades in all Mozilla offices except Beijing
** will upgrade Beijing sometime this week (will coordinate with them on an outage time)
** major changes to the way extensions in Toronto are set up
** backend changes to the way calls are delivered between all of the offices
** If anyone runs into anything strange (things that used to work that don't anymore, etc) track down justdave or file a bug in Server Ops
** New user-visible features with this upgrade, mostly around conference rooms. Will be rolling that out sometime this week after we get the new config set up.
* Final MySQL 4 -> 5 migration (Tuesday), will affect:

Upcoming Maintenance
* mailman upgrades (<tt>mail.mozilla.org</tt>)
* Zimbra upgrade

== Release Engineering ==

== QA ==

Firefox 3.0.x
* tested a patch for Norton 360 issue

Firefox 3.1
* The team is [[QA/Firefox3.1/TestPlan/Beta1|testing Beta1]]. Running smoke tests, BFTs, bug fix verifications, etc. Found [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=459082%2C+458968%2C+459399%2C+459111%2C+459157%2C+459256%2C+459406%2C+459282%2C+459289%2C+459108&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= 10 new bugs].
* Feature testing:
** Worker Threads - Waiting for API to be solidified before adding more tests [adam]
** Started to write [[QA/Firefox3.1/Acid3|Test plan]] [tomcat]
** Got review comments on border radius patch [ctalbert]
** Got Review on CSS Transforms patch, need to address those comments [ctalbert]
** Completed analysis on XHR. See [[QA/Firefox3.1/XHR_TestPlan|test plan]] [ctalbert]
** Ran Private Browsing Tryserver builds [marcia]
* Progressing with Global 500 TopSite Testing for leaks, assertions and crashed [tomcat]

Test Dev
* [[QA/TDAI/MozMillTestTool|MozMill]] (AKA GristMill): Beta 2 released. Working on functionality for inspecting and building keypress automation, debugging some event listener problems with drop downs and local event listeners interfering with the inspector. [adam]
* Generated i-Bench Benchmarks for Safari, FFx 3.1, FFx 3.0.3, IE 8 B2 [tomcat]

JavaScript Testing - Triaged bugs, reducing backlog of un-reviewed bugs from over 170, to approximately 90, with 30 bugs queued for test addition. Added tests to [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=418314%2C+421621%2C+432075%2C+435497%2C+450176%2C+450199%2C+450529%2C+451580%2C+451588%2C+451787%2C+451806%2C+452476%2C+452563%2C+453024%2C+453462%2C+454682%2C+455413%2C+455605%2C+455691%2C+455748%2C+455757%2C+455775%2C+455982%2C+456370%2C+456477%2C+456540%2C+456826%2C+457351%2C+457456%2C+457580%2C+457778%2C+457795%2C+457824%2C+458076%2C+458959%2C+459077%2C+459085%2C+459185%2C+459186%2C+459233&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= 40 bugs].[bc]

Localization - Worked with SethB, choffman to improve our strategy for connecting with localization testers and maximize the L10n testing discussions at the EU Camp at the end of October. [marcia, tomcat, tchung, timr]

Mobil -

== Security ==

== Marketing/PR ==

'''PR'''
* Mobile
** [http://www.networkworld.com/news/2008/100908-firefox-mobile.html NWW interview with Jay]
** [http://arstechnica.com/journals/linux.ars/2008/10/11/mozillas-fennec-browser-ported-to-windows-mobile Screenshots of Windows Mobile]
* Labs
** [http://tech.blorge.com/Structure:%20/2008/10/09/mozilla-firefox-goes-local-with-new-geode-location-plugin/ Geode]
** Developer Tools Lab
* [http://blog.mozilla.com/news/ Above the Fold up and running]

'''Events'''

Europe:
* [http://www.jdll.org/ JDLL], Lyon, France, Oct 17 - 18: Tristan and the Mozilla FR community to attend.
* [http://www.opensourceworldconference.com/oswc/presenta Open Source World Conference, Malaga, Spain, Oct. 20 - 21: Tristan keynoting.
* [http://en.oreilly.com/webexberlin2008/ Web 2.0 Berlin], Oct 21 - 23: John Lilly is keynoting.
* Moz Camp, Barcelona, Spain, Oct. 25 - 26
* Mozilla Labs EU Innovation Tour: Aza Raskin & Dan Mills will be in Europe from Oct 20-26 for both press meetings and labs meetups.
* Internet CEE Conference, Warsaw, Poland Oct 28: Seth Bindernagel will hold a session on the Importance of Localization in Open Source

U.S. and more:

* ICMC/USP Computer Science Week, Oct. 13, San Carlos, Brazil: Remote presentation for students at San Carlos University today at 3:30.
* [http://legionoftech.org/blog/?p=34 WhereCamp PDX], Oct. 17 - 19, Portland, OR - Dietrich Ayala demo'ing Geode.
* [http://fsoss.senecac.on.ca/2008/ FSOSS], Oct. 24 - 24, Seneca College, Toronto - Several Mozilla speakers!
* [http://www.aspirationtech.org/events/devsummit08 Nonprofit Software Development Summit], Nov. 17 - 19, Oakland, CA: Please check it out if you are local!
* [http://www.greenfestivals.org/ Green Festival], San Francisco, Nov. 14 - 16: Mozilla will have passes for 200 people. Please let Mary or Julie know if you want to attend.
* [http://www.fosscamp.org/ FOSSCamp], Mountain View, Dec. 5 - 6: Organized by Ubuntu folks. Please check it out if you are local!

'''Impact Mozilla'''
* since launch: 80,000 unique visitors to [http://impactmozilla.com impactmozilla.com]
* discussion forum: 90 members have joined
* submissions: approx. 100 emails received
* Please help us spread the word among student groups and marketing professionals... initial deadline is two weeks away!

== Support ==
* Time for a new Support Firefox Day!
** Friday, November 21st
** Focus will be on localization, so the event will be split up into more than one time slot to allow people to participate around the globe.
** More info about the event to follow shortly.

== Metrics ==

== Evangelism ==
* Mozilla Developer Center
** [http://developer.mozilla.org/En/CSS/Using_CSS_transforms CSS transforms] documentation is now complete.
** [http://developer.mozilla.org/En/CSS/Media_queries CSS media queries] documentation is now complete.
** The [http://developer.mozilla.org/En/HTML/Element/Audio HTML 5 <code>audio</code> element] is now documented.
** The [http://developer.mozilla.org/En/HTML/Element/Video HTML 5 <code>video</code> element] is now documented.
** [http://developer.mozilla.org/En/Using_geolocation Geolocation] is now documented.
** The [http://developer.mozilla.org/en/Gecko-Specific_DOM_Events#MozAfterPaint <code>MozAfterPaint</code>] event is now documented.
** Documentation of worker threads has been pushed back to beta 2, since we're still working on matching the spec.
** Planning to deploy the Deki 8.08.1 update this Thursday, which picks up a few bug fixes and a couple of security improvements.
** Continuing to engage with MindTouch on plans for the next major release of Deki, which is shaping up to have a lot of big wins for MDC. We're a major factor in their design process for this release, once again. MindTouch is very eager to make us happy. See [http://wiki.developer.mindtouch.com/MindToucH_Deki/Release/Lyons "Lyons" release's roadmap] for details.

== Labs ==
* welcoming dion almaer & ben galbraith to mozilla full-time to lead a new [http://labs.mozilla.com/2008/10/developer-tools-and-the-open-web/ developer tools lab]

== Webdev, Add-ons, AMO ==
* AMO 4.0.2 [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=addons.mozilla.org&target_milestone=4.0.2&long_desc_type=allwordssubstr&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=---&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&known_name=AMO-3.5&query_based_on=AMO-4.0.2&field0-0-0=noop&type0-0-0=noop&value0-0-0= open bugs] & [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=addons.mozilla.org&target_milestone=4.0.2&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&resolution=FIXED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&known_name=AMO4.0.2&query_based_on=AMO4.0.2-fixed&field0-0-0=noop&type0-0-0=noop&value0-0-0= fixed bugs] -- Code freeze Monday night, midnight
* Lars Lohn and Frank Griswold are in the final stages of re-engineering the Socorro filesystem -- [http://blog.mozilla.com/webdev/2008/10/10/socorros-file-system-storage/ read Lars' post about it] or the [http://code.google.com/p/socorro/wiki/SocorroFileSystem SocorroFileSystem wiki page]
* Austin King [https://bugzilla.mozilla.org/show_bug.cgi?id=426389 posted a patch] for the Socorro topcrashers cron job (woot)
* Les Orchard worked on an activity feed for all '''public''' Mozilla activity -- looking at fleshing this out over the next few weeks, but [http://people.mozilla.org/~lorchard/lizardfeeder/ here is a demo of his work]
* [http://article.gmane.org/gmane.comp.misc.translate.pootle/1844 pootle 1.2.0] and [http://micropipes.com/blog/2008/10/08/verbatim-alpha-release/ verbatim alpha] released
* SUMO release schedule for the rest of 2008 [https://wiki.mozilla.org/Support/SUMOdev_Meeting_Notepad#October_9_2008], 0.7.1 in progress with freeze Thursday.

== L10n ==

= Foundation Updates =

=== Highlights ===

* Mark was in Mountain View for the Mozilla Foundation board meeting and various other meetings with Foundation and Corporation folks, including discussions on Foundation plans and budgets for 2008Q4 and 2009, possible new Foundation initiatives, Foundation/Corporation interactions, the Mozilla Store, and other topics.
* The Mozilla Foundation is making a $5K grant to the [http://www.tug.org/ TeX Users Group] to support the [http://www.openfontlibrary.org/ Open Font Library] initiative to make high-quality free fonts available for use with the [http://www.css3.info/preview/web-fonts-with-font-face/ @font-face font downloading feature] implemented in Firefox 3.1 (bug [https://bugzilla.mozilla.org/show_bug.cgi?id=70132 70132]) and other browsers.

=== Program activities ===

* Education
** Zak worked to research who is doing what in open source education, to help in planning and making decisions about our own program efforts.
* Grants
** [http://www.paciellogroup.com/ The Paciello Group] is making good progress on their Foundation-funded project to develop a Firefox/Mozilla accessibility reporting panel and ARIA QA extension. [http://juicystudio.com/index.php Gez Lemon] of TPG has produced a set of blog posts describing use of [https://addons.mozilla.org/en-US/firefox/addon/9108 the extension] for examining WAI ARIA [http://juicystudio.com/article/examining-wai-aria-live-regions.php live regions], [http://juicystudio.com/article/examining-wai-aria-document-andmark-roles.php document landmark roles], [http://juicystudio.com/article/examining-wai-aria-roles.php roles], and [http://juicystudio.com/article/examining-wai-aria-properties.php properties].
* CAs
** [http://groups.google.com/group/mozilla.dev.tech.crypto/browse_thread/thread/416427a350db11a9/ Public discussion] of the CA inclusion request from [http://www.mozilla.org/projects/security/certs/pending/#Microsec Microsec Ltd] is ongoing, but Frank wasn't able to do the preliminary decision on schedule, so now will need to push the overall CA schedule out.
** Frank worked with Kathleen Wilson to get her CVS access so that she can update the [http://www.mozilla.org/projects/security/certs/pending/ CA pending list] herself.

=== Public communications and community outreach ===

* Powered by Mozilla
** David worked on the "Powered by Mozilla" design guidelines page with John Slater and Tara, and worked on a Bugzilla template for "Powered by Mozilla" logo requests
* www.mozilla.org
** David continued with archiving, redirect and bug triage work, posted new [http://www.mozilla.org/projects/technologies.html Mozilla Technologies] and [http://www.mozilla.org/projects/specifications.html Mozilla Specifications] pages, and archived the [http://www-archive.mozilla.org/projects/list.html old Projects page].

=== Upcoming activities ===

* Gerv will be representing the Mozilla Foundation at the mySociety fifth birthday event (October 14, London).
* Mark and Frank will attend and participate in the [http://fsoss.senecac.on.ca/ FSOSS 2008 conference] at Seneca College (October 23-24, Toronto).
* Mark will attend [https://wiki.mozilla.org/EU_MozCamp_2008 EU Mozilla Camp] (October 25-26, Barcelona).
* We have a Mozilla Foundation staff retreat planned for late October (October 28-30, Mountain View).
* Zak will deliver the opening keynote for the [http://afup.org AFUP] (French PHP User Group) [http://afup.org/pages/forumphp2008/sessions.php Forum PHP conference] (December 8, Paris)

= Roundtable =

= Other Business =

Labs/Ubiquity/Commands In The Wild

2008-08-19T14:52:04Z

Cbeard:

Back to [[Labs/Ubiquity]].

'''LEGAL NOTICE: Mozilla is providing links to these third-party Ubiquity commands as a courtesy, and makes no representations regarding the commands or any information related there to. Any questions, complaints or claims regarding the commands must be directed to the appropriate developer or software vendor.'''

= Commands in the Wild =

Bookmark any of the following pages, and tag it with "ubiquity" to add its functionality to your command pool.

== There Be Dragons Here ==
Pioneering can be crazy fun, but also a bit dangerous. The commands referenced here have not been reviewed by Mozilla. They may contain malicious code, so use them only at your own risk. Until Ubiquity becomes more mature, we recommend only adding commands that come from people you trust, or if you've read the code and know that they are safe.

== Commands ==
Atul's personal commands.

[http://labs.toolness.com/commands/commands.js commands.js]

[http://foyrek.com/ubi.html Abi's commands]

== Quotebb.js ==
Quote text for BB-style forums.

[http://www.gialloporpora.netsons.org/ubiquity/quotebb.js Quotebb.js]

== Quotehtml.js ==
Quotes HTML entities in your selection.

[http://www.gialloporpora.netsons.org/ubiquity/quotehtml.js quotehtml.js]

== Gmail.js ==
Opens Gmail in a new tab, as well as showing you the last couple of new messages in the preivew.

[http://ubiquity-firefox.googlegroups.com/web/ubiquity_gmail.js?gda=gHCQx0IAAAD_mC6ocghADlnwgKtOZarHy0pz4L1zdfNBZQ-WVQEtDWG1qiJ7UbTIup-M2XPURDThhrjtatuGnhW3da2gcLyrMQ4HhOIVlic7wv2V2HiqYg Gmail.s]

== Twitter.js ==
Let's you Twitter from anywhere. This command has been moved into Ubiquity core.

[http://theunfocused.net/moz/ubiquity/verbs/twitter.js Twitter.js]]

== Identi.ca ==
Another micro-blogging service like Twitter/Pounce/etc., but open source

Essentially identical code to Twitter+Ubiquity above, except for renaming of constants and web addresses

[http://ubiquity-firefox.googlegroups.com/web/identica%20(2).js?gda=4oc_PEkAAACqaO7Aax4IB5JX_WYSl8iOrBnsuQS45ejhBtvVuEfs-xpD7Q4I70bg7A2QUTeiVCyg9p4rhRQ_Rj874eUFNZ-HhAioEG5q2hncZWbpWmJ7IQ identica(2).js]

== Digg This ==

[http://www.gialloporpora.netsons.org/ubiquity/diggthis.js DiggThis.js]

This command open Digg to vote a story. When you have found an interesting article, you can execute this command. Possible effect:
* if the page are already submitted to digg, in preview panel are shown the diggs that it have received. Pressing ENTER you are redirected to the digg story page to vote;
* if page is not submitted to digg, in preview panel are shown some useful data to help you to submit story. When you press ENTER, you are redirected to the submit page.

[[Image:http://i250.photobucket.com/albums/gg274/gialloporpora/digg2.png]]

[[Image:http://i250.photobucket.com/albums/gg274/gialloporpora/digg.png]]

== tolower.js ==
Converts your selection to lower case.

[http://www.gialloporpora.netsons.org/ubiquity/tolower.js tolower.js]

== Bitly.js ==

Shorten URL using bit.ly service: http://bit.ly/18Fsn2

== nofollow.js ==
Preview counts no-follow links and execute highlights them.

Install Page:http://surfmind.com/lab/mozilla/ubiquity/nofollow.html
Script: http://surfmind.com/lab/mozilla/ubiquity/nofollow.js
Preview: http://flickr.com/photos/andyed/2767130077/in/photostream/

Summit2008/Sessions/Proposals/Labs Concept Browsers

2008-08-05T06:47:33Z

Cbeard:

__NOTOC__
__NOTOC__
=Mozilla Labs Concept Series & Open Design Initiative=

See: [http://labs.mozilla.com/2008/08/introducing-the-concept-series-call-for-participation/ http://labs.mozilla.com/2008/08/introducing-the-concept-series-call-for-participation/]

Summit2008/Sessions/Proposals/Labs Concept Browsers

2008-07-25T22:08:18Z

Cbeard:

__NOTOC__
__NOTOC__
=Mozilla Labs Concept Series & Open Design Initiative=

Led by [http://cbeard.typepad.com Chris Beard], [http://azarask.in/blog Aza Raskin] & [http://www.jjg.net Jesse James Garrett]

==Overview==
In this session we'll present a brief overview of the Open Design Initiative, and specifically the Concept Series that is being launched as part of it.

The bulk of the session will be allocated to a case study and discussion with Jesse James Garrett, the co-founder of an experience strategy & design firm that has volunteered its time as part of the Open Design Initiative to produce one of the first concept videos.

==Open Design Initiative==
The Open Design Initiative is a [http://labs.mozilla.com Mozilla Labs] outreach program to engage wide participation in exploring and prototyping future directions for the Web.

Mozilla has fostered the growth of a large and active community of highly technical contributors. A significant part of this initiative will revolve around engaging and creating a focal point for non-technical design expertise.

Specific focus will be on engaging and recruiting designers as individuals and from industry and [http://en.wikipedia.org/wiki/Higher_education higher education] to take part in a collaborative open design process.

==Concept Series==
The Concept Series is a project to grow community around the surfacing of new ideas and concepts through pictures, sketches or videos as part of the Open Design Initiative.

==Aurora==
Aurora is the code name for one of the first community efforts to produce a video use case exploration showing one possible future user experience for the Web produced as part of the Concept Series. It is being developed by Jesse James Garrett and his team at [http://www.adaptivepath.com Adaptive Path], an experience strategy & design firm based in San Francisco.

Summit2008/Sessions/Schedule

2008-07-25T22:07:38Z

Cbeard: /* Wednesday */

__TOC__

== Scheduling Guidelines ==
* '''Emerald''' and '''Callaghan''' follow a fixed schedule for technical and non-technical "Mozilla in 2010 and Beyond" tracks (some spots have intentionally been left empty to allow more participants to attend the session in the larger room)
* '''Glacier''' room is reserved for Mozilla Messaging topics
* The schedule for '''Alpine C, D & E''' has been set with effort taken to avoid conflicts
* As much unscheduled space as possible in '''Alta''' and '''Crystal''' has been left to allow for sessions to be moved and scheduled as required during the week

Participants and session leaders should feel free to reschedule or add new sessions during the Summit for any space with a white background. Spaces with grey backgrounds should '''not be altered''' without consulting Dan Portillo.

{|border=1 padding=2|
|-
|width="50px|
|session slot may be scheduled or moved by session leaders
|-
|bgcolor="#CCCCCC" width="50px"|
|session slot may '''not''' be scheduled or moved without asking dan, beltzner, or mconnor
|-
|}

== Monday ==
* 6:00pm - 9:00pm Welcome Reception (casual dress)

== Tuesday ==
{| border=1 |
|-
{{SummitHeaderRow}}
|-
{{SummitFullRow
|time=8-9:30
|all=Breakfast
}}
|-
{{SummitFullRow
|time=10-12
|all=Welcome Introduction -- Baker & Lilly
}}
|-
{{SummitFullRow
|time=12:00-1:00
|all=Lunch
}}
|-
{{SummitRow
|time=1:00 - 2:00
|emerald=[[Summit2008/Sessions/Proposals/History_&_Future:_Imagining_the_Web_Browser_of_2015|History & Future: Imagining the web browser of 2015 ]]
|callaghan=
|alpineC=[[Summit2008/Sessions/Proposals/Tracing_and_JavaScript_performance|Tracing and JavaScript performance]]
|alpineD=
|alpineE=Reserved for Jesse
|glacier=
|alta=
|crystal=
}}
{{SummitRow
|time=2:15-3:15
|emerald=[[Summit2008/Sessions/Proposals/1.9.1_Progress_&_Updates|1.9.1 Progress & Updates]]
|callaghan=[[Summit2008/Sessions/Proposals/PR_Case_Studies|Open Source PR: Sharing the Story ]]
|alpineC=[[Summit2008/Sessions/Proposals/New_and_Improved_MDC|New and Improved MDC]]
|alpineD=[[Summit2008/Sessions/Proposals/Localizing_Firefox_3|Localizing Firefox 3]]
|alpineE=[[Summit2008/Sessions/Proposals/Mobile:_Device_APIs|Mobile: Device APIs]]
|glacier=[[Summit2008/Sessions/Proposals/Thunderbird_3|Thunderbird 3]]
|alta=
|crystal=
}}
{{SummitRow
|time=3:30-4:30
|emerald=[[Summit2008/Sessions/Proposals/Web_Standards_&_Strategy|Web Standards & Strategy]]
|callaghan=[[Summit2008/Sessions/Proposals/Mozilla_Foundation_2.0|Mozilla Foundation 2.0]]
|alpineC=[[Summit2008/Sessions/Proposals/QA_Tools: Litmus/Hendrix|Mozilla QA & Tools we use]]
|alpineD=L10N: [[Summit2008/Sessions/Proposals/L10n_with_Verbatim|Verbatim]] & [[Summit2008/Sessions/Proposals/Moz2po|Moz2po]]
|alpineE=[[Summit2008/Sessions/Proposals/Add-on_Manager|Add-ons Management]]
|glacier=[[Summit2008/Sessions/Proposals/Calendar_Integration|Calendar integration & futures]]
|alta=[[Summit2008/Sessions/Proposals/Graphics_Roadmap_Planning|Graphics Roadmap Planning]]
|crystal=[[Summit2008/Sessions/Proposals/State_of_Spread_Firefox|State of Spreadfirefox.com]]
}}
{{SummitRow
|time=4:45-5:45
|emerald=[[Summit2008/Sessions/Proposals/Firefox_3_Post-Mortem|Firefox 3 Post-Mortem]]
|callaghan=
|alpineC=
|alpineD=[[Summit2008/Sessions/Proposals/Problems_people_find_using_Firefox_and_how_to_solve_them|Problems people find using Firefox and how to solve them]]
|alpineE=
|glacier=[[Summit2008/Sessions/Proposals/QA_for_Thunderbird|QA for Thunderbird, Calendar, Seamonkey]]
|alta=
|crystal=
}}
|-
{{SummitFullRow
|time=7:30-10pm
|all=Dine Around, restaurants will be chosen at the hospitality desk. (Casual Dress)
}}
|}

== Wednesday ==
{| border=1 |
|-
{{SummitHeaderRow}}
|-
{{SummitFullRow
|time=8-9:30
|all=Breakfast
}}
|-
{{SummitFullRow
|time=10-12
|all=[[Summit2008/Sessions/Proposals/Product_and_Technology_Roadmap|Products & Technology Roadmap (Firefox, Engineering Operations, Mobile & Labs)]]
}}
|-
{{SummitFullRow
|time=12:00-1:00
|all=Lunch
}}
|-
{{SummitRow
|time=1:00 - 2:00pm
|emerald=Lightning Talks
|callaghan=[[Summit2008/Sessions/Proposals/PR_Training_Presentation|Media Training I (Presentation)]]
|alpineC=[[Summit2008/Sessions/Proposals/Mozdev_%26_the_Wider_Dev_Community|Mozdev & the Wider Dev Community]]
|alpineD=
|alpineE=
|glacier=[[Summit2008/Sessions/Proposals/UX_for_Thunderbird|UX for Thunderbird]]
|alta=
|crystal=
}}
{{SummitRow
|time=2:15 - 3:15pm
|emerald=[[Summit2008/Sessions/Proposals/Fennec|Fennec]]
|callaghan=[[Summit2008/Sessions/Proposals/Open_Source_Marketing_in_Europe|Mozilla in Europe - lessons in open source, community & culture]]
|alpineC=[[Summit2008/Sessions/Proposals/XPCOMGC|XPCOMGC]]
|alpineD=[[Summit2008/Sessions/Proposals/Why_I_didn't_write_a_test|Why I didn't write a Test]]
|alpineE=[[Summit2008/Sessions/Proposals/Malware_Trends|Security Topics: Malware Trends]]
|glacier=[[Summit2008/Sessions/Proposals/Radical_Ideas_for_Spreading_T-Bird|Radical Ideas for Spreading T-Bird]]
|alta=[[Summit2008/Sessions/Proposals/PR_Training_Presentation|Media Training II (Mock Interviews)]]
|crystal=
}}
{{SummitRow
|time=3:30 - 4:30pm
|emerald=[[Summit2008/Sessions/Proposals/Labs_Concept_Browsers|Mozilla Labs Concept Series]]
|callaghan=Firefox 3 in [[Summit2008/Sessions/Proposals/Firefox_3_in_China|China]] & [[Summit2008/Sessions/Proposals/Firefox_3_in_Japan|Japan]]
|alpineC=[[Summit2008/Sessions/Proposals/Mobile/Embedding|Embedding]]
|alpineD=[[Summit2008/Sessions/Proposals/L10N_Build_Process|L10N Build Process]]
|alpineE=[[Summit2008/Sessions/Proposals/Writing_Secure_Software_&_Basic_Hacking Techniques|Security Topics: Writing Secure Software]]
|glacier=
|alta=[[Summit2008/Sessions/Proposals/PR_Training_Presentation|Media Training II (Mock Interviews)]]
|crystal=
}}
{{SummitRow
|time=4:45 - 5:45pm
|emerald=[[Summit2008/Sessions/Proposals/Mozilla_Identity|Mozilla Project Identity]]
|callaghan=[[Summit2008/Sessions/Proposals/Open_Source_Marketing|Open Source Marketing]]
|alpineC=[[Summit2008/Sessions/Proposals/Snowl: Messaging in the Browser|Snowl: Messaging in the Browser]]
|alpineD=[[Summit2008/Sessions/Proposals/L10N_for_Mobile|L10N for Mobile]]
|alpineE=[[Summit2008/Sessions/Proposals/Platform/WebPerformanceTools|Performance & Memory Tools]]
|glacier=
|alta=[[Summit2008/Sessions/Proposals/PR_Training_Presentation|Media Training II (Mock Interviews)]]
|crystal=
}}
|-
{{SummitFullRow
|time=6:00-6:30pm
|all=[[Summit2008/Sessions/Proposals/LightofFirefox|Light of Firefox]]
}}
|-
{{SummitFullRow
|time=7:30-10pm
|all=Open evening, vouchers available for dining at the Westin.
}}
|}

== Thursday ==
{| border=1 |
|-
{{SummitHeaderRow}}
|-
{{SummitFullRow
|time=8-9:30
|all=Breakfast
}}
|-
{{SummitRow
|time=9:30 - 10:30am
|emerald=[[Summit2008/Sessions/Proposals/Weave|Weave]]
|callaghan=Data I: [[Summit2008/Sessions/Proposals/Data_Needed_to_Improve_Contributions|What's Needed to Improve Contributions]] & [[Summit2008/Sessions/Proposals/Collecting_&_Using_Data|Collecting & Using Data]]
|alpineC=[[Summit2008/Sessions/Proposals/D-Trace|D-Trace]]
|alpineD=[[Summit2008/Sessions/Proposals/Mozilla_Design_Process|Mozilla Design Process]]
|alpineE=[[Summit2008/Sessions/Proposals/Firefox_in_India|Firefox in India]]
|glacier=
|alta=[[Summit2008/Sessions/Proposals/Working_Better_With_Linux_Distros|Firefox & Linux Distros]]
|crystal=
}}
|-
{{SummitRow
|time=10:45 - 11:45am
|emerald=[[Summit2008/Sessions/Proposals/Ubiquity|Ubiquity]]
|callaghan=Data II: [[Summit2008/Sessions/Proposals/Data:_What_Should_we_be_Asking?|What Should we be Asking?]]
|alpineC=[[Summit2008/Sessions/Proposals/XUL_Runner|XUL Runner]]
|alpineD=[[Summit2008/Sessions/Proposals/Intern Wrap-Up & Brainstorming|Intern Wrap-Up & Brainstorming]]
|alpineE=[[Summit2008/Sessions/Proposals/Issues_Facing_Small_Translation_Teams|Issues Facing Small Translation Teams]]
|glacier=[[Summit2008/Sessions/Proposals/Messaging_Futures|Messaging Futures]]
|alta=
|crystal=
}}
|-
{{SummitFullRow
|time=12:00-1:00
|all=Lunch
}}
|-
{{SummitRow
|time=1:00 - 2:00pm
|emerald=Lightning Talks
|callaghan=
|alpineC=
|alpineD=
|alpineE=
|glacier=
|alta=
|crystal=
}}
{{SummitRow
|time=2:15 - 3:15pm
|emerald=[[Summit2008/Sessions/Proposals/AMO_Roadmap|AMO: Roadmap & Directions]]
|callaghan=[[Summit2008/Sessions/Proposals/Mobile_UX|Mobile UX]]
|alpineC=[[Summit2008/Sessions/Proposals/Guerrilla_Marketing|Guerrilla Marketing]]
|alpineD=[[Summit2008/Sessions/Proposals/RelEng_infra|RelEng infrastructure on hg]]
|alpineE=[[Summit2008/Sessions/Proposals/Mozilla.org_Site|Mozilla.org Site]]
|glacier=
|alta=[[Summit2008/Sessions/Proposals/CodeImprovement|Priorities For Code Cleanup And Improvement]]
|crystal=
}}
{{SummitRow
|time=3:30 - 4:30pm
|emerald=[[Summit2008/Sessions/Proposals/Using_Mercurial|Using Mercurial]]
|callaghan=[[Summit2008/Sessions/Proposals/Community_Development|L10n Community Development]]
|alpineC=[[Summit2008/Sessions/Proposals/Firebug_&_Chrome|Firebug & Chromebug]]
|alpineD=[[Summit2008/Sessions/Proposals/Automating_Firefox_UI_Testing|Automating Firefox UI Testing]]
|alpineE=[[Summit2008/Sessions/Proposals/Moving_the_SVG_implementation_Forward|Moving the SVG Implementation Forward]]
|glacier=[[Summit2008/Sessions/Proposals/Comm_Extension_Points|Thunderbird/Calendar Extension Points]]
|alta=
|crystal=
}}
{{SummitRow
|time=4:45 - 5:45pm
|emerald=
|callaghan=[[Summit2008/Sessions/Proposals/Rich_Media_on_Web|Rich Media on Web]]
|alpineC=[[Summit2008/Sessions/Proposals/AMO:_Editorial_Process|AMO: Editorial Process]]
|alpineD=[[Summit2008/Sessions/Proposals/Static_Analysis|Static Analysis]]
|alpineE=[[Summit2008/Sessions/Proposals/Growth_in_Asia|Growth in Asia]]
|glacier=Hacking session based on above topic
|alta=
|crystal=
}}
|-
{{SummitFullRow
|time=6:30-11pm
|all=Dinner at the Roundhouse. (Casual Dress)
}}
|}

== Friday ==
* Brunch will be served
* Buses will shuttle people to Vancouver International Airport
** '''please arrange your shuttle time at the hotel amenities desk before Friday'''

== To be Scheduled ==
Lightning Talks?
* [[Summit2008/Sessions/Proposals/Design_Demos|Design Demos]]
* [[Summit2008/Sessions/Proposals/RelEng_branching_releases|repeat of brownbag explaining branching and releases]]
* [[Summit2008/Sessions/Proposals/What_Are_People_Doing_With_Browsers%3F|What Are People Doing With Browsers]]
* Lightning talk: Tips and tricks for searching Bugzilla (Jesse Ruderman)
* How to stop guessing what the community thinks—the Community Surveys project [sethb, stas]
* XPConnect Wrappers http://developer.mozilla.org/en/docs/XPConnect_wrappers

Unscheduled / Need Definition:
* [[Summit2008/Sessions/Proposals/Firefox_Branding|Firefox Branding]]
* [[Summit2008/Sessions/Proposals/Automated_Tests_in_Release|Automated Tests in Release]]

Summit2008/Sessions/Proposals/Weave

2008-07-23T20:50:53Z

Cbeard: /* Overview */

=Weave=

Led by Chris Beard and Dan Mills
__NOTOC__
==Overview==
In this session we'll provide a detailed status update on the Weave project along with demos of upcoming capabilities, information on new APIs and discussion on where we're heading.

==Background==
As the Web continues to evolve and more of our lives move online, we believe that Web browsers like Firefox can and should do more to broker rich experiences while increasing user control over their data and personal information.

One important area for exploration is the blending of the desktop and the Web through deeper integration of the browser with online services.

Launched in December, Weave is the project within Mozilla Labs to formally explore this integration.

Just like Mozilla enables massive innovation by making Firefox open on many levels, we will aim to do the same with Weave by developing an open extensible framework for services integration.

==Project Update==

==Roadmap==

==Demos==

==APIs==

Summit2008/Sessions/Proposals/Labs Concept Browsers

2008-07-22T21:17:38Z

Cbeard: /* Aurora */

__NOTOC__
__NOTOC__
=Open Design Initiative: Concept Series =

Led by [http://cbeard.typepad.com Chris Beard], [http://azarask.in/blog Aza Raskin] & [http://www.jjg.net Jesse James Garrett]

==Overview==
In this session we'll present a brief overview of the Open Design Initiative, and specifically the Concept Series that is being launched as part of it.

The bulk of the session will be allocated to a case study and discussion with Jesse James Garrett, the co-founder of an experience strategy & design firm that has volunteered its time as part of the Open Design Initiative to produce one of the first concept videos.

==Open Design Initiative==
The Open Design Initiative is a [http://labs.mozilla.com Mozilla Labs] outreach program to engage wide participation in exploring and prototyping future directions for the Web.

Mozilla has fostered the growth of a large and active community of highly technical contributors. A significant part of this initiative will revolve around engaging and creating a focal point for non-technical design expertise.

Specific focus will be on engaging and recruiting designers as individuals and from industry and [http://en.wikipedia.org/wiki/Higher_education higher education] to take part in a collaborative open design process.

==Concept Series==
The Concept Series is a project to grow community around the surfacing of new ideas and concepts through pictures, sketches or videos as part of the Open Design Initiative.

==Aurora==
Aurora is the code name for one of the first community efforts to produce a video use case exploration showing one possible future user experience for the Web produced as part of the Concept Series. It is being developed by Jesse James Garrett and his team at [http://www.adaptivepath.com Adaptive Path], an experience strategy & design firm based in San Francisco.