Re: Team page on Cordova website

There are existing tools that do what you suggest Raphael, mostly to put contributors into READMEs of projects but I am sure that could be abused to put it into a Markdown file that is included in the docs. Apache also has a site that lists all PMC members etc (that I think uses some AJAX + a JSON

Re: [PROPOSAL] Enable Probot Apps to Improve Issue Tracker

I think in the past we also got pushback from INFRA on using bots via apps because of access to data etc (similar to CI services etc). Not sure if that changed in the last few months. J Am Fr., 17. Apr. 2020 um 13:44 Uhr schrieb Niklas Merz : > > I think I have to agree there. > > I would vote -0

Re: [VOTE] Unarchive & Un-deprecate cordova-plugin-device-orientation

+1 Am Di., 18. Aug. 2020 um 08:46 Uhr schrieb Dave Alden < d...@workingedge.co.uk>: > +1 > > On Tue, 18 Aug 2020, 05:47 Bryan Ellis, wrote: > > > This vote is only for the purpose of unarchive and remove the deprecation > > status for the plugin of: > > > > cordova-plugin-device-orientation >

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

+1 Am Di., 18. Aug. 2020 um 06:59 Uhr schrieb Norman Breau < nor...@normanbreau.com>: > 1+ > > Norman Breau > Software Developer > > nor...@normanbreau.com ( > https://link.getmailspring.com/link/26afd337-8d43-4f5e-9b5d-b565ffb5f...@getmailspring.com/0?redirect=mailto%3Anorman%40normanbreau.com&r

Re: [VOTE] Unarchive & Un-deprecate cordova-plugin-file-transfer

+1 Am Di., 18. Aug. 2020 um 08:31 Uhr schrieb Tim Brust : > +1 > > Sent from my iPhone > > > On 18. Aug 2020, at 8:22 AM, Dave Alden wrote: > > > > +1 > > > >> On Tue, 18 Aug 2020, 05:47 Bryan Ellis, wrote: > >> > >> This vote is only for the purpose of unarchive and remove the > deprecation >

Re: 💡Cordova as a monorepo - ??

> and it would help us to keep the issues and discussions all in one place. I would challenge you actually want that. To be able to properly work on one plugin, you would need to have labelled all issues and PRs and then filter all views for that. In my experience this only makes sense for closel

Re: Migrate Sauce Labs user used in CI testing from snay to cordova

You might go slow on this - somewhere in the back of my head I have _something_ why we did not follow through with this in the past but I can not figure out what it was, sorry :/ Hopefully it is nothing and will just work. J Am So., 30. Aug. 2020 um 19:55 Uhr schrieb Tim Brust : > Hi there, >

Re: [DISCUSS] Moving JIRA issues to Github

If people post their issue at the wrong repo (which of course can and will happen from time to time), there is a way to move them over with minimal loss of information: https://github.com/ionic-team/ionic/issues/12542 https://github.com/ionic-team/ionic-cli/issues/2597 This works for issues where

Re: [DISCUSS] Moving JIRA issues to Github

going to get more high quality bug reports using Github? This may >> not be answerable without trying it out, but making issues easier to create >> issues could cause an influx of questions and non-cordova related bugs. >> This could add on to the difficulties of triaging and mig

Re: [DISCUSS] Moving JIRA issues to Github

r Github based projects do that) -J 2017-08-03 11:55 GMT+02:00 julio cesar sanchez : > What about security issues? > > El 3 ago. 2017 4:53 a. m., "Jan Piotrowski" escribió: > >> >> As a user, I’ll occasionally skim the recently opened bugs in Jira >> across th

Re: github update

Off-list: Why do the repos have to be moved to the apache org? Having a cordova org would have been a much better central place to group all and highlight the important repos and what is going on. -J 2017-08-17 20:34 GMT+02:00 Steven Gill : > So we have officially moved 4 repos under apache org f

Re: [DISCUSS] [Play Services Version]

Is this the same problem that (allegedly) can be fixed by using this plugin? https://github.com/dpa99c/cordova-android-support-gradle-release 2017-08-18 18:02 GMT+02:00 julio cesar sanchez : > This problem is not only present on Play Services version, any other > library or framework, from Android

Re: [DISCUSS] cordova-ios 4.1.1 Release

... like all Ionic projects for example: https://github.com/ionic-team/ionic2-app-base/blob/master/config.xml#L87 Will this trip these up somehow? -J 2017-08-31 23:44 GMT+02:00 Filip Maj : > By the way, I think we should include notes about > cordova-plugin-console being integrated in the blog p

Re: [DISCUSS][DOCS] Revert a change

I am actually surprised deploying is a manual process at all. Having read the steps, I understand why of course. As a person that jumps in on all kinds of projects, I absolutely prefer docs that list each and every little step needed (including all the `cd` etc). The need for manual steps or chec

Re: [proposal] Remove tool generated docs from camera plugin?

The "not aware" problem can probably be resolved (80/20) by adding comments to the template that are also in the generated output. But it the TEMPLATE.md actually a good idea? Is it worth the extra effort? -J 2017-10-15 0:01 GMT+02:00 julio cesar sanchez : > cordova-plugin-camera docs work on a

Re: PR to add native-scroll-to-top option to cordova-plugin-statusbar

Sounds like a useful change. -J 2017-10-20 19:22 GMT+02:00 julio cesar sanchez : > Any other opinions about this? > > > > 2017-10-01 15:56 GMT+02:00 julio cesar sanchez : > >> I'm +1 on this >> >> 2017-09-30 0:56 GMT+02:00 Lu Wang : >> >>> This is in regards to the following PR: https://github.co

Re: Small UI Bug

Hm, am I correct to assume that your initial email included a screenshot of a visual problem? Seems the mailing list filters these out. I reported a bug some time ago that could match the description in your email: https://issues.apache.org/jira/browse/CB-13402 2017-10-23 11:53 GMT+02:00 Sridhar

Re: [DISCUSS] Cordova-Android 6.4.0 Release

Yep, PR for it is here: https://github.com/apache/cordova-docs/pull/757 2017-11-13 19:07 GMT+01:00 julio cesar sanchez : > Are we having a blog post about it? > > 2017-11-01 22:39 GMT+01:00 julio cesar sanchez : > >> +1 >> >> El 1 nov. 2017 6:48 p. m., "Steven Gill" >> escribió: >> >>> Do it! >>>

Re: [DISCUSS] Cordova-iOS 4.5.4 Release

>From Slack: > michaelbschmidt [9:30 AM] > @surajpindoria for the upcoming cordova-ios release 4.5.4: please merge the > pull request on CB-13523 - this is needed for releasing in Xcode 9 in some > circumstances > https://github.com/apache/cordova-ios/pull/347 https://cordova.slack.com/archives

Re: Cordova-plugin-screen-orientation on iOS

Hey Dan, I don't know enough Obj-C to review this, but this sounds like a _really_ useful feature and change. Hope someone else can review this, so it can become part of the plugin. Thanks for the great work! -J 2017-11-25 2:27 GMT+01:00 Dan Field : > Hi all, > > I've submitted a pull request

Re: Regarding pull request CB-13409 in cordova-plugin-inappbrowser

Hi Steinar, the changes from the PR sound pretty useful to me. I don't know enough Obj-C to review your actual code, but I hope someone else can do that and get your code merged. Thanks for the work! -J Ps: "will someone officially review this or what?" is not the most appropriate language. We

Re: [DISCUSS] Cordova-Android 7.0.0

Awesome! For reference, you are talking about https://github.com/apache/cordova-android/pull/389, correct? What can I / one do to test this locally? -J 2017-11-28 19:53 GMT+01:00 Joe Bowser : > Hey > > I'm going to merge in StudioProjectCompat into Master today. Once that's > done, I'd like to

Re: [DISCUSS] Cordova-Android 7.0.0

//github.com/infil00p/cordova-android.git#StudioProjectCompat > > On Tue, Nov 28, 2017 at 12:24 PM, Jan Piotrowski wrote: >> >> Awesome! >> >> For reference, you are talking about >> https://github.com/apache/cordova-android/pull/389, correct? >> >> Wha

Re: [DISCUSS] Cordova-Android 7.0.0

/master/docs/platforms-release-process.md > > I'll be merging this in tomorrow morning (was going to be later today, but > I don't like merging when the CI isn't green) and anyone who is pulling > directly from master should be seeing these changes. > > On Tue, Nov 2

Re: [DISCUSS] Cordova-Android 7.0.0

will need to be updated to the new > paths. > > On Tue, Nov 28, 2017 at 4:26 PM, Joe Bowser wrote: >> On Tue, Nov 28, 2017 at 3:35 PM, Jan Piotrowski >> wrote: >> >>> Is there any "beta" release process defined (7.0.0-beta?) that could >>>

Re: Transparent Splash Screen Background - Windows 10

Sounds like a very useful change that will improve Cordova apps on Windows. +1 2018-01-11 11:56 GMT+01:00 Terence M. Bandoian : > Julio suggested I bring this up for discussion so... related to: > > CB-13641 - https://issues.apache.org/jira/browse/CB-13641 > and https://github.com/apache/c

Re: Transparent Splash Screen Background - Windows 10

it becomes conflicted? > > -Terence > > > > On 1/11/2018 5:58 AM, Jan Piotrowski wrote: >> >> Sounds like a very useful change that will improve Cordova apps on >> Windows. >> +1 >> >> 2018-01-11 11:56 GMT+01:00 Terence M. Bandoian : >>> &

[DISCUSS] Cordova-Windows Release

Does anyone have any reason to delay a cordova-windows platform release? Any outstanding patches to land? If not, I will start the release soon. J - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional comma

Re: [DISCUSS] Cordova-Windows Release

you when there is major progress. Best, Jan 2018-01-19 12:00 GMT+01:00 Jan Piotrowski : > Does anyone have any reason to delay a cordova-windows platform release? > Any outstanding patches to land? > > If not, I will st

Re: [DISCUSS] Cordova-Windows Release

Awesome. I am working on it in #testing in Slack. -J 2018-01-22 3:03 GMT+01:00 Jesse : > I can help you thru this in a bit, give me a couple hours and I’ll jump in > there. > >> On Jan 21, 2018, at 11:00 AM, Jan Piotrowski wrote: >> >> Ok, so release is "i

Re: [DISCUSS] Cordova-Windows Release

am to force 8.1 on one set of them, and modify the other set to look for the correct files that _are_ there. Best, Jan 2018-01-22 11:33 GMT+01:00 Jan Piotrowski : > Awesome. > > I am working on it in #testing in Slack. > > -J > > 2018-01-22 3:03 GMT+01:00 Jesse : >> I can h

Re: [DISCUSS] Cordova-Windows Release

ests to match. imho > >> On Jan 22, 2018, at 8:08 AM, Jan Piotrowski wrote: >> >> Ok, found the culprit: >> >> The default target version was changed from 8.1 to UAP/UWP, as VS-2017 >> doesn't include the tooling for the older ones any more. >> This cha

[DISCUSS] Cordova-Windows 6.0.0

Hello. After we had to scrap release 5.1.0 because of an unexpected breaking change (and broken CI and failing tests), I took the time to work a bit on this and am now planning to go forward with a 6.0.0 release of cordova-windows soonish. Current status: Must - https://github.com/apache/cordova

Re: [DISCUSS] Cordova-Windows 6.0.0

gt; > > @purplecabbage > risingj.com > > On Thu, Jan 25, 2018 at 3:54 PM, Jan Piotrowski > wrote: > >> Hello. >> >> After we had to scrap release 5.1.0 because of an unexpected breaking >> change (and broken CI and failing tests), I took the tim

Re: [DISCUSS] Cordova-Windows 6.0.0

ld be really helpful if you could check out `master` and see if you can reproduce. (Test runs of last commit to master can be seen here: https://ci.appveyor.com/project/Humbedooh/cordova-windows/build/1.0.854) Best, Jan 2018-01-26 1:42 GMT+01:00 Jan Piotrowski : > The failures in https://gi

Re: [DISCUSS] Mark cordova-windows 6.0.0-dev

Changing the version number is part of the release process: https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md#prepare-release We can discuss if this order makes sense, but that is the documented process right now and should be followed. @purplecabbage: PR https:/

Re: Fix crash on cordova-windows@5

I do not think this change necessitates a 5.0.1 or 5.1 release. Cutting another release before 6.0.0 will just confuse people. Just fork the repo and apply the change on your fork, then use that in your app. Although if anyone wants to run the release process, I of course won't stop you. (But I wi

Re: Fix crash on cordova-windows@5

gt; > that > > > they have to use cordova-android@4 for Windows 8.,1 until we get a new > > > release with this crash resolved. > > > > > > Since #247 was already merged into 5.0.x I would be happiest to see it > > > released. I do not see how this kind of a fix cou

Re: [DISCUSS] Cordova-Windows 6.0.0

All that change existing functionality a user could depend on. In this case: https://issues.apache.org/jira/browse/CB-13237 Possibly also the ones disabling the tests (which happened before that one, otherwise this would have been caught) J 2018-02-08 17:06 GMT+01:00 Chris Brody : > Can someone

Re: [DISCUSS] Cordova-Windows 6.0.0

Yes. No. -J 2018-02-09 15:36 GMT+01:00 Chris Brody : > I wonder if we should also consider CB-12499 to be breaking, considering > that Default.rd.xml triggers the test failure on AppVeyor. > > All tests are enabled now right? Or am I mistaken? > > On Thu, Feb 8, 2018 at

Re: [DISCUSS] Cordova-Windows 6.0.0

11:12 AM, Jesse wrote: >> >>> Do the tests pass on your machines? If so, I think we should move forward >>> with the 6.0.0 release, and write this off as a CI environment issue. >>> >>> On Feb 9, 2018, at 7:45 AM, Jan Piotrowski wrote: >>>

Re: [DISCUSS] Cordova-Windows 6.0.0

ase in the near future when we work out the details of a configurable > target/minimum version. > > > > > > @purplecabbage > risingj.com > > On Fri, Feb 9, 2018 at 1:14 PM, Chris Brody wrote: > >> On Feb 9, 2018 3:15 PM, "Jan Piotrowski" wrote: &

Re: [DISCUSS] Cordova-Windows 6.0.0

ndows machine and make sure you can create >>>> and run a new cordova-windows project without having to modify the jsproj >>>> file manually. >>>> >>> > +1. As I said in cordova-windows PR#250 it works for me on Visual Studio > 2015 and Visu

Re: [DISCUSS] Cordova-Windows 6.0.0

After some investigration I now understand the problem, see the update on CB-13870. I consider this a blocking bug for a release of 6.0.0 as `cordova requirements` functionality is broken with current tooling. Let's see if we can fix this... J 2018-02-12 13:42 GMT+01:00 Jan Piotrowski : &

Re: [DISCUSS] Cordova-Windows 6.0.0

nPath` returns the correct path we want to look for the build tools, so we can probably use that. I will have to rewrite the MSBuildTools.js a bit, but that isn't the worst idea anyway as it evolved over time and also has strange duplication. J 2018-02-12 14:52 GMT+01:00 Jan Piotrowski : &g

cordova-windows as first repo with activated GitHub issues?

Hi all! As I am working towards a (bumpy...) 6.0.0 release of cordova-windows, I also went through its JIRA issues again and resolved, closed or moved some of them. I noticed that we are down to 1 page of ~50 issues: https://issues.apache.org/jira/issues/?jql=project%20%3D%20CB%20AND%20status%20i

Re: cordova-windows as first repo with activated GitHub issues?

t; > +1. > You need to file an issue with INFRA. > https://issues.apache.org/jira/browse/INFRA > > On Tue, Feb 13, 2018 at 10:58 PM, Jan Piotrowski > wrote: > > Hi all! > > As I am working towards a (bumpy...) 6.0.0 release of cordova-windows, > I also went through it

[DISCUSS] cordova-windows, AppVeyor: Enable Rolling builds, disable duplicate builds for PR/branches

Hi all. Everybody who has worked on cordova-windows and AppVeyor knows that it can take quite a long time until the builds actually start which is caused by all the other Apache projects also using the same (free) account, with only one build at a time. But I noticed there are also some things we

Re: [DISCUSS] cordova-windows, AppVeyor: Enable Rolling builds, disable duplicate builds for PR/branches

got rid of node versions matrix and decided to just test node v8 ( > for my own quick and dirty experiments ) > > > @purplecabbage > risingj.com > > On Tue, Feb 13, 2018 at 1:36 PM, Jan Piotrowski > wrote: > >> Hi all. >> >> Everybody who has worked on cordova

Re: [DISCUSS] Cordova-Windows 6.0.0

ll correct and I agree, except we do need to update >>>> TargetPlatformVersion >>>> pr here: https://github.com/apache/cordova-windows/pull/250 >>>> Please test this pr on your windows machine and make sure you can create >>>> and run a new cordova-win

Re: [DISCUSS] Cordova-Windows 6.0.0

of `cordova requirements windows` for environment information). Also let me know if everything is fine of course - I actually prefer those ;) Thank you! Jan 2018-02-15 1:09 GMT+01:00 Jan Piotrowski : > Another update: > > - TargetPlatformVersion problem was solved by adding a `prepare`

[DISCUSS] Cordova-Android Release 6.0.0

Does anyone have any reason to delay a cordova-android platform release? Any outstanding patches to land? If not, I will start the release soon-ish. - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional comm

Re: [DISCUSS] Cordova-Android Release 6.0.0

Meh, ignore please. I messed up the title :( 2018-02-19 16:57 GMT+01:00 Jan Piotrowski : > Does anyone have any reason to delay a cordova-android platform release? > Any outstanding patches to land? > > If not, I will start the rele

[DISCUSS] Cordova-Windows Release 6.0.0

Does anyone have any reason to delay a cordova-windows platform release? Any outstanding patches to land? If not, I will start the release soon-ish. - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional comm

Re: cordova-windows as first repo with activated GitHub issues?

Issue created: https://issues.apache.org/jira/browse/INFRA-16061 2018-02-13 17:01 GMT+01:00 Jan Piotrowski : > Ok, thanks. > Then let's wait a bit to see if we get any -1 on this - then I will go > ahead and create the INFRA issue. > > As this is our first repo I suggest we

Re: [DISCUSS] Cordova-Windows Release 6.0.0

JIRA issue to follow the release: https://issues.apache.org/jira/browse/CB-13896 2018-02-19 16:58 GMT+01:00 Jan Piotrowski : > Does anyone have any reason to delay a cordova-windows platform release? > Any outstanding patches to land? > > If not, I will start the rele

Re: cordova-windows as first repo with activated GitHub issues?

And already activated: https://github.com/apache/cordova-windows/issues 2018-02-19 17:04 GMT+01:00 Jan Piotrowski : > Issue created: https://issues.apache.org/jira/browse/INFRA-16061 > > 2018-02-13 17:01 GMT+01:00 Jan Piotrowski : >> Ok, thanks. >> Then let's wait a bit

Re: [DISCUSS] cordova-android release

+1 Looking good. 2018-02-20 19:53 GMT+01:00 Steven Gill : > Issue: https://issues.apache.org/jira/browse/CB-13912 > > I'm thinking minor bump to 7.1.0. You can see the change log in the > comments of the issue > > On Sat, Feb 17, 2018 at 1:51 PM, Simon MacDonald > wrote: > >> +1 >> >> The change

[VOTE] Cordova-Windows@6.0.0 Release

Please review and vote on this 6.0.0 Windows Release by replying to this email (and keep discussion on the DISCUSS thread) Release issue: https://issues.apache.org/jira/browse/CB-13896 The archive has been published to dist/dev: https://dist.apache.org/repos/dist/dev/cordova/CB-13896 The package

Re: [VOTE] Cordova-Windows@6.0.0 Release

The vote has now closed. The results are: Positive Binding Votes: 4 Jesse MacFadyen Alexander Sorokin Steven Gill Jan Piotrowski The vote has passed. Thank you all. 2018-02-22 18:10 GMT+01:00 Jesse : > I vote +1 > > * Ran coho verify-archive > * Ran coho audit-license-headers

Translation Bankruptcy?

Hi all, while doing some work on cordova-docs I also took a look at the translations again. Translations are (theoretically) done on Crowdin, synced from and to Github: https://crowdin.com/project/cordova Unfortunately this doesn't really seem to work: 1. There is no (working) documentation on

Re: Translation Bankruptcy?

me consuming, and if such efforts would be discarded just > for pure change of internal implementation, there no reason to even try. > > Sent from Mail for Windows 10 > > From: Jan Piotrowski > Sent: Tuesday, February 27, 2018 7:22 PM > To: dev > Subject: Translation Bankruptc

Re: Stepping Back

That's a real shame, hope you landed in a interesting new area. Thanks for your work over the years! J 2018-06-20 20:22 GMT+02:00 Joe Bowser : > Hey > > As many people may be aware, I've moved on to another team at Adobe, so I > will no longer be able to be the primary maintainer of Cordova for A

Re: Cross-referencing GH issues?

Github issues have links, I would just include it in the description. "Shorthand" for a link could also be `user/repo#123`. -J 2018-07-17 19:49 GMT+02:00 Chris Brody : > Suppose I would open a GH issue somewhere, then cross-reference it > from a commit or a PR. But the original GH issue is in a d

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

While our repositories are already fully on GitHub [1], our issues mainly still live in JIRA. We previously decided this should be changed [2] so issues live with code. We also did some first switches that were pretty successful: https://github.com/apache/cordova-docs/issues https://github.com/ap

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

r > discussing issues and cordova-discuss has proven to be such an > unpopular repo > On Tue, Jul 31, 2018 at 10:54 AM Jan Piotrowski wrote: >> >> While our repositories are already fully on GitHub [1], our issues >> mainly still live in JIRA. We previously decided this shou

Re: Better discussion forum?

It's an Apache thing: > Apache projects use mailing lists to coordinate development of the software > and administration of the organization. Mailing lists also serve as a primary > support channel where users can help each other learn to use the software. https://apache.org/foundation/mailing

Re: Time to mark major Cordova release & remove committed node_modules?

So this would e.g. bump cordova-windows master from 6.1.0-dev to 7.0.0-dev, so it would be clear that the next release would most probably be a major one, correct? Actual release of that version would only happen if there are enough "real" changes that justify a major release anyway, right? -J 2

Re: Activate issues on all active Cordova repos?

See this [DISCUSS] thread from yesterday: https://lists.apache.org/thread.html/b08341c97a0b9de8207681d601773fc3e697734889284d806d44270f@%3Cdev.cordova.apache.org%3E Please keep discussion on that topic there. -J 2018-08-01 9:07 GMT+02:00 Chris Brody : > I think this is needed pretty badly. I thi

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

Another one: f) Find and activate way for Github issue (and PR) updates to be posted so Slack #issues 2018-07-31 18:14 GMT+02:00 Jan Piotrowski : > The npm forum solves a very different problem for npm - they had too > much noise in Github issues because of the project's popularity.

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

+1 - everything that modernizes the tooling that can be used and actually uses its added functionality is a win. 2018-08-02 7:43 GMT+02:00 Chris Brody : > Just raised https://issues.apache.org/jira/browse/CB-14248 > > Thanks for the helpful responses > On Thu, Aug 2, 2018 at 12:12 AM Shazron wrot

[cordova-android] Fwd: Important reminder about Android targetSdkVersion requirement

Anything we should do about that for Cordova Android or the default Cordova project? What should other projects using Cordova Android do? (e.g. Ionic) -J -- Forwarded message -- From: Google Play Date: 2018-08-02 4:51 GMT+02:00 Subject: Important reminder about Android targetSdk

Re: Do another cordova-android patch release?

> Also considered adding this one about Android Studio compatibility, but was > not sure if the change might be considered breaking or at least minor, so > didn't do it. What would be an argument for this to be considered breaking? 2018-08-02 13:26 GMT+02:00 julio cesar sanchez : > I've sent the

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

ommits, pr, new issues, code reviews, and >> more. >> >> >> > On Aug 1, 2018, at 22:22, Jan Piotrowski wrote: >> > >> > Another one: >> > >> > f) Find and activate way for Github issue (and PR) updates to be >> > posted so

