I sent a request to our management team for travel, I don't think it's
going to get approved in this short time notice.
We would like to participate if you guys do a 1 hour hangout at the end of
the day maybe to recap.
If not just recording some of the meetings for later viewing that might be
help
Wiki has being updated
https://wiki.apache.org/cordova/CommitterWorkflow
list which repos can be use with post-review, and using github as
alternative for code review.
Oh and I manage to get Jesse's cell number so its there also :-)
--Carlos
On Wed, Oct 16, 2013 at 1:56 AM, Carlos Santana wrot
1. How do I use post-review on cordova-wp8 repo then? without
.reviewboardrc it doesn't work
cordova-wp8:(master)$ post-review
Unable to find a Review Board server for this source code tree.
2. I agree 100% (lets kill dev branch)
But today How do I use post-review to submit a review for a commit
My thoughts:
1. No,
2. master SHOULD be used for development, and considered unstable, but
probably should have passing tests.
- this is not currently the case, but we need to change this. plugman,
I believe is still pulling from master where it should be pulling from a
version tag
3. use gith
No worries -- sorry about the upcoming spam :)
On Tue, Oct 15, 2013 at 9:16 PM, Anis KADRI wrote:
> I did not. I wasn't aware of this "Release" function. Apologies.
>
> On Tue, Oct 15, 2013 at 9:07 PM, Shazron wrote:
> > Did you move the 3.1.0 issues to 3.2.0 automatically? (this is a feature
1. Should all repos contain a file ".reviewboardrc" ? Some repos are
missing this file
2. Should the plugins repos contain the file ".reviewboardrc" and it should
have a variable TRACKING_BRANCH = 'origin/dev'? since 'master' is not being
use for development.
3. Is obligatory to only use reviewbo
I did not. I wasn't aware of this "Release" function. Apologies.
On Tue, Oct 15, 2013 at 9:07 PM, Shazron wrote:
> Did you move the 3.1.0 issues to 3.2.0 automatically? (this is a feature of
> the Release function). Didn't receive the usual flurry of emails. If not,
> everyone needs to check 3.1.
Did you move the 3.1.0 issues to 3.2.0 automatically? (this is a feature of
the Release function). Didn't receive the usual flurry of emails. If not,
everyone needs to check 3.1.0 issues in JIRA, and either remove the 3.1.0
version from each issue or move to 3.2.0
On Tue, Oct 15, 2013 at 2:15 PM,
Hey Anis,
plugman command line is better than what I have been doing :)
I failed to find the multiple registry issue. Can you forward it if you
find it.
Of course it is up to the provider but does that mean there is no curation
and cordova.io registry may carry plugins that has never worked?
--
Go
I agree that they should be encouraged.
configuration is stored in plugman (even for cordova-cli) and one can
easily set a registry with `plugman config set registry
http://newregistry' (exactly like NPM).
There were discussions about adding multiple registry support as well
as a fallback to the
3.5
(Or six months.)
But ya, what Jesse said.
On Tuesday, October 15, 2013, Jesse wrote:
> I would not add iOS7 support.
> I would consider adding any plugin changes if it is not too difficult to do
> so.
>
> @purplecabbage
> risingj.com
>
>
> On Tue, Oct 15, 2013 at 4:56 PM, Shazron >
> wrote:
I would not add iOS7 support.
I would consider adding any plugin changes if it is not too difficult to do
so.
@purplecabbage
risingj.com
On Tue, Oct 15, 2013 at 4:56 PM, Shazron wrote:
> Nothing is "completely" broken in iOS 7, although with iOS 7 issues that is
> debatable. If we keep patchin
Nothing is "completely" broken in iOS 7, although with iOS 7 issues that is
debatable. If we keep patching 2.9.x no one will move on to 3.x... (at
least for iOS). There has to be an ending...
On Tue, Oct 15, 2013 at 4:53 PM, Jesse wrote:
> Decide what is completely broken in your platform, that
Decide what is completely broken in your platform, that is reasonable to
fix, and fix it.
No promises ... just fix what we can, and document that it is fixed. I
think...
@purplecabbage
risingj.com
On Tue, Oct 15, 2013 at 3:10 PM, Shazron wrote:
> One question about this that was not answered.
Should 3rd party plugin registries be encouraged or not? I personally would
like to see more of them but I do not think we are technically supporting
them enough. Introducing a new registry to plugman/cli is done through
config.js. I guess the first problem is that "it is done through config.js"
ra
+1 for some kind of list
Whenever the documented API refers to plugins which are not found in
what I thought was the official set plugins at
https://github.com/search?q=%40apache+cordova-plugin my brain hurts.
e.g. https://issues.apache.org/jira/browse/CB-5090
Peter.
-Original Message-
One question about this that was not answered. When does back-porting end?
I'm not sure what we promised for 2.9.x support going forward...
On Tue, Oct 15, 2013 at 1:16 PM, Jesse wrote:
> Okay, I am actively working on back-porting plugin fixes into 2.9.1 for
> WP7, WP8, and Windows8
> What is
oversight
opened a bug: http://issues.cordova.io/5089
On Tue, Oct 15, 2013 at 4:24 PM, Marcel Kinard wrote:
> Here's the question I'm wondering about:
>
> The console plugin is not documented in cordova-docs. Is that an
> oversight, or is it a plugin that is treated differently?
>
> My take is
done
On Tue, Oct 15, 2013 at 2:09 PM, Marcel Kinard wrote:
> Could one of the folks with Jira karma add "3.1.0" to the list of released
> versions? Thanks!
Could one of the folks with Jira karma add "3.1.0" to the list of released
versions? Thanks!
Here's the question I'm wondering about:
The console plugin is not documented in cordova-docs. Is that an oversight, or
is it a plugin that is treated differently?
My take is that it is an oversight. If not, then what is the reasoning?
Okay, I am actively working on back-porting plugin fixes into 2.9.1 for
WP7, WP8, and Windows8
What is the status of Android, BB, iOS, ... ?
@purplecabbage
risingj.com
On Mon, Oct 7, 2013 at 12:58 PM, Jesse MacFadyen wrote:
> Yes, now that 3.1.0 is out the door, we can do this.
>
> Sent from
I was doing separate searches on "Lucas" and "Holmquist" and not finding you.
It would be nice if the public name on the ICLA had your last name. An entry
saying only "Luke" is fairly ambiguous. Would you be OK asking the secretary to
make that change?
Begin forwarded message:
> From: "Lucas H
yea, i didn't realize it was going to be like that :)
On Oct 15, 2013, at 3:17 PM, Marcel Kinard wrote:
> I was doing separate searches on "Lucas" and "Holmquist" and not finding you.
> It would be nice if the public name on the ICLA had your last name. An entry
> saying only "Luke" is fairly
The tacit plan is to observe the plugin installation/download counts to
inform our decisions about what remains official and not. I suspect we
maintain more stuff than our community currently uses or needs.
Also, agree w/ Andrew that we should start migrating docs to the plugins
themselves.
On T
I think it depends on what your definition of "officially supported" is. If
it's that we'll try and fix bugs that arise in them, I think they are all
officially supported.
In a 3.0 world, I think we'll move more towards having docs bundled with
plugins instead of hosted on docs.cordova.io, so I do
As we're breaking out and developing more and more plugins, one question I have
been getting is "what is the set of plugins officially supported by the Cordova
community?" It's unclear to me what defines this set. Here's how I've been
categorizing them.
Supported
1) Publicly documented APIs o
This is interesting (I like the 3 platforms support) - if this gets in, I
propose retiring the cordova-osx repo.
On Tue, Oct 15, 2013 at 11:00 AM, Maxime LUCE wrote:
> Yes Jesse,
>
> It's about supporting node-webkit as a new, different platform.
> I see some great value added to a desktop plat
Yes Jesse,
It's about supporting node-webkit as a new, different platform.
I see some great value added to a desktop platform :
- Really easy to debug (chromium dev tools integrated)
- Allow kiosk mode and other desktop integration which can be usefull in touch
aware application.
- Allow packagi
No, we are talking about node-webkit OR appjs as another target platform to
support, which would mean we could build for apps for Windows, Linux, OSX
desktop applications.
I think node-webkit is the more mature platform, but I have only glanced at
both. Definitely interesting.
@purplecabbage
risi
phones...and tablets :-)
On Tue, Oct 15, 2013 at 10:38 AM, Brian LeRoux wrote:
> Cordova is mostly about phones (except when its OS X and Windows). Node
> support is not a project goal though I would encourage you to look at
> authoring plugins for iOS, Android, Windows Phone that mimic Node APIs
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/14621/#review27033
---
Ship it!
Ship It!
- Jeffrey Heifetz
On Oct. 12, 2013, 2:45 a.m.,
Cordova is mostly about phones (except when its OS X and Windows). Node
support is not a project goal though I would encourage you to look at
authoring plugins for iOS, Android, Windows Phone that mimic Node APIs if
that is something you're looking for.
On Tue, Oct 15, 2013 at 1:27 PM, Maxime LUC
What about a node-webkit or appjs platform integration ?
It could help debugging with Cordova related projects and permit to add three
platform with one platform : "Windows", "Linux", "OSX".
I'm thinking about a platform proxy for node-webkit and/or appjs-deskshell.
What do you think of this imp
In spite of that fact that it needs a tooling change, I like the added
tag / prepare steps.
The tooling change should be small and it means no runtime impact on apps.
I love the approach - a very positive step to cleaning up testing.
David Kemp
On Tue, Oct 15, 2013 at 12:18 PM, Michal Mocny
Achana, Good questions. I've been reorganizing the content a great
deal, and have been meaning to write up some sort of doc roadmap,
which I'll bootstrap here.
The "Platform Guides" are where most of the platform-specific content
lives, in various directories within edge/guide/platforms. See the
Braden, you're right, good catch.
Discussing locally how we could support "prepare --mode=..." in the most
generalized form, we remembered an old suggestion to just support
tags.
The benefits seem to be:
- No need to add custom tag-prefix/attributes for the combinations of
js-module mode=, asset
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/14621/#review27024
---
Ship it!
Ship It!
- Braden Shepherdson
On Oct. 12, 2013, 2:45 a.
It's not true that adding these tests only creates larger binaries. They
will be fetched and parsed by the plugin loader code at app startup time.
It goes through the list of all plugins in cordova_plugins.js and loads
them all. That parses them, and runs the outermost layer, which is the
wrapping
This is coming up this Thursday! What do people want to talk about? Here's
a couple to get us going:
- Plugin registry download counts (Are these available yet)
- Idea: Split cordova-cli-lib from cordova-cli on NPM (have cordova-cli and
phonegap-cli depend on cordova-cli-lib)
- Michal's work on CD
Awesome! Glad that you guys can come!
>From the Google side - I think everyone will be here except for Braden
(he's going to MTV to give a talk on AngularJS!).
Here's a slightly expanded list of work topics I've thought of. Feel free
to add or to take ownership of topics:
- API Audit of File API
Thanks! We will test this out today and get it merged in.
On Mon, Oct 14, 2013 at 5:01 PM, Maxime LUCE wrote:
> Thanks it's OK now !!
> So quick !!!
>
> I created a pull request on Github :
> https://github.com/apache/cordova-blackberry/pull/105
> If someone could review it and merge into apach
42 matches
Mail list logo
