Re: Plans for Cordova user & contributor survey

[pieter van poyer]

Hey Niklas

+1

The questions are good, the survey is short and I think it's best to keep
it that way.

You could dig deeper into the  'Have you migrated apps from Cordova to
alternative solutions? If yes what did you use?'  - question.
For example 'Why did you migrate your app to an alternative solution? '
(Too much native requirements?, Decision from the company?, Lack of
interest or trus in mobile hybrid development? ... )
- This question can also be answered in the 'What are your pain points with
Cordova ?' - question.

Maybe it is also good to know why someone did pick Cordova for his or her
app?

Kind regards

Pieter



Op di 21 nov 2023 om 18:46 schreef Niklas Merz :

> Thanks for the feedback. December is usually a busy month but I'm hoping
> the active users find the survey and respond in time. If we don't get
> many responses we can still extend the deadline. When I answer a survey
> I do so immediatly otherwise I forget about so I don't think a long time
> gets us better results.
>
> I would like to send the announcement this Friday 24th so there is
> exactly one month until the Christmas holidays. (Selfishly ;) I'm off
> from work the week after and I could use that to compile the results.)
>
> If nobody objects I will prepare everything on Friday.
>
> On November 19, 2023, Norman Breau  wrote:
> > +1
> >
> > If I'd change anything, I'd push the closing date into at least the
> > second week of January 2024, because people might be busy in
> > the month of December going into the holidays. But this isn't
> > something I'd block the motion for, so if Decembet 24th works
> > better for you, then that's okay too.
> >
> > On 2023-11-18 8:29 a.m., Niklas Merz wrote:
> > > Hey everyone,
> > >
> > > As discussed I started building a survey using Google forms. This is
> > the
> > > current version: https://forms.gle/2HKWATLcRQdw85mE6 .The results
> > are
> > > stored in a Google Sheet and I can invite you as editors if you
> > want.
> > >
> > > I will only continue this effort if at least 3 other PMC members
> > share
> > > their consensus with a +1 vote.
> > >
> > > I also drafted an announcement for the blog as a PR. Feel free to
> > review
> > > or just edit it there: https://github.com/apache/cordova-
> > docs/pull/1341
> > >
> > > For the timeline I suggest the following:
> > >
> > > Announcement via blog, mailing list and social media: November 24th
> > 2023
> > > Closing: December 24th 2023
> > > Sharing results: End of 2023 (I would prepare another blog post and
> > > email with numbers)
> > > Online Hangout to discuss results and conclusions: Start of 2024
> > >
> > > What do you think? Let me know your honest opinion on the questions,
> > > communication and timeline.
> > >
> > > Personally I'm really interested in the results and I would love to
> > get
> > > clearer picture about what we should work on and what users actually
> > do.
> > >
> > > Kind regards
> > > Niklas
> > >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > For additional commands, e-mail: dev-h...@cordova.apache.org
>

Re: [VOTE] Cordova-OSX 7.0.0 Release

[pieter van poyer]

I vote +1
* blog post looks good
* changes are looking good

Kind regards
Pieter

Op zo 6 mrt. 2022 om 12:13 schreef Niklas Merz :

> Please review and vote on this 7.0.0 OSX Release
> by replying to this email (and keep discussion on the DISCUSS thread)
>
> The archive has been published to dist/dev:
> https://dist.apache.org/repos/dist/dev/cordova/osx-7.0.0/
>
> The package was published from its corresponding git tag:
> cordova-osx: 7.0.0 (d96f2a68ec)
>
> Note that you can test it out via:
>
> cordova platform add https://github.com/apache/cordova-osx#7.0.0
>
> !! Please also review the announcement blog post where we should use the
> opportunity to finally announce the platform deprecation and point users
> to the alternatives electron and ios with Catalyst:
> https://github.com/apache/cordova-docs/pull/1233
>
>
> Upon a successful vote I will upload the archive to dist/, publish it to
> npm, and post the blog post.
>
> Voting guidelines: https://github.com/apache/cordova-
> coho/blob/master/docs/release-voting.md
>
> Voting will go on for a minimum of 48 hours.
>
> I vote +1:
> * Ran coho audit-license-headers over the relevant repos
> * Ran coho check-license to ensure all dependencies and subdependencies
> have Apache-compatible licenses
> * Ensured continuous build was green when repo was tagged
> * Short tests that IAB and camera plugin are available in a new hello
> world project
> * Tests pass locally
>

Re: [DISCUSS] Release cordova-osx platform 6.0.1

[pieter van poyer]

Hi

I agree to deprecate the OSX platform, and the blog post would be a good
moment to announce the deprecation.

However, I have no experience with the Catalyst workflow. But I am always
sceptical with Mac tools, a lot of times it is too much closed source IMO.

But when I think about making a webbased crossplatform native desktop app,
I would automatically look at Electron.
I have some experience with Electron (not with the electron cordova
platform), and I did like developing the web part of an Electron app.
When working on the installers and native progressbars and stuff like that
it became more difficult.
We did develop our Electron app for Windows.

As I said, I have no experience with the Cordova Electron platform, but *if
it is cross platform and it supports building for OSx, Linux and Windows*,
I would suggest the *Electron Cordova platform (or Electron plain) platform
as an alternative*.

Kind regards
Pieter

Op di 1 feb. 2022 om 21:05 schreef Chris Brody :

> I think there is an issue with using plug-ins together with Cordova-osx
> would be happy to further explain or demonstrate if needed.
>
> On Tue, Feb 1, 2022, 2:43 PM Niklas Merz  wrote:
>
> > Hi all,
> >
> > I just merged a PR [1] that makes the OSX platform work on M1 Macs,
> > because some people need it. The platform hasn't seen much activity but
> > I step up to fix up the version number in master and do a small patch
> > release if nobody objects.
> >
> > With a release we could make a small userbase happy and use the
> > announcement blog post to ask them to try out Catalyst with cordova-ios.
> >
> > I remember we had discussions to deprecate the platform as we focus our
> > resouces on Android and iOS and Catalyst which let's you run iOS apps on
> > macOS [2]. But I remember no formal decission to deprecate it so far.
> > Maybe we get some feedback to finally make the decission.
> >
> > What do you think?
> >
> > Regards
> > Niklas
> >
> >
> >
> >
> > [1] https://github.com/apache/cordova-osx/pull/105
> > [2] https://lists.apache.org/thread/lqq2xoy3pjqcyl052gv0qom2f31zgg8k
> >
>

Re: [VOTE] Media Plugin 5.0.4 Release

[pieter van poyer]

I vote +1
* changes look good

Op vr 21 jan. 2022 17:12 schreef Niklas Merz :

> I vote +1
>
> * signature and hash ok
> * tag ok
> * npm ok
> * no license issues
> * changes look good
>
> On January 21, 2022, Norman Breau  wrote:
> > I vote +1:
> >
> > * Ran npm audit locally (linux, no found vulnerabilities)
> > * Ran npm test locally (linux, only eslint runs, no raised issues)
> > * Tags verified
> > * Archive verified
> >
> > On 2022-01-21 8:18 a.m., Bryan Ellis wrote:
> > > Please review and vote on this Cordova Plugin Media Release v5.0.4
> > > by replying to this email (and keep discussion on the DISCUSS
> > thread)
> > >
> > > The archive has been published to dist/dev:
> > >
> > > https://dist.apache.org/repos/dist/dev/cordova/media-v5.0.4
> > >
> > > The package was published from its corresponding git tag:
> > >
> > > cordova-plugin-media: 5.0.4 (fcc8db2696)
> > >
> > > Upon a successful vote I will upload the archive to dist/, publish
> > it to npm, and post the blog post.
> > >
> > > Voting guidelines: https://github.com/apache/cordova-
> > coho/blob/master/docs/release-voting.md
> > >
> > > Voting will go on for a minimum of 48 hours.
> > >
> > > 
> > >
> > > I vote +1:
> > >
> > > * Ran coho audit-license-headers over the relevant repos
> > > * Ran coho check-license to ensure all dependencies and sub-
> > dependencies have Apache-compatible licenses
> > > * Ensured the npm audit report was sufficient for release
> > >
> > > * AS there are CI testing and latest platform related issues, I have
> > manually tested:
> > > * Build Mobile Spec project for iOS & Android w/ CLI
> > > * Run Mobile Spec project on iOS & Android simulator w/ CLI
> > > * Executed the Mobile Spec Jasmine tests on iOS & Android
> > >
> > > Audit Report:
> > >
> > > 0 vulnerabilities found
> > >
> > >
> > >
> > >
> > -
> > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > > For additional commands, e-mail: dev-h...@cordova.apache.org
> > >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > For additional commands, e-mail: dev-h...@cordova.apache.org
>

Re: [VOTE] cordova-cli 11.0.0 Release

[pieter van poyer]

I vote +1:

* changes look good.

Kind regards
Pieter Van Poyer

Op za 18 dec. 2021 om 13:09 schreef Niklas Merz :

