GitHub user piotrowski opened a pull request:
https://github.com/apache/cordova-ios/pull/300
Fix list in README
Github changed parsing of .md files, broke lots of stuff in lots of
repositories in the process
(Sorry, not going to create an account, write tickets etc for a
Github user piotrowski commented on a diff in the pull request:
https://github.com/apache/cordova-docs/pull/697#discussion_r114571600
--- Diff: www/docs/de/6.x/guide/overview/index.md ---
@@ -23,19 +23,19 @@ toc_title: Overview
# Ãbersicht
-Apache Cordova ist
Github user piotrowski commented on a diff in the pull request:
https://github.com/apache/cordova-docs/pull/697#discussion_r114571912
--- Diff: www/docs/de/6.x/guide/overview/index.md ---
@@ -23,19 +23,19 @@ toc_title: Overview
# Ãbersicht
-Apache Cordova ist
Github user piotrowski commented on a diff in the pull request:
https://github.com/apache/cordova-docs/pull/697#discussion_r114571985
--- Diff: www/docs/de/6.x/guide/overview/index.md ---
@@ -23,19 +23,19 @@ toc_title: Overview
# Ãbersicht
-Apache Cordova ist
Github user piotrowski commented on a diff in the pull request:
https://github.com/apache/cordova-docs/pull/699#discussion_r114967465
--- Diff: www/_posts/2017-04-21-cordova-7.md ---
@@ -0,0 +1,146 @@
+---
+layout: post
+author:
+name: Audrey So
+url
Github user piotrowski commented on a diff in the pull request:
https://github.com/apache/cordova-docs/pull/699#discussion_r114967632
--- Diff: www/_posts/2017-04-21-cordova-7.md ---
@@ -0,0 +1,146 @@
+---
+layout: post
+author:
+name: Audrey So
+url
Github user piotrowski commented on a diff in the pull request:
https://github.com/apache/cordova-docs/pull/699#discussion_r114969800
--- Diff: www/_posts/2017-04-21-cordova-7.md ---
@@ -0,0 +1,146 @@
+---
+layout: post
+author:
+name: Audrey So
+url
Github user piotrowski commented on the issue:
https://github.com/apache/cordova-docs/pull/699
Thanks @stevengill for the responses on my comments, all makes sense. I
also noticed I am a bit late as the blog post is already published.
But: This is missing from the blog post
Github user piotrowski commented on the issue:
https://github.com/apache/cordova-lib/pull/558
Which files will this affect?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user piotrowski commented on a diff in the pull request:
https://github.com/apache/cordova-docs/pull/703#discussion_r117999300
--- Diff: www/docs/en/dev/guide/appdev/security/index.md ---
@@ -27,69 +27,155 @@ description: Information and tips for building a
secure
Github user piotrowski commented on a diff in the pull request:
https://github.com/apache/cordova-docs/pull/703#discussion_r118000286
--- Diff: www/docs/en/dev/guide/appdev/security/index.md ---
@@ -27,69 +27,155 @@ description: Information and tips for building a
secure
Github user piotrowski commented on a diff in the pull request:
https://github.com/apache/cordova-docs/pull/703#discussion_r118000396
--- Diff: www/docs/en/dev/guide/appdev/security/index.md ---
@@ -27,69 +27,155 @@ description: Information and tips for building a
secure
Github user piotrowski commented on the issue:
https://github.com/apache/cordova-docs/pull/697
@shazron Yes, great improvement on the current text.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
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
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
+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
>
+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
+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
>
> 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
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,
>
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
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
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
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
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
... 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
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
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
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
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
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!
>>>
>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
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
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
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
//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
/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
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
>>>
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
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 :
>>>
&
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
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
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
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
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
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
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
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
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:/
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
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
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
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
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:
>>>
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:
&
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
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 :
&
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
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
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
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
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
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
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`
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
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
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
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
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
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
+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
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
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
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
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
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
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
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
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
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
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
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
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.
+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
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
> 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
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
> 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
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
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
>>
>> 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
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
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
) 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
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
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
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
>>
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
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
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
>>
1 - 100 of 250 matches
Mail list logo
