Re: Nomination for a new chair for Apache Cordova

+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

[PMC] Password management for services we use

Suggestion: https://github.com/1Password/1password-teams-open-source Instead of putting passwords in a text file in the private PMC svn.

Re: [BOARD REPORT DRAFT] June 2019 Cordova Board Report

LGTM On Tue, Jun 11, 2019 at 10:50 AM Jesse wrote: > Bad link. > > https://github.com/apache/cordova-apache-board-reports/blob/master/2019/2019-06.md > > > On Jun 11, 2019, at 7:55 AM, Shazron wrote: > > > > I don't think the PMC thing is correct. Was

Re: [BOARD REPORT DRAFT] June 2019 Cordova Board Report

I don't think the PMC thing is correct. Was this generated in Whimsy? May be a whimsy bug. I think we added Dave Alden and Tim Brust since Bryan Ellis. On Mon, Jun 10, 2019 at 11:30 PM Jesse wrote: > Please review and comment. > https://github.com/apache/cordova-apache-board-reports >

Re: [DISCUSS] Node 6.x & 8.x Deprecation & Node 12.x Support

+1000 On Wed, Apr 10, 2019 at 1:17 PM wrote: > Sounds reasonable and well thought out to me. > > Bryan Ellis schrieb am Mi., 10. Apr. 2019, 09:42: > > > I would like to start the discussion around Cordova's planning for > > deprecating Node 6.x and Node 8.x as well as starting to support Node

Re: [BOARD REPORT DRAFT] March 2019 Cordova Board Report

This is correct (auto generated). All 3 were added on the same day, but the system probably chose the first based on its sorting (alphabetical most like). On Tue, Mar 12, 2019 at 5:42 AM Chris Brody wrote: > I thought Ken was added after Bryan, may be mistaken though. > > On Mon, Mar 11, 2019

Re: So....how did this happen? (Git commit weirdness)

IMO I would generally avoid this type of thing unless it was a really significant change (the change seems trivial). On Tue, Feb 12, 2019 at 4:09 AM Chris Brody wrote: > I listed you as a co-author since you authored some of the changes > included in the commit. I hope it is OK. > > On Mon,

Re: Transferring Cordova issues on GitHub

Not sure what they think about installing Probot: https://probot.github.io/apps/move/ Seems like a good compromise -- since we have write permissions for the source and target repos. On Wed, Jan 16, 2019 at 11:47 PM Chris Brody wrote: > > Thanks guys. I completely get it that it is not possible

Re: [VOTE] cordova-common@3.1.0 tools release

+1 On Tue, Dec 25, 2018 at 2:47 AM Chris Brody wrote: > > Please review and vote on this Tools Release by replying to this email > (and keep discussion on the DISCUSS thread). > > Artifacts have been published to dist/dev: > https://dist.apache.org/repos/dist/dev/cordova/common-3.1.0/ > > The

Re: Latest cordova-android version not in maven repository

Uploading to bintray/maven is not required for a release, but it is a nice to have that we have always relied on. Since it is done post-release, perhaps we can have some automation (cordova-status?) that checks for these things that can be overlooked. On Mon, Dec 17, 2018 at 10:02 PM Jan

Re: Windows Cordova Platform for Desktop Application!!

Sorry looks like Windows Store only On Thu, Dec 13, 2018 at 11:25 AM Meraj Jilani wrote: > Hi, > > I am trying to develop a cross platform windows desktop application. I went > through different sites and found that Apache's Cordova platform is best to > develop a cross platform hybrid

Re: [PR] "Create a Minimal Reproduction Repository or Sample"

I feel to repro an issue all we need is: 1. config.xml 2. contents of the 'www' folder This assumes that they've already `--save`d their platforms and plugins, and we can just put it in a new project and run `cordova prepare` to populate. We could even have a command (?) somehow to package this

Re: [dev] Introduce ES6 classes or not?

I'm in favor of whatever makes it easier to contribute, and if a contributor uses classes and it was appropriate (like there could be more than one instance of it), should be fine On Sat, Dec 1, 2018 at 12:28 AM Gearóid M wrote: > > I'm definitely in favour of using classes. Personally I find