> I vote +1:
>
> I checked:
>
> * signature and hash ok
> * license and notice look good
> * headers look good
> * basic tests with cli successfull
> * latest android, ios and electron platforms default
>
> On December 17, 2021, Erisu  wrote:
> > Please review and vote on this cordova-cli release v11.0.0
> > by replying to this email (and keep discussion on the DISCUSS thread)
> >
> > The archive has been published to dist/dev:
> >
> >  https://dist.apache.org/repos/dist/dev/cordova/cli-11.0.0
> >
> > The package was published from its corresponding git tag:
> >
> >  cordova-cli: 11.0.0 (94a5b68075)
> >
> > Upon a successful vote I will upload the archive to dist/, publish it
> > to npm, and post the blog post.
> >
> > Voting guidelines: https://github.com/apache/cordova-
> > coho/blob/master/docs/release-voting.md
> >
> > Voting will go on for a minimum of 48 hours.
> >
> > I vote +1:
> >
> > * Ran coho audit-license-headers over the relevant repos
> > * Ran coho check-license to ensure all dependencies and sub-
> > dependencies have Apache-compatible licenses
> > * Ensured the continuous build was green when repo was tagged
> > * Ran `npm test`
> >
> > * Ran `npm audit`
> >  8 moderate severity vulnerabilities
> >  Five of the vulnerabilities are related to the "insight" dependency,
> > a production dependency.
> >  The suggested solution by npm, to downgrade to `insight@0.8.4`, is
> > not a viable solution. The current version which we are using
> > introduced macOS Monteray support. Downgrading will break support for
> > macOS users.
> >
> > * Ran various `cordova` test w/ sample app:
> >  * `cordova`
> >  * `cordova -v`
> >  * `cordova create`
> >  * `cordova info`
> >  * `cordova help`
> >  * `cordova config ls`
> >  * `cordova requirements`
> >  * `cordova telemetry`
> >  * `cordova plugin`
> >  * `cordova plugin add`
> >  * `cordova plugin rm`
> >  * `cordova platform`
> >  * `cordova platform add`
> >  * `cordova platform rm`
> >  * `cordova build`
> >  * `cordova prepare`
> >  * `cordova compile`
> >  * `cordova run`
> >  * `cordova serve`
>

Re: [VOTE] Cordova-Android 10.1.0 Release

[pieter van poyer]

I vote +1

Changes look good.

Op vr 13 aug. 2021 08:53 schreef Niklas Merz :

> I vote +1 (binding).
>
> I checked:
>
> - Hash & Signature
> - Tag Hash
> - Tests pass locally
> - License exists
> - License headers
>
> On August 13, 2021, Benjamin Tietze  wrote:
> > I vote +1 (non-binding)
> >
> > I checked the following:
> > - Licence
> > - Change log
> > - Quick test with our app
> > - Release Hash
> >
> >
> > Am Fr., 13. Aug. 2021 um 07:06 Uhr schrieb Bryan Ellis
> > :
> >
> > > Please review and vote on this Cordova-Android Release v10.1.0
> > > by replying to this email (and keep discussion on the DISCUSS
> > thread)
> > >
> > > The archive has been published to dist/dev:
> > > https://dist.apache.org/repos/dist/dev/cordova/android-v10.1.0
> > >
> > > The package was published from its corresponding git tag:
> > > cordova-android: 10.1.0 (c3fd6bca4a)
> > >
> > > Note that you can test it out via:
> > >
> > > cordova platform add https://github.com/apache/cordova-
> > android#10.1.0
> > >
> > > Upon a successful vote I will upload the archive to dist/, publish
> > it to
> > > npm, and post the blog post.
> > >
> > > Voting guidelines:
> > > https://github.com/apache/cordova-coho/blob/master/docs/release-
> > voting.md
> > >
> > > Voting will go on for a minimum of 48 hours.
> > >
> > > ===
> > >
> > > I vote +1:
> > >
> > > * Ran coho audit-license-headers over the relevant repos
> > > * Ran coho check-license to ensure all dependencies and
> > subdependencies
> > > have Apache-compatible licenses
> > > * Ensured continuous build was green when repo was tagged
> > > * NPM Audit (See Below)
> > > * NPM Test (Executed Individual Steps in Order)
> > > * npm run lint
> > > * npm run unit-test
> > > * npm run e2e-tests
> > > * npm run java-unit-tests
> > > * Ran `cordova build` test
> > > * Ran `cordova run` emulator test
> > > * Ran `cordova plugin add` test
> > >
> > >
> > > ==NPM Audit Report==
> > >
> > > One moderate severity vulnerability was detected. It is from a
> > > sub-dependencies of cordova-common. Rebuilding the package-lock.json
> > for
> > > this package does not resolve it. The "cordova-common" package will
> > require
> > > a new release in the future. This detection should not block this
> > > cordova-android release vote.
> > >
> > -
> > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > > For additional commands, e-mail: dev-h...@cordova.apache.org
> > >
> > >
>

Re: [VOTE] Camera Plugin Release v5.0.3

[pieter van poyer]

I vote +1

* changes look good


Op do 5 aug. 2021 om 16:15 schreef Niklas Merz :

> I vote +1
>
> I checked:
>
> * hash
> * signature
> * tag
> * changes look good
>
> On August 4, 2021, Erisu  wrote:
> > Please review and vote on this Cordova Plugin Camera Release v5.0.3
> > by replying to this email (and keep discussion on the DISCUSS thread)
> >
> > The archive has been published to dist/dev:
> > https://dist.apache.org/repos/dist/dev/cordova/camera-v5.0.3
> >
> > The package was published from its corresponding git tag:
> >  cordova-plugin-camera: 5.0.3 (d523142cf2)
> >
> > Upon a successful vote I will upload the archive to dist/, publish it
> > to npm, and post the blog post.
> >
> > Voting guidelines: https://github.com/apache/cordova-
> > coho/blob/master/docs/release-voting.md
> >
> > Voting will go on for a minimum of 48 hours.
> >
> > ==
> >
> > I vote +1:
> >
> > * Ran coho audit-license-headers over the relevant repos
> > * Ran coho check-license to ensure all dependencies and sub-
> > dependencies have Apache-compatible licenses
> > * Ensured the npm audit report was sufficient for release
> >
> > * AS there are issues within the CI testing service accross ALL
> > plugins, for this release I have manually tested:
> >  * Build Mobile Spec project for iOS & Android w/ CLI
> >  * Run Mobile Spec project on iOS & Android simulator w/ CLI
> >  * Executed the Mobile Spec Jasmine tests on iOS & Android
> >
> > Audit Report:
> >
> >  0 vulnerabilities found
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > For additional commands, e-mail: dev-h...@cordova.apache.org
>

Re: [VOTE] Cordova-Android 10.0.0 Release

[pieter van poyer]

I vote +1

Changes look good.
I am unable to do any further testing right now.

Kind regards
Pieter

Op za 17 jul. 2021 10:42 schreef Niklas Merz :

> I vote +1
>
> I did:
>
> * checked signature
> * checked hash
> * checked license
> * checked git tag
> * tests pass locally
> * ci green
> * no lint issues
> * short test with new and existing app
>
> On July 17, 2021, Erisu  wrote:
> > Please review and vote on this Android Release v10.0.0
> > by replying to this email (and keep discussion on the DISCUSS thread)
> >
> > The archive has been published to dist/dev:
> > https://dist.apache.org/repos/dist/dev/cordova/android-v10.0.0/
> >
> > The package was published from its corresponding git tag:
> >  cordova-android: 10.0.0 (7572fc4912)
> >
> > Note that you can test it out via:
> >
> >  cordova platform add https://github.com/apache/cordova-android#10.0.0
> >
> > Upon a successful vote I will upload the archive to dist/, publish it
> > to npm, and post the blog post.
> >
> > Voting guidelines: https://github.com/apache/cordova-
> > coho/blob/master/docs/release-voting.md
> >
> > Voting will go on for a minimum of 48 hours.
> >
> > I vote +1:
> > * Ran coho audit-license-headers over the relevant repos
> > * Ran coho check-license to ensure all dependencies and
> > subdependencies have Apache-compatible licenses
> > * Ensured continuous build was green when repo was tagged
> > * NPM Audit
> > * NPM Test (Executed Individual Steps in Order)
> >  * npm run lint
> >  * npm run unit-test
> >  * npm run e2e-tests
> >  * npm run java-unit-tests
> > * Ran `cordova build` test
> > * Ran `cordova run` emulator test
> > * Ran `cordova plugin add` test
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > For additional commands, e-mail: dev-h...@cordova.apache.org
>

Re: [VOTE] cordova-js 6.1.0 Release

[pieter van poyer]

I vote +1:
* Tested it with a cordova-android 9.0  with a camera plugin project.

Op ma 12 jul. 2021 om 09:43 schreef :

> I vote +1:
> * CI was successful at tagged version
> * Set of changes is OK for a minor release
> * Uploaded tarball contains the expected files
> * cordova-electron#194
>  works
> with uploaded tarball
>
> Am Mo., 12. Juli 2021 um 06:30 Uhr schrieb Bryan Ellis :
>
> > Please review and vote on this cordova-js release v6.1.0
> > by replying to this email (and keep discussion on the DISCUSS thread)
> >
> > The archive has been published to dist/dev:
> > https://dist.apache.org/repos/dist/dev/cordova/js-6.1.0
> >
> > The package was published from its corresponding git tag:
> > cordova-js: 6.1.0 (ed4135a40f)
> >
> > Upon a successful vote I will upload the archive to dist/, publish it to
> > npm, and post the blog post.
> >
> > Voting guidelines:
> >
> https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
> >
> > Voting will go on for a minimum of 48 hours.
> >
> > I vote +1:
> > * Ran coho audit-license-headers over the relevant repos
> > * Ran coho check-license to ensure all dependencies and sub-dependencies
> > have Apache-compatible licenses
> > * Ensured the continuous build was green when repo was tagged
> > * Ensured the npm audit report was sufficient for release
> > * Ran `npm test`
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > For additional commands, e-mail: dev-h...@cordova.apache.org
> >
> >
>

[DISCUSS] Heic format on Android phones

[pieter van poyer]

Dear Cordova Devs

I'ld like to bring a little bit attention on next PR:
https://github.com/apache/cordova-plugin-camera/pull/731

