Received: by 10.68.201.168 with SMTP id kb8mr234171pbc.3.1335989562197;
        Wed, 02 May 2012 13:12:42 -0700 (PDT)
Path: r9ni124644pbh.0!nntp.google.com!news2.google.com!news1.google.com!Xl.tags.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local2.nntp.dca.giganews.com!nntp.mozilla.org!news.mozilla.org.POSTED!not-for-mail
NNTP-Posting-Date: Wed, 02 May 2012 15:12:41 -0500
Return-Path: <j...@mozilla.com>
X-Original-To: dev-plann...@lists.mozilla.org
Delivered-To: dev-plann...@lists.mozilla.org
X-Virus-Scanned: amavisd-new at mozilla.org
Received-SPF: none (mozilla.com: No applicable sender policy available)
	receiver=notorious.mozilla.org; identity=mailfrom;
	envelope-from="j...@mozilla.com"; helo=dm-mail03.mozilla.org;
	client-ip=10.2.74.48
Subject: Re: Kilimanjaro Product Draft Feedback/Questions
From: JP Rosevear <j...@mozilla.com>
To: Ben Adida <benad...@mozilla.com>
In-Reply-To: <TLqdna2vApd1kz3SnZ2dnUVZ_oSdnZ2d@mozilla.org>
References: <mailman.24560.1335832409.31724.dev-planning@lists.mozilla.org>
	<TLqdna2vApd1kz3SnZ2dnUVZ_oSdnZ2d@mozilla.org>
Organization: Mozilla
Date: Wed, 02 May 2012 14:29:25 -0400
Mime-Version: 1.0
X-Mailer: Evolution 2.32.1
Cc: dev-plann...@lists.mozilla.org
X-BeenThere: dev-plann...@lists.mozilla.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Planning for future releases <dev-planning.lists.mozilla.org>
List-Unsubscribe: <https://lists.mozilla.org/options/dev-planning>,
	<mailto:dev-planning-requ...@lists.mozilla.org?subject=unsubscribe>
List-Post: <mailto:dev-plann...@lists.mozilla.org>
List-Help: <mailto:dev-planning-requ...@lists.mozilla.org?subject=help>
List-Subscribe: <https://lists.mozilla.org/listinfo/dev-planning>,
	<mailto:dev-planning-requ...@lists.mozilla.org?subject=subscribe>
Newsgroups: mozilla.dev.planning
Message-ID: <mailman.24931.1335989561.31724.dev-planning@lists.mozilla.org>
Lines: 49
X-Usenet-Provider: http://www.giganews.com
NNTP-Posting-Host: 63.245.208.166
X-AuthenticatedUsername: NoAuthUser
X-Trace: sv3-qz4mhOCDCiK/OL/rtSPRgc0/EPEIOU8MsVDk4p27RuwBVDLqki0h+ZwWpEMRkvNxSKuT1RXT32TTc8/!CvcFUh1IneN903RhNPylvMKR/I0QSD+Nwt3Ye1PQhHblS/3AkF+IN4Ln8vuvyNhAh4Pqu+sWI+lK!MlQMloS8j1Zsqry8EZEnsD8ZRJ5ozpe77g97
X-Complaints-To: ab...@mozilla.org
X-DMCA-Complaints-To: ab...@mozilla.org
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 4142
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit

On Tue, 2012-05-01 at 09:27 -0700, Ben Adida wrote:
> On 4/30/12 5:33 PM, JP Rosevear wrote:
> > I'm surprised that the "table stakes" for this is only contacts and
> > apps.  I understand that we have a working sync solution for
> > desktop/fennec for the P2 items, but what about bookmarks, passwords,
> > etc on B2G?
> 
> Let's see if I can channel Dan for a second.
> 
> <pm impersonation>
> 
> Most initial users of B2G will use the phone as their primary computing 
> device and will not have another FF instance to sync with. So what 
> counts is a backup service for contacts (which are super annoying if 
> lost) and apps (which the user paid for.) The rest is, *initially*, less 
> important, given the expected user profile.
> 
> I'm only making a relative prioritization statement, not an absolute 
> one. I know there are ongoing discussions right now regarding the 
> absolute prioritization of contacts & apps, and I don't mean to imply 
> anything about that discussion.
> 
> </pm impersonation>

Ok, that is a reasonable position to take for prioritization.

> > 2) DOM bindings for Sign In
> >
> > Surprised this is P3, it is unclear to me how we will do Persona on B2G
> > in this case other than for a browser app.
> 
> It's technically very possible for Persona to work using the existing 
> shim as long as B2G supports window.open (which it probably should 
> support for other reasons, e.g. Facebook Connect, OAuth dialogs, etc.) 
> To get an idea of what that looks like, see Persona's iOS support: it 
> works and looks quite nice.

The B2G browser may support window.open, but what about the core OS
itself? (Think Accounts on Android)  It seems weird to hit a server
there.

Thanks,


-JP
-- 
JP Rosevear <j...@mozilla.com>
Mozilla