Re: [DISCUSS] cordova-node-xcode@1.0.1 release

+1 On Mon, Dec 10, 2018 at 9:04 PM Chris Brody wrote: > > I would like to publish cordova-node-xcode as xcode@1.0.1 later today, > which moves pegjs to devDependencies, has Travis CI enabled, and some > other minor fixes before starting 2.0.0-dev. This is in case we need > the fixes for anything

Re: FILE_URI vs NATIVE_URI question (camera plugin)

Seems to me we could simplify things to one type and let the developer process what is returned whether file://, content:// or cdvfile:// On Fri, Nov 23, 2018 at 9:25 PM julio cesar sanchez wrote: > > So in Camera plugin you can choose FILE_URI or NATIVE_URI, but it's not > clear to me what

Re: [DISCUSS] cordova-node-xcode@2.0.0 release

+1 On Mon, Dec 10, 2018 at 7:22 AM Chris Brody wrote: > > I would like to publish a new major release of cordova-node-xcode as > xcode@2.0.0 with some changes discussed in > . > > Any objections? > > Does anyone have any reason to delay a

[BOARD REPORT DRAFT] Dec 2018 Cordova Board Report

Please review and comment: https://github.com/apache/cordova-apache-board-reports/blob/master/2018/2018-12.md I want to get this out before the end of this week. Thanks! - To unsubscribe, e-mail:

Re: Nomination for a new chair for Apache Cordova

Now, now -- there's plenty of money in open source, that's why! See https://www.youtube.com/watch?v=PyeWRd7ZEBs On Tue, Dec 11, 2018 at 6:27 PM Jesse wrote: > > Thank you Shazron for your continuous and unwavering commitment to > Apache Cordova, you leave heavy shoes to fill and I am

Re: Nomination for a new chair for Apache Cordova

http://www.apache.org/dev/pmc.html#newchair On Tue, Dec 11, 2018 at 11:26 AM Shazron wrote: > > Thank you everyone. > It looks like we have consensus (and votes by PMC members). > According to "How to change your PMC's Chair" I have prepared the resolution > below tha

Re: Nomination for a new chair for Apache Cordova

c 19, 2018 - ## Resolution to change the chair of a project A. Change the Apache Cordova Project Chair WHEREAS, the Board of Directors heretofore appointed Shazron Abdullah (shazron) to the office of Vice President, Apache Cordova, and WHEREAS, the Board of Directors is

Nomination for a new chair for Apache Cordova

Hello beloved Community! I have been the chair of Apache Cordova since around April 2014 (~4.5 years). The duties are 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

Re: vote duration discrepancy

at 11:41 PM Shazron wrote: > > To be honest I didn't expect the vote to end so fast especially with > the notice "Voting will go on for a minimum of 48 hours." in the vote > thread itself. > If this was expressed as a duration of 24 hours and expressed as an > emer

Re: vote duration discrepancy

I think we would have been fine with that -- but the vote did say 48 hours.On Fri, Sep 28, 2018 at 11:35 PM Shazron wrote: > > Jesse sums up what I would have said. We all agreed on the 48 hours > (somewhere way back), especially with our project with 60+ repos where > we were changin

Re: vote duration discrepancy

Jesse sums up what I would have said. We all agreed on the 48 hours (somewhere way back), especially with our project with 60+ repos where we were changing rapidly (not so much now of course), and 72 hours was too late for a release. 48 seems to be a good midpoint for the rule to include people

Re: [iOS] State of Xcode 10 support

I think we should just bake in this build flag (implicitly) for the next cordova-ios release, in the interim. I haven't tested on Xcode 9 whether this will cause problems on the command line, I hope not. On Sat, Sep 15, 2018 at 1:26 AM Darryl Pogue wrote: > > A few issues have started to come in

Re: [BOARD REPORT DRAFT] Sept 2018 Cordova Board Report

ed, as it is based on _now_ and can change over time (when > more of those items are closed as time progresses). > (On the other hand: It can be useful to know how many of the new items > are already taken care of already.) > > Does that make sense? > Or should we have different q