The camera plugin can be configured to return a .png or a .jpeg image.
But when a wrong image type is selected then the image is returned in his
original type.

Samsung can work with .heic formats, when you take a picture the image is
returned in a .heic format. It is not possible to render the picture in an
img tag for example. I think we don't want to force backends to be able to
process this format.

So the PR transfers a .heic image to the encodingType (png or jpeg). This
seems to work great.
*What is your opinion on this? Is this okay? And can this be merged?*

*Should we try to do this same routine for other types too (like GIF, BMP,
... )?*
I'ld love to make a ticket for that.

As a side note, when you select a .gif file now, a .gif is returned, but
when you convert it to a .jpeg, then the animations are lost.
As a second side note, it seems like the ios implementation also returns a
..jpeg after selecting a .gif, and the animations are lost.

Kind regards
Pieter

[ANNOUNCE] Plugin Release cordova-plugin-whitelist

[pieter van poyer]

cordova-plugin-whitelist@1.3.5 has been released!

Blog:
https://cordova.apache.org/news/2021/06/28/whitelist-plugin-release.html

RE: [VOTE] Whitelist 1.3.5 Plugins Release

[pieter van poyer]

The vote has now closed. The results are:

Positive Binding Votes: 3

Niklas Merz
Norman Breau
Pieter van Poyer

Negative Binding Votes: 0 Other Votes: 0

The vote has passed.

Thank you all for your time.

Pieter Van Poyer



-Oorspronkelijk bericht-
Van: Niklas Merz 
Verzonden: dinsdag 29 juni 2021 08:05
Aan: dev@cordova.apache.org
Onderwerp: Re: [VOTE] Whitelist 1.3.5 Plugins Release



I vote +1



* checked hash and signature

* no audit issues

* checked version numbers

* verified tag



On June 29, 2021, Norman Breau  wrote:

> I vote +1:

>

> * Ran verify-archive

> * Ran verify-tags

> * Checked Travis CI for mentioned failure -- Appears to be

>  failing when testing against iOS, despite this plugin having an

> iOS implementation.

>  Agreed that this is not a blocker for this release, which is to

> finalize the deprecation of this plugin.

>

> On 2021-06-28 4:51 p.m., pieter van poyer wrote:

> > Please review and vote on the release of this plugins release by

> > replying to this email (and keep discussion on the DISCUSS thread)

> >

> > The plugins have been published to dist/dev:

> > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdi

> > st.apache.org%2Frepos%2Fdist%2Fdev%2Fcordova%2Fcordova-plugin-d

> > ata=04%7C01%7CPieter.VanPoyer%40portofantwerp.com%7Ccd245db608f74cbc

> > 782e08d93ac3e3b5%7C2337dcc63a214d95bf72da5551a9b048%7C0%7C0%7C637605

> > 435303513649%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2l

> > uMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=PYjn%2FL7ULApGB

> > ueeAaxYHMhtEL8jbJQP%2FL0LYR7HeHY%3Dreserved=0

> whitelist20210626/

> >

> > The packages were published from their corresponding git tags:

> > cordova-plugin-whitelist: 1.3.5 (2e5db06c9a)

> >

> > Upon a successful vote I will upload the archives to dist/, upload

> > them to npm, and post the corresponding blog post.

> >

> > Voting guidelines:

> > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgi

> > thub.com%2Fapache%2Fcordova-coho%2Fblob%2Fmaster%2Fdocs%2Frelease-

> > mp;data=04%7C01%7CPieter.VanPoyer%40portofantwerp.com%7Ccd245db608f7

> > 4cbc782e08d93ac3e3b5%7C2337dcc63a214d95bf72da5551a9b048%7C0%7C0%7C63

> > 7605435303513649%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjo

> > iV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=i03cXYYs10p

> > wxcVZ%2FSa%2FCDleia0O5PigSlHCJeIXEg0%3Dreserved=0

> voting.md

> > How to vote on a plugins release at

> > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgi

> > thub.com%2Fapache%2Fcordova-coho%2Fblob%2Fmaster%2Fdocs%2Fplugins-

> > mp;data=04%7C01%7CPieter.VanPoyer%40portofantwerp.com%7Ccd245db608f7

> > 4cbc782e08d93ac3e3b5%7C2337dcc63a214d95bf72da5551a9b048%7C0%7C0%7C63

> > 7605435303513649%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjo

> > iV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=RP9nGrslEku

> > %2Fm8kMtH06kxVaSbPfesALmFRkOIlTVXQ%3Dreserved=0

> release-process.md#voting

> >

> > Voting will go on for a minimum of 48 hours.

> >

> > I vote +1:

> > * Ran coho audit-license-headers over the relevant repos

> > * Ran coho check-license to ensure all dependencies and

> > subdependencies have Apache-compatible licenses

> > * Ensured continuous build was green when repos were tagged - some

> > MacOS CI builds are failing for a long time, no reason to delay the

> > reason.* Checked npm audit & npm outdated -> there are no npm

> > dependencies in the package.json

> >

> > Release notes:

> > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgi

> > thub.com%2Fapache%2Fcordova-plugin-data=04%7C01%7CPieter.VanPoy

> > er%40portofantwerp.com%7Ccd245db608f74cbc782e08d93ac3e3b5%7C2337dcc6

> > 3a214d95bf72da5551a9b048%7C0%7C0%7C637605435303513649%7CUnknown%7CTW

> > FpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVC

> > I6Mn0%3D%7C1000sdata=h8b4uZoNtq%2FZ9GKPQka6%2FNDYPXj0WxXWaJNtay

> > 91itc%3Dreserved=0

> whitelist/blob/1.3.x/RELEASENOTES.md#135-jun-26-2021

> > Announcement Blog Post PR:

> > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgi

> > thub.com%2Fapache%2Fcordova-data=04%7C01%7CPieter.VanPoyer%40po

> > rtofantwerp.com%7Ccd245db608f74cbc782e08d93ac3e3b5%7C2337dcc63a214d9

> > 5bf72da5551a9b048%7C0%7C0%7C637605435303513649%7CUnknown%7CTWFpbGZsb

> > 3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3

> > D%7C1000sdata=%2BVdWzxIiA%2BFdtEtHNDvak2g0KfVErEUMQYsMbMWpLtM%3

> > Dreserved=0

> docs/pull/1180

> >

> > Kind regards

> > Pieter

> >

>

> -

> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org

> For additional commands, e-mail: dev-h...@cordova.apache.org

[VOTE] Whitelist 1.3.5 Plugins Release

[pieter van poyer]

Please review and vote on the release of this plugins release by
replying to this email (and keep discussion on the DISCUSS thread)

The plugins have been published to dist/dev:
https://dist.apache.org/repos/dist/dev/cordova/cordova-plugin-whitelist20210626/

The packages were published from their corresponding git tags:
cordova-plugin-whitelist: 1.3.5 (2e5db06c9a)

Upon a successful vote I will upload the archives to dist/, upload
them to npm, and post the corresponding blog post.

Voting guidelines:
https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
How to vote on a plugins release at
https://github.com/apache/cordova-coho/blob/master/docs/plugins-release-process.md#voting

Voting will go on for a minimum of 48 hours.

I vote +1:
* Ran coho audit-license-headers over the relevant repos
* Ran coho check-license to ensure all dependencies and
subdependencies have Apache-compatible licenses
* Ensured continuous build was green when repos were tagged - some
MacOS CI builds are failing for a long time, no reason to delay the
reason.* Checked npm audit & npm outdated -> there are no npm
dependencies in the package.json

Release notes: 
https://github.com/apache/cordova-plugin-whitelist/blob/1.3.x/RELEASENOTES.md#135-jun-26-2021
Announcement Blog Post PR: https://github.com/apache/cordova-docs/pull/1180

Kind regards
Pieter

[DISCUSS] cordova-plugin-whitelist final release 1.3.5

[pieter van poyer]

Does anyone have any reason to delay a cordova-plugin-whitelist final
release patch 1.3.5 release? Any outstanding patches to land?

If not, I will try to start the release process shortly.

This release is meant to deprecate the plugin for the future
cordova-android 10.
On cordova-android 10, the plugin should not be installed anymore.

==Changes==

https://github.com/apache/cordova-plugin-whitelist/compare/rel/1.3.4...master

Kind regards

Pieter Van Poyer

[ANNOUNCE] Plugin Release

[pieter van poyer]

cordova-plugin-network-information@3.0.0 has been released!

Blog:
https://cordova.apache.org/news/2021/06/03/network-information-plugin-release.html

RE: [VOTE] Network Information 3.0.0 Plugins Release

[pieter van poyer]

The vote has now closed. The results are:



Positive Binding Votes: 3



Niklas Merz

Norman Breau

Pieter van Poyer



Negative Binding Votes: 0

Other Votes: 0



The vote has passed.



Thank you all for your time.



Pieter Van Poyer



-Oorspronkelijk bericht-
Van: Niklas Merz 
Verzonden: vrijdag 4 juni 2021 00:18
Aan: dev@cordova.apache.org
Onderwerp: Re: [VOTE] Network Information 3.0.0 Plugins Release



I vote +1



* checked hash & signature

* checked tag

* no audit issues

* checked license headers

* coho check-license success



Thanks Pieter for starting this long overdue release.



Just a tiny suggestion for your next release. package-lock.json still
contains the version with the -dev suffix. If you run npm install after the
the version changes it should change automatically. You could also change
it by hand.



This does not matter for the release because the published package won't
contain the package-lock file. It's just nicer in git because you now get
any uncommited changes if you checkout the tag and run npm install.



On June 3, 2021, Norman Breau  wrote:

> I vote +1:

