[DISCUSS] cordova-ios 7.1.1 Release

[Bryan Ellis]

Does anyone have any reason to delay a release for cordova-ios?

* cordova-ios (7.1.1)

https://github.com/apache/cordova-ios/compare/rel/7.1.0...master

Any additional outstanding changes to land?

If not, I will start the release process shortly

Re: [DISCUSS] Unarchive & Un-deprecate cordova-plugin-device-motion

[Norman Breau]

I had a look at the repo and made several PRs that I think would be 
necessary
to make a release. I'm not sure if I'll have time to prepare a release 
this week
coming, but after today I think it will be ready to start the release 
process.


On 2024-06-29 08:10, julio cesar sanchez wrote:

I've been triaging issues starting with the repositories that were less
active and while installing this plugin I noticed the latest released
version is still the deprecated version.
Not sure if somebody would be interested in releasing the 3.0.0 version.

El mar, 18 ago 2020 a las 6:51, Bryan Ellis () escribió:


This discussion is to unarchive & un-deprecate the plugin:

   cordova-plugin-device-motion

This plugin is now requires because iOS w/ Custom Schemes does provide the
support necessary to use Web APIs.
-
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: [DISCUSS] Unarchive & Un-deprecate cordova-plugin-device-motion

[julio cesar sanchez]

I've been triaging issues starting with the repositories that were less
active and while installing this plugin I noticed the latest released
version is still the deprecated version.
Not sure if somebody would be interested in releasing the 3.0.0 version.

El mar, 18 ago 2020 a las 6:51, Bryan Ellis () escribió:

> This discussion is to unarchive & un-deprecate the plugin:
>
>   cordova-plugin-device-motion
>
> This plugin is now requires because iOS w/ Custom Schemes does provide the
> support necessary to use Web APIs.
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

[ANNOUNCEMENT] cordova-plugin-device 3.0.0 Release

[Bryan Ellis]

We have just released an update to our plugin!

- cordova-plugin-device@3.0.0

Re: [VOTE] cordova-plugin-device 3.0.0 Release

[Bryan Ellis]

The vote has now closed. The results are:

Positive Binding Votes: 3

Bryan Ellis
Norman Breau
Niklas Merz

Negative Binding Votes: 0

Positive Non-Binding Votes: 0

The vote has passed.



On Fri, Jun 14, 2024 at 7:49 PM Niklas Merz  wrote:

> I vote +1
>
> * hash ok
> * signature ok
> * tag ok
> * license headers ok
> * no flagged licenses
> * tests look good
>
> On June 12, 2024, Norman Breau  wrote:
> > I vote +1:
> >
> > - NPM Audit is green
> > - NPM test passes
> > - Android Paramedic Test passes
> > - Verified Archive
> > - Verified Tags
> >
> > On 2024-06-11 22:49, Bryan Ellis wrote:
> > > Please review and vote on this cordova-plugin-device Release v3.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/device-v3.0.0
> > >
> > > The package was published from its corresponding git tag:
> > >
> > > cordova-plugin-device: 3.0.0 (da852c3624)
> > >
> > > Note that you can test it out via:
> > >
> > > cordova plugin add https://github.com/apache/cordova-plugin-
> > device#3.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
> > > * NPM audit
> > > * 0 vulnerabilities
> > > * NPM Test
> > > * Ran `cordova build` test
> > > * Launched and tested on emulators with Android Studio & Xcode
> > > * 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-plugin-device 3.0.0 Release

[Niklas Merz]

I vote +1

* hash ok
* signature ok
* tag ok
* license headers ok
* no flagged licenses
* tests look good

On June 12, 2024, Norman Breau  wrote:
> I vote +1:
>
> - NPM Audit is green
> - NPM test passes
> - Android Paramedic Test passes
> - Verified Archive
> - Verified Tags
>
> On 2024-06-11 22:49, Bryan Ellis wrote:
> > Please review and vote on this cordova-plugin-device Release v3.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/device-v3.0.0
> >
> > The package was published from its corresponding git tag:
> >
> > cordova-plugin-device: 3.0.0 (da852c3624)
> >
> > Note that you can test it out via:
> >
> > cordova plugin add https://github.com/apache/cordova-plugin-
> device#3.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
> > * NPM audit
> > * 0 vulnerabilities
> > * NPM Test
> > * Ran `cordova build` test
> > * Launched and tested on emulators with Android Studio & Xcode
> > * 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: [PR] Cordova iOS 8 proposal [cordova-discuss]

[via GitHub]

dpogue commented on PR #113:
URL: https://github.com/apache/cordova-discuss/pull/113#issuecomment-2163618052

   It should still be possible to use Objective-C categories to add the methods 
for handling push token events, but it would need to extend the 
`CDVAppDelegate` base class rather than the `AppDelegate` at the app level.
   Example:
   
https://github.com/AyogoHealth/cordova-plugin-ayogo-push/blob/master/src/ios/CDVAppDelegate%2BPush.h
   
https://github.com/AyogoHealth/cordova-plugin-ayogo-push/blob/master/src/ios/CDVAppDelegate%2BPush.m
   
   I remember trying to do this sort of thing with Swift extensions and it not 
working, and it seemed to be due to some sort of load ordering thing where the 
extension wasn't getting applied automatically.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

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

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [PR] Cordova iOS 8 proposal [cordova-discuss]

[via GitHub]

jcesarmobile commented on PR #113:
URL: https://github.com/apache/cordova-discuss/pull/113#issuecomment-2163606990

   A problem with moving to Swift templates is that it will break all push 
plugins since they rely on an Objective-C category on the AppDelegate for 
adding the method that gets the token from APNS. 
   
   Example:
   
https://github.com/uniquare/cordova-plugin-push/blob/master/src/ios/AppDelegate%2Bnotification.m
   
   It won't work if there is no `AppDelegate.h` since needs to import it
   
https://github.com/uniquare/cordova-plugin-push/blob/master/src/ios/AppDelegate%2Bnotification.h#L9
   
   Not sure if there is an alternative for getting the token from Swift. I 
tried with Swift extensions for Capacitor and didn't work, but could be related 
to the extension being on the plugins, which are CocoaPods libraries, might 
work if the extension is part of the app as it will be in a Cordova app.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

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

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [VOTE] cordova-plugin-device 3.0.0 Release

[Norman Breau]

I vote +1:

- NPM Audit is green
- NPM test passes
- Android Paramedic Test passes
- Verified Archive
- Verified Tags

On 2024-06-11 22:49, Bryan Ellis wrote:

Please review and vote on this cordova-plugin-device Release v3.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/device-v3.0.0

The package was published from its corresponding git tag:

 cordova-plugin-device: 3.0.0 (da852c3624)

Note that you can test it out via:

 cordova plugin add https://github.com/apache/cordova-plugin-device#3.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
* NPM audit
   * 0 vulnerabilities
* NPM Test
* Ran `cordova build` test
* Launched and tested on emulators with Android Studio & Xcode
* 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: [PR] Cordova iOS 8 proposal [cordova-discuss]

[via GitHub]

dpogue commented on PR #113:
URL: https://github.com/apache/cordova-discuss/pull/113#issuecomment-2162477595

   > I'm not saying we should go to 15 or anything, but requiring iOS 14+ for 
`WKScriptMessageHandlerWithReply` I don't think is a problem. But maintaining 
backwards compatibility with existing plugins that uses the older API is a 
larger issue as you've noted. So for that I think the question is whether we 
want to maintain 2 cordova API entry points.
   
   I need to look at this more closely and try to figure out exactly how we 
would implement it as part of our CDVWebViewEngine and CDVCommandQueue stuff.
   
   I do not want (any more) WebKit-specific classes getting exposed publicly in 
Cordova API, because I'm certain that will come back to bite us at some point 
the way having UIWebView stuff did. We have the engine abstraction layer, we 
should be strict about maintaining that boundary.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

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

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [PR] report: June 2024 [cordova-apache-board-reports]

[via GitHub]

erisu merged PR #22:
URL: https://github.com/apache/cordova-apache-board-reports/pull/22


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

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

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[VOTE] cordova-plugin-device 3.0.0 Release

[Bryan Ellis]

Please review and vote on this cordova-plugin-device Release v3.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/device-v3.0.0

The package was published from its corresponding git tag:

cordova-plugin-device: 3.0.0 (da852c3624)

Note that you can test it out via:

cordova plugin add https://github.com/apache/cordova-plugin-device#3.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
* NPM audit
  * 0 vulnerabilities
* NPM Test
* Ran `cordova build` test
* Launched and tested on emulators with Android Studio & Xcode
* Ran `cordova plugin add` test

Re: [PR] Cordova iOS 8 proposal [cordova-discuss]

[via GitHub]

jcesarmobile commented on PR #113:
URL: https://github.com/apache/cordova-discuss/pull/113#issuecomment-2160595158

   Requiring a code 15 is not a problem, we already have a PR for it
   https://github.com/apache/cordova-ios/pull/1425
   
   The dependency of Cordova plugins to the Cordova-ios SPM is only needed if 
we want the plugin to build independently without adding it to an app. 
   I removed it from my WIP PR
   https://github.com/apache/cordova-plugin-device/pull/196
   
   At the moment plugins don’t build independently neither, so it’s not a big 
deal to continue like that


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

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

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [PR] Cordova iOS 8 proposal [cordova-discuss]

[via GitHub]

breautek commented on PR #113:
URL: https://github.com/apache/cordova-discuss/pull/113#issuecomment-2160362178

   Just as a data point... 
   
   Google Maps uses a min deployment target of iOS 15, and even support for 
that is "frozen", e.g. they aren't addressing any issues with it, and will be 
removing support in next/future major release.
   
   I'm not saying we should go to 15 or anything, but requiring iOS 14+ for 
`WKScriptMessageHandlerWithReply` I don't think is a problem. But maintaining 
backwards compatibility with existing plugins that uses the older API is a 
larger issue as you've noted. So for that I think the question is whether we 
want to maintain 2 cordova API entry points.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

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

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [PR] june 2024 report [cordova-apache-board-reports]

[via GitHub]

NiklasMerz commented on code in PR #22:
URL: 
https://github.com/apache/cordova-apache-board-reports/pull/22#discussion_r1634498118


##
2024/04.md:
##
@@ -0,0 +1,75 @@
+## Status report for the Apache Cordova project - March 2024

Review Comment:
   Thanks for pointing that out. 



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

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

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Proposal for Cordova iOS 8 major version

[Darryl Pogue]

Hi folks,
Now that WWDC24's keynote is behind us (and we survived mostly unscathed),
I wanted to present a proposal for some larger-scale breaking changes that
I think would be good to try to accomplish in the next major version of
Cordova-iOS.

I've put together a proposal on the cordova-discuss repo to allow for easy
commenting and feedback:
https://github.com/apache/cordova-discuss/pull/113/files

While several of these sound like bit items, the goal is to keep the actual
impact of them as minimal as possible in terms of API breakage for plugins.
Primarily, the goal is to modernize the template app to be more in line
with current platform best practices, and to make CordovaLib a bit easier
to work with. I expect I can have draft PRs for most of these changes
fairly quickly if we decide to move ahead with them, but I would suggest we
aim to do a release closer to September when iOS 18 officially launches
(just in case any last-minute issues arise).

There are definitely some other items on the wishlist for Cordova iOS 8, as
found on the GitHub milestone:
https://github.com/apache/cordova-ios/milestone/12

I suspect a few other people might have additional (or parallel) ideas for
Cordova iOS 8, so it would be good to get folks aligned on what we want to
do moving forward.

Thanks,
~Darryl

[PR] Cordova iOS 8 proposal [cordova-discuss]

[via GitHub]

dpogue opened a new pull request, #113:
URL: https://github.com/apache/cordova-discuss/pull/113

   Please view the proposal on the Files tab and leave comments there  


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

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

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [PR] june 2024 report [cordova-apache-board-reports]

[via GitHub]

dpogue commented on code in PR #22:
URL: 
https://github.com/apache/cordova-apache-board-reports/pull/22#discussion_r1634264348


##
2024/04.md:
##
@@ -0,0 +1,75 @@
+## Status report for the Apache Cordova project - March 2024

Review Comment:
   This should be "June 2024"? and the filename should be `06.md`?



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

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

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [PR] june 2024 report [cordova-apache-board-reports]

[via GitHub]

NiklasMerz commented on code in PR #22:
URL: 
https://github.com/apache/cordova-apache-board-reports/pull/22#discussion_r1632314095


##
2024/04.md:
##
@@ -0,0 +1,76 @@
+## Status report for the Apache Cordova project - March 2024
+
+## Description
+
+A platform for building native mobile applications using HTML, CSS and 
JavaScript.
+
+## Project Status
+
+**Current project status:**
+
+Our current work continues on staying updated with changes to iOS and Android, 
our most utilized platforms, alongside ensuring regular updates to plugins.
+
+Our status dashboard at http://status.cordova.io remains mostly all green and 
our nightly builds are still extremely stable.
+
+Committers made a major release to update the cordova-electron and 
cordova-android platform to update dependencies. cordova-ios minor and 
cordova-plugin-file release were published to comply with Apple's new privacy 
requirements.

