Re: Reviving Face-to-Face video meetings?

Yes! Sorry for missing my intended deadline here, some unexpected work challenges combined with moving house and not having my full computer set up yet have caused me to drop a few things, including following up on scheduling this. I've set up a Doodle poll with dates for next week, let's try to h

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 (so no accessing the > paren

Nightly build #814 for cordova has succeeded!

Nightly build #814 for cordova has succeeded! The latest nightly has been published and you can try it out with 'npm i -g cordova@nightly' For details check build console at https://builds.apache.org/job/cordova-nightly/814/consoleFull - Jenkins for Apache Cordova -

Re: Reviving Face-to-Face video meetings?

Hi Darryl, I see it had past Aug 3rd and I wanted to find out if we are still planning to set up a web conference. I am looking forward to the web conference. Please let me know if there is anything I can do to help get this moving. > On Jul 19, 2018, at 14:23, Shazron wrote: > > +1! > On T

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

Julio, Darryl mentioned " iframes being cross origin (so no accessing the parent/child document)" which means that it is a break from existing UIWebView behaviour that users expect, that will now break. There are workarounds: https://medium.com/@DrawandCode/how-to-communicate-with-iframes-inside-w

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

What's exactly the iframe problem? El mié., 8 ago. 2018 a las 10:05, Niklas Merz () escribió: > +1 > > I am really happy to hear about the WKwebview future. I tried WKwebview > some time ago and it did not work well with our app. I think the changes > mentioned in the blog post will make the tran

Re: Major Cordova release idea

We pin the platform versions with ~, so as next cordova-android is a patch version it will be picked once released. (If we update this to ~7.1.0 https://github.com/apache/cordova-lib/blob/master/src/platforms/platformsConfig.json#L18). No need to delay a lib release because of that. I have not ign

Re: Major Cordova release idea

I am fine to continue with the cordova-fetch, cordova-lib, and cordova-cli patch releases needed to do the following: * fix repo url in cordova-fetch as already proposed in https://github.com/apache/cordova-fetch/pull/38 * cordova-lib pins the released platforms and resolve audit issues * cordova-c

Re: Major Cordova release idea

I prefer a minor CLI release that just pins the recently released platforms (or in progress of being released) and no other changes. The other proposed changes sounds good, but for a future major release with no rush. El mié., 8 ago. 2018 a las 14:07, Jan Piotrowski () escribió: > You are talkin

Re: Major Cordova release idea

You are talking about Cordova CLI, correct? Do you only want to release a new CLI or also the other stuff? What about the platforms - major or minor releases? What about core plugins - major or minor releases? Maybe I misunderstood, but why rush all this instead of just do the work in all the re

Major Cordova release idea

I would like to propose the following idea: make a major Cordova release (Cordova 9), based on what was already published for Cordova 8, with a very limited set of changes such as: * drop Node.js 4 support * remove committed node_modules from all supported Cordova platforms * commit package-lock.js

Re: Dealing with deprecated repos

+1 cordova.apache.org/contribute/deprecation_policy.html maybe? Should include summary of what was discussed here, and best also the deprecation notice template in markdown for copy paste. -J 2018-08-08 12:55 GMT+02:00 Shazron : > Fo

Re: Dealing with deprecated repos

> I wouldn't point to a fork, because that will mean we have to search for > the forks and decide which one is better. Also in case we want to do that, > we should do it before archiving. If a better fork appears after archiving > we won't be able to change. > > I think best option is to point to n

Re: Dealing with deprecated repos

Formal as in this is our policy. From what Julio Cesar Sanchez said earlier: "This is the deprecation policy from cordova-plugin-contacts Deprecation Notice This plugin is being deprecated. No more work will be done on this plugin by the Cordova development community. You can continue to use this

Re: Dealing with deprecated repos

We can probably unarchive and re-archive, but as long as we need to ask infra to do it, I don't find it reasonable to do it to just edit the README to point to a new repo. I would only do it in case there are some security fix we have to land. Anyway, even for security fixes I think we have a 6 mo

Re: Dealing with deprecated repos

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 archiving process formal or make something else formal? What kind of repo? > or section in the docs somewhere. The question is always where? On Wed, Aug 8, 2018 at 6:24

Re: Dealing with deprecated repos

I wouldn't point to a fork, because that will mean we have to search for the forks and decide which one is better. Also in case we want to do that, we should do it before archiving. If a better fork appears after archiving we won't be able to change. I think best option is to point to network tab

Re: Dealing with deprecated repos

+1 for archiving repos and documenting them. On Wednesday, August 8, 2018, Shazron wrote: > 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 th

Re: Dealing with deprecated repos

> Is there any way users can find out about new forks of deprecated > repos? Fork network view on Github maybe? I just forked https://github.com/nodejs/wiki-archive which they archived. My fork show up in: https://github.com/nodejs/wiki-archive/network/member My fork has PRs enabled by default. I

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 th

Re: Dealing with deprecated repos

Please note that this part of the discussion with me playing devil's advocate - I pretty much agree with what you are saying. Is there any way users can find out about new forks of deprecated repos? Fork network view on Github maybe? Then adding a link to that in the deprecation notice would be a

Re: Dealing with deprecated repos

This is the deprecation policy from cordova-plugin-contacts Deprecation Notice This plugin is being deprecated. No more work will be done on this plugin by the Cordova development community. You can continue to use this plugin and it should work as-is in the future but any more arising issues will

Re: Dealing with deprecated repos

Great, then this seems to be Cordova's deprecation policy. Write it down, publish it, link to it from the deprecated projects so users know about it - problem solved. Just to be on the safe side: Was this previously discussed and decided? -J 2018-08-08 10:49 GMT+02:00 julio cesar sanchez : > No,

Re: Dealing with deprecated repos

No, when we deprecate something it means no more work will be done on it. Triaging issues, reviewing and merging other people prs and continuing doing releases it’s work. We aren’t supposed to do anything else when we deprecate. People can freely create and maintain a fork, but it won’t be offici

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

> 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 We should probably "just" define our deprecation and archival policy (see other active thread). Depending on that, we can create another INFRA issue to get taken ca

Re: Dealing with deprecated repos

Let me play devil's advocate: Archiving means disabling everything - issues, PRs, etc. Don't we want to let people create PRs with bug fixes or changes (we may or may not choose to merge) for other people to benefit from? -J 2018-08-08 3:40 GMT+02:00 Gearóid M : > +1 on archiving deprecated repo

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

+1 I am really happy to hear about the WKwebview future. I tried WKwebview some time ago and it did not work well with our app. I think the changes mentioned in the blog post will make the transition to WKwebview easier. Not supporting some features like iframes may be an issue for some users t

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

+1. Please post it. I think it is better to put it out there and get feedback from the wider community, than sit and try to perfect a message here with a subset of subscribers. We can only do the best we can with what we have. Regarding things like iframes, I am not sure they are worth keeping ar

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 > secure),

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

Apple has other goals with WKWebView (a lot deals with making it more secure), and I doubt they are aligned with Cordova's goals (although they did a patch to load file urls for iOS 9 I believe, that helped us avoid the local webserver route). I think almost all of us know that WKWebView usage by C

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

We definitely have to explore this more. I doubt we can ever be perfect at the first run at it, but we've got to lay the foundation for the eventual patches. On Fri, Aug 3, 2018 at 11:30 AM Darryl Pogue wrote: > > One concern with the Oracle plugin is that it's only patching the > obvious cases