Nightly build #145 for cordova has succeeded!

2016-09-13 Thread Apache Jenkins Server
Nightly build #145 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/145/consoleFull - Jenkins for Apache Cordova

[DRAFT] Apache Cordova Board Report for Sept 2016

2016-09-13 Thread Shazron
Please review, comment on it, etc: https://github.com/cordova/apache-board-reports/blob/master/2016/2016-09.md

[CORDOVA-LIB] CocoaPods CI testing stalled CB-11811

2016-09-13 Thread Shazron
See: https://issues.apache.org/jira/browse/CB-11811 Does anyone have experience with CocoaPods testing on Travis CI? Keep getting git errors no matter what I do. Doesn't help that for each test it needs to download the whole CocoaPods repo at ~500MB

Re: [DISCUSS] Not requiring an iCLA for contributions

2016-09-13 Thread Steven Gill
+1 On Tue, Sep 13, 2016 at 11:09 AM, Simon MacDonald wrote: > +1 to making it easier to allow people to contribute trivial changes. > > One thing Shaz just mentioned was adding a check box the the PR template so > that people can explicitly indicate their intent. > >

Re: [Discuss] Cordova-Android 6.0.x

2016-09-13 Thread Joe Bowser
No, I have no intention of pulling that into this release, since the corresponding Android code caused performance issues due to numerous file reads. On Tue, Sep 13, 2016 at 11:21 AM, Darryl Pogue wrote: > Just wanted to check whether this cordova-lib change was intended to

Re: [Discuss] Cordova-Android 6.0.x

2016-09-13 Thread Simon MacDonald
I'd love to help out testing but I'm traveling all week. Happy to assist you next week with more testing if you can't find enough other folks to help out this week. Simon Mac Donald http://hi.im/simonmacdonald On Tue, Sep 13, 2016 at 10:30 AM, Joe Bowser wrote: > OK, so it

Re: Regarding Cordova and Gamepad

2016-09-13 Thread Joe Bowser
On Tue, Sep 13, 2016 at 7:56 AM, iono sphere <999ionosphe...@gmail.com> wrote: > I am developing a game using Construct 2 which could export the project to > Cordova. Then, I could put the game into Crosswalk and play the game on my > Android. My Construct 2 game supports gamepad, and this is the

Re: [DISCUSS] Not requiring an iCLA for contributions

2016-09-13 Thread Simon MacDonald
+1 to making it easier to allow people to contribute trivial changes. One thing Shaz just mentioned was adding a check box the the PR template so that people can explicitly indicate their intent. Eventually it would be nice to be able to digitally sign the CLA. Simon Mac Donald

Re: [DISCUSS] Not requiring an iCLA for contributions

2016-09-13 Thread Shazron
An easy definition of trivial IMO is "if they decide to pull this code away from us, is it not a big deal?" The reasons why the code needs to be pulled, who knows what lurks in the minds of lawyers. Typos, doc changes, one liners, are not a big deal usually. On Tue, Sep 13, 2016 at 10:53 AM,

Re: [DISCUSS] Not requiring an iCLA for contributions

2016-09-13 Thread Kerri Shotts
+1 ~ Kerri > On Sep 13, 2016, at 12:27, Shazron wrote: > > Bump. There can't be lazy consensus on this. Before I potentially waste > time on drafting a proposal, trying to feel the temperature on this change. > > On Fri, Sep 9, 2016 at 3:34 PM, Shazron

Regarding Cordova and Gamepad

2016-09-13 Thread iono sphere
I am developing a game using Construct 2 which could export the project to Cordova. Then, I could put the game into Crosswalk and play the game on my Android. My Construct 2 game supports gamepad, and this is the issue: While my HTML5 game could respond to gamepad input just fine on Desktop, I

Re: [DISCUSS] Not requiring an iCLA for contributions

2016-09-13 Thread Joe Bowser
So, it's basically the same system that we have now. I still think we should get clear intent from the author, since that's more useful and easy than determining whether it's trivial. I mean, isn't sending a PR through GitHub already clear intent? On Tue, Sep 13, 2016 at 10:41 AM, Jesse

Re: [DISCUSS] Not requiring an iCLA for contributions

2016-09-13 Thread Jesse
You decide per pr if you think it is trivial. @purplecabbage risingj.com On Tue, Sep 13, 2016 at 10:36 AM, Joe Bowser wrote: > I'll agree to this, since I don't know what the definition of trivial is > w.r.t. Apache. > > +1 > > On Tue, Sep 13, 2016 at 10:30 AM, Jesse

Re: [DISCUSS] Not requiring an iCLA for contributions

2016-09-13 Thread Joe Bowser
I'll agree to this, since I don't know what the definition of trivial is w.r.t. Apache. +1 On Tue, Sep 13, 2016 at 10:30 AM, Jesse wrote: > +1 > > > @purplecabbage > risingj.com > > On Tue, Sep 13, 2016 at 10:27 AM, Shazron wrote: > > > Bump. There

Re: [Discuss] Cordova-Android 6.0.x

2016-09-13 Thread Joe Bowser
OK, so it looks like all our ducks are lined up and we should be ready for a 6.0 release pretty soon. How do people feel about doing testing this week, and getting the vote thread going on Monday? I know the vote thread is only 72 hours, so I want a bit more testing on the major before we do it

Re: [DISCUSS] Not requiring an iCLA for contributions

2016-09-13 Thread Jesse
+1 @purplecabbage risingj.com On Tue, Sep 13, 2016 at 10:27 AM, Shazron wrote: > Bump. There can't be lazy consensus on this. Before I potentially waste > time on drafting a proposal, trying to feel the temperature on this change. > > On Fri, Sep 9, 2016 at 3:34 PM, Shazron

Re: [DISCUSS] Not requiring an iCLA for contributions

2016-09-13 Thread Shazron
Bump. There can't be lazy consensus on this. Before I potentially waste time on drafting a proposal, trying to feel the temperature on this change. On Fri, Sep 9, 2016 at 3:34 PM, Shazron wrote: > It's up to us to decide, and right now we require the iCLA except for > trivial

Re: CB-9762 iOS Launch Storyboard update

2016-09-13 Thread Shazron
We can either roll this in to cordova-ios 4.3.0 or cordova-ios 4.4.0. cordova-ios 4.3.0 has a new feature, CocoaPods support. On Sat, Sep 10, 2016 at 3:31 PM, Kerri Shotts wrote: > So, in playing around with my PR, I've discovered the following: > > - Travis CI fails