>

> - Ran verify-archive

> - Ran verify-tags

> - Ran npm audit (0 vulnerabities found)

>

> On 2021-06-03 4:17 p.m., pieter van poyer wrote:

> > Please review and vote on the release of this plugins release by

> replying

> > to this email (and keep discussion on the DISCUSS thread)

> >

> >

> >

> > The plugins have been published to dist/dev:

> >

> > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdi

> > st.apache.org%2Frepos%2Fdist%2Fdev%2Fcordova%2Fcordova-plugin-d

> > ata=04%7C01%7CPieter.VanPoyer%40portofantwerp.com%7C6f49ddf8f5144ab3

> > c69d08d926dd64b4%7C2337dcc63a214d95bf72da5551a9b048%7C0%7C0%7C637583

> > 554596049893%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2l

> > uMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=Na4wwkyWmRn6qdR

> > RNlx58J1tN4xGoJAwHgwr7UEXJMQ%3Dreserved=0

> network-information20210603/

> >

> >

> >

> >

> > The packages were published from their corresponding git tags:

> >

> > cordova-plugin-network-information: 3.0.0 (96ad38fba2)

> >

> >

> >

> > Please also check the blog post:

> > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgi

> > thub.com%2Fapache%2Fcordova-docs%2Fpull%2F1176%2Ffilesdata=04%7

> > C01%7CPieter.VanPoyer%40portofantwerp.com%7C6f49ddf8f5144ab3c69d08d9

> > 26dd64b4%7C2337dcc63a214d95bf72da5551a9b048%7C0%7C0%7C63758355459605

> > 9888%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJ

> > BTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=wQQ%2BFTwXh8YJ3JpiJj6SN

> > YCTSURhI%2BpI71HLiHpLs2A%3Dreserved=0

> >

> >

> >

> > Upon a successful vote I will upload the archives to dist/, upload

> them to

> > npm, and post the corresponding blog post.

> >

> >

> > Voting guidelines:

> > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgi

> > thub.com%2Fapache%2Fcordova-coho%2Fblob%2Fmaster%2Fdocs%2Frelease-

> > mp;data=04%7C01%7CPieter.VanPoyer%40portofantwerp.com%7C6f49ddf8f514

> > 4ab3c69d08d926dd64b4%7C2337dcc63a214d95bf72da5551a9b048%7C0%7C0%7C63

> > 7583554596059888%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjo

> > iV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=fcO3KqfZH5s

> > rTwSku94spSBel8%2FRypqjbypEXTI18hQ%3Dreserved=0

> voting.md

> >

> >

> >

> > How to vote on a plugins release at

> > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgi

> > thub.com%2Fapache%2Fcordova-coho%2Fblob%2Fmaster%2Fdocs%2Fplugins-

> > mp;data=04%7C01%7CPieter.VanPoyer%40portofantwerp.com%7C6f49ddf8f514

> > 4ab3c69d08d926dd64b4%7C2337dcc63a214d95bf72da5551a9b048%7C0%7C0%7C63

> > 7583554596059888%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjo

> > iV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=cyRyDdZ0Ppj

> > YLbtYR5PczQaaq624aAjV8SEm%2FKLEzRI%3Dreserved=0

> release-process.md#voting

> >

> >

> >

> >

> > Voting will go on for a minimum of 48 hours.

> >

> >

> >

> > I vote +1:

> >

> > * Ran coho audit-license-headers over the relevant repos

> >

> > * Ran coho check-license to ensure all dependencies and

> subdependencies

> > have Apache-compatible licenses

> >

> > * Ensured continuous build was green when repos were tagged

> >

> >

> >

> > * Checked npm audit & npm outdated

> >

> >

> >

> > Kind regards

> >

> >

> >

> > Pieter Van Poyer

> >

>

> -

> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org

> For additional commands, e-mail: dev-h...@cordova.apache.org

[VOTE] Network Information 3.0.0 Plugins Release

[pieter van poyer]

Please review and vote on the release of this plugins release by replying
to this email (and keep discussion on the DISCUSS thread)



The plugins have been published to dist/dev:

https://dist.apache.org/repos/dist/dev/cordova/cordova-plugin-network-information20210603/




The packages were published from their corresponding git tags:

cordova-plugin-network-information: 3.0.0 (96ad38fba2)



Please also check the blog post:
https://github.com/apache/cordova-docs/pull/1176/files



Upon a successful vote I will upload the archives to dist/, upload them to
npm, and post the corresponding blog post.


Voting guidelines:
https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md



How to vote on a plugins release at
https://github.com/apache/cordova-coho/blob/master/docs/plugins-release-process.md#voting




Voting will go on for a minimum of 48 hours.



I vote +1:

* Ran coho audit-license-headers over the relevant repos

* Ran coho check-license to ensure all dependencies and subdependencies
have Apache-compatible licenses

* Ensured continuous build was green when repos were tagged



* Checked npm audit & npm outdated



Kind regards



Pieter Van Poyer

[DISCUSS] cordova-plugin-network-information major release 3.0.0

[Pieter Van Poyer]

Does anyone have any reason to delay a cordova-plugin-network-information major 
3.0.0 release? Any outstanding changes to land?

If not, I will try to start the release process shortly.

==Changes== 
https://github.com/apache/cordova-plugin-network-information/compare/rel/2.0.2...master

Kind regards

Pieter Van Poyer



Deze e-mail en alle gekoppelde bestanden zijn officiele documenten van 
Havenbedrijf Antwerpen NV van publiek recht en kunnen vertrouwelijke of 
persoonlijke informatie bevatten. Gelieve de afzender onmiddellijk via e-mail 
of telefonisch te verwittigen als u deze e-mail per vergissing heeft ontvangen 
en verwijder vervolgens de e-mail zonder deze te lezen, te reproduceren, te 
verspreiden of te ontsluiten naar derden. Havenbedrijf Antwerpen NV van publiek 
recht is op geen enkele manier verantwoordelijk voor fouten of 
onnauwkeurigheden in de inhoud van deze e-mail. Havenbedrijf Antwerpen NV van 
publiek recht kan niet aansprakelijk gesteld worden voor directe of indirecte 
schade, verlies of ongemak veroorzaakt als gevolg van een onnauwkeurigheid of 
fout in deze e-mail.

English Translation: This e-mail and all attached files are official documents 
of Antwerp Port Authority and may contain confidential or personal information. 
If you have received this e-mail in error, you are asked to inform the sender 
by e-mail or telephone immediately, and to remove it from your system without 
reading or reproducing it or passing it on to other parties. Antwerp Port 
Authority is in no way responsible for any errors or inaccuracies in the 
contents of this e-mail, nor can it be held liable for any direct or indirect 
loss, damage or inconvenience arising from any such errors or inaccuracies.

Subject: [ANNOUNCE] Camera Plugin Release

[Pieter Van Poyer]

cordova-plugin-camera@5.0.2 has been released!

Blog: https://cordova.apache.org/news/2021/05/11/camera-plugin-release.html

Kind regards
Pieter Van Poyer




Deze e-mail en alle gekoppelde bestanden zijn officiele documenten van 
Havenbedrijf Antwerpen NV van publiek recht en kunnen vertrouwelijke of 
persoonlijke informatie bevatten. Gelieve de afzender onmiddellijk via e-mail 
of telefonisch te verwittigen als u deze e-mail per vergissing heeft ontvangen 
en verwijder vervolgens de e-mail zonder deze te lezen, te reproduceren, te 
verspreiden of te ontsluiten naar derden. Havenbedrijf Antwerpen NV van publiek 
recht is op geen enkele manier verantwoordelijk voor fouten of 
onnauwkeurigheden in de inhoud van deze e-mail. Havenbedrijf Antwerpen NV van 
publiek recht kan niet aansprakelijk gesteld worden voor directe of indirecte 
schade, verlies of ongemak veroorzaakt als gevolg van een onnauwkeurigheid of 
fout in deze e-mail.

English Translation: This e-mail and all attached files are official documents 
of Antwerp Port Authority and may contain confidential or personal information. 
If you have received this e-mail in error, you are asked to inform the sender 
by e-mail or telephone immediately, and to remove it from your system without 
reading or reproducing it or passing it on to other parties. Antwerp Port 
Authority is in no way responsible for any errors or inaccuracies in the 
contents of this e-mail, nor can it be held liable for any direct or indirect 
loss, damage or inconvenience arising from any such errors or inaccuracies.

RE: [VOTE] Camera 5.0.2 Plugins Release

[Pieter Van Poyer]

The vote has now closed. The results are:

Positive Binding Votes: 3

Niklas Merz
Norman Breau
Pieter van Poyer

Negative Binding Votes: 0
Other Votes: 0

The vote has passed.

Thank you all for your time.

Pieter Van Poyer

-Oorspronkelijk bericht-
Van: Niklas Merz 
Verzonden: woensdag 12 mei 2021 08:42
Aan: dev@cordova.apache.org
Onderwerp: Re: [VOTE] Camera 5.0.2 Plugins Release

I vote +1

* checked hash and signature
* npm test passes locally
* CI green for tagged commit
* changes look good 
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fcordova-plugin-data=04%7C01%7CPieter.VanPoyer%40portofantwerp.com%7Cb4af8b94c5a245f460b908d91542%7C2337dcc63a214d95bf72da5551a9b048%7C0%7C0%7C637563985324597019%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=APT%2FEYz1PWKKwTY7P5E59NQjOv%2F4ygrXgf17CZJG29I%3Dreserved=0
camera/compare/rel/5.0.1...5.0.2
* checked tag
* small local smoke test