Re: [BOARD REPORT DRAFT] Sept 2018 Cordova Board Report

Copy pasta mistake. Should be: PRs closed/merged - 299 closed/merged --> 9 issues less from 308 above On Mon, Sep 17, 2018 at 9:36 AM Shazron wrote: > > Thanks Jan! > Some issues with the queries, the math doesn't add up. > > Referring to Sept Q3. > > Issues created - 103

Re: [BOARD REPORT DRAFT] Sept 2018 Cordova Board Report

ow > from the unmerged/closed/merged stuff now. > > It might be worth reporting "open issues and open PRs right now", but > I was not able to think how to build this in a search query for any > point of time. Anyone an idea? > > -J > > 2018-09-14 18:56 GMT+02:00

Re: [BOARD REPORT DRAFT] Sept 2018 Cordova Board Report

just in case he missed the draft and can chime in to > > provide more information. > > > > El vie., 14 sept. 2018 a las 2:34, Shazron () escribió: > >> > >> What Julio said -- broad strokes only. > >> Julio -- if we have those numbers, we could

Re: [BOARD REPORT DRAFT] Sept 2018 Cordova Board Report

eem to be missing. > > > > On Thu, Sep 13, 2018, 12:14 AM Shazron wrote: > > > > > Please review and comment > > > > > > > > https://github.com/apache/cordova-apache-boar

[BOARD REPORT DRAFT] Sept 2018 Cordova Board Report

Please review and comment https://github.com/apache/cordova-apache-board-reports/blob/master/2018/2018-09.md I want to get this out before the end of this week. Thanks! - To unsubscribe, e-mail:

Re: [DISCUSS] [JIRA -> GitHub Issues] The way forward

