Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (nike.apache.org: domain of fil@adobe.com designates
 64.18.1.181 as permitted sender)
From: Filip Maj <fil@adobe.com>
To: "dev@cordova.apache.org" <dev@cordova.apache.org>
Date: Tue, 19 Feb 2013 13:24:27 -0800
Subject: Re: Proposition to split cordova-blackberry into two separate
 plugins
Thread-Topic: Proposition to split cordova-blackberry into two separate
 plugins
Thread-Index: Ac4O54Dc58FmbZOGTaWXoZ2gfn7faw==
Message-ID: <CD492D6B.1816E%fil@adobe.com>
In-Reply-To: <2D04CA88799BFF41A56DAE6575F62B7E23F8041A@XMB111CNC.rim.net>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.3.1.130117
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Sounds fine to me.

As for process, assuming there are no objections (would wait a couple
days), file a JIRA issue on the INFRA project
(issues.apache.org/jira/browser/INFRA)

On 2/19/13 1:15 PM, "Jeffrey Heifetz" <jheifetz@rim.com> wrote:

>With all this talk of re-organizing cordova plugins we here at BlackBerry
>(RIM no more) have been discussing better alleging ourselves with the
>approach by splitting our existing cordova-blackberry platform into two
>separate platforms. (I saw a similar call here as well
>http://callback.markmail.org/thread/xnhpidbnxg5ps7zr#query:+page:1+mid:xnh
>pidbnxg5ps7zr+state:results)
>
>We propose adding a new platform, "blackberry10" with the longterm
>understanding that once BB10 is ported to playbook the original repo
>would only be for BBOS. Ideally the end result of this is that we would
>have an up to date cordova-blackberry10 platform following all of the
>best practices (plugins moved into their own repos, etc) and we can
>better contribute resources to Cordova in general.
>
>Hopefully no one has any objections to this as structurally they are
>really separate platforms. Additionally it'll make the flow within CLI a
>lot cleaner.
>
>If everyone agrees, what is the process for getting a new apache repo for
>it?
>
>---------------------------------------------------------------------
>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-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 this transmission by unintended recipients is not
>authorized and may be unlawful.