Re: ios-deploy questions

> 1. Why not make ios-deploy a dependency of cordova-ios that would then > be automatically installed? Historically, I think, commands that should be able to be called via the command line had to be installed globally with npm to work. Is this not the case any more? 2018-08-02 15:26 GMT+02:00 Chr

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

Many Cordova users out there are probably using https://github.com/ionic-team/cordova-plugin-ionic-webview. Does this play any role in regards to the 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 pos

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

ues that concern more than one repo (Can we >productively use whatever tools GitHub provides here, or will we have to >get permission from INFRA for every little thing we do?) > > I fear that if we blindly rush into this, all we will get is an even more > fragmented landsca

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

>> >> As long as we don't break pluggable webviews, I don't think it's needed, >> there are other wkwebview plugins (from telerik, oracle, etc). >> >> But as some (or all) of them started as forks, there will be probably >> problems with duplicate class

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

That would be really great. Thanks! 2018-08-02 17:16 GMT+02:00 Shazron : > 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 c

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

Created INFRA issue at https://issues.apache.org/jira/browse/INFRA-16876 2018-08-02 17:29 GMT+02:00 : >> >> For Cordova tooling I expect no one outside of the developers to >> > really know what happens where - but if I see it correctly we almost >> don't have any tooling JIRA issues as well, ri

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

) etc. 2018-08-06 13:09 GMT+02:00 Chris Brody : > On Mon, Aug 6, 2018 at 6:48 AM Jan Piotrowski wrote: >> >> Created INFRA issue at https://issues.apache.org/jira/browse/INFRA-16876 > > +100 > > - &g