On May 12, 2021, Norman Breau  wrote:
> I vote +1:
> * Ran verify-tags
> * Ran verify-archive
> * Ran npm test locally
>
> On 2021-05-11 7:27 p.m., Pieter Van Poyer wrote:
> > Please review and vote on the release of this plugins release by
> > replying to this email (and keep discussion on the DISCUSS
> thread)
> >
> > The plugins have been published to dist/dev:
> > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdi
> > st.apache.org%2Frepos%2Fdist%2Fdev%2Fcordova%2Fcordova-plugin-d
> > ata=04%7C01%7CPieter.VanPoyer%40portofantwerp.com%7Cb4af8b94c5a245f4
> > 60b908d91542%7C2337dcc63a214d95bf72da5551a9b048%7C0%7C0%7C637563
> > 985324597019%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2l
> > uMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=ik0%2FAB56Bg%2B
> > R6QZ902weY26Iqr78JiTZ%2FCLp%2Bnlq9mw%3Dreserved=0
> camera20210511/
> >
> > The packages were published from their corresponding git tags:
> > cordova-plugin-camera: 5.0.2 (e419a74546)
> >
> > Please also check the blog post:
> > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgi
> > thub.com%2Fapache%2Fcordova-data=04%7C01%7CPieter.VanPoyer%40po
> > rtofantwerp.com%7Cb4af8b94c5a245f460b908d91542%7C2337dcc63a214d9
> > 5bf72da5551a9b048%7C0%7C0%7C637563985324597019%7CUnknown%7CTWFpbGZsb
> > 3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3
> > D%7C1000sdata=m8YTkZqQVHDjLWsJ%2BpVuTmGhpTixLz19F8YWFeyGEFw%3D&
> > amp;reserved=0
> docs/pull/1174
> >
> > Upon a successful vote I will upload the archives to dist/, upload
> them to npm, and post the corresponding blog post.
> >
> > Voting guidelines:
> > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgi
> > thub.com%2Fapache%2Fcordova-data=04%7C01%7CPieter.VanPoyer%40po
> > rtofantwerp.com%7Cb4af8b94c5a245f460b908d91542%7C2337dcc63a214d9
> > 5bf72da5551a9b048%7C0%7C0%7C637563985324597019%7CUnknown%7CTWFpbGZsb
> > 3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3
> > D%7C1000sdata=m8YTkZqQVHDjLWsJ%2BpVuTmGhpTixLz19F8YWFeyGEFw%3D&
> > amp;reserved=0
> coho/blob/master/docs/release-voting.md
> > How to vote on a plugins release at
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgith
> ub.com%2Fapache%2Fcordova-coho%2Fblob%2Fmaster%2Fdocs%2Fplugins-d
> ata=04%7C01%7CPieter.VanPoyer%40portofantwerp.com%7Cb4af8b94c5a245f460
> b908d91542%7C2337dcc63a214d95bf72da5551a9b048%7C0%7C0%7C6375639853
> 24597019%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiL
> CJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=4JcYr%2FU%2FjdmbABR4UMr
> Rj%2FhpPO4z4lTEWYIJH0ZNM%2FY%3Dreserved=0
> release-process.md#voting
> >
> > Voting will go on for a minimum of 48 hours.
> >
> > I vote +1:
> > * Ran coho audit-license-headers over the relevant repos
> > * Ran coho check-license to ensure all dependencies and
> subdependencies have Apache-compatible licenses
> > * Ensured continuous build was green when repos were tagged
> >
> > * Checked npm audit & npm outdated
> >
> > Kind regards
> >
> > Pieter Van Poyer
> >
> > 
> >
> > Deze e-mail en alle gekoppelde bestanden zijn officiele documenten
> van Havenbedrijf Antwerpen NV van publiek recht en kunnen
> vertrouwelijke of persoonlijke informatie bevatten. Gelieve de
> afzender onmiddellijk via e-mail of telefonisch te verwittigen als u
> deze e-mail per vergissing heeft ontvangen en verwijder vervolgens de
> e-mail zonder deze te lezen, te reproduceren, te verspreiden of te
> ontsluiten naar derden. Havenbedrijf Antwerpen NV van publiek re

[VOTE] Camera 5.0.2 Plugins Release

[Pieter Van Poyer]

Please review and vote on the release of this plugins release
by replying to this email (and keep discussion on the DISCUSS thread)

The plugins have been published to dist/dev:
https://dist.apache.org/repos/dist/dev/cordova/cordova-plugin-camera20210511/

The packages were published from their corresponding git tags:
cordova-plugin-camera: 5.0.2 (e419a74546)

Please also check the blog post: 
https://github.com/apache/cordova-docs/pull/1174

Upon a successful vote I will upload the archives to dist/, upload them to npm, 
and post the corresponding blog post.

Voting guidelines: 
https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
How to vote on a plugins release at 
https://github.com/apache/cordova-coho/blob/master/docs/plugins-release-process.md#voting

Voting will go on for a minimum of 48 hours.

I vote +1:
* Ran coho audit-license-headers over the relevant repos
* Ran coho check-license to ensure all dependencies and subdependencies have 
Apache-compatible licenses
* Ensured continuous build was green when repos were tagged

* Checked npm audit & npm outdated

Kind regards

Pieter Van Poyer



Deze e-mail en alle gekoppelde bestanden zijn officiele documenten van 
Havenbedrijf Antwerpen NV van publiek recht en kunnen vertrouwelijke of 
persoonlijke informatie bevatten. Gelieve de afzender onmiddellijk via e-mail 
of telefonisch te verwittigen als u deze e-mail per vergissing heeft ontvangen 
en verwijder vervolgens de e-mail zonder deze te lezen, te reproduceren, te 
verspreiden of te ontsluiten naar derden. Havenbedrijf Antwerpen NV van publiek 
recht is op geen enkele manier verantwoordelijk voor fouten of 
onnauwkeurigheden in de inhoud van deze e-mail. Havenbedrijf Antwerpen NV van 
publiek recht kan niet aansprakelijk gesteld worden voor directe of indirecte 
schade, verlies of ongemak veroorzaakt als gevolg van een onnauwkeurigheid of 
fout in deze e-mail.

English Translation: This e-mail and all attached files are official documents 
of Antwerp Port Authority and may contain confidential or personal information. 
If you have received this e-mail in error, you are asked to inform the sender 
by e-mail or telephone immediately, and to remove it from your system without 
reading or reproducing it or passing it on to other parties. Antwerp Port 
Authority is in no way responsible for any errors or inaccuracies in the 
contents of this e-mail, nor can it be held liable for any direct or indirect 
loss, damage or inconvenience arising from any such errors or inaccuracies.

Subject: [DISCUSS] cordova-plugin-camera patch release 5.0.2

[Pieter Van Poyer]

Does anyone have any reason to delay a cordova-plugin-camera patch 5.0.2 
release?
Any outstanding patches to land?


If not, I will try to start the release process shortly.


==Changes==
https://github.com/apache/cordova-plugin-camera/compare/rel/5.0.1...master


Kind regards
Pieter Van Poyer



Deze e-mail en alle gekoppelde bestanden zijn officiele documenten van 
Havenbedrijf Antwerpen NV van publiek recht en kunnen vertrouwelijke of 
persoonlijke informatie bevatten. Gelieve de afzender onmiddellijk via e-mail 
of telefonisch te verwittigen als u deze e-mail per vergissing heeft ontvangen 
en verwijder vervolgens de e-mail zonder deze te lezen, te reproduceren, te 
verspreiden of te ontsluiten naar derden. Havenbedrijf Antwerpen NV van publiek 
recht is op geen enkele manier verantwoordelijk voor fouten of 
onnauwkeurigheden in de inhoud van deze e-mail. Havenbedrijf Antwerpen NV van 
publiek recht kan niet aansprakelijk gesteld worden voor directe of indirecte 
schade, verlies of ongemak veroorzaakt als gevolg van een onnauwkeurigheid of 
fout in deze e-mail.

English Translation: This e-mail and all attached files are official documents 
of Antwerp Port Authority and may contain confidential or personal information. 
If you have received this e-mail in error, you are asked to inform the sender 
by e-mail or telephone immediately, and to remove it from your system without 
reading or reproducing it or passing it on to other parties. Antwerp Port 
Authority is in no way responsible for any errors or inaccuracies in the 
contents of this e-mail, nor can it be held liable for any direct or indirect 
loss, damage or inconvenience arising from any such errors or inaccuracies.

RE: [DISCUSS] Moving forward with the WebView on AndroidX and cordova-android 10

[Pieter Van Poyer]

Hey

I have to agree with Bryan and Julio.
Make it opt-out with a next major release. That's my prefered option.

A lot of Cordova users will never enable this feature if it is an opt-in 
feature.
And yes it would be great if someone did already have some guidelines about 
data migration.

Kind regards
Pieter Van Poyer


-Oorspronkelijk bericht-
Van: Niklas Apache 
Verzonden: woensdag 28 april 2021 12:14
Aan: dev@cordova.apache.org
Onderwerp: Re: [DISCUSS] Moving forward with the WebView on AndroidX and 
cordova-android 10

I would agree with Bryan and Julio that we should use the opportunity of this 
breaking release to move the defaults to current Android best practices and 
remove deprecated settings.

I just started a PR [1] that introduces a preference to allow the use file URLs 
with this release. This means the deprecated settings [2][3] are only set with 
this settings as well. Darryl is right that probably many still need to run 
their app on the file protocol and they should have an easy option to do this 
with the new release. We can now push new users to avoid this and current users 
need to check the change log and enable this if they really need to.

I agree we shouldn't take the responsibilty of a data migration.

