Return-Path: X-Original-To: apmail-cordova-dev-archive@www.apache.org Delivered-To: apmail-cordova-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B37F9F30D for ; Mon, 13 May 2013 14:33:16 +0000 (UTC) Received: (qmail 38413 invoked by uid 500); 13 May 2013 14:33:13 -0000 Delivered-To: apmail-cordova-dev-archive@cordova.apache.org Received: (qmail 38379 invoked by uid 500); 13 May 2013 14:33:13 -0000 Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cordova.apache.org Delivered-To: mailing list dev@cordova.apache.org Received: (qmail 38365 invoked by uid 99); 13 May 2013 14:33:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 May 2013 14:33:13 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW X-Spam-Check-By: apache.org Received-SPF: error (nike.apache.org: local policy) Received: from [209.85.216.174] (HELO mail-qc0-f174.google.com) (209.85.216.174) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 May 2013 14:33:06 +0000 Received: by mail-qc0-f174.google.com with SMTP id m16so3354651qcq.19 for ; Mon, 13 May 2013 07:32:25 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type:x-gm-message-state; bh=31w6I7LnnZRqLDiBqYIxjuTUgjILpTjhWjX7ewNBbPo=; b=dxJadlYSck9XjlRHTMhBlWdk9y57d6QA2jP8qMNs7vdlQ8mBHMnz9cJHM8OqvNED04 KQvy0kZ5sB+D7i91YCo7QSoaOUGG/yza7nreiauW/ENkz/SwnB0v/N07+h1VFE+8Wp/v za0psq9MGSM5O/lTJGaKwRNTPmXuaQNIvmg8DozK8dZX5aN5L/l3Kx8n1fY5pH78stIj uErQjBFl5qLWe6L4y9x62u9EDt8QLIqjg8Ds0bw6e6pfhC9OUd6wUjUlxlbs3rT0jmiJ xw9Y1ZZVe5t/mRoNz4O9gmTABB0wpwPUjjMg7gYxbYIIc4Xtrgbh8CVES7pOl7HNjSTy RDOw== MIME-Version: 1.0 X-Received: by 10.224.190.6 with SMTP id dg6mr20946721qab.85.1368455545076; Mon, 13 May 2013 07:32:25 -0700 (PDT) Received: by 10.49.81.202 with HTTP; Mon, 13 May 2013 07:32:24 -0700 (PDT) In-Reply-To: <42C7A58253BA3C44BE8534C00002182A69D5FE@XMB117CNC.rim.net> References: <20130506230717.5030019.67417.1021@blackberry.com> <42C7A58253BA3C44BE8534C00002182A69D5FE@XMB117CNC.rim.net> Date: Mon, 13 May 2013 10:32:24 -0400 Message-ID: Subject: Re: blackberry 10 migration From: Bryan Higgins To: dev@cordova.apache.org Content-Type: multipart/alternative; boundary=20cf300fb37fa7cb5404dc9a62a1 X-Gm-Message-State: ALoCoQnFK2k/3NcAcgZNxPC7NGvv6QXUjgQzfHgK1rl+kRSajMEC/10MSZ01qH8v3WCrai1/istG X-Virus-Checked: Checked by ClamAV on apache.org --20cf300fb37fa7cb5404dc9a62a1 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi Lorin, The first drafts of getting started and plugin development are out on a pull request. Command line usage should be there as well today. https://github.com/apache/cordova-docs/pull/40 There are a few other pull requests in cordova-blackberry and cordova-js which are ready to be merged in. Could you help with that? I created JIRA issues for all of them last week. Anything which has been reviewed and tested will have a "ready to merge" comment. It would be good to get them into future before merging into master so we don't have to re-target everything again. Thanks, Bryan On Tue, May 7, 2013 at 1:28 PM, Ken Wallis wrote: > Thanks Lorin. Exciting times for us to see this in Apache. ;) > > -- > > Ken Wallis > > Product Manager =96 WebWorks > > BlackBerry > > 289-261-4369 > > ________________________________________ > From: Lorin Beer [lorin.beer.dev@gmail.com] > Sent: Tuesday, May 07, 2013 8:26 AM > To: dev > Subject: Re: blackberry 10 migration > > pulled into apache: > > github.com/blackberry/ > cordova-blackberry to future branch > cordova-js to future branch > cordova-cli to apache future-bb10 branch > cordova-plugman to apache future branch > > > spoke briefly with Anis concerning merging into plugman and cli, this wil= l > likely wait until Fil Maj is back from Max. The plugman changes seem to b= e > orthogonal to the master/future branch (ie non-breaking). > > as for cordova-js and cordova-blackberry, plan is to merge those as soon = as > docs are in place. > > It can take a few hours for the github mirrors to catch up to git-apache, > but retarget those pull requests anytime. > > > On Mon, May 6, 2013 at 4:32 PM, Lorin Beer > wrote: > > > will do > > > > > > On Mon, May 6, 2013 at 4:23 PM, Bryan Higgins >wrote: > > > >> Ok, I'm about to merge from blackberry/blackberry10-rebase into > >> blackberry/blackberry10 > >> > >> Let me know when you have pushed into apache. There are some open pull > >> requests which I will re-target. > >> > >> > >> On Mon, May 6, 2013 at 7:07 PM, Jeffrey Heifetz < > jheifetz@blackberry.com > >> >wrote: > >> > >> > What about plugman and cli? > >> > > >> > Sent from my BlackBerry 10 smartphone on the Rogers network. > >> > From: Lorin Beer > >> > Sent: Monday, May 6, 2013 7:04 PM > >> > To: dev > >> > Reply To: dev@cordova.apache.org > >> > Subject: Re: blackberry 10 migration > >> > > >> > > >> > ok, we'll pull the code from Blackberry/Blackberry-Cordova and > >> > Blackberry/Cordova-JS into branches in the apache repos. When the do= cs > >> are > >> > ready, we'll merge them into master. > >> > > >> > On Mon, May 6, 2013 at 3:36 PM, Bryan Higgins < > bhiggins@blackberry.com > >> > >wrote: > >> > > >> > > Hi Lorin, > >> > > > >> > > That's great. I think we should be able to get out a rough draft > over > >> the > >> > > next couple days. > >> > > > >> > > > >> > > On Mon, May 6, 2013 at 1:43 PM, Lorin Beer < > lorin.beer.dev@gmail.com> > >> > > wrote: > >> > > > >> > > > Hi Bryan, a quick update: > >> > > > > >> > > > I'll be pulling the code in as soon as docs are in place. Let me > >> know > >> > > when > >> > > > you can push a rough draft at us! > >> > > > > >> > > > - Lorin > >> > > > > >> > > > > >> > > > On Fri, May 3, 2013 at 9:43 AM, Lorin Beer < > >> lorin.beer.dev@gmail.com> > >> > > > wrote: > >> > > > > >> > > > > sounds awesome! Brian is trying to set up a meetings with our > >> teams > >> > > next > >> > > > > week after Max, so I think we are pushing for a post-Max > migration > >> > > date, > >> > > > > late next week. > >> > > > > > >> > > > > thanks for the update Bryan, > >> > > > > > >> > > > > Lorin > >> > > > > > >> > > > > > >> > > > > On Fri, May 3, 2013 at 5:24 AM, Bryan Higgins < > >> > bhiggins@blackberry.com > >> > > > >wrote: > >> > > > > > >> > > > >> Hi Lorin, > >> > > > >> > >> > > > >> We will update to 2.7.0 today and I'm meeting with the docs > >> people > >> > > this > >> > > > >> afternoon. > >> > > > >> > >> > > > >> If they don't have anything ready, I can bang out a draft whi= le > >> I'm > >> > > > flying > >> > > > >> out to Max on Sunday. > >> > > > >> > >> > > > >> Thanks, > >> > > > >> Bryan > >> > > > >> > >> > > > >> > >> > > > >> On Thu, May 2, 2013 at 5:45 PM, Lorin Beer < > >> > lorin.beer.dev@gmail.com> > >> > > > >> wrote: > >> > > > >> > >> > > > >> > Hi Bryan, > >> > > > >> > > >> > > > >> > any progress on the doc side of things? From my experience > with > >> > the > >> > > > new > >> > > > >> > codebase, I shouldn't think that documenting the necessary > >> > workflows > >> > > > >> > (plugins, getting started, etc) should be too time consumin= g. > >> > > > >> > Currently docs and updating to 2.7.0 are the only blockers = to > >> > > pulling > >> > > > >> the > >> > > > >> > blackerry/cordova-blackberry repo into Apache. I would real= ly > >> like > >> > > to > >> > > > >> see > >> > > > >> > this happen this week or early next week. > >> > > > >> > > >> > > > >> > - Lorin > >> > > > >> > > >> > > > >> > > >> > > > >> > On Wed, May 1, 2013 at 12:23 PM, Lorin Beer < > >> > > lorin.beer.dev@gmail.com > >> > > > >> > >wrote: > >> > > > >> > > >> > > > >> > > thanks Bryan > >> > > > >> > > > >> > > > >> > > 1. great to hear, once docs are in place, we'll pull thos= e > in > >> > > > >> alongside > >> > > > >> > > the core BB implementation > >> > > > >> > > > >> > > > >> > > 2. ok, I see. There was a little confusion on our end abo= ut > >> > this. > >> > > > What > >> > > > >> > I'd > >> > > > >> > > like to see is node not visible as an external dependency= . > >> > > > >> > > > >> > > > >> > > 4. check to see why it's building projects with 2.4.0-rc1 > >> > > > >> > > > >> > > > >> > > 5. saw that, this will be pulled in alongside docs and th= e > >> core > >> > BB > >> > > > >> repo > >> > > > >> > > > >> > > > >> > > > >> > > > >> > > On Wed, May 1, 2013 at 12:11 PM, Bryan Higgins < > >> > > > >> bryan@bryanhiggins.net > >> > > > >> > >wrote: > >> > > > >> > > > >> > > > >> > >> Thanks for following up Lorin. > >> > > > >> > >> > >> > > > >> > >> We're actively working on a bunch of things, some of thi= s > >> > > included. > >> > > > >> You > >> > > > >> > >> can > >> > > > >> > >> follow commits in the blackberry10 branch on our forks t= o > >> keep > >> > > tabs > >> > > > >> on > >> > > > >> > us. > >> > > > >> > >> > >> > > > >> > >> I'll go update the JIRA tickets, but here are the answer= s > to > >> > your > >> > > > >> > specific > >> > > > >> > >> questions: > >> > > > >> > >> > >> > > > >> > >> 1. Our docs team is working on these, but they haven't y= et > >> > pushed > >> > > > >> > anything > >> > > > >> > >> to the fork. I'll follow up. > >> > > > >> > >> > >> > > > >> > >> 2. We don't actually have node packaged in the repo. For > >> > > WebWorks, > >> > > > >> it is > >> > > > >> > >> added in during the build process of the distributable. > I'm > >> > fine > >> > > > with > >> > > > >> > >> adding it and I also think it makes sense to call npm > >> install > >> > on > >> > > > >> > >> ./bin/create if the node_modules aren't present. > >> > > > >> > >> > >> > > > >> > >> 3. Agree, help message could be improved > >> > > > >> > >> > >> > > > >> > >> 4. We re-based the forks a week or so ago, but still nee= d > to > >> > > bring > >> > > > in > >> > > > >> > >> hello > >> > > > >> > >> world and update versions. > >> > > > >> > >> > >> > > > >> > >> 5. We have a fork of cordova-js that introduces > blackberry10 > >> > as a > >> > > > >> > >> platform. > >> > > > >> > >> > >> > > > >> > >> > >> > > > >> > >> > >> > > > >> > >> > >> > > > >> > >> On Wed, May 1, 2013 at 2:37 PM, Lorin Beer < > >> > > > lorin.beer.dev@gmail.com > >> > > > >> > > >> > > > >> > >> wrote: > >> > > > >> > >> > >> > > > >> > >> > I want to keep the conversation going concerning the > >> imminent > >> > > > >> > migration > >> > > > >> > >> of > >> > > > >> > >> > BlackBerry's BB10 implementation to Apache Cordova, > >> replacing > >> > > the > >> > > > >> > >> existing > >> > > > >> > >> > implementation. > >> > > > >> > >> > > >> > > > >> > >> > The issues that need to be completed are being tracked > >> here: > >> > > > >> > >> > https://issues.apache.org/jira/browse/CB-3070 > >> > > > >> > >> > > >> > > > >> > >> > With the file system implemented, the BB10 > implementation > >> is > >> > > > only 3 > >> > > > >> > >> tests > >> > > > >> > >> > behind the existing Cordova BB10 implementation, and i= s > >> > stable > >> > > > >> enough > >> > > > >> > to > >> > > > >> > >> > accept. > >> > > > >> > >> > There are, however, a few minor obstacles: > >> > > > >> > >> > > >> > > > >> > >> > 1. documentation > >> > > > >> > >> > - BB10 plugin development > >> > > > >> > >> > - getting started guide > >> > > > >> > >> > > >> > > > >> > >> > both need to be updated to match the new implementatio= n. > >> If > >> > > this > >> > > > >> work > >> > > > >> > is > >> > > > >> > >> > done, please point me to it, but I couldn't see it in > the > >> > > > >> > >> > Blackberry/cordova-docs fork > >> > > > >> > >> > > >> > > > >> > >> > 2. create script > >> > > > >> > >> > the create script for BB10 depends on node. This is no= t > an > >> > > issue, > >> > > > >> as I > >> > > > >> > >> > understand that node comes packaged with. However, I > would > >> > like > >> > > > to > >> > > > >> see > >> > > > >> > >> > package configuration to happen automatically (the npm > >> > install > >> > > > >> step) > >> > > > >> > >> rather > >> > > > >> > >> > than explicitly. > >> > > > >> > >> > > >> > > > >> > >> > 3. project create scripts > >> > > > >> > >> > needs better help messages and documentation > >> > > > >> > >> > > >> > > > >> > >> > 4. 2.7.0 support > >> > > > >> > >> > build tools seem to use 2.4.0-rc1. This needs to be > >> brought > >> > up > >> > > to > >> > > > >> > 2.7.0 > >> > > > >> > >> > > >> > > > >> > >> > 5. cordova-js > >> > > > >> > >> > it looks like BB10 uses it's own version of cordova.js= , > we > >> > need > >> > > > to > >> > > > >> add > >> > > > >> > >> this > >> > > > >> > >> > to platforms in cordova-js > >> > > > >> > >> > > >> > > > >> > >> > Ken, Bryan and any of the BlackBerry folks, please chi= me > >> in > >> > to > >> > > > >> correct > >> > > > >> > >> any > >> > > > >> > >> > misunderstandings, point us to completed work, or > discuss > >> the > >> > > > >> above. > >> > > > >> > >> > > >> > > > >> > >> > I would also encourage participation on the jira issue > >> > > discussion > >> > > > >> > >> threads. > >> > > > >> > >> > > >> > > > >> > >> > - Lorin > >> > > > >> > >> > > >> > > > >> > >> > >> > > > >> > > > >> > > > >> > > > >> > > > >> > > >> > > > >> > >> > > > > > >> > > > > > >> > > > > >> > > > >> > > >> > --------------------------------------------------------------------= - > >> > This transmission (including any attachments) may contain confidenti= al > >> > information, privileged material (including material protected by th= e > >> > solicitor-client or other applicable privileges), or constitute > >> non-public > >> > information. Any use of this information by anyone other than the > >> intended > >> > recipient is prohibited. If you have received this transmission in > >> error, > >> > please immediately reply to the sender and delete this information > from > >> > your system. Use, dissemination, distribution, or reproduction of th= is > >> > transmission by unintended recipients is not authorized and may be > >> unlawful. > >> > > >> > > > > > > --------------------------------------------------------------------- > This transmission (including any attachments) may contain confidential > information, privileged material (including material protected by the > solicitor-client or other applicable privileges), or constitute non-publi= c > information. Any use of this information by anyone other than the intende= d > recipient is prohibited. If you have received this transmission in error, > please immediately reply to the sender and delete this information from > your system. Use, dissemination, distribution, or reproduction of this > transmission by unintended recipients is not authorized and may be unlawf= ul. > --20cf300fb37fa7cb5404dc9a62a1--