[DISCUSS] Delete apache/cordova-fauxton-server repository?

During enabling of issues and removing of "Mirror of ..." on our Github repos INFRA noticed that we have a repo without any content (issues, history, ...): https://github.com/apache/cordova-fauxton-server I will ask INFRA to remove/delete this repo at the end of the week if there are no objection

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

nt? What did you use in JIRA that you couldn't find for Github? Shouldn't be too hard to whip something up. -J 2018-08-06 16:05 GMT+02:00 Jan Piotrowski : > That worked, the ticket was just resolved and issues are now enabled > for all repos (beside cordova-weinre which is archive

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

he sake of easy writing & editing. > > Really nice! > On Tue, Aug 7, 2018 at 11:01 AM Jan Piotrowski wrote: >> >> You may have noticed the first issues coming in on some repositories. >> >> 1. In hindsight enabling issues for deprecated platforms, plugins etc >>

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

Now that Github Issues are enabled on all repositories, it makes sense to create a (or several) new Issue and PR template(s) that doesn't point to JIRA any more and also uses the current state of the art. Current Cordova issue and PR template: - no issue template - https://github.com/apache/cordo

Re: Dealing with deprecated repos

What is the current (probably unwritten) rule regarding deprecation and archival of Cordova repositories? -J 2018-08-07 17:16 GMT+02:00 Chris Brody : > Continuation of discussion from > https://lists.apache.org/thread.html/affbc74f0ff4d34bc09657c3c302e185cc98b946d260184847fdf191@%3Cdev.cordova.ap

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

Aug 7, 2018 at 12:59 PM gandhi rajan >> wrote: >> > >> > Hi Jan, >> > >> > I like your suggestions. But curious to understand how to take care of >> > existing issues which are currently available in JIRA? Should it be >> ported >>

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

What exactly do you mean by "integrate"? Apps built with Cordova (and Ionic) are pretty well supported by Fastlane, /platforms/ios|android are just native projects after all - even though you have to take some extra measures to handle the generated projects. I wrote some articles about how can wor

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

All very good points Chris. >> > 3. Merge Conventions / Protected Branch: > Nice idea. The one exception is that committers sometimes have to tag > and push individual commits when making releases. We will definitely have to check how this works with current workflows defined in coho and in othe

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

gating (one day) as it really works well. -J 2018-08-07 22:54 GMT+02:00 Chris Brody : > Nice, especialy about ionic.zone/fastlane. Shouldn't we feature > fastlane on cordova.io? > On Tue, Aug 7, 2018 at 4:03 PM Jan Piotrowski wrote: >> >> What exactly do you mean by &

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

om/features/ci-cd-integrations > > If they ask to be featured, then sure, lets, but I don't think we need to > be chasing them. > A simple cordova blog post explaining how to get cordova working with > fastlane, et al would be great. > > > > > > @purplecabbage > risi

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

Update to my initial email: I just noticed we actually _do_ have an issue template in use in the cordovs-docs repository: https://github.com/apache/cordova-docs/blob/master/.github/ISSUE_TEMPLATE.md J 2018-08-07 23:18 GMT+02:00 julio cesar sanchez : > I think us as committers should decide if th

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: [DISCUSS] [JIRA -> GitHub Issues] The way forward

ink is server side or it could be client side as well (via > JavaScript). Perhaps on the https://cordova.apache.org/contribute/ > (contribute.cordova.io) page. That massive github link could also be > auto-generated as well on that page, somehow. Let me know how I can > help. > On Tue, Aug 7, 201

Re: Dealing with deprecated repos

in a fork, but it won’t be official and > won’t live in the Apache repo. > > > El miércoles, 8 de agosto de 2018, Jan Piotrowski > escribió: > >> Let me play devil's advocate: >> >> Archiving means disabling everything - issues, PRs, etc. >> Don'

Re: Dealing with deprecated repos

deprecated repos open for issues/PRs in case > somebody want to fix something will just bring frustration to those people > as their PRs won't be reviewed/merged. And if we plan on continuing > reviewing/merging on deprecated repos, why did we deprecate them on the > first place? &

Re: Dealing with deprecated repos

ork has a few other forks itself with some > other extra commits. > > El mié., 8 ago. 2018 a las 12:15, Shazron () escribió: > > > 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,

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: 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

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

Now that we have Github issues enabled for all our repositories, another new thing we have to talk about are Github Issue and Pull Request labels. If you are not aware of Github labels, here is a nice introduction: https://help.github.com/articles/about-labels/ This also contains a list of the d

  1   2   3   >