You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Shazron <sh...@gmail.com> on 2017/06/09 00:09:58 UTC
Re: [CORE PLUGINS][DISCUSS] Roadmap 2017
Deadline has passed for:
https://issues.apache.org/jira/browse/CB-12708
I believe I captured consensus in the issues as best I could. If there was
no consensus, the status quo prevails (KEEP).
On Tue, May 30, 2017 at 12:58 PM, Shazron <sh...@gmail.com> wrote:
> Good point, I can imagine that after June 5 they will possibly bake things
> into Safari and improve WKWebView, but that will only apply to iOS 11
> onwards and would not affect most decisions since we need to be backwards
> compat for quite a while.
>
> For June 1st, it looks like consensus is there for the majority of the
> plugins. I'm comfortable to move the deadline to June 6th. If there are any
> earth-shattering announcements from Apple, we can bump it up one more week.
>
>
> On Tue, May 30, 2017 at 2:07 AM, julio cesar sanchez <
> jcesarmobile@gmail.com> wrote:
>
>> With the WWDC being next week, should we wait a few more days before
>> making
>> the final decision?
>> After a sneak peek into iOS 11 announcements maybe we can make a better
>> decision
>>
>> 2017-05-22 18:47 GMT+02:00 Shazron <sh...@gmail.com>:
>>
>> > Deadline of June 1st is in 11 days, so get your comments in.
>> >
>> > On Wed, Apr 26, 2017 at 1:01 PM, Shazron <sh...@gmail.com> wrote:
>> >
>> > > I'm going to put a deadline of June 1st, 2017 to wrap up discussion of
>> > the
>> > > Roadmap, we need it to be finalized by then if not it will just be
>> left
>> > in
>> > > the wind like previous proposals.
>> > >
>> > > This gives us a month, more than enough I think, to nail this down --
>> > also
>> > > since most of the Adobe team will be away on conferences (like
>> PhoneGap
>> > Day
>> > > EU 2017 http://pgday.phonegap.com/eu2017/ -- see you there if you are
>> > > going) so this extra time will help.
>> > >
>> > >
>> > >
>> > > On Tue, Apr 25, 2017 at 7:11 PM, Shazron <sh...@gmail.com> wrote:
>> > >
>> > >> The PR for the Plugin Audit is originally here:
>> > https://github.com/cordo
>> > >> va/cordova-discuss/pull/58
>> > >>
>> > >> On Tue, Apr 25, 2017 at 6:55 PM, Shazron <sh...@gmail.com> wrote:
>> > >>
>> > >>> This is the start of a conversation:
>> > >>> https://issues.apache.org/jira/browse/CB-12708
>> > >>>
>> > >>> Take these two issues below into consideration:
>> > >>>
>> > >>> 1. Cordova's plugin audit sometime back:
>> > >>> https://github.com/stevengill/cordova-discuss/blob/836ce2c07
>> > >>> d7c28ee09509cd8a676886aebc21a28/proposals/PluginsAudit2015/audit.md
>> > >>>
>> > >>> 2. The Adobe team's commitment statement w.r.t core plugins:
>> > >>> https://blog.phonegap.com/our-continued-commitment-bca4121f5d39
>> > >>>
>> > >>>
>> > >>>
>> > >>>
>> > >>
>> > >
>> >
>>
>
>
Re: [CORE PLUGINS][DISCUSS] Roadmap 2017
Posted by Filip Maj <ma...@gmail.com>.
There is a clear path forward for most plugins. The plugins-next board
has ~60 issues to tackle to sunset, integrate and update 'em all. Lots
of work to do, but it should be healthy for the project.
One thing I wanted to point out is that the decision on the Dialogs
plugin has been waffling (full discussion in the issue [1]).
Initially, we had voted to keep + update to polyfill the HTML <dialog>
element. Turns out there is a Google-written polyfill out there
already [2]. Simon and I think we should switch the decision on this
plugin to "SUNSET", that is, announce that we will no longer be
maintaining the plugin, let the community take it over if they wish,
and toss up a blog post detailing how to transition to the <dialog>
element / leverage the polyfill if necessary.
If you have opinions on this, please chime in on the thread. On Monday
I'll move forward with formalizing the decision/tasks in there.
[1] https://issues.apache.org/jira/browse/CB-12719
[2] https://github.com/GoogleChrome/dialog-polyfill
On Fri, Jul 28, 2017 at 12:57 PM, Filip Maj <ma...@gmail.com> wrote:
> Small update on this topic:
>
> - still need to clarify next steps on some of the INTEGRATE plugins
> - I think the Dialogs plugin's KEEP + UPDATE decision needs a bit of
> clarification as well
> - I am trying to work with the W3C's web platform tests [1] to
> validate latest spec adherance on the Android and iOS OS versions that
> cordova-android and cordova-ios currently support. For now looking at
> APIs such as the File API and XHR. The reason I am doing this is to
> understand _what_ APIs we still need to polyfill for these
> platforms+versions. Ideally, a lot of these APIs are built in and
> passing the tests, so moving forward we only have to implement the
> minimum set of APIs where support is still wobbly inside cordova. I
> will be reporting these results in the relevant issues per API.
>
> For those wanting to get the w3c-platform-tests working with cordova,
> I got it working by changing the `host` property in the
> config.default.json file to a local-network IP (e.g. 192.168.xxx.xxx,
> which I use to access the tests from my device), and creating a new
> cordova app that whitelists that IP (on port 8000), and pointing the
> <content src=""> location to that IP + port.
>
> [1] https://github.com/w3c/web-platform-tests
>
> On Tue, Jul 25, 2017 at 9:59 AM, Kerri Shotts <ke...@gmail.com> wrote:
>> Just wanted to say “THANKS!” for the work you’ve done on this! :-) It’s much appreciated!
>>
>> ~ Kerri
>>
>>> On Jul 22, 2017, at 14:43, Filip Maj <ma...@gmail.com> wrote:
>>> ...
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: [CORE PLUGINS][DISCUSS] Roadmap 2017
Posted by Filip Maj <ma...@gmail.com>.
Small update on this topic:
- still need to clarify next steps on some of the INTEGRATE plugins
- I think the Dialogs plugin's KEEP + UPDATE decision needs a bit of
clarification as well
- I am trying to work with the W3C's web platform tests [1] to
validate latest spec adherance on the Android and iOS OS versions that
cordova-android and cordova-ios currently support. For now looking at
APIs such as the File API and XHR. The reason I am doing this is to
understand _what_ APIs we still need to polyfill for these
platforms+versions. Ideally, a lot of these APIs are built in and
passing the tests, so moving forward we only have to implement the
minimum set of APIs where support is still wobbly inside cordova. I
will be reporting these results in the relevant issues per API.
For those wanting to get the w3c-platform-tests working with cordova,
I got it working by changing the `host` property in the
config.default.json file to a local-network IP (e.g. 192.168.xxx.xxx,
which I use to access the tests from my device), and creating a new
cordova app that whitelists that IP (on port 8000), and pointing the
<content src=""> location to that IP + port.
[1] https://github.com/w3c/web-platform-tests
On Tue, Jul 25, 2017 at 9:59 AM, Kerri Shotts <ke...@gmail.com> wrote:
> Just wanted to say “THANKS!” for the work you’ve done on this! :-) It’s much appreciated!
>
> ~ Kerri
>
>> On Jul 22, 2017, at 14:43, Filip Maj <ma...@gmail.com> wrote:
>> ...
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: [CORE PLUGINS][DISCUSS] Roadmap 2017
Posted by Kerri Shotts <ke...@gmail.com>.
Just wanted to say “THANKS!” for the work you’ve done on this! :-) It’s much appreciated!
~ Kerri
> On Jul 22, 2017, at 14:43, Filip Maj <ma...@gmail.com> wrote:
> ...
Re: [CORE PLUGINS][DISCUSS] Roadmap 2017
Posted by Filip Maj <ma...@gmail.com>.
By the way I think the details around how to handle INTEGRATED plugins
is the last discussion point left to clarify for the plugin audit /
core plugin roadmap next steps. After that we can start cranking on
the plugins and axing/updating/integrating them.
On Sun, Jul 23, 2017 at 10:57 AM, Filip Maj <ma...@gmail.com> wrote:
> Thanks for the breakdown. I'll move discussion on this topic into the
> issue you linked to.
>
> On Sat, Jul 22, 2017 at 11:30 PM, Shazron <sh...@gmail.com> wrote:
>> Thanks for all this work Fil!
>>
>> Let me clarify https://issues.apache.org/jira/browse/CB-12903 - this task
>> is to list integration issues with respect to users trying to install older
>> versions of the plugin. A lot of this can be mitigated with the engines
>> tag/key but we haven't been using it for the plugins (like
>> cordova-plugin-console), so if someone did try to install the older version
>> of the plugin, it will cause issues.
>>
>> In the case of iOS, and I'm sure Android as well, it relates to the
>> "namespacing" of the integrated plugin.
>> I'm not sure in the case of Android, if the classloader tries to load a
>> class with the same namespace that is already loaded, what happens -- I
>> assume the attempted class that was to be loaded won't be loaded.
>>
>> For iOS, it will create a linker error since it will be a duplicate symbol.
>>
>> To fix this, we can rename the classes, but then it will just be a native
>> side fix. For JavaScript, we want the integrated plugin's native code to
>> prevail (thus it's JavaScript not to be clobbered), not the older version
>> of the plugin -- we can discuss this more at length in the issue.
>>
>>
>>
>> On Sat, Jul 22, 2017 at 12:43 PM, Filip Maj <ma...@gmail.com> wrote:
>>
>>> I just wanted to provide an update on the general topic of modernizing
>>> the core plugins and tracking specific next steps.
>>>
>>> I've been doing my best to work through some of the details and open
>>> questions that came up as part of the Core Plugins Roadmap top-level
>>> issue [1]. In my opinion, this issue is a high priority to execute on
>>> as a) it would make cordova more spec-relevant and inch closer towards
>>> APIs that are showing up natively in the browser and b) would reduce
>>> the total plugin/API surface area the cordova PMC is responsible for.
>>> With over two thousand open or in progress issues in JIRA, I feel like
>>> doing everything we can to make maintenance of cordova sustainable is
>>> not only in the best interest of the cordova PMC but also for the
>>> community.
>>>
>>> In particular, here are some steps I've taken:
>>>
>>> - I've gone through and summarized next steps and filed specific
>>> issues for plugins marked as "KEEP". For some of these, we don't need
>>> to do anything [2]. For other plugins marked "KEEP", the work involves
>>> possibly sunsetting certain specific platforms' code (e.g. vibration
>>> [3] or battery status [4]). The "KEEP" plugins, generally speaking,
>>> probably require the least amount of work in the short-term.
>>> - I have started (but not yet finished!) working through the plugins
>>> marked "SUNSET", for example the file-transfer plugin [5]. As I'm
>>> working through and formalizing next steps, it's looking like this
>>> tends to be quite involved - many sub-steps and lots of little things
>>> to do. However, I think executing on these sooner rather than later
>>> makes cordova more sustainable from a maintenance perspective sooner,
>>> so I'd like to see us put progress into this. I still have to go
>>> through the rest of the "SUNSET" plugins and write up similar next
>>> steps / encapsulate those into JIRA issues.
>>> - I have not yet started going through the plugins marked
>>> "INTEGRATE". I see that Shaz has filed a subtask here about "INTEGRATE
>>> plugin steps" [6], but I'm not exactly sure what you intended with
>>> that. Shaz, can you clarify?
>>>
>>> I've also been tagging all of these Core Plugin Roadmap issues,
>>> whether they are integrate, keep or sunset, with the "plugins-next"
>>> label as described in my recent breakdown of surfacing priority issues
>>> [7].
>>>
>>> As always, questions/comments/highfives welcome.
>>>
>>> Cheers,
>>> Fil
>>>
>>> [1] https://issues.apache.org/jira/browse/CB-12708
>>> [2] https://issues.apache.org/jira/browse/CB-12709
>>> [3] https://issues.apache.org/jira/browse/CB-13045
>>> [4] https://issues.apache.org/jira/browse/CB-13046
>>> [5] https://issues.apache.org/jira/browse/CB-13052
>>> [6] https://issues.apache.org/jira/browse/CB-12903
>>> [7] http://markmail.org/message/nhr7uqvtdbg23fyg
>>>
>>> On Thu, Jun 8, 2017 at 5:17 PM, Filip Maj <ma...@gmail.com> wrote:
>>> > Great job, awesome to see progress on this. 6 plugins to sunset, 5 to
>>> > integrate! Huge progress.
>>> >
>>> > On Thu, Jun 8, 2017 at 7:09 PM, Shazron <sh...@gmail.com> wrote:
>>> >> Deadline has passed for:
>>> >> https://issues.apache.org/jira/browse/CB-12708
>>> >>
>>> >> I believe I captured consensus in the issues as best I could. If there
>>> was
>>> >> no consensus, the status quo prevails (KEEP).
>>> >>
>>> >> On Tue, May 30, 2017 at 12:58 PM, Shazron <sh...@gmail.com> wrote:
>>> >>
>>> >>> Good point, I can imagine that after June 5 they will possibly bake
>>> things
>>> >>> into Safari and improve WKWebView, but that will only apply to iOS 11
>>> >>> onwards and would not affect most decisions since we need to be
>>> backwards
>>> >>> compat for quite a while.
>>> >>>
>>> >>> For June 1st, it looks like consensus is there for the majority of the
>>> >>> plugins. I'm comfortable to move the deadline to June 6th. If there
>>> are any
>>> >>> earth-shattering announcements from Apple, we can bump it up one more
>>> week.
>>> >>>
>>> >>>
>>> >>> On Tue, May 30, 2017 at 2:07 AM, julio cesar sanchez <
>>> >>> jcesarmobile@gmail.com> wrote:
>>> >>>
>>> >>>> With the WWDC being next week, should we wait a few more days before
>>> >>>> making
>>> >>>> the final decision?
>>> >>>> After a sneak peek into iOS 11 announcements maybe we can make a
>>> better
>>> >>>> decision
>>> >>>>
>>> >>>> 2017-05-22 18:47 GMT+02:00 Shazron <sh...@gmail.com>:
>>> >>>>
>>> >>>> > Deadline of June 1st is in 11 days, so get your comments in.
>>> >>>> >
>>> >>>> > On Wed, Apr 26, 2017 at 1:01 PM, Shazron <sh...@gmail.com> wrote:
>>> >>>> >
>>> >>>> > > I'm going to put a deadline of June 1st, 2017 to wrap up
>>> discussion of
>>> >>>> > the
>>> >>>> > > Roadmap, we need it to be finalized by then if not it will just be
>>> >>>> left
>>> >>>> > in
>>> >>>> > > the wind like previous proposals.
>>> >>>> > >
>>> >>>> > > This gives us a month, more than enough I think, to nail this
>>> down --
>>> >>>> > also
>>> >>>> > > since most of the Adobe team will be away on conferences (like
>>> >>>> PhoneGap
>>> >>>> > Day
>>> >>>> > > EU 2017 http://pgday.phonegap.com/eu2017/ -- see you there if
>>> you are
>>> >>>> > > going) so this extra time will help.
>>> >>>> > >
>>> >>>> > >
>>> >>>> > >
>>> >>>> > > On Tue, Apr 25, 2017 at 7:11 PM, Shazron <sh...@gmail.com>
>>> wrote:
>>> >>>> > >
>>> >>>> > >> The PR for the Plugin Audit is originally here:
>>> >>>> > https://github.com/cordo
>>> >>>> > >> va/cordova-discuss/pull/58
>>> >>>> > >>
>>> >>>> > >> On Tue, Apr 25, 2017 at 6:55 PM, Shazron <sh...@gmail.com>
>>> wrote:
>>> >>>> > >>
>>> >>>> > >>> This is the start of a conversation:
>>> >>>> > >>> https://issues.apache.org/jira/browse/CB-12708
>>> >>>> > >>>
>>> >>>> > >>> Take these two issues below into consideration:
>>> >>>> > >>>
>>> >>>> > >>> 1. Cordova's plugin audit sometime back:
>>> >>>> > >>> https://github.com/stevengill/cordova-discuss/blob/836ce2c07
>>> >>>> > >>> d7c28ee09509cd8a676886aebc21a28/proposals/PluginsAudit2015/a
>>> udit.md
>>> >>>> > >>>
>>> >>>> > >>> 2. The Adobe team's commitment statement w.r.t core plugins:
>>> >>>> > >>> https://blog.phonegap.com/our-continued-commitment-bca4121f5d39
>>> >>>> > >>>
>>> >>>> > >>>
>>> >>>> > >>>
>>> >>>> > >>>
>>> >>>> > >>
>>> >>>> > >
>>> >>>> >
>>> >>>>
>>> >>>
>>> >>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>>> For additional commands, e-mail: dev-help@cordova.apache.org
>>>
>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: [CORE PLUGINS][DISCUSS] Roadmap 2017
Posted by Filip Maj <ma...@gmail.com>.
Thanks for the breakdown. I'll move discussion on this topic into the
issue you linked to.
On Sat, Jul 22, 2017 at 11:30 PM, Shazron <sh...@gmail.com> wrote:
> Thanks for all this work Fil!
>
> Let me clarify https://issues.apache.org/jira/browse/CB-12903 - this task
> is to list integration issues with respect to users trying to install older
> versions of the plugin. A lot of this can be mitigated with the engines
> tag/key but we haven't been using it for the plugins (like
> cordova-plugin-console), so if someone did try to install the older version
> of the plugin, it will cause issues.
>
> In the case of iOS, and I'm sure Android as well, it relates to the
> "namespacing" of the integrated plugin.
> I'm not sure in the case of Android, if the classloader tries to load a
> class with the same namespace that is already loaded, what happens -- I
> assume the attempted class that was to be loaded won't be loaded.
>
> For iOS, it will create a linker error since it will be a duplicate symbol.
>
> To fix this, we can rename the classes, but then it will just be a native
> side fix. For JavaScript, we want the integrated plugin's native code to
> prevail (thus it's JavaScript not to be clobbered), not the older version
> of the plugin -- we can discuss this more at length in the issue.
>
>
>
> On Sat, Jul 22, 2017 at 12:43 PM, Filip Maj <ma...@gmail.com> wrote:
>
>> I just wanted to provide an update on the general topic of modernizing
>> the core plugins and tracking specific next steps.
>>
>> I've been doing my best to work through some of the details and open
>> questions that came up as part of the Core Plugins Roadmap top-level
>> issue [1]. In my opinion, this issue is a high priority to execute on
>> as a) it would make cordova more spec-relevant and inch closer towards
>> APIs that are showing up natively in the browser and b) would reduce
>> the total plugin/API surface area the cordova PMC is responsible for.
>> With over two thousand open or in progress issues in JIRA, I feel like
>> doing everything we can to make maintenance of cordova sustainable is
>> not only in the best interest of the cordova PMC but also for the
>> community.
>>
>> In particular, here are some steps I've taken:
>>
>> - I've gone through and summarized next steps and filed specific
>> issues for plugins marked as "KEEP". For some of these, we don't need
>> to do anything [2]. For other plugins marked "KEEP", the work involves
>> possibly sunsetting certain specific platforms' code (e.g. vibration
>> [3] or battery status [4]). The "KEEP" plugins, generally speaking,
>> probably require the least amount of work in the short-term.
>> - I have started (but not yet finished!) working through the plugins
>> marked "SUNSET", for example the file-transfer plugin [5]. As I'm
>> working through and formalizing next steps, it's looking like this
>> tends to be quite involved - many sub-steps and lots of little things
>> to do. However, I think executing on these sooner rather than later
>> makes cordova more sustainable from a maintenance perspective sooner,
>> so I'd like to see us put progress into this. I still have to go
>> through the rest of the "SUNSET" plugins and write up similar next
>> steps / encapsulate those into JIRA issues.
>> - I have not yet started going through the plugins marked
>> "INTEGRATE". I see that Shaz has filed a subtask here about "INTEGRATE
>> plugin steps" [6], but I'm not exactly sure what you intended with
>> that. Shaz, can you clarify?
>>
>> I've also been tagging all of these Core Plugin Roadmap issues,
>> whether they are integrate, keep or sunset, with the "plugins-next"
>> label as described in my recent breakdown of surfacing priority issues
>> [7].
>>
>> As always, questions/comments/highfives welcome.
>>
>> Cheers,
>> Fil
>>
>> [1] https://issues.apache.org/jira/browse/CB-12708
>> [2] https://issues.apache.org/jira/browse/CB-12709
>> [3] https://issues.apache.org/jira/browse/CB-13045
>> [4] https://issues.apache.org/jira/browse/CB-13046
>> [5] https://issues.apache.org/jira/browse/CB-13052
>> [6] https://issues.apache.org/jira/browse/CB-12903
>> [7] http://markmail.org/message/nhr7uqvtdbg23fyg
>>
>> On Thu, Jun 8, 2017 at 5:17 PM, Filip Maj <ma...@gmail.com> wrote:
>> > Great job, awesome to see progress on this. 6 plugins to sunset, 5 to
>> > integrate! Huge progress.
>> >
>> > On Thu, Jun 8, 2017 at 7:09 PM, Shazron <sh...@gmail.com> wrote:
>> >> Deadline has passed for:
>> >> https://issues.apache.org/jira/browse/CB-12708
>> >>
>> >> I believe I captured consensus in the issues as best I could. If there
>> was
>> >> no consensus, the status quo prevails (KEEP).
>> >>
>> >> On Tue, May 30, 2017 at 12:58 PM, Shazron <sh...@gmail.com> wrote:
>> >>
>> >>> Good point, I can imagine that after June 5 they will possibly bake
>> things
>> >>> into Safari and improve WKWebView, but that will only apply to iOS 11
>> >>> onwards and would not affect most decisions since we need to be
>> backwards
>> >>> compat for quite a while.
>> >>>
>> >>> For June 1st, it looks like consensus is there for the majority of the
>> >>> plugins. I'm comfortable to move the deadline to June 6th. If there
>> are any
>> >>> earth-shattering announcements from Apple, we can bump it up one more
>> week.
>> >>>
>> >>>
>> >>> On Tue, May 30, 2017 at 2:07 AM, julio cesar sanchez <
>> >>> jcesarmobile@gmail.com> wrote:
>> >>>
>> >>>> With the WWDC being next week, should we wait a few more days before
>> >>>> making
>> >>>> the final decision?
>> >>>> After a sneak peek into iOS 11 announcements maybe we can make a
>> better
>> >>>> decision
>> >>>>
>> >>>> 2017-05-22 18:47 GMT+02:00 Shazron <sh...@gmail.com>:
>> >>>>
>> >>>> > Deadline of June 1st is in 11 days, so get your comments in.
>> >>>> >
>> >>>> > On Wed, Apr 26, 2017 at 1:01 PM, Shazron <sh...@gmail.com> wrote:
>> >>>> >
>> >>>> > > I'm going to put a deadline of June 1st, 2017 to wrap up
>> discussion of
>> >>>> > the
>> >>>> > > Roadmap, we need it to be finalized by then if not it will just be
>> >>>> left
>> >>>> > in
>> >>>> > > the wind like previous proposals.
>> >>>> > >
>> >>>> > > This gives us a month, more than enough I think, to nail this
>> down --
>> >>>> > also
>> >>>> > > since most of the Adobe team will be away on conferences (like
>> >>>> PhoneGap
>> >>>> > Day
>> >>>> > > EU 2017 http://pgday.phonegap.com/eu2017/ -- see you there if
>> you are
>> >>>> > > going) so this extra time will help.
>> >>>> > >
>> >>>> > >
>> >>>> > >
>> >>>> > > On Tue, Apr 25, 2017 at 7:11 PM, Shazron <sh...@gmail.com>
>> wrote:
>> >>>> > >
>> >>>> > >> The PR for the Plugin Audit is originally here:
>> >>>> > https://github.com/cordo
>> >>>> > >> va/cordova-discuss/pull/58
>> >>>> > >>
>> >>>> > >> On Tue, Apr 25, 2017 at 6:55 PM, Shazron <sh...@gmail.com>
>> wrote:
>> >>>> > >>
>> >>>> > >>> This is the start of a conversation:
>> >>>> > >>> https://issues.apache.org/jira/browse/CB-12708
>> >>>> > >>>
>> >>>> > >>> Take these two issues below into consideration:
>> >>>> > >>>
>> >>>> > >>> 1. Cordova's plugin audit sometime back:
>> >>>> > >>> https://github.com/stevengill/cordova-discuss/blob/836ce2c07
>> >>>> > >>> d7c28ee09509cd8a676886aebc21a28/proposals/PluginsAudit2015/a
>> udit.md
>> >>>> > >>>
>> >>>> > >>> 2. The Adobe team's commitment statement w.r.t core plugins:
>> >>>> > >>> https://blog.phonegap.com/our-continued-commitment-bca4121f5d39
>> >>>> > >>>
>> >>>> > >>>
>> >>>> > >>>
>> >>>> > >>>
>> >>>> > >>
>> >>>> > >
>> >>>> >
>> >>>>
>> >>>
>> >>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
>> For additional commands, e-mail: dev-help@cordova.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: [CORE PLUGINS][DISCUSS] Roadmap 2017
Posted by Shazron <sh...@gmail.com>.
Thanks for all this work Fil!
Let me clarify https://issues.apache.org/jira/browse/CB-12903 - this task
is to list integration issues with respect to users trying to install older
versions of the plugin. A lot of this can be mitigated with the engines
tag/key but we haven't been using it for the plugins (like
cordova-plugin-console), so if someone did try to install the older version
of the plugin, it will cause issues.
In the case of iOS, and I'm sure Android as well, it relates to the
"namespacing" of the integrated plugin.
I'm not sure in the case of Android, if the classloader tries to load a
class with the same namespace that is already loaded, what happens -- I
assume the attempted class that was to be loaded won't be loaded.
For iOS, it will create a linker error since it will be a duplicate symbol.
To fix this, we can rename the classes, but then it will just be a native
side fix. For JavaScript, we want the integrated plugin's native code to
prevail (thus it's JavaScript not to be clobbered), not the older version
of the plugin -- we can discuss this more at length in the issue.
On Sat, Jul 22, 2017 at 12:43 PM, Filip Maj <ma...@gmail.com> wrote:
> I just wanted to provide an update on the general topic of modernizing
> the core plugins and tracking specific next steps.
>
> I've been doing my best to work through some of the details and open
> questions that came up as part of the Core Plugins Roadmap top-level
> issue [1]. In my opinion, this issue is a high priority to execute on
> as a) it would make cordova more spec-relevant and inch closer towards
> APIs that are showing up natively in the browser and b) would reduce
> the total plugin/API surface area the cordova PMC is responsible for.
> With over two thousand open or in progress issues in JIRA, I feel like
> doing everything we can to make maintenance of cordova sustainable is
> not only in the best interest of the cordova PMC but also for the
> community.
>
> In particular, here are some steps I've taken:
>
> - I've gone through and summarized next steps and filed specific
> issues for plugins marked as "KEEP". For some of these, we don't need
> to do anything [2]. For other plugins marked "KEEP", the work involves
> possibly sunsetting certain specific platforms' code (e.g. vibration
> [3] or battery status [4]). The "KEEP" plugins, generally speaking,
> probably require the least amount of work in the short-term.
> - I have started (but not yet finished!) working through the plugins
> marked "SUNSET", for example the file-transfer plugin [5]. As I'm
> working through and formalizing next steps, it's looking like this
> tends to be quite involved - many sub-steps and lots of little things
> to do. However, I think executing on these sooner rather than later
> makes cordova more sustainable from a maintenance perspective sooner,
> so I'd like to see us put progress into this. I still have to go
> through the rest of the "SUNSET" plugins and write up similar next
> steps / encapsulate those into JIRA issues.
> - I have not yet started going through the plugins marked
> "INTEGRATE". I see that Shaz has filed a subtask here about "INTEGRATE
> plugin steps" [6], but I'm not exactly sure what you intended with
> that. Shaz, can you clarify?
>
> I've also been tagging all of these Core Plugin Roadmap issues,
> whether they are integrate, keep or sunset, with the "plugins-next"
> label as described in my recent breakdown of surfacing priority issues
> [7].
>
> As always, questions/comments/highfives welcome.
>
> Cheers,
> Fil
>
> [1] https://issues.apache.org/jira/browse/CB-12708
> [2] https://issues.apache.org/jira/browse/CB-12709
> [3] https://issues.apache.org/jira/browse/CB-13045
> [4] https://issues.apache.org/jira/browse/CB-13046
> [5] https://issues.apache.org/jira/browse/CB-13052
> [6] https://issues.apache.org/jira/browse/CB-12903
> [7] http://markmail.org/message/nhr7uqvtdbg23fyg
>
> On Thu, Jun 8, 2017 at 5:17 PM, Filip Maj <ma...@gmail.com> wrote:
> > Great job, awesome to see progress on this. 6 plugins to sunset, 5 to
> > integrate! Huge progress.
> >
> > On Thu, Jun 8, 2017 at 7:09 PM, Shazron <sh...@gmail.com> wrote:
> >> Deadline has passed for:
> >> https://issues.apache.org/jira/browse/CB-12708
> >>
> >> I believe I captured consensus in the issues as best I could. If there
> was
> >> no consensus, the status quo prevails (KEEP).
> >>
> >> On Tue, May 30, 2017 at 12:58 PM, Shazron <sh...@gmail.com> wrote:
> >>
> >>> Good point, I can imagine that after June 5 they will possibly bake
> things
> >>> into Safari and improve WKWebView, but that will only apply to iOS 11
> >>> onwards and would not affect most decisions since we need to be
> backwards
> >>> compat for quite a while.
> >>>
> >>> For June 1st, it looks like consensus is there for the majority of the
> >>> plugins. I'm comfortable to move the deadline to June 6th. If there
> are any
> >>> earth-shattering announcements from Apple, we can bump it up one more
> week.
> >>>
> >>>
> >>> On Tue, May 30, 2017 at 2:07 AM, julio cesar sanchez <
> >>> jcesarmobile@gmail.com> wrote:
> >>>
> >>>> With the WWDC being next week, should we wait a few more days before
> >>>> making
> >>>> the final decision?
> >>>> After a sneak peek into iOS 11 announcements maybe we can make a
> better
> >>>> decision
> >>>>
> >>>> 2017-05-22 18:47 GMT+02:00 Shazron <sh...@gmail.com>:
> >>>>
> >>>> > Deadline of June 1st is in 11 days, so get your comments in.
> >>>> >
> >>>> > On Wed, Apr 26, 2017 at 1:01 PM, Shazron <sh...@gmail.com> wrote:
> >>>> >
> >>>> > > I'm going to put a deadline of June 1st, 2017 to wrap up
> discussion of
> >>>> > the
> >>>> > > Roadmap, we need it to be finalized by then if not it will just be
> >>>> left
> >>>> > in
> >>>> > > the wind like previous proposals.
> >>>> > >
> >>>> > > This gives us a month, more than enough I think, to nail this
> down --
> >>>> > also
> >>>> > > since most of the Adobe team will be away on conferences (like
> >>>> PhoneGap
> >>>> > Day
> >>>> > > EU 2017 http://pgday.phonegap.com/eu2017/ -- see you there if
> you are
> >>>> > > going) so this extra time will help.
> >>>> > >
> >>>> > >
> >>>> > >
> >>>> > > On Tue, Apr 25, 2017 at 7:11 PM, Shazron <sh...@gmail.com>
> wrote:
> >>>> > >
> >>>> > >> The PR for the Plugin Audit is originally here:
> >>>> > https://github.com/cordo
> >>>> > >> va/cordova-discuss/pull/58
> >>>> > >>
> >>>> > >> On Tue, Apr 25, 2017 at 6:55 PM, Shazron <sh...@gmail.com>
> wrote:
> >>>> > >>
> >>>> > >>> This is the start of a conversation:
> >>>> > >>> https://issues.apache.org/jira/browse/CB-12708
> >>>> > >>>
> >>>> > >>> Take these two issues below into consideration:
> >>>> > >>>
> >>>> > >>> 1. Cordova's plugin audit sometime back:
> >>>> > >>> https://github.com/stevengill/cordova-discuss/blob/836ce2c07
> >>>> > >>> d7c28ee09509cd8a676886aebc21a28/proposals/PluginsAudit2015/a
> udit.md
> >>>> > >>>
> >>>> > >>> 2. The Adobe team's commitment statement w.r.t core plugins:
> >>>> > >>> https://blog.phonegap.com/our-continued-commitment-bca4121f5d39
> >>>> > >>>
> >>>> > >>>
> >>>> > >>>
> >>>> > >>>
> >>>> > >>
> >>>> > >
> >>>> >
> >>>>
> >>>
> >>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
>
Re: [CORE PLUGINS][DISCUSS] Roadmap 2017
Posted by Filip Maj <ma...@gmail.com>.
I just wanted to provide an update on the general topic of modernizing
the core plugins and tracking specific next steps.
I've been doing my best to work through some of the details and open
questions that came up as part of the Core Plugins Roadmap top-level
issue [1]. In my opinion, this issue is a high priority to execute on
as a) it would make cordova more spec-relevant and inch closer towards
APIs that are showing up natively in the browser and b) would reduce
the total plugin/API surface area the cordova PMC is responsible for.
With over two thousand open or in progress issues in JIRA, I feel like
doing everything we can to make maintenance of cordova sustainable is
not only in the best interest of the cordova PMC but also for the
community.
In particular, here are some steps I've taken:
- I've gone through and summarized next steps and filed specific
issues for plugins marked as "KEEP". For some of these, we don't need
to do anything [2]. For other plugins marked "KEEP", the work involves
possibly sunsetting certain specific platforms' code (e.g. vibration
[3] or battery status [4]). The "KEEP" plugins, generally speaking,
probably require the least amount of work in the short-term.
- I have started (but not yet finished!) working through the plugins
marked "SUNSET", for example the file-transfer plugin [5]. As I'm
working through and formalizing next steps, it's looking like this
tends to be quite involved - many sub-steps and lots of little things
to do. However, I think executing on these sooner rather than later
makes cordova more sustainable from a maintenance perspective sooner,
so I'd like to see us put progress into this. I still have to go
through the rest of the "SUNSET" plugins and write up similar next
steps / encapsulate those into JIRA issues.
- I have not yet started going through the plugins marked
"INTEGRATE". I see that Shaz has filed a subtask here about "INTEGRATE
plugin steps" [6], but I'm not exactly sure what you intended with
that. Shaz, can you clarify?
I've also been tagging all of these Core Plugin Roadmap issues,
whether they are integrate, keep or sunset, with the "plugins-next"
label as described in my recent breakdown of surfacing priority issues
[7].
As always, questions/comments/highfives welcome.
Cheers,
Fil
[1] https://issues.apache.org/jira/browse/CB-12708
[2] https://issues.apache.org/jira/browse/CB-12709
[3] https://issues.apache.org/jira/browse/CB-13045
[4] https://issues.apache.org/jira/browse/CB-13046
[5] https://issues.apache.org/jira/browse/CB-13052
[6] https://issues.apache.org/jira/browse/CB-12903
[7] http://markmail.org/message/nhr7uqvtdbg23fyg
On Thu, Jun 8, 2017 at 5:17 PM, Filip Maj <ma...@gmail.com> wrote:
> Great job, awesome to see progress on this. 6 plugins to sunset, 5 to
> integrate! Huge progress.
>
> On Thu, Jun 8, 2017 at 7:09 PM, Shazron <sh...@gmail.com> wrote:
>> Deadline has passed for:
>> https://issues.apache.org/jira/browse/CB-12708
>>
>> I believe I captured consensus in the issues as best I could. If there was
>> no consensus, the status quo prevails (KEEP).
>>
>> On Tue, May 30, 2017 at 12:58 PM, Shazron <sh...@gmail.com> wrote:
>>
>>> Good point, I can imagine that after June 5 they will possibly bake things
>>> into Safari and improve WKWebView, but that will only apply to iOS 11
>>> onwards and would not affect most decisions since we need to be backwards
>>> compat for quite a while.
>>>
>>> For June 1st, it looks like consensus is there for the majority of the
>>> plugins. I'm comfortable to move the deadline to June 6th. If there are any
>>> earth-shattering announcements from Apple, we can bump it up one more week.
>>>
>>>
>>> On Tue, May 30, 2017 at 2:07 AM, julio cesar sanchez <
>>> jcesarmobile@gmail.com> wrote:
>>>
>>>> With the WWDC being next week, should we wait a few more days before
>>>> making
>>>> the final decision?
>>>> After a sneak peek into iOS 11 announcements maybe we can make a better
>>>> decision
>>>>
>>>> 2017-05-22 18:47 GMT+02:00 Shazron <sh...@gmail.com>:
>>>>
>>>> > Deadline of June 1st is in 11 days, so get your comments in.
>>>> >
>>>> > On Wed, Apr 26, 2017 at 1:01 PM, Shazron <sh...@gmail.com> wrote:
>>>> >
>>>> > > I'm going to put a deadline of June 1st, 2017 to wrap up discussion of
>>>> > the
>>>> > > Roadmap, we need it to be finalized by then if not it will just be
>>>> left
>>>> > in
>>>> > > the wind like previous proposals.
>>>> > >
>>>> > > This gives us a month, more than enough I think, to nail this down --
>>>> > also
>>>> > > since most of the Adobe team will be away on conferences (like
>>>> PhoneGap
>>>> > Day
>>>> > > EU 2017 http://pgday.phonegap.com/eu2017/ -- see you there if you are
>>>> > > going) so this extra time will help.
>>>> > >
>>>> > >
>>>> > >
>>>> > > On Tue, Apr 25, 2017 at 7:11 PM, Shazron <sh...@gmail.com> wrote:
>>>> > >
>>>> > >> The PR for the Plugin Audit is originally here:
>>>> > https://github.com/cordo
>>>> > >> va/cordova-discuss/pull/58
>>>> > >>
>>>> > >> On Tue, Apr 25, 2017 at 6:55 PM, Shazron <sh...@gmail.com> wrote:
>>>> > >>
>>>> > >>> This is the start of a conversation:
>>>> > >>> https://issues.apache.org/jira/browse/CB-12708
>>>> > >>>
>>>> > >>> Take these two issues below into consideration:
>>>> > >>>
>>>> > >>> 1. Cordova's plugin audit sometime back:
>>>> > >>> https://github.com/stevengill/cordova-discuss/blob/836ce2c07
>>>> > >>> d7c28ee09509cd8a676886aebc21a28/proposals/PluginsAudit2015/audit.md
>>>> > >>>
>>>> > >>> 2. The Adobe team's commitment statement w.r.t core plugins:
>>>> > >>> https://blog.phonegap.com/our-continued-commitment-bca4121f5d39
>>>> > >>>
>>>> > >>>
>>>> > >>>
>>>> > >>>
>>>> > >>
>>>> > >
>>>> >
>>>>
>>>
>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: [CORE PLUGINS][DISCUSS] Roadmap 2017
Posted by Filip Maj <ma...@gmail.com>.
Great job, awesome to see progress on this. 6 plugins to sunset, 5 to
integrate! Huge progress.
On Thu, Jun 8, 2017 at 7:09 PM, Shazron <sh...@gmail.com> wrote:
> Deadline has passed for:
> https://issues.apache.org/jira/browse/CB-12708
>
> I believe I captured consensus in the issues as best I could. If there was
> no consensus, the status quo prevails (KEEP).
>
> On Tue, May 30, 2017 at 12:58 PM, Shazron <sh...@gmail.com> wrote:
>
>> Good point, I can imagine that after June 5 they will possibly bake things
>> into Safari and improve WKWebView, but that will only apply to iOS 11
>> onwards and would not affect most decisions since we need to be backwards
>> compat for quite a while.
>>
>> For June 1st, it looks like consensus is there for the majority of the
>> plugins. I'm comfortable to move the deadline to June 6th. If there are any
>> earth-shattering announcements from Apple, we can bump it up one more week.
>>
>>
>> On Tue, May 30, 2017 at 2:07 AM, julio cesar sanchez <
>> jcesarmobile@gmail.com> wrote:
>>
>>> With the WWDC being next week, should we wait a few more days before
>>> making
>>> the final decision?
>>> After a sneak peek into iOS 11 announcements maybe we can make a better
>>> decision
>>>
>>> 2017-05-22 18:47 GMT+02:00 Shazron <sh...@gmail.com>:
>>>
>>> > Deadline of June 1st is in 11 days, so get your comments in.
>>> >
>>> > On Wed, Apr 26, 2017 at 1:01 PM, Shazron <sh...@gmail.com> wrote:
>>> >
>>> > > I'm going to put a deadline of June 1st, 2017 to wrap up discussion of
>>> > the
>>> > > Roadmap, we need it to be finalized by then if not it will just be
>>> left
>>> > in
>>> > > the wind like previous proposals.
>>> > >
>>> > > This gives us a month, more than enough I think, to nail this down --
>>> > also
>>> > > since most of the Adobe team will be away on conferences (like
>>> PhoneGap
>>> > Day
>>> > > EU 2017 http://pgday.phonegap.com/eu2017/ -- see you there if you are
>>> > > going) so this extra time will help.
>>> > >
>>> > >
>>> > >
>>> > > On Tue, Apr 25, 2017 at 7:11 PM, Shazron <sh...@gmail.com> wrote:
>>> > >
>>> > >> The PR for the Plugin Audit is originally here:
>>> > https://github.com/cordo
>>> > >> va/cordova-discuss/pull/58
>>> > >>
>>> > >> On Tue, Apr 25, 2017 at 6:55 PM, Shazron <sh...@gmail.com> wrote:
>>> > >>
>>> > >>> This is the start of a conversation:
>>> > >>> https://issues.apache.org/jira/browse/CB-12708
>>> > >>>
>>> > >>> Take these two issues below into consideration:
>>> > >>>
>>> > >>> 1. Cordova's plugin audit sometime back:
>>> > >>> https://github.com/stevengill/cordova-discuss/blob/836ce2c07
>>> > >>> d7c28ee09509cd8a676886aebc21a28/proposals/PluginsAudit2015/audit.md
>>> > >>>
>>> > >>> 2. The Adobe team's commitment statement w.r.t core plugins:
>>> > >>> https://blog.phonegap.com/our-continued-commitment-bca4121f5d39
>>> > >>>
>>> > >>>
>>> > >>>
>>> > >>>
>>> > >>
>>> > >
>>> >
>>>
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org