If we don't find consensus to make the WebViewAssetLoader opt-out we could make 
it opt-in for now. This would make the upgrade more safe but potentially many 
apps less secure because developers don't need to think about this change.

[1] 
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fcordova-android%2Fpull%2F1222data=04%7C01%7CPieter.VanPoyer%40portofantwerp.com%7C3874f4566f504fbf6fca08d90a2e5037%7C2337dcc63a214d95bf72da5551a9b048%7C0%7C0%7C637552016304717784%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=yaRNsgmiLk6XqWC3NgWiceVCCF4RiEcwDzFuYzVVU%2Fg%3Dreserved=0
[2]
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdeveloper.android.com%2Freference%2Fandroid%2Fwebkit%2FWebSettings%23setAllowUniversalAccessFromFileURLsdata=04%7C01%7CPieter.VanPoyer%40portofantwerp.com%7C3874f4566f504fbf6fca08d90a2e5037%7C2337dcc63a214d95bf72da5551a9b048%7C0%7C0%7C637552016304717784%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=ZbClSYsggi0ckZgdsSOHJ1Tq6zermY2krIB4zWjngcw%3Dreserved=0(boolean)
[3]https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdeveloper.android.com%2Freference%2Fandroid%2Fwebkit%2FWebSettings%23setAllowFileAccessdata=04%7C01%7CPieter.VanPoyer%40portofantwerp.com%7C3874f4566f504fbf6fca08d90a2e5037%7C2337dcc63a214d95bf72da5551a9b048%7C0%7C0%7C637552016304717784%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=e%2FP3sN894F9SIYkkBSE9Q%2BFz%2FowbKUu4r1le8TgIcf4%3Dreserved=0(boolean)

On April 28, 2021, julio cesar sanchez  wrote:
> My understanding is that file urls can technically continue working,
> but the defaults changed and some settings need to be enabled, and
> some of them are now deprecated and will stop working at some point in
> the future.
>
> I think defaulting to the old behavior is ok when doing minor releases
> (not just on, but enforced because otherwise it's a breaking change),
> but whenever we make a major release, we should always use the new
> behavior and make the cordova user responsibility to enable the old
> behavior if they need it, because to not "break" existing apps we will
> make all new apps to face the same problem in the future.
>
> About the data loss, the data is not really lost, the data is still
> there, but since the scheme and hostname change it's not accesible
> anymore, so if the cordova users can enable the old behavior they'll
> get the data back and should be their responsibility to do so if
> needed and do it before releasing a new version. We should of course
> warn about it so they will be aware if they read the release blog post
> or change log.
>
> If cordova does the data migration is when we can screw up and do it
> wrong and cause the massive data loss for all users, I prefer to not
> put that responsibility into the project. You have not tried to do it
> in your own apps because it's risky, would you be confident to do it
> for all users?
>
> 2021-04-27 21:15 GMT+02:00, Darryl Pogue :
> > To counter a bit, all of my apps are using the standard Cordova
> > Android WebView, and store all their data in the browser's
> indexedDB.
> > I've had no issues with file URLs (although I expect that will
> change
> > with API 30 enforcement).
> >
> > Losing data in an app update is unacceptable, and for many apps it
> > would be catastrophic (see comments from when Google did a bad
> > indexedDB migration and people lost data[1]). On iOS with WKW

RE: GitHub Actions for paramedic and plugins

[Pieter Van Poyer]

Hey Tim

I am maybe a little late to the party. But this is a great effort.

It would be absolutely great to have a stable and working CI (testing) system.
Now when you submit a PR, the tests on CI are mostly red. That's annoying.

Losing ios 11.4 wouldn't be a disaster.

Kind regards

Pieter Van Poyer
1700
DI/DB

Havenbedrijf Antwerpen/Antwerp Port Authority
Zaha Hadidplein 1
2030 Antwerpen, België
T +32 3 229 76 85
pieter.vanpo...@portofantwerp.com





-Oorspronkelijk bericht-
Van: Brust, Tim 
Verzonden: donderdag 26 november 2020 15:26
Aan: dev@cordova.apache.org
Onderwerp: GitHub Actions for paramedic and plugins

Hi there,

As you might have noticed, our CI is currently red. While it's great that we do 
not block our releases because of it, it's not an ideal situation.

A short background why is broken:
We use Travis CI's virtual machines to execute our tests in combination with 
Sauce Labs, i.e., cordova-paramedic that runs on the Travis CI VM  opens a 
secure tunnel to the Sauce Labs selenium grid.
This allows for instance to test an iOS simulator on a Windows machine, as the 
simulator/emulator runs on another machine and communicates via the WebDriver 
protocol.
Sauce Labs offers real mobile devices and virtualized ones. We only use the 
latter. [1] Unfortunately, there is a network issue between the Sauce Labs and 
the Travis CI VM's, the tunnel seems established but no network requests come 
through - but not for all combos, just for some.
I've reached out to Travis CI's support and they pointed the finger to Sauce 
Labs.
Multiple attempts to have a real network engineer assigned to this task instead 
of the service level 1 assignee failed and they've just closed the ticket.

On top of this issue lies the problem with external contributions (i.e., 
outside from the Apache organization). Obviously, Sauce Labs needs some sort of 
credentials to work. We use the deprecated JWT addon at Travis [2], which might 
be disabled at any time, too.
Sadly, there is no known solution on how to securely pass the credentials to 
external forks/pull requests. There is no solution on how to make secrets 
available to forks on GitHub Actions neither.