e notice it, > we can close the JIRA one as duplicate of the github one. (it has already > happened in at least one issue that I have noticed) > > El jue., 23 ago. 2018 a las 11:42, Shazron () escribió: > > > Back of the napkin calculation... if we took 5 mins (which is quite > >

Re: [DISCUSS] [JIRA -> GitHub Issues] The way forward

, definitely a few months. (of course the work can be run in parallel with more people...) On Thu, Aug 23, 2018 at 5:34 PM Shazron wrote: > > Realistically doing it one by one will take a very long time, nor is > it necessary -- as a volunteer or if you were paid by your employe

Re: [DISCUSS] [JIRA -> GitHub Issues] The way forward

time, > wouldn't make it mandatory. > > > > El jue., 23 ago. 2018 a las 11:06, Shazron () escribió: > > > Thanks Jan - I will hold off until we are ready of course. > > > > Raphael - close as in there can not be any more comments added or > > additions to th

Re: [DISCUSS] [JIRA -> GitHub Issues] The way forward

Piotrowski wrote: > > Just a note to make sure: Please do not proceed with this before issue > and PR templates are in place, labels are unified etc - meaning: > GitHub repos are ready. > (Working on this right now) > Am Do., 23. Aug. 2018 um 10:53 Uhr schrieb Shazron : > > > &g

Re: [DISCUSS] [JIRA -> GitHub Issues] The way forward

me know how I can > > help. > > Yes, I think those could very well be on the Cordova web site as well. > http://cordova.betamo.de/ is built with PHP, I will put its source up > on Github later so someone can rebuild it with JS if needed/wanted. > For now it is just a solution for us committers

Re: What to do with cordova-discuss?

. > > If there are issues left after that, those could be placed into > `apache/cordova` as a "high level cordova discussion" area if we > define it that way. > > J > > > Am Do., 23. Aug. 2018 um 08:01 Uhr schrieb Shazron : > > > > I think we should

Re: INFRA requests based on the F2F meeting

Sorry hit send too quick. I added jira.cordova.io as a transition step for us that points to the current JIRA On Thu, Aug 23, 2018 at 2:04 PM Shazron wrote: > > I've changed the redirect issues.cordova.io to point to > https://github.com/apache/cordova and added a pointer in the README o

Re: INFRA requests based on the F2F meeting

> > -J > > 2018-08-16 10:34 GMT+02:00 Shazron : > > 1. Org Level Project Board https://issues.apache.org/jira/browse/INFRA-16913 > > 2. Lock down JIRA for creation of new issues >

Re: What to do with cordova-discuss?

I think we should stick to one repo -- https://github.com/apache/cordova and archive the discuss repo. We should point to that one repo for all things Cordova w.r.t to dev. On Thu, Aug 23, 2018 at 4:13 AM Chris Brody wrote: > > While I personally think it would continue to fill an existing gap

Re: [DISCUSS] [Github Issues] Issue and Pull Request labels

I would assume since we (committers) can create a New Label in Github, we would have the permission to do so via API... On Wed, Aug 22, 2018 at 2:28 AM wrote: > > Labels that I would like to have: > > - something to show that you are open to suggestions or want to work out > how something is

Re: INFRA requests based on the F2F meeting

Forgot to paste the link: https://github.com/orgs/apache/projects/2 To grab issues from repos, Add Cards -> uncheck "Only show results from linked repositories" then use a query to limit your search On Wed, Aug 22, 2018 at 9:37 AM Shazron wrote: > > The Org Project Level Boa

Re: INFRA requests based on the F2F meeting

The Org Project Level Board has been created. We can add issues from all repos in the Apache org now. https://issues.apache.org/jira/browse/INFRA-16913 On Sat, Aug 18, 2018 at 4:22 PM Shazron wrote: > > Update: INFRA has fixed the issue. We can make modifications on issues > again.

Re: Documentation and plugin search is not working

Doc search is back up, thanks to Algolia for finding the issue! There are some recommendations for us to update our docs to minimize disruption with changes, I will update the JIRA issue -- I probably will migrate it to a Github Issue first and link it. On Tue, Aug 14, 2018 at 11:56 AM Shazron

Re: INFRA requests based on the F2F meeting

Update: INFRA has fixed the issue. We can make modifications on issues again. Creation of issues is disabled -- only CB Project Admins can create new issues. On Sat, Aug 18, 2018 at 4:02 PM Shazron wrote: > > I'll ask INFRA to revert the change. > On Fri, Aug 17, 2018 at 3:51 PM Jan P

Re: INFRA requests based on the F2F meeting

I'll ask INFRA to revert the change. On Fri, Aug 17, 2018 at 3:51 PM Jan Piotrowski wrote: > > Can confirm, Cordova JIRA seems to be fully read only now. Seems we > should roll back and only deactivate after we migrated everything > (somehow). > > 2018-08-17 5:05

Re: INFRA requests based on the F2F meeting

There might be a side effect on locking down JIRA. I can't comment on existing JIRA issues now. On Thu, Aug 16, 2018 at 9:40 PM Shazron wrote: > > Not sure how, maybe edit some project settings in JIRA, need to investigate. > > On Thu, Aug 16, 2018 at 9:18 PM Jan Piotrowski wrote:

Re: INFRA requests based on the F2F meeting

ht direction in > JIRA? > We will now of course update issues.cordova.io, but I assume some > peole have https://issues.apache.org/jira/projects/CB/ or similar URLs > bookmarked. > > -J > > 2018-08-16 10:34 GMT+02:00 Shazron : > > 1. Org Level Project Board > http

Re: [DISCUSS cordova-windows@6.0.1 patch release

ct/Humbedooh/cordova-windows/build/1.0.1020 > > > > The AppVeyor configuration is set to accept the failures as a passing > > result if using Visual Studio 2017. > > > > I had been wanting to fix this so the tests would actually run and pass > > properly but did

INFRA requests based on the F2F meeting

1. Org Level Project Board https://issues.apache.org/jira/browse/INFRA-16913 2. Lock down JIRA for creation of new issues https://issues.apache.org/jira/browse/INFRA-16914 - To unsubscribe, e-mail:

Re: [DISCUSS cordova-windows@6.0.1 patch release

https://github.com/apache/cordova-windows/issues/274 which is not a blocker IMO, but I'm not sure of the splash screen. Technically the app builds and runs... On Wed, Aug 15, 2018 at 1:40 PM Shazron wrote: > > You can debug what requirements it tries to detect for MSBUILD by r

Re: [DISCUSS cordova-windows@6.0.1 patch release

You can debug what requirements it tries to detect for MSBUILD by running: cordova requirements --verbose On Wed, Aug 15, 2018 at 1:39 PM Shazron wrote: > > Repro steps: > > ``` > npm install -g cordova > cordova create foo > cd foo > cordova platform add https://g

[DISCUSS cordova-windows@6.0.1 patch release

Had trouble meeting the requirements to build, using VS 2017 Community edition I had to set the MSBUILDDIR env var explicitly to C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin since our code fails to detect the MSBuild version installed with that, v15.8. The

Documentation and plugin search is not working

Doc search issue: https://issues.apache.org/jira/browse/CB-14266 Plugin search issue: https://issues.apache.org/jira/browse/CB-14265 - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail:

Re: Reviving Face-to-Face video meetings?

in the checkbox > > > to mark it as "possible, but not ideal". > > > > > > ~Darryl > > > > > > On Wed, Aug 8, 2018 at 7:14 PM Bryan Ellis wrote: > > > > > > > > Hi Darryl, > > > > > > > > I se

Re: [VOTE] cordova-osx 4.0.2 patch release

I vote +1 - I could add the platform - I could run 'cordova build' and 'cordova run' successfully On Mon, Jul 30, 2018 at 12:26 PM Chris Brody wrote: > > Please review and vote on this 4.0.2 cordova-osx (macOS) patch release > by replying to this email (and keep discussion on the DISCUSS

Re: WKWebView plugin - issues before baking it in to cordova-ios

Blog post up: https://cordova.apache.org/news/2018/08/01/future-cordova-ios-webview.html Retweet this: https://twitter.com/apachecordova/status/1027397670430601216 On Thu, Aug 9, 2018 at 9:55 AM Shazron wrote: > > Julio, > Darryl mentioned " iframes being cross origin (s

Re: WKWebView plugin - issues before baking it in to cordova-ios

... really what I mean is, we have focused so much on > > >making EVERYTHING-WEB work in cordova, but we may be coming to a time > > >where > > >we have to focus on just the features we need to build good hybrid > > >apps. > > > > > >We never p

Re: Dealing with deprecated repos

ibute page (as a suggestion). If we run into this again, we point to the policy. On Wed, Aug 8, 2018 at 6:33 PM Chris Brody wrote: > > On Wed, Aug 8, 2018 at 6:15 AM Shazron wrote: > > > > Let's make it formal with what we had in the repo > > Does this mean make the archivin

Re: Dealing with deprecated repos

Let's make it formal with what we had in the repo, perhaps a new page or section in the docs somewhere. On Wed, Aug 8, 2018 at 6:09 PM Jan Piotrowski wrote: > > Please note that this part of the discussion with me playing devil's > advocate - I pretty much agree with what you are saying. > > Is

Re: WKWebView plugin - issues before baking it in to cordova-ios

If there are no further comments regarding the blog post, I will publish it by EOD (Pacific Time) Wed August 8th, 2018 https://github.com/apache/cordova-docs/pull/867 On Wed, Aug 8, 2018 at 3:14 PM Shazron wrote: > > Apple has other goals with WKWebView (a lot deals with making it more &g

Re: WKWebView plugin - issues before baking it in to cordova-ios

on to WKWebView, and we will try our best to make it seamless. On Wed, Aug 8, 2018 at 2:27 PM Frederico Galvão wrote: > > My impression as a user on this is that, since the very first few > prototypes with WKWebView from Shazron and some others, to later the Ionic > attempts at sol

Re: WKWebView plugin - issues before baking it in to cordova-ios

NSURLProtocol, > but asynchronous and with limited access to form data. > > On Thu, Aug 2, 2018 at 7:44 PM Shazron wrote: > > > > Our policy has been we support the currently shipping iOS version, > > plus one back. This is because of device version testing complexiti

Re: [DISCUSS] [Github Issues] Issue and PR template + Merge Conventions / Protected Branch

Agree with all 3 points by Jan. @Chris Brody I think we should make use of Github Milestones to track related issues. On Wed, Aug 8, 2018 at 6:59 AM Jan Piotrowski wrote: > > Update to my initial email: > > I just noticed we actually _do_ have an issue template in use in the > cordovs-docs

Re: [DISCUSS] Cordova idea: integrate with fastlane?

Agree with Jesse -- this is more informational and fit for a blog post since a lot of new devs will not know about fastlane On Wed, Aug 8, 2018 at 6:33 AM Jesse wrote: > > track it in a blog post ;) > > Since we use cordova-docs repo for the blog, maybe an issue there would > make the most sense.

Re: [DISCUSS] [JIRA -> GitHub Issues] The way forward

We could whip something up using https://glitch.com for a start On Wed, Aug 8, 2018 at 11:34 AM Shazron wrote: > > Thanks Jan! > > 1. Should we just disable those then? One other way is to add in bold > big letters about the deprecation in the New Issue template > 2. These link

Re: [DISCUSS] [JIRA -> GitHub Issues] The way forward

Thanks Jan! 1. Should we just disable those then? One other way is to add in bold big letters about the deprecation in the New Issue template 2. These links are super useful. Perhaps they should be on the website, what do you all think? Not sure if the scripting for the second link is server side

Re: WKWebView plugin - issues before baking it in to cordova-ios

gue wrote: > > On Sun, Jul 15, 2018 at 11:39 PM Shazron wrote: > > > > 4. XmlHttpRequests don't work, because of Cross-Origin Resource > > Sharing issue (CORS). There is a workaround plugin created by Oracle > > (UPL licensed, which is Apache-2.0 compatible). See > >

Re: WKWebView plugin - issues before baking it in to cordova-ios

We could -- I can just add a suffix or prefix... On Thu, Aug 2, 2018 at 11:14 PM Jan Piotrowski wrote: > > Couldn't the class names be changed when integrating the plugin? > Because the console stuff is still messing with people :/ > > 2018-08-02 17:01 GMT+02:00 Shazron : > >

Re: ios-deploy questions

1. Previously we had node_modules bundled. We couldn't bundle ios-deploy because of its viral license. The only issue is that it tries to build on Windows, but that should be easily fixed: https://github.com/ios-control/ios-deploy/issues/355 . There should be no problem in using a dependency from

Re: WKWebView plugin - issues before baking it in to cordova-ios

blog post? Should this maybe be > > mentioned as an anticipated question? > > > > 2018-08-02 16:31 GMT+02:00 Shazron : > > > Please review the draft of the blog post about this: > > > "The Future of the iOS WebView in Apache Cordova" > > >

Re: WKWebView plugin - issues before baking it in to cordova-ios

Please review the draft of the blog post about this: "The Future of the iOS WebView in Apache Cordova" https://github.com/apache/cordova-docs/pull/867 On Mon, Jul 16, 2018 at 2:38 PM Shazron wrote: > > I've done with my review with all the issues that need to resolved > wit

Re: Commit package-lock.json in next major Cordova release or not?

yes +1 On Thu, Aug 2, 2018 at 4:28 AM Chris Brody wrote: > > I think we should start to commit package-lock.json in the next major > release but am not 100% sure. My understanding is that > package-lock.json mostly serves a couple major purposes: > * preserve the structure of node_modules

Re: Any reason to support Xcode pre-9 on cordova-ios@4 or cordova-osx?

No to all. On Thu, Aug 2, 2018 at 11:54 AM Chris Brody wrote: > > From https://github.com/apache/cordova-docs/issues/863 it is clear > that we are not allowed to use Xcode pre-9.0 with Apple's App Store. I > suspect there are also not too many volunteers testing on Xcode > pre-9.0. I just raised

Re: [VOTE] cordova-wndroid@6.0.1 patch release

The subject says "[VOTE] cordova-wndroid@6.0.1 patch release". A bit ambiguous, I propose re-doing the vote. On Sat, Jul 28, 2018 at 7:23 AM Chris Brody wrote: > > Please review and vote on this 6.0.1 Windows patch release by replying > to this email (and keep discussion on the DISCUSS thread). >

Re: Dealing with cordova-windows license header audit issue

+1 to your proposal. I added a review comment in two of the PRs. On Fri, Jul 27, 2018 at 9:06 AM Chris Brody wrote: > > While getting ready to make a cordova-windows patch release I > discovered that coho audit-license-headers flags an issue with > template/Properties/Default.rd.xml ([1]).

Re: [DISCUSS] cordova--ios 4.5.5 patch release

at 10:18 PM Chris Brody wrote: > Thanks Shazron for your efforts to deal with ios-deploy. I would like > to get ios-deploy with the latest fixes in the build of cordova-ios, > hopefully in the near future (don't want to delay this one). Am I > right that ios-deploy@1.9.3 would resolv

Re: [VOTE] cordova-ios 4.5.5 patch release

I vote +1: - Could create a blank iOS project - Could run the iOS project in the simulator and device On Tue, Jul 24, 2018 at 5:12 AM Chris Brody wrote: > > Please review and vote on this cordova-ios 4.5.5 patch release by > replying to this email (and keep discussion on the DISCUSS thread) > >

Re: [DISCUSS] cordova--ios 4.5.5 patch release

I've fixed the ios-deploy issue with a new 1.9.3 release, so that shouldn't affect things anymore. On Tue, Jul 24, 2018 at 11:43 AM Shazron wrote: > > https://github.com/ios-control/ios-deploy/issues/349 > On Tue, Jul 24, 2018 at 11:38 AM Shazron wrote: > > > >

Re: [DISCUSS] cordova--ios 4.5.5 patch release

https://github.com/ios-control/ios-deploy/issues/349 On Tue, Jul 24, 2018 at 11:38 AM Shazron wrote: > > Some issues , related to an external tool ios-deploy that we use: > node 8.11.2 > (note that issues are only related to running and building for device, > related to the

[DISCUSS] cordova--ios 4.5.5 patch release

Some issues , related to an external tool ios-deploy that we use: node 8.11.2 (note that issues are only related to running and building for device, related to the ios-deploy tool that we use. Emulator is fine) I don't think this should hold up the release. 1. --- # this defaults to building

Re: Reviving Face-to-Face video meetings?

+1! On Thu, Jul 19, 2018 at 1:17 PM Bryan Ellis wrote: > > I also believe that this is a great idea and would be interested in > participating. > > Anytime between now and August 3rd will work for me. > > On Thu, Jul 19, 2018 at 10:50 AM Gearóid M wrote: > > > Great idea, I'd like to get to know

Re: http error 404 retrieving version 3.6.3 for www

This is a dev list for developing on Cordova itself, not a user list. Please file an issue at issues.cordova.io if its a bug with complete repro steps. Judging with what vague info you've presented, it is not enough. On Thu, Jul 19, 2018 at 10:26 AM Roshan Agrawal wrote: > > Hello Team, > > I am

Re: Nightly builds

Thanks Darryl! On Thu, Jul 19, 2018 at 1:05 PM Darryl Pogue wrote: > > Apologies for the Jenkins spam, the builds were failing after npm > revoked all auth tokens and we needed to reauthenticate. > > I've figured that part out, so our nightly builds are back to usually > failing for flaky reasons

Re: https redirect needed

Thanks! https://issues.apache.org/jira/browse/CB-14210 On Tue, Jul 17, 2018 at 2:21 AM wrote: > > Depending on how the site is deployed, you might need > https://stackoverflow.com/a/37006232/380229 > > Full disclosure: that's an answer by me. > > Shazron schrieb am Mo.,

Re: https redirect needed

r project pages? > On Mon, Jul 16, 2018 at 1:50 AM Shazron wrote: > > > > How: > > https://stackoverflow.com/a/13376283 > > > > Where: > > https://svn.apache.org/repos/asf/cordova/site/public/.htaccess > > > > > > On Mon, Jul 16, 201

WKWebView plugin - issues before baking it in to cordova-ios

I've done with my review with all the issues that need to resolved with the plugin before it can be baked in to the platform for a major version release. I'm going to discuss issues with respect to migration of developers from UIWebView (features that will be lost or are different) 1. Cookies

Re: [DISCUSS] Cordova-Android 7.1.1 patch release

Need one more vote for Cordova-Android to wrap it up. On Thu, Jul 12, 2018 at 7:49 PM Chris Brody wrote: > > Thanks Shazron for reviewing. I just raised CB-14205 > <https://issues.apache.org/jira/browse/CB-14205> to add hints and help > links to error messages. > >

Re: https redirect needed

How: https://stackoverflow.com/a/13376283 Where: https://svn.apache.org/repos/asf/cordova/site/public/.htaccess On Mon, Jul 16, 2018 at 11:21 AM Shazron wrote: > > I've made the redirect changes for the naked domain, as well as www subdomain. > > Redirecting http://c.a.o to https:

Re: Nightly build #781 for cordova has failed

We control npm access. Members of the cordova npm org (which you are part of) can create a new user token. On Fri, Jul 13, 2018 at 4:17 PM Darryl Pogue wrote: > > All npm auth tokens were revoked on Thursday following a security > incident, so we probably need to open a ticket with infra to get a

Re: https redirect needed

I've made the redirect changes for the naked domain, as well as www subdomain. Redirecting http://c.a.o to https://c.a.o - we will have to configure .htaccess ourselves (there will be no foundation-wide redirects

Re: Cordova-Android 7.1.1 patch release

I vote +1: On nodes 4, 6, 8 and 10: - Could create a blank Android project - Could run the Android project in Android Studio emulator On Thu, Jul 12, 2018 at 10:15 AM Chris Brody wrote: > > Please review and vote on this Cordova-Android 7.1.1 pelease by > replying to this email (and keep

Re: [DISCUSS] Cordova-Android 7.1.1 patch release

Darryl Pogue wrote: > > I believe on macOS you'll need to install gradle through something > like Homebrew. > > On Wed, Jul 11, 2018 at 10:42 PM Shazron wrote: > > > > Sorry, Android newbie here. > > > > I have Android 3.1.3 installed on macOS, with co

[DISCUSS] Cordova-Android 7.1.1 patch release

Sorry, Android newbie here. I have Android 3.1.3 installed on macOS, with cordova 8.0.0. I did: cordova platform add https://github.com/apache/cordova-android#7.1.1 cordova build I get this error:

Re: Roadmap for next major versions

good pull request on this. > > I flag like this sounds like a good way to test this in our app. > > Am 3. Juli 2018, 06:39, um 06:39, Shazron schrieb: > >I was thinking that the feature flag is just a convenience feature for > >setting/removing (depends on if the flag is set/

Re: Roadmap for next major versions

, Jul 3, 2018 at 12:27 PM Darryl Pogue wrote: > Thanks Shazron! > > Regarding point 3 on your list, does that need to be a feature flag > since the WebView engine is already controlled via a preference in > config.xml? People should be able to opt-in that way just by adding

Re: Roadmap for next major versions

Thanks Darryl, I'll be working on getting the WKWebView plugin up to snuff this week (read the comment thread in your doc). 1. Review and resolve all existing PRs 2. Integrate the WKWebView plugin into the cordova-ios repo 3. Turn on WKWebView support via a feature flag (eventually this will be

Re: [VOTE] cordova-common@2.2.5 tools release (patch release)

+1 On Sat, Jun 30, 2018 at 10:23 AM Jesse wrote: > I vote +1 > > * [+] no known vulnerabilities found [440 packages audited] > * ran tests at tagged commit 2.2.5 > * Ran coho audit-license-headers > * Ran coho check-license > * Ran coho verify-archive on release artifacts > * Ensured continuous

Re: Stepping Back

Thanks for all the years shepherding this Joe, and being the father of PhoneGap/Cordova Android! I'm sure it's been an interesting experience, but now it's time for someone else to take up the mantle and be the lead for Cordova Android with your absence. I know everyone will chip in, but ideally

Re: Android 4.4 support?

"We should consider KitKat 'abandoned'" w.r.t. the media plugin, not Cordova... On Tue, Jun 19, 2018 at 11:47 PM Shazron wrote: > Using http might fix the test, for sure - but I think we should move on to > testing https only, as the new normal. > > Although this is thr

  1   2   3   4   5   6   7   8   9   10   >