• Time: Tuesday at 9:15 AM PST / 12:15 PM EST / 5:15 PM UTC.
• Place: Mozilla HQ, North Bridge
• Phone (US/Intl): 650 903 0800 x92 Conf: 8616#
• Phone (Toronto): 416 848 3114 x92 Conf: 8616#
• Phone (US): 800 707 2533 (pin 369) Conf: 8616#

Contents 1 Ops 1.1 Loadtest 2 Engineering 2.1 Account Registration/Management 2.1.1 Python Registration Server (reg/sreg) (Tarek) 2.1.2 Account Portal (Toby) 2.1.3 Node Assignment (Toby) 2.2 Sync 2.2.1 Python Sync Server (Tarek) 2.2.2 PHP Sync Server (Toby) 2.2.3 Sync Client (philikon/rnewman) 2.3 Identity 2.3.1 Server (JR) 2.3.2 Client (ddahl) 2.4 System Management 2.4.1 Big Lebowski (rtilder) 2.5 Notifications 2.5.1 Engineering (Paul/JR) 3 QA 3.1 Testing and Sign-offs (tracy) 3.2 Automated Testing (jgriffin, ocoutts) 3.2.1 Grinder Scripts (ocoutts) 4 Deployment Requests 5 Metrics 5.1 Reports and Monitoring (daniel) 6 Product 6.1 Sync 6.1.1 Firefox 6 6.1.2 Beyond 7 Security 8 Marketing 9 Roundtable 9.1 Notes and actions 9.2 Follow ups from last week 9.3 Other issues

Who's away?: .

Ops

• jv is on jury duty and may be super-laggy or completely afk.

Loadtest

• It's testing load. Have hit and fixed various bottlenecks. Found a tough one yesterday. See the email thread for more info.

Engineering

Account Registration/Management

Python Registration Server (reg/sreg) (Tarek)

• Auth Refactoring in progress w/ Toby
• Intermediate LDAP edits being made to smooth transition (see train below)

Account Portal (Toby)

Node Assignment (Toby)

Sync

Python Sync Server (Tarek)

• Waiting for load test infra

PHP Sync Server (Toby)

Sync Client (philikon/rnewman)

Changes this week:

• bug 661972
• bug 662253
• bug 650941
• bug 662181
• bug 658675
• bug 662178
• bug 610832
• bug 661587
• bug 664046

Assorted future work spinning along. mconnor might have divined the cause of our HMAC woes: go mconnor!

Identity

Server (JR)

Done:

• Finished up bulk of server core rebuild
• Code review for ID server (via rmiller)
• First run at ID Engineering plan

Doing:

• Integration with client code
• Divide and clean up the Engineering plan (sep. into 3 elements)
• I see those coordination and scheduling bugs, I be filin'.

Not Sure Why, But Kinda Needs To Be Done Anyway:

• Writing up a simple python sync server install recipe page.

Client (ddahl)

System Management

Big Lebowski (rtilder)

Notifications

Engineering (Paul/JR)

Paul:

• Got a jetpack enabled client running against push1 (can now distribute a stable, mini-client for experimentation)
• Start work on some back-end issues with RabbitMQ memory management and other issues (finally)

& JR:

• meeting with mobile folks re: fennec integration issues and concerns.

QA

Testing and Sign-offs (tracy)

• no client or server train last week.
• sign off for this weeks client due this afternoon
• updated Sync test plan with descriptions of various test levels
• ID test plan in progress

Automated Testing (jgriffin, ocoutts)

Grinder Scripts (ocoutts)

• Have worked with petef to setup testing environment running on infrastructure in pheonix.
• Running some of the existing tests and refactoring
• Plan to start adding new tests this week.

Deployment Requests

Server-Core: Fix for email headers and transitional ldap syncNode write (detailed in bug 664175)

Metrics

Reports and Monitoring (daniel)

Product

Sync

Firefox 6

• Sync Discovery looking good

Beyond

• Sync Brown Bag - Wednesday 12 PM PST
• Blog posts going out on various Sync topics
• EOL of Sync Add-on by end of quarter
• Executing on the road map ....

Security

Marketing

SYNC

• SEO: bug 658884
• Website improvements to design and copy
• Promo banners with Firefox 5: bug 659513, bug 661625
  

The Numbers:

• Mobile ADUs: 121,972 (27,105 x 4.5) (-.01%) (3% of total Sync accounts, 28% of active mobile users)
• Desktop ADUs: 958,447 (-2%) (28% of total Sync accounts)
  

Roundtable

Notes and actions

Follow ups from last week

Other issues

• What is the timeline for the beta environement? (tchung)
  • Oh, found it, Phase 1. "Target is to be able to launch in early July. The initial service deployed to Beta is expected to be Identity. "