User:Mconnor/Past/Weave1H2010

	THIS PAGE IS A WORKING DRAFT
	The page may be difficult to navigate, and some information on its subject might be incomplete and/or evolving rapidly. If you have any questions or ideas, please add them as a new topic on the discussion page.

Key Points

Weave Sync is generally independent in implementation, and uses stable(ish) APIs where we touch app data
Weave Sync (and subsequent Weave components) will be a standalone optional module with app-provided UI
Code reorganization is a key first step to getting to inclusion
There is a lot of work on testing and code cleanup that make landing on trunk premature
Server scaling is, as of yet, unsolved, so timeline for core inclusion is not something we can lock down

Development will proceed in add-on space
Code stabilization and re-organization to clean front-end/back-end splits will happen starting now
Integration points with apps to be determined with the app UX leads driving direction
Additional data types rolled out over multiple releases (add-ons, search engines, tab sync rewrite)
Work on scaling solution in conjunction with user growth, and can determine from there whether uplift is viable in Firefox for desktop PCs