As we are moving to GitHub Actions (or at least that's our goal), I've taken a 
look how to tackle the above problem.
Given the fact that we test simulators and emulators on Sauce Labs anyways, we 
might be able to execute everything via GitHub Actions only, i.e., no 
credentials issue.

The GitHub Actions runner have a big variety of available Xcode and iOS 
versions in their virtual environments. [3] And to have some good news - iOS 
works! [4] - the only downside is that we can't test iOS 11.4, but IMHO this 
loss would be OK.

In theory, Android works, too. With the help of the 
reactivecircus/android-emulator-runner action we can setup the emulators with a 
specific target API level. It also handles accepting the permissions etc. [5] 
At least, the logs show that the emulator booted and some things happened (like 
installing the APK)

For the browser tests, some changes in cordova-serve would be needed. In order 
to launch Chrome, Firefox etc. in headless mode, we would need to pass those 
arguments. Currently there is an open issue to add this functionality. [6]

My plan for the next week(s) is to investigate the Android timeouts and to test 
if a patch in cordova-serve would be enough to make headless launching possible 
to make the CI green.
If this works, we would have a blueprint that could be copied to the plugins. 
With the matrix syntax of GitHub Actions we can generate an easy to maintain 
and extendable testing matrix.
One feature I really like is splitting the configs in different files, as 
opposed to the gigantic .travis.yml.

Let me know what you think, I'm eager to get some feedback.
My work can be seen in the feature branch feat/gh-actions [7], especially this 
commit: [8] Cheers, Tim

[1] - 
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapp.saucelabs.com%2Fopen_sauce%2Fuser%2Fsnay%2Ftestsdata=04%7C01%7CPieter.VanPoyer%40portofantwerp.com%7Ca73853478c014d3b99c508d892172a68%7C2337dcc63a214d95bf72da5551a9b048%7C0%7C0%7C637419975492593209%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=4n5QjT2zqfDVCOiu%2FMiz6cMsLn9LvhSBqXBBGpgMnJA%3Dreserved=0
[2] - 
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fblog.travis-ci.com%2F2018-01-23-jwt-addon-is-deprecateddata=04%7C01%7CPieter.VanPoyer%40portofantwerp.com%7Ca73853478c014d3b99c508d892172a68%7C2337dcc63a214d95bf72da5551a9b048%7C0%7C0%7C637419975492593209%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=5RZBQeg%2FNYeEUK4VJrLrnDyXKID1dbqMmpFYftkOOeI%3Dreserved=0
[3] - 
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Factions%2Fvirtual-environments%2Fblob%2Fmain%2Fimages%2Fmacos%2Fmacos-10.15-Readme.md%23xcodedata=04%7C01

RE: Minimum Target SDK

[Pieter Van Poyer]

Hi

> Sounds like the stance we are to take is to officially only support
> the cordova default target/compile sdk version (which is currently
> 29). Users can change this if they wish at their own risk.

I think this absolutely a good decision.
This gives the developers the oppurtunity to develop with modern features.

Changing is at their own risk.
If it is easy to give them the possibility to set it lower than the min SDK, we 
should consider this, I think.

Maybe a warning message should be better, but I think, we should only do an 
effort if it's not too much work.

There are more important issues IMO, that need more attention. (AndroidX)

Kind regards

Pieter Van Poyer
1700
DI/DB

Havenbedrijf Antwerpen/Antwerp Port Authority
Zaha Hadidplein 1
2030 Antwerpen, België
T +32 3 229 76 85
pieter.vanpo...@portofantwerp.com





-Oorspronkelijk bericht-
Van: julio cesar sanchez 
Verzonden: zondag 18 oktober 2020 13:39
Aan: dev@cordova.apache.org
Onderwerp: Re: Minimum Target SDK

Related to this. Should we allow setting the min SDK lower than the min SDK 
cordova-android uses?
At the moment it’s not possible, I closed this issue because I thought we 
didn’t allow it, but if we allow it then should be reopened and fixed

https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fcordova-android%2Fissues%2F1070data=04%7C01%7CPieter.VanPoyer%40portofantwerp.com%7C313f74b78f3f4255abdf08d8735a7657%7C2337dcc63a214d95bf72da5551a9b048%7C0%7C0%7C637386179661479118%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=B%2BlQQHhsOI%2BOjwgs3ypBDk7BL5N3P%2BFrFm7xxPPhDy4%3Dreserved=0

El jueves, 15 de octubre de 2020, Norman Breau 
escribió:

> To recap our hangouts meeting on this topic
>
> Sounds like the stance we are to take is to officially only support
> the cordova default target/compile sdk version (which is currently
> 29). Users can change this if they wish at their own risk.
> Norman Breau
> Software Developer
>
> nor...@normanbreau.com (mailto:nor...@normanbreau.com)
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbrea
> utek.com%2Fdata=04%7C01%7CPieter.VanPoyer%40portofantwerp.com%7C3
> 13f74b78f3f4255abdf08d8735a7657%7C2337dcc63a214d95bf72da5551a9b048%7C0
> %7C0%7C637386179661479118%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAi
> LCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=JqeZv9
> lHYgH%2BTEkKZCLPph05ZtQSq7MnJAnn1NNxa7I%3Dreserved=0
>
> On Oct 15 2020, at 6:05 am, Pieter Van Poyer  portofantwerp.com> wrote:
> >
> > Hi
> >
> >
> > I'd like to give my opinion. Because the discussion about the sdk
> version was with me.
> >
> > I don't like to disagree with Norman, but the problem with the
> CameraPlugin was IMO not with the targetSdkVersion. I could lower the
> targetSdkVersion to 22 without any problems.
> >
> > The problem was with the compileSdkVersion.
> > I was not able to use a constant available in android 28
> (Build.VERSION_CODES.P, if I am right), because Norman suggested it
> would be able to compile with android level 22.
> > So I did change it to the numerical 28 .
> >
> >
> >
> >
> >
> >
> > So IMO, there may be more guidelines About the targetSdkVersion. Not
> > sure about that one. (
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdeve
> loper.android.com%2Fguide%2Ftopics%2Fmanifest%2Fuses-data=04%7C01
> %7CPieter.VanPoyer%40portofantwerp.com%7C313f74b78f3f4255abdf08d8735a7
> 657%7C2337dcc63a214d95bf72da5551a9b048%7C0%7C0%7C637386179661479118%7C
> Unknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1h
> aWwiLCJXVCI6Mn0%3D%7C1000sdata=TLglZpNd3Jfg4rVrw5uz2tV%2FSJfIsthq
> aG7r2ftww7w%3Dreserved=0
> sdk-element.html#target )
> > About the compileSdkVersion (only support officially the one used
> > for
> cordova-android – 29).
> > With using the latest compileSdkVersion and skipping the previous
> > (now
> 22 – 28), plugin developers can use the features from api 29.
> >
> >
> >
> >
> > And for a plugin, this settings must indeed be based on the
> > supported
> cordova (-android) version of that plugin. It must indeed be able to
> run on the defaultMinSdkVersion for the supported cordova-android versions.
> >
> > Kind regards
> > Pieter Van Poyer
> >
> > -Oorspronkelijk bericht-
> > Van: julio cesar sanchez 
> > Verzonden: donderdag 15 oktober 2020 00:39
> > Aan: dev@cordova.apache.org
> > Onderwerp: Re: Minimum Target SDK
> >
> >
> >
> > Despite we allow users to configure the target SDK, I don’t think we
> should allow other than the default on latest cordova-android.

RE: Minimum Target SDK

[Pieter Van Poyer]

Hi



I'd like to give my opinion. Because the discussion about the sdk version was 
with me.



I don't like to disagree with Norman, but the problem with the CameraPlugin was 
IMO not with the targetSdkVersion. I could lower the targetSdkVersion to 22 
without any problems.


The problem was with the compileSdkVersion.
I was not able to use a constant available in android 28 
(Build.VERSION_CODES.P, if I am right), because Norman suggested it would be 
able to compile with android level 22.
So I did change it to the numerical 28 .



[cid:image001.png@01D6A2DF.6FFEBAE0]



So IMO, there may be more guidelines

  1.  About the targetSdkVersion. Not sure about that one. ( 
https://developer.android.com/guide/topics/manifest/uses-sdk-element.html#target
 )
  2.  About the compileSdkVersion (only support officially the one used for 
cordova-android – 29).
With using the latest compileSdkVersion and skipping the previous (now 22 – 
28), plugin developers can use the features from api 29.



And for a plugin, this settings must indeed be based on the supported cordova 
(-android) version of that plugin. It must indeed be able to run on the 
defaultMinSdkVersion for the supported cordova-android versions.



Kind regards

Pieter Van Poyer



-Oorspronkelijk bericht-
Van: julio cesar sanchez 
Verzonden: donderdag 15 oktober 2020 00:39
Aan: dev@cordova.apache.org
Onderwerp: Re: Minimum Target SDK



Despite we allow users to configure the target SDK, I don’t think we should 
allow other than the default on latest cordova-android.



By allow I mean on issues, users are free to use whatever they want, but if 
they don’t use latest they should take care of possible problems themselves.

With that being said, camera plugin requires latest cordova-android, so that 
means target sdk 29.



But also we need to have in mind that if the plugin allowed older 
cordova-android versions and we add some code that requires a higher sdk than 
the default on that cordova-android version we should bump the dependency to 
the version that targets that sdk as default.



BTW, sdk 29 is already a requirement for new apps since August, November is for 
existing apps.



El El mié, 14 oct 2020 a las 23:46, Norman Breau 
mailto:nor...@normanbreau.com>>

escribió:



> Hi team,

>

> A recent discussion came up about what the minimum Target SDK we

> should support. Google enforces apps to be built with at least Target

> SDK 28 (soon to be 29 coming November), but Cordova users may not be

> publishing to the Google Play store, particularly with enterprise

> businesses with internal distribution systems.

> This is currently not documented and I would like it to be documented

> because we were close to merging a PR that would make the camera

> plugin require Target SDK 28. But before I submit a documentation PR I

> would like some feedback on what our minimum Target SDK should be.

> Logically I think it makes the most sense to say that whatever what

> our Minimum SDK level is should be our minimum supported Target SDK

> (which is currently 22 for cordova-android@9).

> For clarity because terminology here is a little confusion:

> Minimum SDK = The minimum supported OS Target SDK = The SDK level used

> to compile an app.

>

> Norman Breau

> Software Developer

>

> nor...@normanbreau.com<mailto:nor...@normanbreau.com> (

> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flink

> .getmailspring.com%2Flink%2FC6CAC914-84D1-430D-9FD4-ACD8F2BCDEB2%40get

> mailspring.com%2F0%3Fredirect%3Dmailto%253Anorman%2540normanbreau.com%

> 26recipient%3DZGV2QGNvcmRvdmEuYXBhY2hlLm9yZw%253D%253Ddata=04%7C0

> 1%7CPieter.VanPoyer%40portofantwerp.com%7Cecf599a37cc34aa15b0908d87091

> fc11%7C2337dcc63a214d95bf72da5551a9b048%7C0%7C0%7C637383119593982450%7

> CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1

> haWwiLCJXVCI6Mn0%3D%7C1000sdata=p5d0xNO3r2jfgXWzReOH%2Fannd0WAln3

> VilI68tFngyY%3Dreserved=0

> )

> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbrea

> utek.com%2Fdata=04%7C01%7CPieter.VanPoyer%40portofantwerp.com%7Ce

> cf599a37cc34aa15b0908d87091fc11%7C2337dcc63a214d95bf72da5551a9b048%7C0

> %7C0%7C637383119593982450%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAi

> LCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=jERwWv

> Q8Kr04RoFF6NReZLtVZCpixqaRG%2FVL%2B0A4PeU%3Dreserved=0 (

> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flink

> .getmailspring.com%2Flink%2FC6CAC914-84D1-430D-9FD4-ACD8F2BCDEB2%40get

> mailspring.com%2F2%3Fredirect%3Dhttps%253A%252F%252Fbreautek.com%26rec

> ipient%3DZGV2QGNvcmRvdmEuYXBhY2hlLm9yZw%253D%253Ddata=04%7C01%7CP

> ieter.VanPoyer%40portofantwerp.com%7Cecf599a37cc34aa15b0908d87091fc11%

> 7C2337dcc63a214d95bf72da5551a9b048%7C0%7C0%7C637383119593982450%7CUnkn

> own

RE: Greenfield for cordova-plugin-network-information + release version 3.0.0

[Pieter Van Poyer]

Hi

Thanks for the responses. I did read the responses. And I did subscribe myself 
to the dev list.
There seems to be some different visions.

Some highlights:
Niklas stated:
'
A new major version could possibly change that if we can get consensus about 
this but someone would need to do the work.
'
This is the purpose of my mail finding the right place/spot to discuss a next 
major (breaking) version.
Do I open a discussion on https://github.com/apache/cordova-discuss/ ?

Jesse states:
‘
The best proposals are pull-requests.
All your suggestions sound perfectly reasonable, and I personally would love to 
see this happen.
‘
I agree, but first I would like a basic agreement about the specs. It’s about a 
core plugin, I wouldn’t like to do an effort and afterwards have to discuss the 
specs.
When there is an agreement, I would love to do an effort for the Android and 
the Browser v4 implementation.

And off course the reasoning why I would like some changes is important. So.

-   When online, only detect following types: WIFI, MOBILE
  -> My reasoning for this is all about Keep It Simple.
  IMO most users are using this plugin to detect online or offline.
  Keeping specs about 2G, 3G, Ethernet, makes the code more difficult. 
Difficult code makes it more difficult for future plugin contributers.
  Another reason is, the more strict security and privacy restrictions on 
ios and android.
  This restriction could stop them from giving information about the 
network types. The browser doesn’t even reveal the type.
  A more specific plugin could indeed be about detecting all the different 
types (2G, 3G, 4G). But IMO this is no core feature.

-   Drop Windows platform support
-> Obvious I think. Keeps the codebase free from the Windows platform.

-   For android: use the NetworkCallback 
https://developer.android.com/reference/android/net/ConnectivityManager.NetworkCallback
 API
  instead of the deprecated CONNECTIVITY_ACTION from the 
Connectivitymanager.
  -> Remove the deprecated 
https://developer.android.com/reference/android/net/ConnectivityManager#CONNECTIVITY_ACTION
 android API. Make the android codebase future proof.

-   There can be more suggestions/improvements. Use Swift instead of 
Objective-C. (Although the ios part seems to be stable).

And about the release of the 3.0 version (current master), the previous version 
was released by Jan Piotrowski. But I do not think he is still an active 
maintainer of the plugin right now. Norman Breau did the most of the code 
review for version 3, but I do not think he has npm publish rights fort his 
plugin ( https://github.com/apache/cordova-plugin-network-information ).

Kind regards
Pieter Van Poyer

-Oorspronkelijk bericht-
Van: julio cesar sanchez 
Verzonden: maandag 7 september 2020 01:32
Aan: dev@cordova.apache.org
Onderwerp: Re: Greenfield for cordova-plugin-network-information + release 
version 3.0.0

It would be good that instead of just saying what you would like to see 
changed, you also say why you would like it (benefits, reasoning, etc.)

El lunes, 7 de septiembre de 2020, Niklas Merz 
mailto:niklasm...@apache.org>>
escribió:

> Hi Pieter
>
> At first a warm welcome to the list.
>
> If you would like to open a proposal for discussion I can point you to
> the cordova-discuss repository:
> https://github.com/apache/cordova-discuss/ . We track some proposals
> in issues and pull requests there.
>
> I am not really familiar with the plugin but looking at the
> description and recent activity it looks like it was designed to
> implement the old version of the Network Information API. Other
> community members probably know more about that.
>
> A new major version could possibly change that if we can get consensus
> about this but someone would need to do the work.
>
> It looks you already got your own requirements ready and I personally
> would build and publish this plugin myself in this case. Creating
> plugins is not that hard if you start with the skeleton of an existing
> one. Contact me if you need any help.
>
> Kind regards
> Niklas
>
> Am 07.09.20 um 00:06 schrieb Pieter Van Poyer:
> > Hey Cordova devs
> >
> > You are doing a great job with Cordova.
> > I've got a question, suggestion for the cordova-plugin-network-
> information.
> >
> > Is it possible to open an issue, a milestone, a metaticket or
> > something
> to discuss the future requirements of the plugin (v4).
> > Something like a whitepaper.
> >
> >
> > My suggestions for a whitepaper are:
> >
> > Loosen the requirements of the plugin to it's barebone's essentials.
> > Requirements
> >
> >   *   Detect online/offline only when the app is active.
> >   *   When online, only detect following types: WIFI, MOBILE
> > 

Greenfield for cordova-plugin-network-information + release version 3.0.0

[Pieter Van Poyer]

Hey Cordova devs

You are doing a great job with Cordova.
I've got a question, suggestion for the cordova-plugin-network-information.

Is it possible to open an issue, a milestone, a metaticket or something to 
discuss the future requirements of the plugin (v4).
Something like a whitepaper.


My suggestions for a whitepaper are:

Loosen the requirements of the plugin to it's barebone's essentials.
Requirements

  *   Detect online/offline only when the app is active.
  *   When online, only detect following types: WIFI, MOBILE
Stop with next requirements

  *   Detect online/offline when the app is not active.
  *   Don't try to detect other network type's beside WIFI and MOBILE.
  *   Do not let this plugin support background work like fileupload's and 
datasyncs. Remove it from the doc's.
  *   Drop Windows platform support.
For android: use the 
NetworkCallback<https://developer.android.com/reference/android/net/ConnectivityManager.NetworkCallback.html>
 API instead of the deprecated Connectivitymanager.

Maybe we could take some insparation by looking at the Capacitor plugin 
https://github.com/ionic-team/capacitor-plugins/tree/main/network or Flutter 
plugin.


Is it also possible to release version 3.0.0 of the plugin.

Kind regards

Pieter Van Poyer



Deze e-mail en alle gekoppelde bestanden zijn officiele documenten van 
Havenbedrijf Antwerpen NV van publiek recht en kunnen vertrouwelijke of 
persoonlijke informatie bevatten. Gelieve de afzender onmiddellijk via e-mail 
of telefonisch te verwittigen als u deze e-mail per vergissing heeft ontvangen 
en verwijder vervolgens de e-mail zonder deze te lezen, te reproduceren, te 
verspreiden of te ontsluiten naar derden. Havenbedrijf Antwerpen NV van publiek 
recht is op geen enkele manier verantwoordelijk voor fouten of 
onnauwkeurigheden in de inhoud van deze e-mail. Havenbedrijf Antwerpen NV van 
publiek recht kan niet aansprakelijk gesteld worden voor directe of indirecte 
schade, verlies of ongemak veroorzaakt als gevolg van een onnauwkeurigheid of 
fout in deze e-mail.

English Translation: This e-mail and all attached files are official documents 
of Antwerp Port Authority and may contain confidential or personal information. 
If you have received this e-mail in error, you are asked to inform the sender 
by e-mail or telephone immediately, and to remove it from your system without 
reading or reproducing it or passing it on to other parties. Antwerp Port 
Authority is in no way responsible for any errors or inaccuracies in the 
contents of this e-mail, nor can it be held liable for any direct or indirect 
loss, damage or inconvenience arising from any such errors or inaccuracies.

Time to release

[Pieter Van Poyer]

Hi Cordova,

Thanks for merging my pull request in the master!

Maybe it is time to release a 2.1.0 version to npm?

[cid:image001.png@01D4F3D1.08855FE0]

Kind regards,

Pieter Van Poyer
1700
DI/DB

Havenbedrijf Antwerpen/Antwerp Port Authority
Zaha Hadidplein 1
2030 Antwerpen, België
T +32 3 229 76 85
pieter.vanpo...@portofantwerp.com<mailto:pieter.vanpo...@portofantwerp.com>

[logo]<https://www.portofantwerp.com/>

[Baseline_handtekening]<https://www.portofantwerp.com/>




Deze e-mail en alle gekoppelde bestanden zijn officiele documenten van 
Havenbedrijf Antwerpen NV van publiek recht en kunnen vertrouwelijke of 
persoonlijke informatie bevatten. Gelieve de afzender onmiddellijk via e-mail 
of telefonisch te verwittigen als u deze e-mail per vergissing heeft ontvangen 
en verwijder vervolgens de e-mail zonder deze te lezen, te reproduceren, te 
verspreiden of te ontsluiten naar derden. Havenbedrijf Antwerpen NV van publiek 
recht is op geen enkele manier verantwoordelijk voor fouten of 
onnauwkeurigheden in de inhoud van deze e-mail. Havenbedrijf Antwerpen NV van 
publiek recht kan niet aansprakelijk gesteld worden voor directe of indirecte 
schade, verlies of ongemak veroorzaakt als gevolg van een onnauwkeurigheid of 
fout in deze e-mail.

English Translation: This e-mail and all attached files are official documents 
of Antwerp Port Authority and may contain confidential or personal information. 
If you have received this e-mail in error, you are asked to inform the sender 
by e-mail or telephone immediately, and to remove it from your system without 
reading or reproducing it or passing it on to other parties. Antwerp Port 
Authority is in no way responsible for any errors or inaccuracies in the 
contents of this e-mail, nor can it be held liable for any direct or indirect 
loss, damage or inconvenience arising from any such errors or inaccuracies.

Request to merge https://github.com/apache/cordova-plugin-network-information/pull/74

[Pieter Van Poyer]

Hello Cordova,

I've made a Pull Request for the cordova-plugin-network-information.  
https://github.com/apache/cordova-plugin-network-information/pull/74
It solves a really annoying android bug.

The PR got a lot of thumbs up, my repo has been forked multiple times by other 
users.
Nobody seems to have time or seems to have sufficient rights to merge the pull 
request.

Can someone from the Apache Foundation shine a light on this (or merge it?).

Kind regards,
Pieter Van Poyer



Deze e-mail en alle gekoppelde bestanden zijn officiele documenten van 
Havenbedrijf Antwerpen NV van publiek recht en kunnen vertrouwelijke of 
persoonlijke informatie bevatten. Gelieve de afzender onmiddellijk via e-mail 
of telefonisch te verwittigen als u deze e-mail per vergissing heeft ontvangen 
en verwijder vervolgens de e-mail zonder deze te lezen, te reproduceren, te 
verspreiden of te ontsluiten naar derden. Havenbedrijf Antwerpen NV van publiek 
recht is op geen enkele manier verantwoordelijk voor fouten of 
onnauwkeurigheden in de inhoud van deze e-mail. Havenbedrijf Antwerpen NV van 
publiek recht kan niet aansprakelijk gesteld worden voor directe of indirecte 
schade, verlies of ongemak veroorzaakt als gevolg van een onnauwkeurigheid of 
fout in deze e-mail.

English Translation: This e-mail and all attached files are official documents 
of Antwerp Port Authority and may contain confidential or personal information. 
If you have received this e-mail in error, you are asked to inform the sender 
by e-mail or telephone immediately, and to remove it from your system without 
reading or reproducing it or passing it on to other parties. Antwerp Port 
Authority is in no way responsible for any errors or inaccuracies in the 
contents of this e-mail, nor can it be held liable for any direct or indirect 
loss, damage or inconvenience arising from any such errors or inaccuracies.