Review Comment:
   ```suggestion
   Committers made a major release to update the cordova-android platform to 
update dependencies. cordova-ios minor and cordova-plugin-file releases were 
published to comply with Apple's new privacy requirements.
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

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

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [PR] june 2024 report [cordova-apache-board-reports]

[via GitHub]

jcesarmobile commented on code in PR #22:
URL: 
https://github.com/apache/cordova-apache-board-reports/pull/22#discussion_r1632296293


##
2024/04.md:
##
@@ -0,0 +1,76 @@
+## Status report for the Apache Cordova project - March 2024
+
+## Description
+
+A platform for building native mobile applications using HTML, CSS and 
JavaScript.
+
+## Project Status
+
+**Current project status:**
+
+Our current work continues on staying updated with changes to iOS and Android, 
our most utilized platforms, alongside ensuring regular updates to plugins.
+
+Our status dashboard at http://status.cordova.io remains mostly all green and 
our nightly builds are still extremely stable.
+
+Committers made a major release to update the cordova-electron and 
cordova-android platform to update dependencies. cordova-ios minor and 
cordova-plugin-file release were published to comply with Apple's new privacy 
requirements.
+
+**Issues for the board:**
+
+There are no issues requiring board attention at this time.
+
+## Membership Data
+
+There are currently 99 committers and 96 PMC members in this project.
+
+The Committer-to-PMC ratio is roughly 1:1.
+
+**Community changes, past quarter:**
+
+- No new PMC members. Last addition was Pieter Van Poyer on 2021-04-06.
+- No new committers. Last addition was Pieter Van Poyer on 2021-04-06.
+
+## Project Activity
+
+Our project made releases this quarter for our core platforms to keep up with 
current requirements.
+
+**Releases:**
+
+- cordova-plugin-file@8.1.0 was released on 2024-06-05.
+- cordova-android@13.0.0 was released on 2024-05-23.
+- cordova-ios@7.1.0 was released on 2024-04-03.
+- cordova-eslint@5.1.0 was released on 2024-03-27.
+- cordova-electron@4.0.0 was released on 2024-03-11.

Review Comment:
   ```suggestion
   ```
   Electron release was already part of the last report



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

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

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

June Board Report

[Niklas Merz]

Hi folks,

I created a draft for the board report. Feel free to review or add
anything you think should be included.

https://github.com/apache/cordova-apache-board-reports/pull/22

Regards
Niklas

[PR] june 2024 report [cordova-apache-board-reports]

[via GitHub]

NiklasMerz opened a new pull request, #22:
URL: https://github.com/apache/cordova-apache-board-reports/pull/22

   (no comment)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

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

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[ANNOUNCEMENT] cordova-plugin-file 8.1.0 Release

[Bryan Ellis]

We have just released an update to our plugin!

- cordova-plugin-file@8.1.0

Re: [VOTE] cordova-plugin-file 8.1.0 Release

[Bryan Ellis]

The vote has now closed. The results are:

Positive Binding Votes: 3

Bryan Ellis
Norman Breau
Niklas Merz

Negative Binding Votes: 0

Positive Non-Binding Votes: 0

The vote has passed.



On Sat, Jun 1, 2024 at 6:52 PM Niklas Merz  wrote:

> I vote +1:
>
> - hash & signature ok
> - tag ok
> - license ok
> - headers ok
> - npm audit green
> - test app builds on system with android/linux
>
>
> On May 31, 2024, Norman Breau  wrote:
> > I vote +1:
> >
> > - Ran NPM test
> > - NPM Audit is green
> > - Ran paramedic on android/linux platform against API 34
> > - Verified Archive
> > - Verified Tags
> >
> > On 2024-05-31 02:12, Bryan Ellis wrote:
> > > Please review and vote on this cordova-plugin-file Release v8.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/file-v8.1.0
> > >
> > > The package was published from its corresponding git tag:
> > >
> > > cordova-plugin-file: 8.1.0 (b0ac75c00d)
> > >
> > > Note that you can test it out via:
> > >
> > > cordova plugin add https://github.com/apache/cordova-plugin-
> > file#8.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
> > > * NPM audit
> > > * 0 vulnerabilities
> > > * NPM Test
> > > * Ran `cordova build` test
> > > * Ran `cordova run` emulators (iOS & Android)
> > > * 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-plugin-file 8.1.0 Release

[Niklas Merz]

I vote +1:

- hash & signature ok
- tag ok
- license ok
- headers ok
- npm audit green
- test app builds on system with android/linux


On May 31, 2024, Norman Breau  wrote:
> I vote +1:
>
> - Ran NPM test
> - NPM Audit is green
> - Ran paramedic on android/linux platform against API 34
> - Verified Archive
> - Verified Tags
>
> On 2024-05-31 02:12, Bryan Ellis wrote:
> > Please review and vote on this cordova-plugin-file Release v8.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/file-v8.1.0
> >
> > The package was published from its corresponding git tag:
> >
> > cordova-plugin-file: 8.1.0 (b0ac75c00d)
> >
> > Note that you can test it out via:
> >
> > cordova plugin add https://github.com/apache/cordova-plugin-
> file#8.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
> > * NPM audit
> > * 0 vulnerabilities
> > * NPM Test
> > * Ran `cordova build` test
> > * Ran `cordova run` emulators (iOS & Android)
> > * 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-plugin-file 8.1.0 Release

[Norman Breau]

I vote +1:

- Ran NPM test
- NPM Audit is green
- Ran paramedic on android/linux platform against API 34
- Verified Archive
- Verified Tags

On 2024-05-31 02:12, Bryan Ellis wrote:

Please review and vote on this cordova-plugin-file Release v8.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/file-v8.1.0

The package was published from its corresponding git tag:

 cordova-plugin-file: 8.1.0 (b0ac75c00d)

Note that you can test it out via:

 cordova plugin add https://github.com/apache/cordova-plugin-file#8.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
* NPM audit
   * 0 vulnerabilities
* NPM Test
* Ran `cordova build` test
* Ran `cordova run` emulators (iOS & Android)
* Ran `cordova plugin add` test



-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[VOTE] cordova-plugin-file 8.1.0 Release

[Bryan Ellis]

Please review and vote on this cordova-plugin-file Release v8.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/file-v8.1.0

The package was published from its corresponding git tag:

cordova-plugin-file: 8.1.0 (b0ac75c00d)

Note that you can test it out via:

cordova plugin add https://github.com/apache/cordova-plugin-file#8.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
* NPM audit
  * 0 vulnerabilities
* NPM Test
* Ran `cordova build` test
* Ran `cordova run` emulators (iOS & Android)
* Ran `cordova plugin add` test

[ANNOUNCEMENT] Cordova Android 13.0.0 Release

[Bryan Ellis]

We have just released an update to our android platform!

- cordova-android@13.0.0

You can view the release blog post at
https://cordova.apache.org/announcements/2024/05/23/cordova-android-13.0.0.html

Re: [VOTE] Cordova-Android 13.0.0 Release

[Bryan Ellis]

The vote has now closed. The results are:

Positive Binding Votes: 3

Bryan Ellis
Norman Breau
Niklas Merz

Negative Binding Votes: 0

Positive Non-Binding Votes: 1

Alexandre Alves

The vote has passed.


On Mon, May 20, 2024 at 3:26 PM Niklas Merz  wrote:

> I vote +1
>
> * signature & hash ok
> * tag ok
> * licenses ok
> * headers ok
> * tests pass on my machine
> * build runs on my machine
>
> On May 17, 2024, alexandre alves  wrote:
> > I vote +1:
> >
> > - Ran NPM Test on Windows with NodeJS 18
> > - Verified Archive
> > - Verified Tags
> > - NPM Audit is OK
> > - Build and ran a production app with no issues
> >
> > Alexandre Alves
> > 
> > From: Norman Breau 
> > Sent: Wednesday, May 15, 2024 1:35:08 PM
> > To: dev@cordova.apache.org 
> > Subject: Re: [VOTE] Cordova-Android 13.0.0 Release
> >
> > I vote +1:
> >
> > - Ran NPM Test on Linux/Fedora with NodeJS 20
> > - Ran NPM Test on MacOS with NodeJS 20
> > - Verified Archive
> > - Verified Tags
> > - NPM Audit is good
> >
> > On 2024-05-15 08:01, Bryan Ellis wrote:
> > > Please review and vote on this Cordova-Android Release v13.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-v13.0.0
> > >
> > > The package was published from its corresponding git tag:
> > >
> > > cordova-android: 13.0.0 (2143045d4e)
> > >
> > > Note that you can test it out via:
> > >
> > > cordova platform add https://github.com/apache/cordova-
> > android#13.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
> > > * 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-Android 13.0.0 Release

[Niklas Merz]

I vote +1

* signature & hash ok
* tag ok
* licenses ok
* headers ok
* tests pass on my machine
* build runs on my machine

On May 17, 2024, alexandre alves  wrote:
> I vote +1:
>
> - Ran NPM Test on Windows with NodeJS 18
> - Verified Archive
> - Verified Tags
> - NPM Audit is OK
> - Build and ran a production app with no issues
>
> Alexandre Alves
> 
> From: Norman Breau 
> Sent: Wednesday, May 15, 2024 1:35:08 PM
> To: dev@cordova.apache.org 
> Subject: Re: [VOTE] Cordova-Android 13.0.0 Release
>
> I vote +1:
>
> - Ran NPM Test on Linux/Fedora with NodeJS 20
> - Ran NPM Test on MacOS with NodeJS 20
> - Verified Archive
> - Verified Tags
> - NPM Audit is good
>
> On 2024-05-15 08:01, Bryan Ellis wrote:
> > Please review and vote on this Cordova-Android Release v13.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-v13.0.0
> >
> > The package was published from its corresponding git tag:
> >
> > cordova-android: 13.0.0 (2143045d4e)
> >
> > Note that you can test it out via:
> >
> > cordova platform add https://github.com/apache/cordova-
> android#13.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
> > * 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: [DISCUSS] cordova-android 13.0.0 Release

[Niklas Merz]

Thanks again. We could update this on docs just to be sure.

My build problem was due to an old version of SDK command line tools.

On May 20, 2024, Norman Breau  wrote:
> Gradle 8.x supports JDK 11 - 17. Cordova android @12 used AGP 7.x
> which required 11, but 7.4 introduced support for JDK 17, it wasn't
> required.AGP 8.x introduces the requirement of JDK 17.What you might
> be thinking of though is command line tools package, one of the recent
> releases required JDK 17 (wanna say v13 but don't quite remember)Sent
> via the Samsung Galaxy Note9, an AT 5G Evolution capable smartphone
>  Original message From: julio cesar sanchez
>  Date: 5/19/24 4:00 PM (GMT-05:00) To:
> dev@cordova.apache.org Subject: Re: [DISCUSS] cordova-android 13.0.0
> Release Unless something changed last minute, I think the gradle
> version usedrequired JDK 17, which has been bundled with Android
> Studio for around 1yearEl El dom, 19 may 2024 a las 21:17, Niklas Merz
> escribió:> Which version of Java is required
> for this release? Is 11 from the docs> still up-to date? I had a build
> error and updated Java and Gradle.>>
>  Gradle
> 8.3> 
> Build time:> 2023-08-17 07:06:47 UTC Revision:>
> 8afbf24b469158b714b36e84c6f4d4976c86fcd5 Kotlin: 1.9.0 Groovy: 3.0.17>
> Ant: Apache Ant(TM) version 1.10.13 compiled on January 4 2023 JVM:>
> 21.0.3 (Eclipse Adoptium 21.0.3+9-LTS) OS: Linux 6.5.0-35-generic
> amd64>> Now I get an error while building:>> BUILD SUCCESSFUL in 8s 1
> actionable task: 1 executed Subproject Path:> CordovaLib Subproject
> Path: app BUILD SUCCESSFUL in 1s 50 actionable> tasks: 50 up-to-date
> Built the following apk(s):>>
> /home/niklas/apache/vote/android/app/platforms/android/app/build/outputs/apk/debug/app-
> > debug.apk Checking Java JDK and Android SDK versions>
> ANDROID_HOME=/home/niklas/Android/Sdk (recommended setting)>
> ANDROID_SDK_ROOT=/home/niklas/Android/Sdk (DEPRECATED) Using Android>
> SDK: /home/niklas/Android/Sdk Command failed with exit code 1:>
> apkanalyzer manifest target-sdk>>
> /home/niklas/apache/vote/android/app/platforms/android/app/build/outputs/apk/debug/app-
> > debug.apk Exception in thread "main"
> java.lang.NoClassDefFoundError:> javax/xml/bind/annotation/XmlSchema
> at>>
> com.android.repository.api.SchemaModule$SchemaModuleVersion.(SchemaModule.java:156)>
> at
> com.android.repository.api.SchemaModule.(SchemaModule.java:75)>
> at>>
> com.android.sdklib.repository.AndroidSdkHandler.(AndroidSdkHandler.java:81)>
> at>>
> com.android.tools.apk.analyzer.ApkAnalyzerCli.getAaptInvokerFromSdk(ApkAnalyzerCli.java:277)>
> at>
> com.android.tools.apk.analyzer.ApkAnalyzerCli.main(ApkAnalyzerCli.java:129)>
> Caused by: java.lang.ClassNotFoundException:>
> javax.xml.bind.annotation.XmlSchema at>>
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)>
> at>>
> java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)>
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:526) ...
> 5> more>>> On May 13, 2024, Erisu  wrote:> > Does
> anyone have any reason to delay a release for cordova-android?> >> > *
> cordova-android (13.0.0)> >> > https://github.com/apache/cordova-
> android/compare/rel/12.0.1...master> >> > Any additional outstanding
> changes to land?> >> > If not, I will start the release process
> shortly>

Re: [DISCUSS] cordova-android 13.0.0 Release

[Norman Breau]

Gradle 8.x supports JDK 11 - 17. Cordova android @12 used AGP 7.x which 
required 11, but 7.4 introduced support for JDK 17, it wasn't required.AGP 8.x 
introduces the requirement of JDK 17.What you might be thinking of though is 
command line tools package, one of the recent releases required JDK 17 (wanna 
say v13 but don't quite remember)Sent via the Samsung Galaxy Note9, an AT 5G 
Evolution capable smartphone
 Original message From: julio cesar sanchez 
 Date: 5/19/24  4:00 PM  (GMT-05:00) To: 
dev@cordova.apache.org Subject: Re: [DISCUSS] cordova-android 13.0.0 Release 
Unless something changed last minute, I think the gradle version usedrequired 
JDK 17, which has been bundled with Android Studio for around 1yearEl El dom, 
19 may 2024 a las 21:17, Niklas Merz escribió:> Which 
version of Java is required for this release? Is 11 from the docs> still up-to 
date? I had a build error and updated Java and Gradle.>> 
 Gradle 8.3> 
 Build time:> 
2023-08-17 07:06:47 UTC Revision:> 8afbf24b469158b714b36e84c6f4d4976c86fcd5 
Kotlin: 1.9.0 Groovy: 3.0.17> Ant: Apache Ant(TM) version 1.10.13 compiled on 
January 4 2023 JVM:> 21.0.3 (Eclipse Adoptium 21.0.3+9-LTS) OS: Linux 
6.5.0-35-generic amd64>> Now I get an error while building:>> BUILD SUCCESSFUL 
in 8s 1 actionable task: 1 executed Subproject Path:> CordovaLib Subproject 
Path: app BUILD SUCCESSFUL in 1s 50 actionable> tasks: 50 up-to-date Built the 
following apk(s):>> 
/home/niklas/apache/vote/android/app/platforms/android/app/build/outputs/apk/debug/app->
 debug.apk Checking Java JDK and Android SDK versions> 
ANDROID_HOME=/home/niklas/Android/Sdk (recommended setting)> 
ANDROID_SDK_ROOT=/home/niklas/Android/Sdk (DEPRECATED) Using Android> SDK: 
/home/niklas/Android/Sdk Command failed with exit code 1:> apkanalyzer manifest 
target-sdk>> 
/home/niklas/apache/vote/android/app/platforms/android/app/build/outputs/apk/debug/app->
 debug.apk Exception in thread "main" java.lang.NoClassDefFoundError:> 
javax/xml/bind/annotation/XmlSchema at>> 
com.android.repository.api.SchemaModule$SchemaModuleVersion.(SchemaModule.java:156)>
 at com.android.repository.api.SchemaModule.(SchemaModule.java:75)> at>> 
com.android.sdklib.repository.AndroidSdkHandler.(AndroidSdkHandler.java:81)>
 at>> 
com.android.tools.apk.analyzer.ApkAnalyzerCli.getAaptInvokerFromSdk(ApkAnalyzerCli.java:277)>
 at> 
com.android.tools.apk.analyzer.ApkAnalyzerCli.main(ApkAnalyzerCli.java:129)> 
Caused by: java.lang.ClassNotFoundException:> 
javax.xml.bind.annotation.XmlSchema at>> 
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)>
 at>> 
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)>
 at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:526) ... 5> 
more>>> On May 13, 2024, Erisu  wrote:> > Does anyone have 
any reason to delay a release for cordova-android?> >> > * cordova-android 
(13.0.0)> >> > 
https://github.com/apache/cordova-android/compare/rel/12.0.1...master> >> > Any 
additional outstanding changes to land?> >> > If not, I will start the release 
process shortly>

Re: [DISCUSS] cordova-android 13.0.0 Release

[Norman Breau]

Jdk 17 will be a requirement. Don't think cordova-docs has an update or a PR 
yet.Sent via the Samsung Galaxy Note9, an AT 5G Evolution capable smartphone
 Original message From: Niklas Merz  
Date: 5/19/24  3:17 PM  (GMT-05:00) To: dev@cordova.apache.org Subject: Re: 
[DISCUSS] cordova-android 13.0.0 Release Which version of Java is required for 
this release? Is 11 from the docsstill up-to date? I had a build error and 
updated Java and 
Gradle. Gradle 
8.3 Build 
time:2023-08-17 07:06:47 UTC Revision:8afbf24b469158b714b36e84c6f4d4976c86fcd5 
Kotlin: 1.9.0 Groovy: 3.0.17Ant: Apache Ant(TM) version 1.10.13 compiled on 
January 4 2023 JVM:21.0.3 (Eclipse Adoptium 21.0.3+9-LTS) OS: Linux 
6.5.0-35-generic amd64Now I get an error while building:BUILD SUCCESSFUL in 8s 
1 actionable task: 1 executed Subproject Path:CordovaLib Subproject Path: app 
BUILD SUCCESSFUL in 1s 50 actionabletasks: 50 up-to-date Built the following 
apk(s):/home/niklas/apache/vote/android/app/platforms/android/app/build/outputs/apk/debug/app-debug.apk
 Checking Java JDK and Android SDK 
versionsANDROID_HOME=/home/niklas/Android/Sdk (recommended 
setting)ANDROID_SDK_ROOT=/home/niklas/Android/Sdk (DEPRECATED) Using 
AndroidSDK: /home/niklas/Android/Sdk Command failed with exit code 
1:apkanalyzer manifest 
target-sdk/home/niklas/apache/vote/android/app/platforms/android/app/build/outputs/apk/debug/app-debug.apk
 Exception in thread "main" 
java.lang.NoClassDefFoundError:javax/xml/bind/annotation/XmlSchema 
atcom.android.repository.api.SchemaModule$SchemaModuleVersion.(SchemaModule.java:156)at
 
com.android.repository.api.SchemaModule.(SchemaModule.java:75)atcom.android.sdklib.repository.AndroidSdkHandler.(AndroidSdkHandler.java:81)atcom.android.tools.apk.analyzer.ApkAnalyzerCli.getAaptInvokerFromSdk(ApkAnalyzerCli.java:277)atcom.android.tools.apk.analyzer.ApkAnalyzerCli.main(ApkAnalyzerCli.java:129)Caused
 by: java.lang.ClassNotFoundException:javax.xml.bind.annotation.XmlSchema 
atjava.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)atjava.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)at
 java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:526) ... 5moreOn 
May 13, 2024, Erisu  wrote:> Does anyone have any reason to 
delay a release for cordova-android?>> * cordova-android (13.0.0)>> 
https://github.com/apache/cordova-android/compare/rel/12.0.1...master>> Any 
additional outstanding changes to land?>> If not, I will start the release 
process shortly

Re: [DISCUSS] cordova-android 13.0.0 Release

[julio cesar sanchez]

Unless something changed last minute, I think the gradle version used
required JDK 17, which has been bundled with Android Studio for around 1
year

El El dom, 19 may 2024 a las 21:17, Niklas Merz 
escribió:

> Which version of Java is required for this release? Is 11 from the docs
> still up-to date? I had a build error and updated Java and Gradle.
>
>  Gradle 8.3
>  Build time:
> 2023-08-17 07:06:47 UTC Revision:
> 8afbf24b469158b714b36e84c6f4d4976c86fcd5 Kotlin: 1.9.0 Groovy: 3.0.17
> Ant: Apache Ant(TM) version 1.10.13 compiled on January 4 2023 JVM:
> 21.0.3 (Eclipse Adoptium 21.0.3+9-LTS) OS: Linux 6.5.0-35-generic amd64
>
> Now I get an error while building:
>
> BUILD SUCCESSFUL in 8s 1 actionable task: 1 executed Subproject Path:
> CordovaLib Subproject Path: app BUILD SUCCESSFUL in 1s 50 actionable
> tasks: 50 up-to-date Built the following apk(s):
>
> /home/niklas/apache/vote/android/app/platforms/android/app/build/outputs/apk/debug/app-
> debug.apk Checking Java JDK and Android SDK versions
> ANDROID_HOME=/home/niklas/Android/Sdk (recommended setting)
> ANDROID_SDK_ROOT=/home/niklas/Android/Sdk (DEPRECATED) Using Android
> SDK: /home/niklas/Android/Sdk Command failed with exit code 1:
> apkanalyzer manifest target-sdk
>
> /home/niklas/apache/vote/android/app/platforms/android/app/build/outputs/apk/debug/app-
> debug.apk Exception in thread "main" java.lang.NoClassDefFoundError:
> javax/xml/bind/annotation/XmlSchema at
>
> com.android.repository.api.SchemaModule$SchemaModuleVersion.(SchemaModule.java:156)
> at com.android.repository.api.SchemaModule.(SchemaModule.java:75)
> at
>
> com.android.sdklib.repository.AndroidSdkHandler.(AndroidSdkHandler.java:81)
> at
>
> com.android.tools.apk.analyzer.ApkAnalyzerCli.getAaptInvokerFromSdk(ApkAnalyzerCli.java:277)
> at
> com.android.tools.apk.analyzer.ApkAnalyzerCli.main(ApkAnalyzerCli.java:129)
> Caused by: java.lang.ClassNotFoundException:
> javax.xml.bind.annotation.XmlSchema at
>
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)
> at
>
> java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:526) ... 5
> more
>
>
> On May 13, 2024, Erisu  wrote:
> > Does anyone have any reason to delay a release for cordova-android?
> >
> > * cordova-android (13.0.0)
> >
> > https://github.com/apache/cordova-android/compare/rel/12.0.1...master
> >
> > Any additional outstanding changes to land?
> >
> > If not, I will start the release process shortly
>

Re: [DISCUSS] cordova-android 13.0.0 Release

[Niklas Merz]

Which version of Java is required for this release? Is 11 from the docs
still up-to date? I had a build error and updated Java and Gradle.

 Gradle 8.3
 Build time:
2023-08-17 07:06:47 UTC Revision:
8afbf24b469158b714b36e84c6f4d4976c86fcd5 Kotlin: 1.9.0 Groovy: 3.0.17
Ant: Apache Ant(TM) version 1.10.13 compiled on January 4 2023 JVM:
21.0.3 (Eclipse Adoptium 21.0.3+9-LTS) OS: Linux 6.5.0-35-generic amd64

Now I get an error while building:

BUILD SUCCESSFUL in 8s 1 actionable task: 1 executed Subproject Path:
CordovaLib Subproject Path: app BUILD SUCCESSFUL in 1s 50 actionable
tasks: 50 up-to-date Built the following apk(s):
/home/niklas/apache/vote/android/app/platforms/android/app/build/outputs/apk/debug/app-
debug.apk Checking Java JDK and Android SDK versions
ANDROID_HOME=/home/niklas/Android/Sdk (recommended setting)
ANDROID_SDK_ROOT=/home/niklas/Android/Sdk (DEPRECATED) Using Android
SDK: /home/niklas/Android/Sdk Command failed with exit code 1:
apkanalyzer manifest target-sdk
/home/niklas/apache/vote/android/app/platforms/android/app/build/outputs/apk/debug/app-
debug.apk Exception in thread "main" java.lang.NoClassDefFoundError:
javax/xml/bind/annotation/XmlSchema at
com.android.repository.api.SchemaModule$SchemaModuleVersion.(SchemaModule.java:156)
at com.android.repository.api.SchemaModule.(SchemaModule.java:75)
at
com.android.sdklib.repository.AndroidSdkHandler.(AndroidSdkHandler.java:81)
at
com.android.tools.apk.analyzer.ApkAnalyzerCli.getAaptInvokerFromSdk(ApkAnalyzerCli.java:277)
at
com.android.tools.apk.analyzer.ApkAnalyzerCli.main(ApkAnalyzerCli.java:129)
Caused by: java.lang.ClassNotFoundException:
javax.xml.bind.annotation.XmlSchema at
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)
at
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:526) ... 5
more


On May 13, 2024, Erisu  wrote:
> Does anyone have any reason to delay a release for cordova-android?
>
> * cordova-android (13.0.0)
>
> https://github.com/apache/cordova-android/compare/rel/12.0.1...master
>
> Any additional outstanding changes to land?
>
> If not, I will start the release process shortly

Re: [VOTE] Cordova-Android 13.0.0 Release

[Alexandre Alves]

I vote +1:

- Ran NPM Test on Windows with NodeJS 18
- Verified Archive
- Verified Tags
- NPM Audit is OK
- Build and ran a production app with no issues

Alexandre Alves

From: Norman Breau 
Sent: Wednesday, May 15, 2024 1:35:08 PM
To: dev@cordova.apache.org 
Subject: Re: [VOTE] Cordova-Android 13.0.0 Release

I vote +1:

- Ran NPM Test on Linux/Fedora with NodeJS 20
- Ran NPM Test on MacOS with NodeJS 20
- Verified Archive
- Verified Tags
- NPM Audit is good

On 2024-05-15 08:01, Bryan Ellis wrote:
> Please review and vote on this Cordova-Android Release v13.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-v13.0.0
>
> The package was published from its corresponding git tag:
>
>  cordova-android: 13.0.0 (2143045d4e)
>
> Note that you can test it out via:
>
>  cordova platform add https://github.com/apache/cordova-android#13.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
> * 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-Android 13.0.0 Release

[Norman Breau]

I vote +1:

- Ran NPM Test on Linux/Fedora with NodeJS 20
- Ran NPM Test on MacOS with NodeJS 20
- Verified Archive
- Verified Tags
- NPM Audit is good

On 2024-05-15 08:01, Bryan Ellis wrote:

Please review and vote on this Cordova-Android Release v13.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-v13.0.0

The package was published from its corresponding git tag:

 cordova-android: 13.0.0 (2143045d4e)

Note that you can test it out via:

 cordova platform add https://github.com/apache/cordova-android#13.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
* 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

[VOTE] Cordova-Android 13.0.0 Release

[Bryan Ellis]

Please review and vote on this Cordova-Android Release v13.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-v13.0.0

The package was published from its corresponding git tag:

cordova-android: 13.0.0 (2143045d4e)

Note that you can test it out via:

cordova platform add https://github.com/apache/cordova-android#13.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
* Ran `cordova build` test
* Ran `cordova run` emulator test
* Ran `cordova plugin add` test

Community over Code EU 2024: The countdown has started!

[Ryan Skraba]

[Note: You're receiving this email because you are subscribed to one
or more project dev@ mailing lists at the Apache Software Foundation.]

We are very close to Community Over Code EU -- check out the amazing
program and the special discounts that we have for you.

Special discounts

You still have the opportunity to secure your ticket for Community
Over Code EU. Explore the various options available, including the
regular pass, the committer and groups pass, and now introducing the
one-day pass tailored for locals in Bratislava.

We also have a special discount for you to attend both Community Over
Code and Berlin Buzzwords from June 9th to 11th. Visit our website to
find out more about this opportunity and contact te...@sg.com.mx to
get the discount code.

Take advantage of the discounts and register now!
https://eu.communityovercode.org/tickets/

Check out the full program!

This year Community Over Code Europe will bring to you three days of
keynotes and sessions that cover topics of interest for ASF projects
and the greater open source ecosystem including data engineering,
performance engineering, search, Internet of Things (IoT) as well as
sessions with tips and lessons learned on building a healthy open
source community.

Check out the program: https://eu.communityovercode.org/program/

Keynote speaker highlights for Community Over Code Europe include:

* Dirk-Willem Van Gulik, VP of Public Policy at the Apache Software
Foundation, will discuss the Cyber Resiliency Act and its impact on
open source (All your code belongs to Policy Makers, Politicians, and
the Law).

* Dr. Sherae Daniel will share the results of her study on the impact
of self-promotion for open source software developers (To Toot or not
to Toot, that is the question).

* Asim Hussain, Executive Director of the Green Software Foundation
will present a framework they have developed for quantifying the
environmental impact of software (Doing for Sustainability what Open
Source did for Software).

* Ruth Ikegah will  discuss the growth of the open source movement in
Africa (From Local Roots to Global Impact: Building an Inclusive Open
Source Community in Africa)

* A discussion panel on EU policies and regulations affecting
specialists working in Open Source Program Offices

Additional activities

* Poster sessions: We invite you to stop by our poster area and see if
the ideas presented ignite a conversation within your team.

* BOF time: Don't miss the opportunity to discuss in person with your
open source colleagues on your shared interests.

* Participants reception: At the end of the first day, we will have a
reception at the event venue. All participants are welcome to attend!

* Spontaneous talks: There is a dedicated room and social space for
having spontaneous talks and sessions. Get ready to share with your
peers.

* Lighting talks: At the end of the event we will have the awaited
Lighting talks, where every participant is welcome to share and
enlighten us.

Please remember:  If you haven't applied for the visa, we will provide
the necessary letter for the process. In the unfortunate case of a
visa rejection, your ticket will be reimbursed.

See you in Bratislava,

Community Over Code EU Team

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [DISCUSS] cordova-plugin-device 3.0.0 Release

[julio cesar sanchez]

I’ve merged my two breaking PRs.

We could also merge https://github.com/apache/cordova-plugin-device/pull/62
It would require to set engines to cordova-android >= 7, which is very old
anyway

El lunes, 13 de mayo de 2024, Bryan Ellis  escribió:

> Does anyone have any reason to delay a release for cordova-plugin-device?
>
> * cordova-plugin-device (3.0.0)
>
> https://github.com/apache/cordova-plugin-device/compare/rel/2.1.0...master
>
> Any additional outstanding changes to land?
>
> If not, I will start the release process shortly
>

[DISCUSS] cordova-android 13.0.0 Release

[Bryan Ellis]

Does anyone have any reason to delay a release for cordova-android?

* cordova-android (13.0.0)

https://github.com/apache/cordova-android/compare/rel/12.0.1...master

Any additional outstanding changes to land?

If not, I will start the release process shortly

Re: [DISCUSS] cordova-plugin-device 2.2.0 Release

[Bryan Ellis]

This thread is closed and replaced with "[DISCUSS] cordova-plugin-device
3.0.0 Release" as there were no objections to target the next major release.


On Tue, May 7, 2024 at 10:29 PM julio cesar sanchez 
wrote:

> The breaking changes don’t really affect non deprecated platforms, so I
> don’t see a problem going with the major release directly.
>
> El El mar, 7 may 2024 a las 14:18, Bryan Ellis 
> escribió:
>
> > Are there any objections if we change the target release to a major
> > release?
> >
> > The main changes currently in the branch are:
> >
> > - Added bundled resources for privacy manifest in iOS.
> > - Fixed electron to use the correct engine version 2.1.0 in package.json.
> >
> > Would the corrected engine version necessitate a minor release,
> considering
> > we typically don't backport changes? If it isn't necessary, I might not
> > find any reasons to object to proceeding with a major release.
> >
> >
> >
> > On Tue, May 7, 2024 at 7:01 PM julio cesar sanchez <
> jcesarmob...@gmail.com
> > >
> > wrote:
> >
> > > I have two pending PRs, but they are breaking (removing deprecated
> > > platforms and unused code), so if they get merged, the release would be
> > > 3.0.0. not 2.2.0
> > >
> > > El mar, 7 may 2024 a las 7:17, Bryan Ellis ()
> > escribió:
> > >
> > > > Does anyone have any reason to delay a release for
> > cordova-plugin-device?
> > > >
> > > > * cordova-plugin-device (2.2.0)
> > > >
> > > >
> > >
> >
> https://github.com/apache/cordova-plugin-device/compare/rel/2.1.0...master
> > > >
> > > > Any additional outstanding changes to land?
> > > >
> > > > If not, I will start the release process shortly
> > > >
> > >
> >
>

[DISCUSS] cordova-plugin-device 3.0.0 Release

[Bryan Ellis]

Does anyone have any reason to delay a release for cordova-plugin-device?

* cordova-plugin-device (3.0.0)

https://github.com/apache/cordova-plugin-device/compare/rel/2.1.0...master

Any additional outstanding changes to land?

If not, I will start the release process shortly

Re: Notice for API 34 PR

[Norman Breau]

For record-keeping,

We've found a way to avoid checking in the wrapper while still 
maintaining the ability to use wide range of gradle versions to 
initialize the wrapper. This means the PR is no longer redistributing 
the JAR or any other gradle wrapper files.


On 2024-05-09 14:53, Norman Breau wrote:

Hi Team,

I just want to highlight some things about the Android 34 PR[4] to 
make sure it's reviewed properly.


Namely around the Gradle management changes that the PR introduces. To 
summarize, Cordova-android@12 and earlier utilised an empty 
wrapper.gradle file to create a wrapper task to install the wrapper of 
a given version. The empty wrapper.gradle file allowed gradle to do 
it's thing without importing AGP or any other modules that may require 
a specific gradle version. This in turn allowed end users to have 
pretty much any gradle version installed and we would be able to 
install the wrapper at the version that the android project needs.


However this strategy relies on the deprecated/removed -b flag which 
allowed you to specify a "build.gradle" file. This means we can't 
specify the wrapper.gradle file anymore.


The PR went through several iterations but I'll skip ahead to the 
current state.


As recommended by Gradle[1], the PR now includes the wrapper in the 
repository, including the .jar file. Cordova-Android tooling no longer 
uses the system gradle at all, and exclusively uses this wrapper. 
Otherwise the end-user would have to have a system gradle version that 
satisfies AGP requirements (currently that is Gradle >= 8.6). There 
was some concerns about redistributing this wrapper file and/or binary 
files with our releases, so I reviewed Apache Licensing policy[2].


I believe we are in the clear because the policy has instructions for 
how to bundle dependencies, and what is acceptable vs not acceptable. 
For context, the Gradle build tools is licensed[3] under Apache 2-0.


Under bundling Apache 2-0, the policy states:

"Assuming that the bundled dependency itself contains no bundled 
sub-components under other licenses, so the ALv2 applies uniformly to 
all files, there is no need to modify LICENSE. However, for 
completeness it is useful to list the products and their versions, as 
is done for products under other licenses.


If the dependency supplies a NOTICE file, its contents must be 
analyzed and the relevant portions bubbled up into the top-level 
NOTICE file."


Gradle Wrapper itself doesn't provide any LICENSE or NOTICE files 
along, so there isn't anything to bubble up in our NOTICE file. 
Therefore the only thing that is recommended (but not required) is to 
list the Gradle Wrapper and it's version within our own license file.


Additionally, Apache's instructions has Binary distribution section 
which reads as follows:


"What applies to canonical source distributions also applies to all 
redistributions, including binary redistributions:


All redistributions must obey the licensing requirements of the contents.

When assembling binary distributions, it is common to pull in and 
bundle additional dependencies which are not bundled with the source 
distribution. You must account for these additional dependencies in 
LICENSE and NOTICE. As a result, the LICENSE and NOTICE files for a 
binary distribution may differ from those in the source distribution 
it was built from.


In any case, the principle remains the same: LICENSE and NOTICE must 
exactly represent the contents of the distribution they reside in."


In otherwords, binary redistristributions are to be handled exactly 
the same way as source redistributions.


I just wanted to highlight this detail in case if there are further 
concerns that should be addressed before the PR is merged.


Cheers,

[1] 
https://docs.gradle.org/current/userguide/gradle_wrapper.html#sec:adding_wrapper

[2] https://infra.apache.org/licensing-howto.html#bundle-asf-product
[3] https://docs.gradle.org/current/userguide/licenses.html
[4] https://github.com/apache/cordova-android/pull/1678



-
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

Notice for API 34 PR

[Norman Breau]

Hi Team,

I just want to highlight some things about the Android 34 PR[4] to make 
sure it's reviewed properly.


Namely around the Gradle management changes that the PR introduces. To 
summarize, Cordova-android@12 and earlier utilised an empty 
wrapper.gradle file to create a wrapper task to install the wrapper of a 
given version. The empty wrapper.gradle file allowed gradle to do it's 
thing without importing AGP or any other modules that may require a 
specific gradle version. This in turn allowed end users to have pretty 
much any gradle version installed and we would be able to install the 
wrapper at the version that the android project needs.


However this strategy relies on the deprecated/removed -b flag which 
allowed you to specify a "build.gradle" file. This means we can't 
specify the wrapper.gradle file anymore.


The PR went through several iterations but I'll skip ahead to the 
current state.


As recommended by Gradle[1], the PR now includes the wrapper in the 
repository, including the .jar file. Cordova-Android tooling no longer 
uses the system gradle at all, and exclusively uses this wrapper. 
Otherwise the end-user would have to have a system gradle version that 
satisfies AGP requirements (currently that is Gradle >= 8.6). There was 
some concerns about redistributing this wrapper file and/or binary files 
with our releases, so I reviewed Apache Licensing policy[2].


I believe we are in the clear because the policy has instructions for 
how to bundle dependencies, and what is acceptable vs not acceptable. 
For context, the Gradle build tools is licensed[3] under Apache 2-0.


Under bundling Apache 2-0, the policy states:

"Assuming that the bundled dependency itself contains no bundled 
sub-components under other licenses, so the ALv2 applies uniformly to 
all files, there is no need to modify LICENSE. However, for completeness 
it is useful to list the products and their versions, as is done for 
products under other licenses.


If the dependency supplies a NOTICE file, its contents must be analyzed 
and the relevant portions bubbled up into the top-level NOTICE file."


Gradle Wrapper itself doesn't provide any LICENSE or NOTICE files along, 
so there isn't anything to bubble up in our NOTICE file. Therefore the 
only thing that is recommended (but not required) is to list the Gradle 
Wrapper and it's version within our own license file.


Additionally, Apache's instructions has Binary distribution section 
which reads as follows:


"What applies to canonical source distributions also applies to all 
redistributions, including binary redistributions:


All redistributions must obey the licensing requirements of the contents.

When assembling binary distributions, it is common to pull in and bundle 
additional dependencies which are not bundled with the source 
distribution. You must account for these additional dependencies in 
LICENSE and NOTICE. As a result, the LICENSE and NOTICE files for a 
binary distribution may differ from those in the source distribution it 
was built from.


In any case, the principle remains the same: LICENSE and NOTICE must 
exactly represent the contents of the distribution they reside in."


In otherwords, binary redistristributions are to be handled exactly the 
same way as source redistributions.


I just wanted to highlight this detail in case if there are further 
concerns that should be addressed before the PR is merged.


Cheers,

[1] 
https://docs.gradle.org/current/userguide/gradle_wrapper.html#sec:adding_wrapper

[2] https://infra.apache.org/licensing-howto.html#bundle-asf-product
[3] https://docs.gradle.org/current/userguide/licenses.html
[4] https://github.com/apache/cordova-android/pull/1678



-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [DISCUSS] cordova-plugin-device 2.2.0 Release

[julio cesar sanchez]

The breaking changes don’t really affect non deprecated platforms, so I
don’t see a problem going with the major release directly.

El El mar, 7 may 2024 a las 14:18, Bryan Ellis  escribió:

> Are there any objections if we change the target release to a major
> release?
>
> The main changes currently in the branch are:
>
> - Added bundled resources for privacy manifest in iOS.
> - Fixed electron to use the correct engine version 2.1.0 in package.json.
>
> Would the corrected engine version necessitate a minor release, considering
> we typically don't backport changes? If it isn't necessary, I might not
> find any reasons to object to proceeding with a major release.
>
>
>
> On Tue, May 7, 2024 at 7:01 PM julio cesar sanchez  >
> wrote:
>
> > I have two pending PRs, but they are breaking (removing deprecated
> > platforms and unused code), so if they get merged, the release would be
> > 3.0.0. not 2.2.0
> >
> > El mar, 7 may 2024 a las 7:17, Bryan Ellis ()
> escribió:
> >
> > > Does anyone have any reason to delay a release for
> cordova-plugin-device?
> > >
> > > * cordova-plugin-device (2.2.0)
> > >
> > >
> >
> https://github.com/apache/cordova-plugin-device/compare/rel/2.1.0...master
> > >
> > > Any additional outstanding changes to land?
> > >
> > > If not, I will start the release process shortly
> > >
> >
>

Re: [DISCUSS] cordova-plugin-device 2.2.0 Release

[Bryan Ellis]

Are there any objections if we change the target release to a major release?

The main changes currently in the branch are:

- Added bundled resources for privacy manifest in iOS.
- Fixed electron to use the correct engine version 2.1.0 in package.json.

Would the corrected engine version necessitate a minor release, considering
we typically don't backport changes? If it isn't necessary, I might not
find any reasons to object to proceeding with a major release.



On Tue, May 7, 2024 at 7:01 PM julio cesar sanchez 
wrote:

> I have two pending PRs, but they are breaking (removing deprecated
> platforms and unused code), so if they get merged, the release would be
> 3.0.0. not 2.2.0
>
> El mar, 7 may 2024 a las 7:17, Bryan Ellis () escribió:
>
> > Does anyone have any reason to delay a release for cordova-plugin-device?
> >
> > * cordova-plugin-device (2.2.0)
> >
> >
> https://github.com/apache/cordova-plugin-device/compare/rel/2.1.0...master
> >
> > Any additional outstanding changes to land?
> >
> > If not, I will start the release process shortly
> >
>

Re: [DISCUSS] cordova-plugin-device 2.2.0 Release

[julio cesar sanchez]

I have two pending PRs, but they are breaking (removing deprecated
platforms and unused code), so if they get merged, the release would be
3.0.0. not 2.2.0

El mar, 7 may 2024 a las 7:17, Bryan Ellis () escribió:

> Does anyone have any reason to delay a release for cordova-plugin-device?
>
> * cordova-plugin-device (2.2.0)
>
> https://github.com/apache/cordova-plugin-device/compare/rel/2.1.0...master
>
> Any additional outstanding changes to land?
>
> If not, I will start the release process shortly
>

[DISCUSS] cordova-plugin-file 8.1.0 Release

[Bryan Ellis]

Does anyone have any reason to delay a release for cordova-plugin-file?

* cordova-plugin-file (8.1.0)

https://github.com/apache/cordova-plugin-file/compare/rel/8.0.0...master

Any additional outstanding changes to land?

If not, I will start the release process shortly

[DISCUSS] cordova-plugin-device 2.2.0 Release

[Bryan Ellis]

Does anyone have any reason to delay a release for cordova-plugin-device?

* cordova-plugin-device (2.2.0)

https://github.com/apache/cordova-plugin-device/compare/rel/2.1.0...master

Any additional outstanding changes to land?

If not, I will start the release process shortly

[ANNOUNCEMENT] Cordova iOS 7.1.0 Release

[Bryan Ellis]

We have just released an update to our Cordova iOS platform!

- cordova-ios@7.1.0

You can view the release blog post at
https://cordova.apache.org/announcements/2024/04/03/cordova-ios-7.1.0.html

Community over Code EU 2024: Start planning your trip!

[Ryan Skraba]

[Note: You're receiving this email because you are subscribed to one
or more project dev@ mailing lists at the Apache Software Foundation.]

Dear community,

We hope you are doing great, are you ready for Community Over Code EU?
Check out the featured sessions, get your tickets with special
discounts and start planning your trip.

Save your spot! Take a look at our lineup of sessions, panelists and
featured speakers and make your final choice:

* EU policies and regulations affecting open source specialists working in OSPOs

The panel will discuss how EU legislation affects the daily work of
open source operations. Panelists will cover some recent policy
updates, the challenges of staying compliant when managing open source
contribution and usage within organizations, and their personal
experiences in adapting to the changing European regulatory
environment.

* Doing for sustainability, what open source did for software

In this keynote Asim Hussain will explain the history of Impact
Framework, a coalition of hundreds of software practitioners with
tangible solutions that directly foster meaningful change by measuring
the environmental impacts of a piece of software.

Don’t forget that we have special discounts for groups, students and
Apache committers. Visit the website to discover more about these
rates.[1]

It's time for you to start planning your trip. Remember that we have
prepared a “How to get there” guide that will be helpful to find out
the best transportation, either train, bus, flight or boat to
Bratislava from wherever you are coming from. Take a look at the
different options and please reach out to us if you have any
questions.

We have available rooms -with a special rate- at the Radisson Blu
Carlton Hotel, where the event will take place and at the Park Inn
Hotel which is only 5 minutes walking from the venue. [2] However, you
are free to choose any other accommodation options around the city.

See you in Bratislava,
Community Over Code EU Team

[1]: https://eu.communityovercode.org/tickets/ "Register"
[2]: https://eu.communityovercode.org/venue/ "Where to stay"

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Participate in the ASF 25th Anniversary Campaign

[Brian Proffitt]

Hi everyone,

As part of The ASF’s 25th anniversary campaign[1], we will be celebrating
projects and communities in multiple ways.

We invite all projects and contributors to participate in the following
ways:

* Individuals - submit your first contribution:
https://news.apache.org/foundation/entry/the-asf-launches-firstasfcontribution-campaign
* Projects - share your public good story:
https://docs.google.com/forms/d/1vuN-tUnBwpTgOE5xj3Z5AG1hsOoDNLBmGIqQHwQT6k8/viewform?edit_requested=true
* Projects - submit a project spotlight for the blog:
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=278466116
* Projects - contact the Voice of Apache podcast (formerly Feathercast) to
be featured: https://feathercast.apache.org/help/
*  Projects - use the 25th anniversary template and the #ASF25Years hashtag
on social media:
https://docs.google.com/presentation/d/1oDbMol3F_XQuCmttPYxBIOIjRuRBksUjDApjd8Ve3L8/edit#slide=id.g26b0919956e_0_13

If you have questions, email the Marketing & Publicity team at
mark...@apache.org.

Peace,
BKP

[1] https://apache.org/asf25years/

[NOTE: You are receiving this message because you are a contributor to an
Apache Software Foundation project. The ASF will very occasionally send out
messages relating to the Foundation to contributors and members, such as
this one.]

Brian Proffitt
VP, Marketing & Publicity
VP, Conferences

Re: [VOTE] Cordova-iOS 7.1.0 Release

[Bryan Ellis]

The vote has now closed. The results are:

Positive Binding Votes: 4

Bryan Ellis
Ken Naito
Norman Breau
Niklas Merz

Negative Binding Votes: 0

Other Votes: 0

The vote has passed.




On Wed, Apr 3, 2024 at 12:39 AM Niklas Merz  wrote:

> I vote +1
>
> - signature & hash ok
> - tag ok
> - npm audit ok
>
> On April 2, 2024, Norman Breau  wrote:
> > I vote +1:
> >
> > - Ran unit tests
> > - Verified Archive
> > - Verified Tags
> > - NPM Audit is good
> >
> > On 2024-04-01 1:17 a.m., Bryan Ellis wrote:
> > > Please review and vote on this Cordova-iOS Release v7.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/ios-v7.1.0
> > >
> > > The package was published from its corresponding git tag:
> > >
> > > cordova-ios: 7.1.0 (64c3051d2b)
> > >
> > > Note that you can test it out via:
> > >
> > > cordova platform add https://github.com/apache/cordova-ios#7.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
> > > * NPM Test
> > > * 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-iOS 7.1.0 Release

[Niklas Merz]

I vote +1

- signature & hash ok
- tag ok
- npm audit ok

On April 2, 2024, Norman Breau  wrote:
> I vote +1:
>
> - Ran unit tests
> - Verified Archive
> - Verified Tags
> - NPM Audit is good
>
> On 2024-04-01 1:17 a.m., Bryan Ellis wrote:
> > Please review and vote on this Cordova-iOS Release v7.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/ios-v7.1.0
> >
> > The package was published from its corresponding git tag:
> >
> > cordova-ios: 7.1.0 (64c3051d2b)
> >
> > Note that you can test it out via:
> >
> > cordova platform add https://github.com/apache/cordova-ios#7.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
> > * NPM Test
> > * 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-iOS 7.1.0 Release

[Norman Breau]

I vote +1:

- Ran unit tests
- Verified Archive
- Verified Tags
- NPM Audit is good

On 2024-04-01 1:17 a.m., Bryan Ellis wrote:

Please review and vote on this Cordova-iOS Release v7.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/ios-v7.1.0

The package was published from its corresponding git tag:

 cordova-ios: 7.1.0 (64c3051d2b)

Note that you can test it out via:

 cordova platform add https://github.com/apache/cordova-ios#7.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
* NPM Test
* 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-iOS 7.1.0 Release

[Ken Naito]

+1

I did:
* coho verify-archive OK
* coho verify-tags OK
* The current master cecfabb1c856cffe38807fdab585b20c71ca42fc is green.

Thank you.


On 2024/04/01 13:17, Bryan Ellis wrote:

 cordova-ios: 7.1.0 (64c3051d2b)

[DISCUSS] cordova-ios 7.1.0 Release

[Bryan Ellis]

Voting thread has been submitted for:

* cordova-ios (7.1.0)

If anyone has any reason to block the release, please leave a reason why on
this discussion thread and leave your vote on the voting thread.

https://github.com/apache/cordova-ios/compare/rel/7.0.1...7.1.0

[VOTE] Cordova-iOS 7.1.0 Release

[Bryan Ellis]

Please review and vote on this Cordova-iOS Release v7.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/ios-v7.1.0

The package was published from its corresponding git tag:

cordova-ios: 7.1.0 (64c3051d2b)

Note that you can test it out via:

cordova platform add https://github.com/apache/cordova-ios#7.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
* NPM Test
* Ran `cordova build` test
* Ran `cordova run` emulator test
* Ran `cordova plugin add` test

[ANNOUNCEMENT] Cordova ESLint 5.1.0 Release

[Bryan Ellis]

We have just released a minor update to our cordova eslint tool!
- cordova-eslint@5.1.0

Re: [VOTE] Cordova-ESLint 5.1.0 Release

[Bryan Ellis]

Correction

--

The vote has now closed. The results are:

Positive Binding Votes: 3

Bryan Ellis
Norman Breau
Niklas Merz

Negative Binding Votes: 0

Other Votes: 0

The vote has passed.


On Wed, Mar 27, 2024 at 9:28 PM Bryan Ellis  wrote:

> The vote has now closed. The results are:
>
> Positive Binding Votes: 3
>
> Bryan Ellis
> Norman Breau
>
> Negative Binding Votes: 0
>
> Other Votes: 0
>
> The vote has passed.
>
>
> On Tue, Mar 26, 2024 at 12:07 AM Niklas Merz 
> wrote:
>
>> I vote +1
>>
>> - signature & hash ok
>> - tests ok
>> - tag ok
>> - license looks ok
>> - npm audit ok
>>
>> On March 25, 2024, Norman Breau  wrote:
>> > I Vote +1:
>> >
>> > - Ran npm test
>> > - Ran npm audit
>> > - Verified Tags
>> > - Verified Archive
>> >
>> > On 2024-03-25 08:01, Bryan Ellis wrote:
>> > > Please review and vote on this Cordova ESLint Release v5.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/eslint-v5.1.0
>> > >
>> > > The package was published from its corresponding git tag:
>> > > cordova-eslint: 5.1.0 (ade608ad20)
>> > >
>> > > 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
>> > >
>> >
>> > -
>> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
>> > For additional commands, e-mail: dev-h...@cordova.apache.org
>>
>

Re: [VOTE] Cordova-ESLint 5.1.0 Release

[Bryan Ellis]

The vote has now closed. The results are:

Positive Binding Votes: 3

Bryan Ellis
Norman Breau

Negative Binding Votes: 0

Other Votes: 0

The vote has passed.


On Tue, Mar 26, 2024 at 12:07 AM Niklas Merz  wrote:

> I vote +1
>
> - signature & hash ok
> - tests ok
> - tag ok
> - license looks ok
> - npm audit ok
>
> On March 25, 2024, Norman Breau  wrote:
> > I Vote +1:
> >
> > - Ran npm test
> > - Ran npm audit
> > - Verified Tags
> > - Verified Archive
> >
> > On 2024-03-25 08:01, Bryan Ellis wrote:
> > > Please review and vote on this Cordova ESLint Release v5.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/eslint-v5.1.0
> > >
> > > The package was published from its corresponding git tag:
> > > cordova-eslint: 5.1.0 (ade608ad20)
> > >
> > > 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
> > >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > For additional commands, e-mail: dev-h...@cordova.apache.org
>

Community Over Code NA 2024 Travel Assistance Applications now open!

[Gavin McDonald]

Hello to all users, contributors and Committers!

[ You are receiving this email as a subscriber to one or more ASF project
dev or user
  mailing lists and is not being sent to you directly. It is important that
we reach all of our
  users and contributors/committers so that they may get a chance to
benefit from this.
  We apologise in advance if this doesn't interest you but it is on topic
for the mailing
  lists of the Apache Software Foundation; and it is important please that
you do not
  mark this as spam in your email client. Thank You! ]

The Travel Assistance Committee (TAC) are pleased to announce that
travel assistance applications for Community over Code NA 2024 are now
open!

We will be supporting Community over Code NA, Denver Colorado in
October 7th to the 10th 2024.

TAC exists to help those that would like to attend Community over Code
events, but are unable to do so for financial reasons. For more info
on this years applications and qualifying criteria, please visit the
TAC website at < https://tac.apache.org/ >. Applications are already
open on https://tac-apply.apache.org/, so don't delay!

The Apache Travel Assistance Committee will only be accepting
applications from those people that are able to attend the full event.

Important: Applications close on Monday 6th May, 2024.

Applicants have until the the closing date above to submit their
applications (which should contain as much supporting material as
required to efficiently and accurately process their request), this
will enable TAC to announce successful applications shortly
afterwards.

As usual, TAC expects to deal with a range of applications from a
diverse range of backgrounds; therefore, we encourage (as always)
anyone thinking about sending in an application to do so ASAP.

For those that will need a Visa to enter the Country - we advise you apply
now so that you have enough time in case of interview delays. So do not
wait until you know if you have been accepted or not.

We look forward to greeting many of you in Denver, Colorado , October 2024!

Kind Regards,

Gavin

(On behalf of the Travel Assistance Committee)

Re: [VOTE] Cordova-ESLint 5.1.0 Release

[Niklas Merz]

I vote +1

- signature & hash ok
- tests ok
- tag ok
- license looks ok
- npm audit ok

On March 25, 2024, Norman Breau  wrote:
> I Vote +1:
>
> - Ran npm test
> - Ran npm audit
> - Verified Tags
> - Verified Archive
>
> On 2024-03-25 08:01, Bryan Ellis wrote:
> > Please review and vote on this Cordova ESLint Release v5.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/eslint-v5.1.0
> >
> > The package was published from its corresponding git tag:
> > cordova-eslint: 5.1.0 (ade608ad20)
> >
> > 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
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [VOTE] Cordova-ESLint 5.1.0 Release

[Norman Breau]

I Vote +1:

- Ran npm test
- Ran npm audit
- Verified Tags
- Verified Archive

On 2024-03-25 08:01, Bryan Ellis wrote:

Please review and vote on this Cordova ESLint Release v5.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/eslint-v5.1.0

The package was published from its corresponding git tag:
 cordova-eslint: 5.1.0 (ade608ad20)

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



-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[VOTE] Cordova-ESLint 5.1.0 Release

[Bryan Ellis]

Please review and vote on this Cordova ESLint Release v5.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/eslint-v5.1.0

The package was published from its corresponding git tag:
cordova-eslint: 5.1.0 (ade608ad20)

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

[I] Combine multiple projects in one [cordova-discuss]

[via GitHub]

accgdevapps opened a new issue, #112:
URL: https://github.com/apache/cordova-discuss/issues/112

   Is it possible to create different individual projects, and then create a 
main project and include all individual project inside it??
   If yes, can anyone give me some steps?
   Thanks!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

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

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [DISCUSS] Cordova - XCPrivacyManifest & Code Signing Questions

[Michael (WWDR) Wong]

Thanks for getting back to me. Let me circulate with the team. 

> On Mar 18, 2024, at 9:02 AM, Norman Breau  wrote:
> 
> Hi Michael,
> 
> This is Norman, you've reached out to me back in October as a contact for 
> Cordova development on LinkedIn. I've cc'ed this to Cordova's development 
> mailing list so that you're answer will be broadcasted among Cordova 
> contributors. We have a few questions we'd like to ask to confirm our 
> understanding of what is required. First I want to take some time to describe 
> the general workflow of Cordova Projects.
> 
> Some definitions:
> - "End User" - The developer using the Cordova framework and tools.
> - "Developer" - The Cordova contributors that develops Cordova framework & 
> tooling.
> - "App" - Refers to the App's XCode project
> 
> Most end users uses the Cordova CLI which creates and manages a Xcode 
> workspace and projects for the user. This workspace contains 2 projects, 
> CordovaLib which builds a static library target and the iOS app project, 
> which consumes the CordovaLib static library. Apache does not distribute the 
> cordova framework as a static library, rather the sources are distributed and 
> the user will build it as part of their app project. Users can also install 
> cordova plugins, which is usually distributed as raw source code, that is 
> added to the app's project. In other words, the plugin's codebase becomes 
> part of the app's source code, rather than it being it's own project/module 
> with it's own build target & bundle.
> 
> Q1: In this workflow, it's our understanding that there is no bundle for 
> static libraries to package the privacy manifest. Does this mean the privacy 
> manifest must be declared as part of the App Xcode project?
> 
> Q2: It's our understanding that static libraries also cannot be code-signed, 
> so does that mean there is no supply chain verification for static libraries?
> 
> Q3: For Cordova plugins, because they don't have their own build target and 
> instead they become part of the app's source code, it feels safe to assume 
> that any privacy manifest entries that it should have needs to find its way 
> inside the App's privacy manifest file. Is this a correct understanding?
> 
> Q4: On Cordova plugins again, since they are often distributed as raw source, 
> there is also no framework/xcframework to be signed, defeating dependency 
> supply chain verification. Presumably there isn't anything that Cordova needs 
> to do as code signing will be required by the end user when packaging their 
> application. Is this the correct understanding?
> 
> Q5: This is kind of a follow-up question that kind of depends on the answers 
> to the above code-signing questions, but it seems like how Cordova operates 
> currently defeats the supply chain digital signatures, or at least cannot 
> take advantage of potential security checks it provides, as they appear to 
> depend on dependencies being distributed and consumed as xcframeworks. Is it 
> foreseeable to see restrictions against static libraries or some other "push" 
> for app developers to use frameworks over static libraries?
> 
> Thanks for your time Michael, looking forward to see your feedback.
> 

Re: [DISCUSS] Cordova - XCPrivacyManifest & Code Signing Questions

[Norman Breau]

Sorry, pasting the email seemed to have destroyed the formatting, I 
believe it was sent as HTML and then got stripped. Here's a version with 
a paste without formatting:


Hi Michael,

This is Norman, you've reached out to me back in October as a contact 
for Cordova development on LinkedIn. I've cc'ed this to Cordova's 
development mailing list so that you're answer will be broadcasted among 
Cordova contributors. We have a few questions we'd like to ask to 
confirm our understanding of what is required. First I want to take some 
time to describe the general workflow of Cordova Projects.


Some definitions:
- "End User" - The developer using the Cordova framework and tools.
- "Developer" - The Cordova contributors that develops Cordova framework 
& tooling.

- "App" - Refers to the App's XCode project

Most end users uses the Cordova CLI which creates and manages a Xcode 
workspace and projects for the user. This workspace contains 2 projects, 
CordovaLib which builds a static library target and the iOS app project, 
which consumes the CordovaLib static library. Apache does not distribute 
the cordova framework as a static library, rather the sources are 
distributed and the user will build it as part of their app project. 
Users can also install cordova plugins, which is usually distributed as 
raw source code, that is added to the app's project. In other words, the 
plugin's codebase becomes part of the app's source code, rather than it 
being it's own project/module with it's own build target & bundle.


Q1: In this workflow, it's our understanding that there is no bundle for 
static libraries to package the privacy manifest. Does this mean the 
privacy manifest must be declared as part of the App Xcode project?


Q2: It's our understanding that static libraries also cannot be 
code-signed, so does that mean there is no supply chain verification for 
static libraries?


Q3: For Cordova plugins, because they don't have their own build target 
and instead they become part of the app's source code, it feels safe to 
assume that any privacy manifest entries that it should have needs to 
find its way inside the App's privacy manifest file. Is this a correct 
understanding?


Q4: On Cordova plugins again, since they are often distributed as raw 
source, there is also no framework/xcframework to be signed, defeating 
dependency supply chain verification. Presumably there isn't anything 
that Cordova needs to do as code signing will be required by the end 
user when packaging their application. Is this the correct understanding?


Q5: This is kind of a follow-up question that kind of depends on the 
answers to the above code-signing questions, but it seems like how 
Cordova operates currently defeats the supply chain digital signatures, 
or at least cannot take advantage of potential security checks it 
provides, as they appear to depend on dependencies being distributed and 
consumed as xcframeworks. Is it foreseeable to see restrictions against 
static libraries or some other "push" for app developers to use 
frameworks over static libraries?


Thanks for your time Michael, looking forward to see your feedback.

On 2024-03-18 13:02, Norman Breau wrote:
Hi Michael, This is Norman, you've reached out to me back in October 
as a contact for Cordova development on LinkedIn. I've cc'ed this to 
Cordova's development mailing list so that you're answer will be 
broadcasted among Cordova contributors. We have a few questions we'd 
like to ask to confirm our understanding of what is required. First I 
want to take some time to describe the general workflow of Cordova 
Projects. Some definitions: - "End User" - The developer using the 
Cordova framework and tools. - "Developer" - The Cordova contributors 
that develops Cordova framework & tooling. - "App" - Refers to the 
App's XCode project Most end users uses the Cordova CLI which creates 
and manages a Xcode workspace and projects for the user. This 
workspace contains 2 projects, CordovaLib which builds a static 
library target and the iOS app project, which consumes the CordovaLib 
static library. Apache does not distribute the cordova framework as a 
static library, rather the sources are distributed and the user will 
build it as part of their app project. Users can also install cordova 
plugins, which is usually distributed as raw source code, that is 
added to the app's project. In other words, the plugin's codebase 
becomes part of the app's source code, rather than it being it's own 
project/module with it's own build target & bundle. Q1: In this 
workflow, it's our understanding that there is no bundle for static 
libraries to package the privacy manifest. Does this mean the privacy 
manifest must be declared as part of the App Xcode project? Q2: It's 
our understanding that static libraries also cannot be code-signed, so 
does that mean there is no supply chain verification for static 
libraries? Q3: For Cordova plugins, because they don't have their 

[DISCUSS] Cordova - XCPrivacyManifest & Code Signing Questions

[Norman Breau]

Hi Michael, This is Norman, you've reached out to me back in October as 
a contact for Cordova development on LinkedIn. I've cc'ed this to 
Cordova's development mailing list so that you're answer will be 
broadcasted among Cordova contributors. We have a few questions we'd 
like to ask to confirm our understanding of what is required. First I 
want to take some time to describe the general workflow of Cordova 
Projects. Some definitions: - "End User" - The developer using the 
Cordova framework and tools. - "Developer" - The Cordova contributors 
that develops Cordova framework & tooling. - "App" - Refers to the App's 
XCode project Most end users uses the Cordova CLI which creates and 
manages a Xcode workspace and projects for the user. This workspace 
contains 2 projects, CordovaLib which builds a static library target and 
the iOS app project, which consumes the CordovaLib static library. 
Apache does not distribute the cordova framework as a static library, 
rather the sources are distributed and the user will build it as part of 
their app project. Users can also install cordova plugins, which is 
usually distributed as raw source code, that is added to the app's 
project. In other words, the plugin's codebase becomes part of the app's 
source code, rather than it being it's own project/module with it's own 
build target & bundle. Q1: In this workflow, it's our understanding that 
there is no bundle for static libraries to package the privacy manifest. 
Does this mean the privacy manifest must be declared as part of the App 
Xcode project? Q2: It's our understanding that static libraries also 
cannot be code-signed, so does that mean there is no supply chain 
verification for static libraries? Q3: For Cordova plugins, because they 
don't have their own build target and instead they become part of the 
app's source code, it feels safe to assume that any privacy manifest 
entries that it should have needs to find its way inside the App's 
privacy manifest file. Is this a correct understanding? Q4: On Cordova 
plugins again, since they are often distributed as raw source, there is 
also no framework/xcframework to be signed, defeating dependency supply 
chain verification. Presumably there isn't anything that Cordova needs 
to do as code signing will be required by the end user when packaging 
their application. Is this the correct understanding? Q5: This is kind 
of a follow-up question that kind of depends on the answers to the above 
code-signing questions, but it seems like how Cordova operates currently 
defeats the supply chain digital signatures, or at least cannot take 
advantage of potential security checks it provides, as they appear to 
depend on dependencies being distributed and consumed as xcframeworks. 
Is it foreseeable to see restrictions against static libraries or some 
other "push" for app developers to use frameworks over static libraries? 
Thanks for your time Michael, looking forward to see your feedback.

Re: [PR] report: March 2024 [cordova-apache-board-reports]

[via GitHub]

erisu merged PR #21:
URL: https://github.com/apache/cordova-apache-board-reports/pull/21


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

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

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

March 2024 Board Report

[Bryan Ellis]

I have posted the draft PR for this quarter's report.

https://github.com/apache/cordova-apache-board-reports/pull/21

Let me know if there is anything you would like to add/change either here
or on the PR.

- Bryan

[PR] report: March 2024 [cordova-apache-board-reports]

[via GitHub]

erisu opened a new pull request, #21:
URL: https://github.com/apache/cordova-apache-board-reports/pull/21

   (no comment)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

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

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[ANNOUNCEMENT] Cordova Electron 4.0.0 Release

[Bryan Ellis]

We have just released an update to our electron platform!

- cordova-electron@4.0.0

You can view the release blog post at
https://cordova.apache.org/announcements/2024/03/11/cordova-electron-release-4.0.0.html

Re: [VOTE] Cordova-Electron 4.0.0 Release

[Bryan Ellis]

The vote has now closed. The results are:

Positive Binding Votes: 4

Bryan Ellis
Niklas Merz
Jesse MacFadyen
Ken Naito

Negative Binding Votes: 0

Other Votes: 0

The vote has passed.

On Mon, Mar 11, 2024 at 2:10 PM Jesse  wrote:

> +1
>
> - code review
> - built a new electron app
>
> On Sat, Mar 9, 2024 at 3:00 AM Niklas Merz  wrote:
>
> > I vote +1
> >
> > * signature ok
> > * hash ok
> > * new app builds with this platform on my system
> > * tag ok
> > * tests pass locally
> > * changes look good
> > * licenses & headers look ok
> >
> > On March 5, 2024, Erisu  wrote:
> > > Please review and vote on this Electron Release v4.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/electron-v4.0.0
> > >
> > >
> > > The package was published from its corresponding git tag:
> > >  cordova-electron: 4.0.0 (d2192b20dc)
> > >
> > >
> > > Note that you can test it out via:
> > >  cordova platform add https://github.com/apache/cordova-electron#4.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 sub-
> > > dependencies have Apache-compatible licenses
> > > * Ensured the `npm audit` report was sufficient for release
> > > * Ensured continuous build was green when repo was tagged
> > > * Ran `npm test`
> > > * Ran following `cordova` test in sample project:
> > >  * `cordova platform add cordova-electron-4.0.0.tgz`
> > >  * `cordova plugin add`
> > >  * `cordova build electron`
> > >  * `cordova run electron —nobuild`
> > >
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > > For additional commands, e-mail: dev-h...@cordova.apache.org
> >
>

Re: [VOTE] Cordova-Electron 4.0.0 Release

[Ken Naito]

+1

I did:

* coho verify-archive OK
* coho verify-tags OK
* The last commit 
https://github.com/apache/cordova-electron/commit/d2192b20dc40fb22a69fa7752e6681499578737a 
is verified.


Thanks.

Ken Naito.


On 2024/03/05 22:35, Bryan Ellis wrote:

Please review and vote on this Electron Release v4.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/electron-v4.0.0


The package was published from its corresponding git tag:
 cordova-electron: 4.0.0 (d2192b20dc)


Note that you can test it out via:
 cordova platform add https://github.com/apache/cordova-electron#4.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 sub-dependencies have 
Apache-compatible licenses
* Ensured the `npm audit` report was sufficient for release
* Ensured continuous build was green when repo was tagged
* Ran `npm test`
* Ran following `cordova` test in sample project:
   * `cordova platform add cordova-electron-4.0.0.tgz`
   * `cordova plugin add`
   * `cordova build electron`
   * `cordova run electron —nobuild`



-
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-Electron 4.0.0 Release

[Jesse]

+1

- code review
- built a new electron app

On Sat, Mar 9, 2024 at 3:00 AM Niklas Merz  wrote:

> I vote +1
>
> * signature ok
> * hash ok
> * new app builds with this platform on my system
> * tag ok
> * tests pass locally
> * changes look good
> * licenses & headers look ok
>
> On March 5, 2024, Erisu  wrote:
> > Please review and vote on this Electron Release v4.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/electron-v4.0.0
> >
> >
> > The package was published from its corresponding git tag:
> >  cordova-electron: 4.0.0 (d2192b20dc)
> >
> >
> > Note that you can test it out via:
> >  cordova platform add https://github.com/apache/cordova-electron#4.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 sub-
> > dependencies have Apache-compatible licenses
> > * Ensured the `npm audit` report was sufficient for release
> > * Ensured continuous build was green when repo was tagged
> > * Ran `npm test`
> > * Ran following `cordova` test in sample project:
> >  * `cordova platform add cordova-electron-4.0.0.tgz`
> >  * `cordova plugin add`
> >  * `cordova build electron`
> >  * `cordova run electron —nobuild`
> >
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > For additional commands, e-mail: dev-h...@cordova.apache.org
>

Re: [VOTE] Cordova-Electron 4.0.0 Release

[Niklas Merz]

I vote +1

* signature ok
* hash ok
* new app builds with this platform on my system
* tag ok
* tests pass locally
* changes look good
* licenses & headers look ok

On March 5, 2024, Erisu  wrote:
> Please review and vote on this Electron Release v4.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/electron-v4.0.0
>
>
> The package was published from its corresponding git tag:
>  cordova-electron: 4.0.0 (d2192b20dc)
>
>
> Note that you can test it out via:
>  cordova platform add https://github.com/apache/cordova-electron#4.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 sub-
> dependencies have Apache-compatible licenses
> * Ensured the `npm audit` report was sufficient for release
> * Ensured continuous build was green when repo was tagged
> * Ran `npm test`
> * Ran following `cordova` test in sample project:
>  * `cordova platform add cordova-electron-4.0.0.tgz`
>  * `cordova plugin add`
>  * `cordova build electron`
>  * `cordova run electron —nobuild`
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org

[VOTE] Cordova-Electron 4.0.0 Release

[Bryan Ellis]

Please review and vote on this Electron Release v4.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/electron-v4.0.0


The package was published from its corresponding git tag:
cordova-electron: 4.0.0 (d2192b20dc)


Note that you can test it out via:
cordova platform add https://github.com/apache/cordova-electron#4.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 sub-dependencies have 
Apache-compatible licenses
* Ensured the `npm audit` report was sufficient for release
* Ensured continuous build was green when repo was tagged
* Ran `npm test`
* Ran following `cordova` test in sample project:
  * `cordova platform add cordova-electron-4.0.0.tgz`
  * `cordova plugin add`
  * `cordova build electron`
  * `cordova run electron —nobuild`



-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [DISCUSS] cordova-electron 4.0.0 Release

[James Kruth]

On Fri, Mar 1, 2024, at 06:07, Bryan Ellis wrote:
> Does anyone have any reason to delay a release for cordova-electron?
> 
> * cordova-electron (4.0.0)
> 
> Any additional outstanding changes to land?
> 
> If not, I will start the release process shortly
> 
> https://github.com/apache/cordova-electron/compare/rel/3.1.0...master

We're looking forward to the new release here! Thanks for pushing it out.

- James

[DISCUSS] cordova-electron 4.0.0 Release

[Bryan Ellis]

Does anyone have any reason to delay a release for cordova-electron?

* cordova-electron (4.0.0)

Any additional outstanding changes to land?

If not, I will start the release process shortly

https://github.com/apache/cordova-electron/compare/rel/3.1.0...master

Community Over Code Asia 2024 Travel Assistance Applications now open!

[Gavin McDonald]

Hello to all users, contributors and Committers!

The Travel Assistance Committee (TAC) are pleased to announce that
travel assistance applications for Community over Code Asia 2024 are now
open!

We will be supporting Community over Code Asia, Hangzhou, China
July 26th - 28th, 2024.

TAC exists to help those that would like to attend Community over Code
events, but are unable to do so for financial reasons. For more info
on this year's applications and qualifying criteria, please visit the
TAC website at < https://tac.apache.org/ >. Applications are already
open on https://tac-apply.apache.org/, so don't delay!

The Apache Travel Assistance Committee will only be accepting
applications from those people that are able to attend the full event.

Important: Applications close on Friday, May 10th, 2024.

Applicants have until the the closing date above to submit their
applications (which should contain as much supporting material as
required to efficiently and accurately process their request), this
will enable TAC to announce successful applications shortly
afterwards.

As usual, TAC expects to deal with a range of applications from a
diverse range of backgrounds; therefore, we encourage (as always)
anyone thinking about sending in an application to do so ASAP.

For those that will need a Visa to enter the Country - we advise you to
apply
now so that you have enough time in case of interview delays. So do not
wait until you know if you have been accepted or not.

We look forward to greeting many of you in Hangzhou, China in July, 2024!

Kind Regards,

Gavin

(On behalf of the Travel Assistance Committee)

HOPE and Defcon event badge designing with Cordova

[hopespons]

Hello Cordova hackers,

Some of us are trying to introduce electronic hacker badges to a few 
events where Cordova technology could be very welcome. Such badges are 
electronic PCBs of various grades (some very high value with injection 
moulded enclosures) given to each event attendee at the entrance.


If you're enthusiastic about making the phone facing application a 
Cordova one, then I hope you will indicate interest here so that we can 
explore the options together. I think this may be quite easy if enough 
of us collaborate.


The graphics environment running on the badge's ESP32-C6 chip is LVGL by 
the way, and it can communicate with a phone over Bluetooth and NFC.


To learn more about HOPE in New York (July 2024) take a look at the high 
profile speakers like Steve Wozniak and Jello Biafra that have 
contributed in past years https://www.hope.net/


Cheers,
Michael

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Community over Code EU 2024 Travel Assistance Applications now open!

[Gavin McDonald]

Hello to all users, contributors and Committers!

The Travel Assistance Committee (TAC) are pleased to announce that
travel assistance applications for Community over Code EU 2024 are now
open!

We will be supporting Community over Code EU, Bratislava, Slovakia,
June 3th - 5th, 2024.

TAC exists to help those that would like to attend Community over Code
events, but are unable to do so for financial reasons. For more info
on this years applications and qualifying criteria, please visit the
TAC website at < https://tac.apache.org/ >. Applications are already
open on https://tac-apply.apache.org/, so don't delay!

The Apache Travel Assistance Committee will only be accepting
applications from those people that are able to attend the full event.

Important: Applications close on Friday, March 1st, 2024.

Applicants have until the the closing date above to submit their
applications (which should contain as much supporting material as
required to efficiently and accurately process their request), this
will enable TAC to announce successful applications shortly
afterwards.

As usual, TAC expects to deal with a range of applications from a
diverse range of backgrounds; therefore, we encourage (as always)
anyone thinking about sending in an application to do so ASAP.

For those that will need a Visa to enter the Country - we advise you apply
now so that you have enough time in case of interview delays. So do not
wait until you know if you have been accepted or not.

We look forward to greeting many of you in Bratislava, Slovakia in June,
2024!

Kind Regards,

Gavin

(On behalf of the Travel Assistance Committee)

Re: Regarding cordova android build

[Norman Breau]

If you're building the current stable (e.g. v12)...

Gradle 8 isn't supported by cordova-android and is known
to have issues. Normally the system gradle version doesn't matter since 
it's only

used to install the gradle wrapper at the correct version, however Gradle 8
doesn't seem to like installing a Gradle 7 wrapper so I'd advise 
installing the

latest version of 7.x as your system gradle.

There's a API 34 Support PR[1] that makes the changes to support API 34,
and by extension, Gradle 8.

[1] https://github.com/apache/cordova-android/pull/1678

On 2024-01-24 08:31, Riza Dindir wrote:

Hello,

A couple of days ago I was able to build cordova applications. Today I can
not build a cordova application. Did something change?

I am using gradle 8.5 on kernel 5.15.145. The "cordova requirements"
command result is

Requirements check results for android:
Java JDK: installed 17.0.6
Android SDK: installed true
Android target: installed android-33,android-32,android-31
Gradle: installed /usr/share/gradle/bin/gradle

Requirements check results for browser:

And the result for the build command "cordova build android" is

Checking Java JDK and Android SDK versions
ANDROID_HOME=/opt/android-sdk (recommended setting)
ANDROID_SDK_ROOT=/opt/android-sdk (DEPRECATED)
Using Android SDK: /opt/android-sdk

FAILURE: Build failed with an exception.

* What went wrong:
Could not initialize class org.codehaus.groovy.runtime.InvokerHelper

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or
--debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 1s
Command failed with exit code 1: /usr/share/gradle/bin/gradle -p
/home/rdindir/Documents/workspaces/cdv-gas-milage/platforms/android wrapper
-b
/home/rdindir/Documents/workspaces/cdv-gas-milage/platforms/android/wrapper.gradle

Regards



-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Regarding cordova android build

[Riza Dindir]

Hello,

A couple of days ago I was able to build cordova applications. Today I can
not build a cordova application. Did something change?

I am using gradle 8.5 on kernel 5.15.145. The "cordova requirements"
command result is

Requirements check results for android:
Java JDK: installed 17.0.6
Android SDK: installed true
Android target: installed android-33,android-32,android-31
Gradle: installed /usr/share/gradle/bin/gradle

Requirements check results for browser:

And the result for the build command "cordova build android" is

Checking Java JDK and Android SDK versions
ANDROID_HOME=/opt/android-sdk (recommended setting)
ANDROID_SDK_ROOT=/opt/android-sdk (DEPRECATED)
Using Android SDK: /opt/android-sdk

FAILURE: Build failed with an exception.

* What went wrong:
Could not initialize class org.codehaus.groovy.runtime.InvokerHelper

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or
--debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 1s
Command failed with exit code 1: /usr/share/gradle/bin/gradle -p
/home/rdindir/Documents/workspaces/cdv-gas-milage/platforms/android wrapper
-b
/home/rdindir/Documents/workspaces/cdv-gas-milage/platforms/android/wrapper.gradle

Regards

Re: [DISCUSS] Thoughts on Cordova Electron Roadmap

[George Henne]

My vote is to go for a single release bumping everything to the latest.

I’m sharing this with the other guys here - I’m sure they will have more 
comments.

- George Henne



> On Jan 18, 2024, at 3:50 PM, Bryan Ellis  wrote:
> 
> Currently the main branch is pinned for next major release 4.0.0 and is quite 
> outdated.
> 
> Looking at some options.
> 
> Release what is currently in the main branch. I believe you can test the 
> current main branch by installing nightly. Again, nightly not recommend in 
> production. It could be unstable, constantly changing, and has not been 
> reviewed or voted on.
> Update to the latest Electron and then prepare a release. 
> https://github.com/apache/cordova-electron/pull/263
> Release multiple majors…
> 
> Follow up with last two options..
> 
> There is a lot of breaking changes between our last release, what’s in our 
> main branch, and what’s in the latest release Electron.
> 
> To sum up some of the main breaking points:
> 
> Our current release version uses Electron is 14.2.9
> Our current main branch, nightly-4.0.0, has already bumped to 19.0.3
> 
> 19.0
> Removes of Linux IA32 Binary
> 20.0
> Removes macOS 10.11 (El Capitan) and macOS 10.12 (Sierra)
> 23.0
> Removes Windows 7, Windows 8, and Windows 8.1
> 25.0
> Deprecated: 
> protocol.{register,intercept}{Buffer,String,Stream,File,Http}Protocol - This 
> is something we used to support custom scheme but there is a replacement.
> 27.0
> Removes macOS 10.13 (High Sierra) and macOS 10.14 (Mojave)
> 
> There is plenty of other breaking changes (deprecation), but in terms of what 
> APIs Cordova uses, its not an issue. You would need to investigate and 
> resolve on your end if your using any of the APIs they deprecated.
> 
> Full Breaking Changes: https://www.electronjs.org/docs/latest/breaking-changes
> 
> I am leaning more towards a single release and just bump to the latest.  The 
> main branch already contains the feature to allow custom Electron versions 
> . The above PR #263 
> should support the use of older Electron versions, if people wish to use an 
> older versions to build for older OS. The only downside I foresee would come 
> from plugins if they choose to use a deprecated or new API.
> 
> Also does anyone develop/maintain plugins made for Cordova Electron? Using 
> the plugin ecosystem that was introduced in version 2.0.0?
> 
> There was a bad pattern that was added accidentally. It doubled wrap the 
> arguments that were passed to the native side. This multidimensional array is 
> not needed and should be resolved.  As the fix would be breaking change I 
> just wanted to hear what others think.
> 
> I did an npmjs search for the keyword cordova-electron and it yielded 37 
> modules. 
> 
> Not all modules maybe be valid. 
> 
> Some didn’t appear to have a source folder for electron. 26 of them appear to 
> be some variations of one plugin.
> 
> Since the number of plugins are small, and possibly still maintained, it 
> might be best to make this change now.
> 
> Let me know if anyone has thoughts:
> 
> -> Merge in PR #263
> -> Remove the accidental multidimensional array from plugin.
> -> Include an upgrade for all the other dependencies
> -> Release a single release with Electron bumped to its latest 28.x
> 
> 

Re: [DISCUSS] Thoughts on Cordova Electron Roadmap

[Norman Breau]

> Remove the accidental multidimensional array from plugin

+1 for this... I think this might become a source of problems later... 
and the longer we wait the more difficult it might be to change.


> Release a single release with Electron bumped to its latest 28.x

I'd favour this but I don't use electron in any of my projects so I'll 
vote +0 (indifferent). Browser engines goes through fast update cycle, 
they are large and complex and as a result, security updates are 
published very frequently. Electron however, unlike other platforms 
don't have access to a independent-upgrading browser runtime like say, 
Android does. This makes keeping up with electron updates rather 
important since they will include being built against updated, possibly 
more secure browser runtimes. So unless if there is any rejection, I 
think we should update electron as quickly as we can.


On 2024-01-18 16:50, Bryan Ellis wrote:

Currently the main branch is pinned for next major release 4.0.0 and is quite 
outdated.

Looking at some options.

Release what is currently in the main branch. I believe you can test the 
current main branch by installing nightly. Again, nightly not recommend in 
production. It could be unstable, constantly changing, and has not been 
reviewed or voted on.
Update to the latest Electron and then prepare a release. 
https://github.com/apache/cordova-electron/pull/263
Release multiple majors…

Follow up with last two options..

There is a lot of breaking changes between our last release, what’s in our main 
branch, and what’s in the latest release Electron.

To sum up some of the main breaking points:

Our current release version uses Electron is 14.2.9
Our current main branch, nightly-4.0.0, has already bumped to 19.0.3

19.0
Removes of Linux IA32 Binary
20.0
Removes macOS 10.11 (El Capitan) and macOS 10.12 (Sierra)
23.0
Removes Windows 7, Windows 8, and Windows 8.1
25.0
Deprecated: 
protocol.{register,intercept}{Buffer,String,Stream,File,Http}Protocol - This is 
something we used to support custom scheme but there is a replacement.
27.0
Removes macOS 10.13 (High Sierra) and macOS 10.14 (Mojave)

There is plenty of other breaking changes (deprecation), but in terms of what 
APIs Cordova uses, its not an issue. You would need to investigate and resolve 
on your end if your using any of the APIs they deprecated.

Full Breaking Changes: https://www.electronjs.org/docs/latest/breaking-changes

I am leaning more towards a single release and just bump to the latest.  The main 
branch already contains the feature to allow custom Electron versions 
. The above PR #263 should 
support the use of older Electron versions, if people wish to use an older versions 
to build for older OS. The only downside I foresee would come from plugins if they 
choose to use a deprecated or new API.

Also does anyone develop/maintain plugins made for Cordova Electron? Using the 
plugin ecosystem that was introduced in version 2.0.0?

There was a bad pattern that was added accidentally. It doubled wrap the 
arguments that were passed to the native side. This multidimensional array is 
not needed and should be resolved.  As the fix would be breaking change I just 
wanted to hear what others think.

I did an npmjs search for the keyword cordova-electron and it yielded 37 
modules.

Not all modules maybe be valid.

Some didn’t appear to have a source folder for electron. 26 of them appear to 
be some variations of one plugin.

Since the number of plugins are small, and possibly still maintained, it might 
be best to make this change now.

Let me know if anyone has thoughts:

-> Merge in PR #263
-> Remove the accidental multidimensional array from plugin.
-> Include an upgrade for all the other dependencies
-> Release a single release with Electron bumped to its latest 28.x





-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[DISCUSS] Thoughts on Cordova Electron Roadmap

[Bryan Ellis]

Currently the main branch is pinned for next major release 4.0.0 and is quite 
outdated.

Looking at some options.

Release what is currently in the main branch. I believe you can test the 
current main branch by installing nightly. Again, nightly not recommend in 
production. It could be unstable, constantly changing, and has not been 
reviewed or voted on.
Update to the latest Electron and then prepare a release. 
https://github.com/apache/cordova-electron/pull/263
Release multiple majors…

Follow up with last two options..

There is a lot of breaking changes between our last release, what’s in our main 
branch, and what’s in the latest release Electron.

To sum up some of the main breaking points:

Our current release version uses Electron is 14.2.9
Our current main branch, nightly-4.0.0, has already bumped to 19.0.3

19.0
Removes of Linux IA32 Binary
20.0
Removes macOS 10.11 (El Capitan) and macOS 10.12 (Sierra)
23.0
Removes Windows 7, Windows 8, and Windows 8.1
25.0
Deprecated: 
protocol.{register,intercept}{Buffer,String,Stream,File,Http}Protocol - This is 
something we used to support custom scheme but there is a replacement.
27.0
Removes macOS 10.13 (High Sierra) and macOS 10.14 (Mojave)

There is plenty of other breaking changes (deprecation), but in terms of what 
APIs Cordova uses, its not an issue. You would need to investigate and resolve 
on your end if your using any of the APIs they deprecated.

Full Breaking Changes: https://www.electronjs.org/docs/latest/breaking-changes

I am leaning more towards a single release and just bump to the latest.  The 
main branch already contains the feature to allow custom Electron versions 
. The above PR #263 should 
support the use of older Electron versions, if people wish to use an older 
versions to build for older OS. The only downside I foresee would come from 
plugins if they choose to use a deprecated or new API.

Also does anyone develop/maintain plugins made for Cordova Electron? Using the 
plugin ecosystem that was introduced in version 2.0.0?

There was a bad pattern that was added accidentally. It doubled wrap the 
arguments that were passed to the native side. This multidimensional array is 
not needed and should be resolved.  As the fix would be breaking change I just 
wanted to hear what others think.

I did an npmjs search for the keyword cordova-electron and it yielded 37 
modules. 

Not all modules maybe be valid. 

Some didn’t appear to have a source folder for electron. 26 of them appear to 
be some variations of one plugin.

Since the number of plugins are small, and possibly still maintained, it might 
be best to make this change now.

Let me know if anyone has thoughts:

-> Merge in PR #263
-> Remove the accidental multidimensional array from plugin.
-> Include an upgrade for all the other dependencies
-> Release a single release with Electron bumped to its latest 28.x

The Cordova Survey results are in!

[Niklas Merz]

I just published the blog post with the survey results. Please have a
look the data if you are interested the feedback.

https://cordova.apache.org/announcements/2024/01/12/survey-results.html

Thank you again for your collaboration on this. There are some paint
points and ideas we could address to make working with Cordova even more
awesome.

Cheers
Niklas

DRAFT: Contributor & user survey results & blog post data

[Niklas Merz]

Hi folks,

I started going through the survey responses and compiled them into
categories. Together with that and Googles charts and some user quotes I
drafted a blog post for announcing the results.

Please have a look: https://github.com/apache/cordova-docs/pull/1343

I'm still thinking about the conclusions / closing words. If you have
anything in mind let me know.

The PR will be open for a while but I would like to put this out in the
next week or so.

Regards
Niklas

Meet our keynote speakers and register to Community Over Code EU!

[Ryan Skraba]

[Note: You're receiving this email because you are subscribed to one or
more project dev@ mailing lists at the Apache Software Foundation.]











*
Merge
with the ASF EUniverse!The registration for Community Over Code Europe is
finally open! Get your tickets now and save your spot!
We are happy to announce that we
have confirmed the first featured speakers
!  - Asim Hussain, Executive
Director at Green Software Foundation- Dirk-Willem Van Gulik, VP of Public
Policy at The Apache Software Foundation- Ruth Ikega, Community Lead at
CHAOSS Africa Visit our website
 to learn more about this
amazing lineup.CFP is openWe are looking forward to hearing all you have to
share with the Apache Community. Please submit your talk proposal
 before January 12, 2024.Interested in
boosting your brand?Take a look at our prospectus

and find out the opportunities we have for you. Be one step ahead and book
your room at the hotel venueWe have a special rate for you at the Radisson
Blu Carlton, the hotel that will hold Community Over Code EU. Learn more
about the location and venue 
and book your accommodation. Should you have any questions, please do not
hesitate to contact us. We wish you Happy Holidays in the company of your
loved ones! See you in Bratislava next year!Community Over Code EU
Organizer Committee*

Re: Nomination for a new chair for Apache Cordova

[Bryan Ellis]

Thank you, Jesse, for recommending me as the next Apache Cordova PMC Chair.

I also want to express my gratitude to everyone else who voted and entrusted me 
with this role.

I'm excited to continue contributing to this amazing project and to fulfill the 
responsibilities of the PMC Chair. Looking forward to achieving more releases 
and further developing the Apache Cordova project.

Bryan Ellis



> On Dec 8, 2023, at 16:20, Jesse  wrote:
> 
> Thank you all.
> It appears we have consensus (and PMC member votes).
> According to "How to change your PMC's Chair" I have prepared the
> resolution below that I will send in 24 hours.
> The change should be in effect if the Board approves it, at the next
> Board meeting on Dec 20, 2023
> 
> -
> # Change Cordova Chair
> 
> ## Resolution to change the chair of a project
> WHEREAS, the Board of Directors heretofore appointed Jesse MacFadyen
> (purplecabbage) to the office of Vice President, Apache Cordova, and
> 
> WHEREAS, the Board of Directors is in receipt of the resignation of
> Jesse MacFadyen from the office of Vice President, Apache Cordova, and
> 
> WHEREAS, the Project Management Committee of the Apache Cordova project
> has chosen by vote to recommend Bryan Ellis (erisu) as the successor to
> the post;
> 
> NOW, THEREFORE, BE IT RESOLVED, that Jesse MacFadyen is relieved and
> discharged from the duties and responsibilities of the office of Vice
> President, Apache Cordova, and
> 
> BE IT FURTHER RESOLVED, that Bryan Ellis be and hereby is appointed to
> the office of Vice President, Apache Cordova, to serve in accordance
> with and subject to the direction of the Board of Directors and the
> Bylaws of the Foundation until death, resignation, retirement, removal
> or disqualification, or until a successor is appointed.
> 
> On Tue, Dec 5, 2023 at 5:36 AM Shazron  wrote:
> 
>> +1 !
>> Bryan will be great.
>> Thank you Jesse for your service!
>> 
>> 
>> On 2 Dec 2023 at 8:17:57 AM, Tim Brust  wrote:
>> 
>>> +1
>>> 
>>> Bryan has been a great a team member and remains dedicated towards the
>>> development since years!
>>> 
>>> On Fri, Dec 1, 2023 at 5:36 PM Norman Breau  wrote:
>>> 
>>> +1
>>> 
>>> 
>>> On 2023-11-29 9:52 p.m., Jesse wrote:
>>> 
 Hello friends! I have been the chair of Apache Cordova since around
>>> 
 December of 2018, roughly 5 years. My duties of late have been mostly
>>> 
 administrative: board reports, PMC management etc. Some of it is listed
>>> 
 here in the README:
>>> 
>>> https://github.com/apache/cordova-apache-board-reports
>>> 
 I think it is time for new leadership and I have decided to resign my
>>> 
 duties as the Apache Cordova chair. I formally nominate Bryan Ellis as
>>> 
>>> the
>>> 
 next chair.
>>> 
 Bryan has been a consistently motivated contributor to the project and
>>> 
>>> has
>>> 
 been diligently pushing through many of our releases over the last
>>> 
>>> several
>>> 
 years.  I believe Bryan will be great in this new role and I will do my
>>> 
 best to help him. Bryan is very familiar with and helps uphold 'The
>>> 
>>> Apache
>>> 
 Way'
>>> 
 (https://www.apache.org/foundation/how-it-works.html) and he will be a
>>> 
 great liaison with the Board. I won't be far, I plan to remain in the
>>> 
 community and will always be reachable, though I am going to be more
>>> 
 focused on personal goals.   I am always available to answer questions
>>> 
>>> and
>>> 
 help sort issues. Cheers,
>>> 
   Jesse
>>> 
 
>>> 
>>> 
>>> -
>>> 
>>> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
>>> 
>>> For additional commands, e-mail: dev-h...@cordova.apache.org
>>> 
>>> 
>>> 
>>> 
>> 

December board report

[Jesse]

Somehow I missed this, usually I get notified ahead of time.  The board
report was supposed to be filed 1 week prior to tomorrow's meeting.

https://github.com/apache/cordova-apache-board-reports/blob/master/2023/12.md

I'll send it now since its late, if anyone has any changes we can amend it,
or mention it in the next report.

Cheers,
  Jesse

REMINDER Cordova Survey is still open for 7 days

[Niklas Merz]

This is a little reminder that the survey is open for another week. We
already got over 200 reponses so far. If you think we we should keep the
survey open a little longer please respond to this thread.

Thank you very much for taking part in this survey. The goal of this
survey is to identify areas that can be improved by the Cordova
community together. The results will be shared on the Cordova blog.

Survey link:


 The survey questions are designed to not contain any personal
information and can be answered anonymously. Please take note that the
survey is using Google Forms to process the responses. The Google
privacy policy is applicable for the data processed:

Re: Nomination for a new chair for Apache Cordova

[Jesse]

Thank you all.
It appears we have consensus (and PMC member votes).
According to "How to change your PMC's Chair" I have prepared the
resolution below that I will send in 24 hours.
The change should be in effect if the Board approves it, at the next
Board meeting on Dec 20, 2023

-
# Change Cordova Chair

## Resolution to change the chair of a project
WHEREAS, the Board of Directors heretofore appointed Jesse MacFadyen
(purplecabbage) to the office of Vice President, Apache Cordova, and

WHEREAS, the Board of Directors is in receipt of the resignation of
Jesse MacFadyen from the office of Vice President, Apache Cordova, and

WHEREAS, the Project Management Committee of the Apache Cordova project
has chosen by vote to recommend Bryan Ellis (erisu) as the successor to
the post;

NOW, THEREFORE, BE IT RESOLVED, that Jesse MacFadyen is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache Cordova, and

BE IT FURTHER RESOLVED, that Bryan Ellis be and hereby is appointed to
the office of Vice President, Apache Cordova, to serve in accordance
with and subject to the direction of the Board of Directors and the
Bylaws of the Foundation until death, resignation, retirement, removal
or disqualification, or until a successor is appointed.

On Tue, Dec 5, 2023 at 5:36 AM Shazron  wrote:

>  +1 !
> Bryan will be great.
> Thank you Jesse for your service!
>
>
> On 2 Dec 2023 at 8:17:57 AM, Tim Brust  wrote:
>
> > +1
> >
> > Bryan has been a great a team member and remains dedicated towards the
> > development since years!
> >
> > On Fri, Dec 1, 2023 at 5:36 PM Norman Breau  wrote:
> >
> > +1
> >
> >
> > On 2023-11-29 9:52 p.m., Jesse wrote:
> >
> > > Hello friends! I have been the chair of Apache Cordova since around
> >
> > > December of 2018, roughly 5 years. My duties of late have been mostly
> >
> > > administrative: board reports, PMC management etc. Some of it is listed
> >
> > > here in the README:
> >
> > https://github.com/apache/cordova-apache-board-reports
> >
> > > I think it is time for new leadership and I have decided to resign my
> >
> > > duties as the Apache Cordova chair. I formally nominate Bryan Ellis as
> >
> > the
> >
> > > next chair.
> >
> > > Bryan has been a consistently motivated contributor to the project and
> >
> > has
> >
> > > been diligently pushing through many of our releases over the last
> >
> > several
> >
> > > years.  I believe Bryan will be great in this new role and I will do my
> >
> > > best to help him. Bryan is very familiar with and helps uphold 'The
> >
> > Apache
> >
> > > Way'
> >
> > > (https://www.apache.org/foundation/how-it-works.html) and he will be a
> >
> > > great liaison with the Board. I won't be far, I plan to remain in the
> >
> > > community and will always be reachable, though I am going to be more
> >
> > > focused on personal goals.   I am always available to answer questions
> >
> > and
> >
> > > help sort issues. Cheers,
> >
> > >Jesse
> >
> > >
> >
> >
> > -
> >
> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> >
> > For additional commands, e-mail: dev-h...@cordova.apache.org
> >
> >
> >
> >
>

Re: Nomination for a new chair for Apache Cordova

[Shazron]

 +1 !
Bryan will be great.
Thank you Jesse for your service!


On 2 Dec 2023 at 8:17:57 AM, Tim Brust  wrote:

> +1
>
> Bryan has been a great a team member and remains dedicated towards the
> development since years!
>
> On Fri, Dec 1, 2023 at 5:36 PM Norman Breau  wrote:
>
> +1
>
>
> On 2023-11-29 9:52 p.m., Jesse wrote:
>
> > Hello friends! I have been the chair of Apache Cordova since around
>
> > December of 2018, roughly 5 years. My duties of late have been mostly
>
> > administrative: board reports, PMC management etc. Some of it is listed
>
> > here in the README:
>
> https://github.com/apache/cordova-apache-board-reports
>
> > I think it is time for new leadership and I have decided to resign my
>
> > duties as the Apache Cordova chair. I formally nominate Bryan Ellis as
>
> the
>
> > next chair.
>
> > Bryan has been a consistently motivated contributor to the project and
>
> has
>
> > been diligently pushing through many of our releases over the last
>
> several
>
> > years.  I believe Bryan will be great in this new role and I will do my
>
> > best to help him. Bryan is very familiar with and helps uphold 'The
>
> Apache
>
> > Way'
>
> > (https://www.apache.org/foundation/how-it-works.html) and he will be a
>
> > great liaison with the Board. I won't be far, I plan to remain in the
>
> > community and will always be reachable, though I am going to be more
>
> > focused on personal goals.   I am always available to answer questions
>
> and
>
> > help sort issues. Cheers,
>
> >Jesse
>
> >
>
>
> -
>
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
>
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>
>
>

Re: Nomination for a new chair for Apache Cordova

[Tim Brust]

+1

Bryan has been a great a team member and remains dedicated towards the
development since years!

On Fri, Dec 1, 2023 at 5:36 PM Norman Breau  wrote:

> +1
>
> On 2023-11-29 9:52 p.m., Jesse wrote:
> > Hello friends! I have been the chair of Apache Cordova since around
> > December of 2018, roughly 5 years. My duties of late have been mostly
> > administrative: board reports, PMC management etc. Some of it is listed
> > here in the README:
> https://github.com/apache/cordova-apache-board-reports
> > I think it is time for new leadership and I have decided to resign my
> > duties as the Apache Cordova chair. I formally nominate Bryan Ellis as
> the
> > next chair.
> > Bryan has been a consistently motivated contributor to the project and
> has
> > been diligently pushing through many of our releases over the last
> several
> > years.  I believe Bryan will be great in this new role and I will do my
> > best to help him. Bryan is very familiar with and helps uphold 'The
> Apache
> > Way'
> > (https://www.apache.org/foundation/how-it-works.html) and he will be a
> > great liaison with the Board. I won't be far, I plan to remain in the
> > community and will always be reachable, though I am going to be more
> > focused on personal goals.   I am always available to answer questions
> and
> > help sort issues. Cheers,
> >Jesse
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

Re: Nomination for a new chair for Apache Cordova

[Norman Breau]

+1

On 2023-11-29 9:52 p.m., Jesse wrote:

Hello friends! I have been the chair of Apache Cordova since around
December of 2018, roughly 5 years. My duties of late have been mostly
administrative: board reports, PMC management etc. Some of it is listed
here in the README: https://github.com/apache/cordova-apache-board-reports
I think it is time for new leadership and I have decided to resign my
duties as the Apache Cordova chair. I formally nominate Bryan Ellis as the
next chair.
Bryan has been a consistently motivated contributor to the project and has
been diligently pushing through many of our releases over the last several
years.  I believe Bryan will be great in this new role and I will do my
best to help him. Bryan is very familiar with and helps uphold 'The Apache
Way'
(https://www.apache.org/foundation/how-it-works.html) and he will be a
great liaison with the Board. I won't be far, I plan to remain in the
community and will always be reachable, though I am going to be more
focused on personal goals.   I am always available to answer questions and
help sort issues. Cheers,
   Jesse



-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: Nomination for a new chair for Apache Cordova

[Ken Naito]

+1 for Bryan Ellis nomination as the new chair!


On 2023/11/30 10:52, Jesse wrote:

Hello friends! I have been the chair of Apache Cordova since around
December of 2018, roughly 5 years. My duties of late have been mostly
administrative: board reports, PMC management etc. Some of it is listed
here in the README: https://github.com/apache/cordova-apache-board-reports
I think it is time for new leadership and I have decided to resign my
duties as the Apache Cordova chair. I formally nominate Bryan Ellis as the
next chair.
Bryan has been a consistently motivated contributor to the project and has
been diligently pushing through many of our releases over the last several
years.  I believe Bryan will be great in this new role and I will do my
best to help him. Bryan is very familiar with and helps uphold 'The Apache
Way'
(https://www.apache.org/foundation/how-it-works.html) and he will be a
great liaison with the Board. I won't be far, I plan to remain in the
community and will always be reachable, though I am going to be more
focused on personal goals.   I am always available to answer questions and
help sort issues. Cheers,
   Jesse



-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org