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 purplecabbage@gmail.com
 designates 209.85.213.178 as permitted sender)
References: 
 <CAE6O_-YZdTwodEirDU2RbcQQiPkhNsFUSaaaNjfivbqCMJ1aOg@mail.gmail.com>
 <CAEeF2Tcxz3O_rQ-=mvqpmq+M2NEpzyHLQeV1nBh47bfSPBAmiw@mail.gmail.com>
 <CAE6O_-YoaH6kC8cTRWNrtWSQizj9SsZbv1L6D_p_E0i8LJ+A7Q@mail.gmail.com>
 <CAKP6k2t1uA8J7T98saNtN9nCP8ZKR80Ttbw9Og-jrZ+Vxv6z+g@mail.gmail.com>
 <D7E040B7-5A40-4E55-B8A6-987CE68CB15A@gmail.com>
 <CANpVHHzpx_X=R=Gjwq6RrhRSV-N9=thzZosJgMG7=x1X-8XYxA@mail.gmail.com>
 <CAE6O_-aSi+WuUABKVsLRG9tMvttsMaawZkbYrzpYeJi3AqYFrA@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: 
 <CAE6O_-aSi+WuUABKVsLRG9tMvttsMaawZkbYrzpYeJi3AqYFrA@mail.gmail.com>
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <531a64d2.827c320a.07d0.0d9e@mx.google.com>
Cc: "dev@cordova.apache.org" <dev@cordova.apache.org>
From: purplecabbage <purplecabbage@gmail.com>
Subject: Re: [cordova-plugins/statusbar] Publishing as core
Date: Fri, 7 Mar 2014 16:31:12 -0800
To: "dev@cordova.apache.org" <dev@cordova.apache.org>

StatusBar wp7+8 is mostly done. Just testing some stuff now.=20

Sent from my iPhone

> On Mar 7, 2014, at 3:30 PM, Shazron <shazron@gmail.com> wrote:
>=20
> Technically there are two platforms right now. Android has minimal support=
,
> and Jesse wants to do WP8 (again minimal), so thats another.
>=20
>=20
>> On Fri, Mar 7, 2014 at 3:23 PM, Anis KADRI <anis.kadri@gmail.com> wrote:
>>=20
>> +1 for labs. it doesn't really make sense to have them in core if they on=
ly
>> support one platform.
>>=20
>>=20
>>> On Thu, Mar 6, 2014 at 8:47 AM, James Jong <wjamesjong@gmail.com> wrote:=

>>>=20
>>> Similar to keyboard plugin, I like the idea of letting this bake in labs=

>>> for now and moving them into core if we see multiple platforms start
>>> needing a similar API.  So (a) and (c) for me.
>>>=20
>>> I would add that the iOS 6/7 specific code may not make sense as "core".=

>>>=20
>>> -James Jong
>>>=20
>>>> On Mar 5, 2014, at 9:10 PM, Jesse <purplecabbage@gmail.com> wrote:
>>>>=20
>>>> I have created a task in JIRA for all the statusbar related discussion.=

>>> [1]
>>>> There are numerous inconsistencies we need to address here.
>>>>=20
>>>> [1] https://issues.apache.org/jira/browse/CB-6177
>>>>=20
>>>> @purplecabbage
>>>> risingj.com
>>>>=20
>>>>=20
>>>>> On Wed, Mar 5, 2014 at 5:15 PM, Shazron <shazron@gmail.com> wrote:
>>>>>=20
>>>>> Some background on the statusbar plugin.
>>>>>=20
>>>>> This was conceived because of iOS 7 where the statusbar overlays the
>>>>> webview, and a lot of people didn't like their UI changing especially
>> if
>>>>> they still support iOS 6. That is the primary purpose of this plugin,
>>> but
>>>>> there are other features in there as well. In the last few weeks,
>> there
>>> was
>>>>> a pull request (now integrated) for StatusBar.hide and StatusBar.show
>>> for
>>>>> Android as well.
>>>>>=20
>>>>> The issues related to the statusbar are under the label
>>> "statusbar-plugin"
>>>>> in JIRA, and there are currently 11 open issues. There are pull
>> requests
>>>>> for it from the PhoneGap Build team that I am waiting to integrate --
>>> not
>>>>> until we get this namespace stuff sorted out.
>>>>>=20
>>>>> I am not opposed to it being under the "labs" namespace. After talking=

>>> to
>>>>> the Adobe team, we could also host the plugin under the PhoneGap
>> Github
>>>>> org, but I'd rather use that as a last resort.
>>>>>=20
>>>>>=20
>>>>> On Wed, Mar 5, 2014 at 11:36 AM, Michal Mocny <mmocny@chromium.org>
>>> wrote:
>>>>>=20
>>>>>> (a) Yes.
>>>>>> (b) No -- some organizations (Adobe) don't like this, and we respect
>>>>> that.
>>>>>> We also want to point users at these plugins, so its good to have
>>>>>> developers protected by Apache.
>>>>>> (c) Sure -- so long as labs is clearly separate, and we leave them
>> out
>>> of
>>>>>> blogs / plugin release notes, and we don't impact the rate of
>> releases
>>>>>> (i.e. we don't force devs to test the labs plugins, just verify the
>>>>>> signatures is enough).
>>>>>> (d) I think the "guardian" of these labs plugins should be free to
>>>>> publish.
>>>>>> There is no reason they are lower quality than anything else.
>>>>>>=20
>>>>>>=20
>>>>>> Separate issue: is statusbar ready for Core?  I think we should leave=

>>> it
>>>>> in
>>>>>> labs for a little bit, have at least a few eyes audit the API and
>>>>>> investigate if there is any other similar work in the field before we=

>>>>> make
>>>>>> users depend on this, but that it should move to core eventually.
>>>>>>=20
>>>>>> -Michal
>>>>>>=20
>>>>>>=20
>>>>>>> On Wed, Mar 5, 2014 at 1:14 PM, Shazron <shazron@apache.org> wrote:
>>>>>>>=20
>>>>>>> statusbar is already published org.apache.cordova.statusbar.
>>>>>>>=20
>>>>>>> And... Since these plugins are somewhat experimental and we're
>>> starting
>>>>>> the
>>>>>>> process of voting and publishing plugins to dist/, I wonder:
>>>>>>>=20
>>>>>>> a) Should we change the ID of these plugins to, say
>>>>>>> "org.apache.cordova.labs"
>>>>>>> b) Should we move these plugins to github and have them not under
>>>>> apache
>>>>>>> for now, e.g.: com.shazron.statusbar
>>>>>>> c) Should we just add them to the plugin release process.
>>>>>>> d) Should we just never publish them to the registry and have people=

>>>>> use
>>>>>>> them via git url.
>>=20