Re: Serve vs. opening an HTML file in the browser
One of the original motivations for cordova serve was for it to watch for changes and automatically run prepare for you. I don't think this is working right now though. On Fri, Aug 2, 2013 at 4:23 PM, Anis KADRI anis.ka...@gmail.com wrote: XHRs won't work by default on certain browsers such as Chrome. I don't think there are any other benefits. This restriction does not exist on a device. On Fri, Aug 2, 2013 at 1:13 PM, John M. Wargo jwarg...@gmail.com wrote: Can someone help me understand why I would want to use cordova serve rather than just loading the web content in the browser directly (through File - Open for example)? Is there something special that serve does that makes this approach better?
Re: Why CLI Plugman are so slow
Whenever I run createmobilespec.sh, I get an EMFILE error, which is caused by shelljs.exec leaking file handles, so it must be calling it a good number of times. Did you replace it with shelljs-ffi in plugman as well? Somewhat related - I tried swapping in shelljs-ffi in coho, but it fails after a while as well due to some cryptic FILE related error. On Fri, Aug 2, 2013 at 5:23 PM, Michal Mocny mmo...@chromium.org wrote: Not nested as in, for any single command we don't launch many subprocesses, maybe just a single invocation. So, the bulk of the time is spent outside of the overhead of this single slow utility. I think! On Fri, Aug 2, 2013 at 3:49 PM, Anis KADRI anis.ka...@gmail.com wrote: not nested as in we're using it in synchronous way ? On Fri, Aug 2, 2013 at 12:30 PM, Michal Mocny mmo...@chromium.org wrote: Just did a few quick tests: while shelljs exec may be slow, seems we are not using it in a nested way (which seems quite obvious). I wrote a quick benchmark to: cordova plugin ls cordova platform ls cordova prepare in a loop a bunch of times and see almost zero time difference replacing shelljs with shelljs-ffi. I would imagine that means very little benefit to replacing with child_process as well, at least for a perf standpoint. It may still be worth doing for other benefits, but in the interest of trying to make cordova-cli faster, I'm going to benchmark for other bottlenecks. -Michal On Thu, Jul 25, 2013 at 1:57 PM, Filip Maj f...@adobe.com wrote: cheers On 7/25/13 10:54 AM, Andrew Grieve agri...@chromium.org wrote: Issues created. https://issues.apache.org/jira/browse/CB-4398 https://issues.apache.org/jira/browse/CB-4397 On Thu, Jul 25, 2013 at 1:41 PM, Filip Maj f...@adobe.com wrote: Chalk it up as another issue. Feel free to help out with CLI/plugman tagged issues everyone. Lots of work there! ;) On 7/25/13 10:39 AM, Anis KADRI anis.ka...@gmail.com wrote: xD. +1 for child_process because it comes with node too eh :) On Thu, Jul 25, 2013 at 10:36 AM, Filip Maj f...@adobe.com wrote: Changed your named to Gmail now huh Jesse? On 7/25/13 10:32 AM, Gmail purplecabb...@gmail.com wrote: +1 to child_process or leave it slow. Sent from my iPhone On Jul 25, 2013, at 10:28 AM, Filip Maj f...@adobe.com wrote: Yeah that¹s how a lot of the hey this works native on windows modules on npm works: they have to compile it D: On 7/25/13 10:26 AM, Andrew Grieve agri...@chromium.org wrote: just tried it, and it does, but only if you have both python and visual studio installed on your machine. Guess it builds the .dll at npm install time :( On Thu, Jul 25, 2013 at 1:23 PM, Anis KADRI anis.ka...@gmail.com wrote: https://github.com/rbranson/node-ffi looks like it does On Thu, Jul 25, 2013 at 10:14 AM, Filip Maj f...@adobe.com wrote: Does it work with Windows? On 7/25/13 10:11 AM, Andrew Grieve agri...@chromium.org wrote: Looks like the fix is pretty easy: agrieve@agrieve-macbookpro ~/git/cordova/tmp$ time node go3.js went 0 times went 10 times went 20 times went 30 times went 40 times went 50 times went 60 times went 70 times went 80 times went 90 times went 100 times real 0m0.444s user 0m0.266s sys 0m0.158s All I did was replace shelljs with shelljs-ffi. On Thu, Jul 25, 2013 at 12:53 PM, Filip Maj f...@adobe.com wrote: Cool, nice work. We could either try to contribute to shelljs or rip it out and go all child process all the time In any case I think this bench should be submitted to shelljs repo. @r2r, dude who maintains it, would probably like to know On 7/25/13 9:50 AM, Andrew Grieve agri...@chromium.org wrote: One reason: shelljs.exec() Did a test to see how many times I could execute true. 9 seconds vs .5 seconds! agrieve@agrieve-macbookpro ~/git/cordova/tmp$ time node shelljstest.js went 0 times went 10 times went 20 times went 30 times went 40 times went 50 times went 60 times went 70 times went 80 times went 90 times went 100 times real 0m8.873s user 0m10.941s sys 0m6.005s agrieve@agrieve-macbookpro ~/git/cordova/tmp$ time node child_processtest.js went 10 times went 20 times went 30 times went 40 times went 50 times went 60 times went 70 times went 80 times went 90 times went 100 times real 0m0.470s user 0m0.278s sys 0m0.228s
Re: Serve vs. opening an HTML file in the browser
file:// urls come with a lot of restrictions in chrome in desktop, but that isn't the intended use case anyway. The intended purpose was to load the web assets from a mobile device instead of loading the bundled versions, so as to get rapid edit-refresh when not making changes to native bits. As Andrew points out 'serve' command will 'prepare' whenever necessary (grunt watch?) and also serve up files via local web server. The simple local alternative may be to just use your own local web server from the top level www/ dir, thus avoiding the need to prepare -- but it only works if and only if you do not use merges/, and none of your plugins have web assets (js-modules are fine I think?), which is not usually the situation. -Michal On Tue, Aug 6, 2013 at 9:53 AM, Andrew Grieve agri...@chromium.org wrote: One of the original motivations for cordova serve was for it to watch for changes and automatically run prepare for you. I don't think this is working right now though. On Fri, Aug 2, 2013 at 4:23 PM, Anis KADRI anis.ka...@gmail.com wrote: XHRs won't work by default on certain browsers such as Chrome. I don't think there are any other benefits. This restriction does not exist on a device. On Fri, Aug 2, 2013 at 1:13 PM, John M. Wargo jwarg...@gmail.com wrote: Can someone help me understand why I would want to use cordova serve rather than just loading the web content in the browser directly (through File - Open for example)? Is there something special that serve does that makes this approach better?
Re: Why CLI Plugman are so slow
Just replaced all instances in cordova-cli and plugman, and removed shelljs from node_modules to make *sure* we don't use that one anywhere. (also forced a syntax error to sanity check that I'm sure I'm using the right local version). Results are zero noticeable improvement in perf. May still be worth the switch for the file handle issues or whatnot, but I don't predict a perf win. -Michal On Tue, Aug 6, 2013 at 10:22 AM, Michal Mocny mmo...@chromium.org wrote: I didn't replace it inside plugman, but assumed that for plugin ls and platform ls it would not call into plugman.. perhaps it always does for some setup, and I'll try replacing *all* instances for good measure. On Tue, Aug 6, 2013 at 9:57 AM, Andrew Grieve agri...@chromium.orgwrote: Whenever I run createmobilespec.sh, I get an EMFILE error, which is caused by shelljs.exec leaking file handles, so it must be calling it a good number of times. Did you replace it with shelljs-ffi in plugman as well? Somewhat related - I tried swapping in shelljs-ffi in coho, but it fails after a while as well due to some cryptic FILE related error. On Fri, Aug 2, 2013 at 5:23 PM, Michal Mocny mmo...@chromium.org wrote: Not nested as in, for any single command we don't launch many subprocesses, maybe just a single invocation. So, the bulk of the time is spent outside of the overhead of this single slow utility. I think! On Fri, Aug 2, 2013 at 3:49 PM, Anis KADRI anis.ka...@gmail.com wrote: not nested as in we're using it in synchronous way ? On Fri, Aug 2, 2013 at 12:30 PM, Michal Mocny mmo...@chromium.org wrote: Just did a few quick tests: while shelljs exec may be slow, seems we are not using it in a nested way (which seems quite obvious). I wrote a quick benchmark to: cordova plugin ls cordova platform ls cordova prepare in a loop a bunch of times and see almost zero time difference replacing shelljs with shelljs-ffi. I would imagine that means very little benefit to replacing with child_process as well, at least for a perf standpoint. It may still be worth doing for other benefits, but in the interest of trying to make cordova-cli faster, I'm going to benchmark for other bottlenecks. -Michal On Thu, Jul 25, 2013 at 1:57 PM, Filip Maj f...@adobe.com wrote: cheers On 7/25/13 10:54 AM, Andrew Grieve agri...@chromium.org wrote: Issues created. https://issues.apache.org/jira/browse/CB-4398 https://issues.apache.org/jira/browse/CB-4397 On Thu, Jul 25, 2013 at 1:41 PM, Filip Maj f...@adobe.com wrote: Chalk it up as another issue. Feel free to help out with CLI/plugman tagged issues everyone. Lots of work there! ;) On 7/25/13 10:39 AM, Anis KADRI anis.ka...@gmail.com wrote: xD. +1 for child_process because it comes with node too eh :) On Thu, Jul 25, 2013 at 10:36 AM, Filip Maj f...@adobe.com wrote: Changed your named to Gmail now huh Jesse? On 7/25/13 10:32 AM, Gmail purplecabb...@gmail.com wrote: +1 to child_process or leave it slow. Sent from my iPhone On Jul 25, 2013, at 10:28 AM, Filip Maj f...@adobe.com wrote: Yeah that¹s how a lot of the hey this works native on windows modules on npm works: they have to compile it D: On 7/25/13 10:26 AM, Andrew Grieve agri...@chromium.org wrote: just tried it, and it does, but only if you have both python and visual studio installed on your machine. Guess it builds the .dll at npm install time :( On Thu, Jul 25, 2013 at 1:23 PM, Anis KADRI anis.ka...@gmail.com wrote: https://github.com/rbranson/node-ffi looks like it does On Thu, Jul 25, 2013 at 10:14 AM, Filip Maj f...@adobe.com wrote: Does it work with Windows? On 7/25/13 10:11 AM, Andrew Grieve agri...@chromium.org wrote: Looks like the fix is pretty easy: agrieve@agrieve-macbookpro ~/git/cordova/tmp$ time node go3.js went 0 times went 10 times went 20 times went 30 times went 40 times went 50 times went 60 times went 70 times went 80 times went 90 times went 100 times real 0m0.444s user 0m0.266s sys 0m0.158s All I did was replace shelljs with shelljs-ffi. On Thu, Jul 25, 2013 at 12:53 PM, Filip Maj f...@adobe.com wrote: Cool, nice work. We could either try to contribute to shelljs or rip it out and go all child process all the time In any case I think this bench should be submitted to shelljs repo. @r2r, dude who maintains it, would probably like to know
Posting Blog Posts
Here's a draft of a how to write a blog post. I intend to add this to the website's README.md. Wanted to get some feedback / +1 since this is a process. Writting a Blog Post Blog posts live in `www/_posts`. To create a new post: 1. Copy one of the existing posts into a new file (changing the name appropriately). 2. Run rake serve in the background. 3. Draft your post. 4. Get your post reviewed by at least one other committer 1. via http://reviews.apache.org. 2. Should be able to do this by running the post-review tool. If the tool is not working, upload the diff manually (via svn diff file, and be sure to add the cordova group to the review request). 5. Update the file name to reflect the commit date (if necessary) 6. Run rake build 7. svn commit *Post guidelines:* * Use the post title as the first header. Including a header as well makes the snippet on the front page look really bad. * Use `rake serve` and refresh frequently. Jekyll does not do a good job at telling you where errors are made. * Review your post yourself before asking for a review. This includes spell-check :).
RE: Serve vs. opening an HTML file in the browser
Thanks. Another question, how is Ripple used with the CLI? John M. Wargo SAP | Charlotte, NC | USA Office: +1 704.321.0265 | Mobile: +1 704.249.7476 Email: john.wa...@sap.com Twitter: @johnwargo -Original Message- From: mmo...@google.com [mailto:mmo...@google.com] On Behalf Of Michal Mocny Sent: Tuesday, August 06, 2013 10:21 AM To: dev Subject: Re: Serve vs. opening an HTML file in the browser file:// urls come with a lot of restrictions in chrome in desktop, but that isn't the intended use case anyway. The intended purpose was to load the web assets from a mobile device instead of loading the bundled versions, so as to get rapid edit-refresh when not making changes to native bits. As Andrew points out 'serve' command will 'prepare' whenever necessary (grunt watch?) and also serve up files via local web server. The simple local alternative may be to just use your own local web server from the top level www/ dir, thus avoiding the need to prepare -- but it only works if and only if you do not use merges/, and none of your plugins have web assets (js-modules are fine I think?), which is not usually the situation. -Michal On Tue, Aug 6, 2013 at 9:53 AM, Andrew Grieve agri...@chromium.org wrote: One of the original motivations for cordova serve was for it to watch for changes and automatically run prepare for you. I don't think this is working right now though. On Fri, Aug 2, 2013 at 4:23 PM, Anis KADRI anis.ka...@gmail.com wrote: XHRs won't work by default on certain browsers such as Chrome. I don't think there are any other benefits. This restriction does not exist on a device. On Fri, Aug 2, 2013 at 1:13 PM, John M. Wargo jwarg...@gmail.com wrote: Can someone help me understand why I would want to use cordova serve rather than just loading the web content in the browser directly (through File - Open for example)? Is there something special that serve does that makes this approach better?
Re: Why CLI Plugman are so slow
cordova plugin ls
cordova platform ls
cordova prepare
I don't think any of these commands invoke shelljs
On Thu, Jul 25, 2013 at 1:57 PM, Filip Maj f...@adobe.com wrote:
cheers
On 7/25/13 10:54 AM, Andrew Grieve agri...@chromium.org wrote:
Issues created.
https://issues.apache.org/jira/browse/CB-4398
https://issues.apache.org/jira/browse/CB-4397
On Thu, Jul 25, 2013 at 1:41 PM, Filip Maj f...@adobe.com wrote:
Chalk it up as another issue.
Feel free to help out with CLI/plugman tagged issues everyone. Lots
of
work there! ;)
On 7/25/13 10:39 AM, Anis KADRI anis.ka...@gmail.com wrote:
xD. +1 for child_process because it comes with node too eh :)
On Thu, Jul 25, 2013 at 10:36 AM, Filip Maj f...@adobe.com wrote:
Changed your named to Gmail now huh Jesse?
On 7/25/13 10:32 AM, Gmail purplecabb...@gmail.com wrote:
+1 to child_process or leave it slow.
Sent from my iPhone
On Jul 25, 2013, at 10:28 AM, Filip Maj f...@adobe.com wrote:
Yeah that¹s how a lot of the hey this works native on windows
modules
on
npm works: they have to compile it D:
On 7/25/13 10:26 AM, Andrew Grieve agri...@chromium.org
wrote:
just tried it, and it does, but only if you have both python
and
visual
studio installed on your machine. Guess it builds the .dll at
npm
install
time :(
On Thu, Jul 25, 2013 at 1:23 PM, Anis KADRI
anis.ka...@gmail.com
wrote:
https://github.com/rbranson/node-ffi
looks like it does
On Thu, Jul 25, 2013 at 10:14 AM, Filip Maj f...@adobe.com
wrote:
Does it work with Windows?
On 7/25/13 10:11 AM, Andrew Grieve agri...@chromium.org
wrote:
Looks like the fix is pretty easy:
agrieve@agrieve-macbookpro ~/git/cordova/tmp$ time node
go3.js
went 0 times
went 10 times
went 20 times
went 30 times
went 40 times
went 50 times
went 60 times
went 70 times
went 80 times
went 90 times
went 100 times
real 0m0.444s
user 0m0.266s
sys 0m0.158s
All I did was replace shelljs with shelljs-ffi.
On Thu, Jul 25, 2013 at 12:53 PM, Filip Maj f...@adobe.com
wrote:
Cool, nice work.
We could either try to contribute to shelljs or rip it out
and go
all
child process all the time
In any case I think this bench should be submitted to
shelljs
repo.
@r2r,
dude who maintains it, would probably like to know
On 7/25/13 9:50 AM, Andrew Grieve agri...@chromium.org
wrote:
One reason: shelljs.exec()
Did a test to see how many times I could execute true. 9
seconds
vs
.5
seconds!
agrieve@agrieve-macbookpro ~/git/cordova/tmp$ time node
shelljstest.js
went 0 times
went 10 times
went 20 times
went 30 times
went 40 times
went 50 times
went 60 times
went 70 times
went 80 times
went 90 times
went 100 times
real 0m8.873s
user 0m10.941s
sys 0m6.005s
agrieve@agrieve-macbookpro ~/git/cordova/tmp$ time node
child_processtest.js
went 10 times
went 20 times
went 30 times
went 40 times
went 50 times
went 60 times
went 70 times
went 80 times
went 90 times
went 100 times
real 0m0.470s
user 0m0.278s
sys 0m0.228s
Here's the code:
shelljstest.js
var shjs = require('shelljs');
for (var i = 0; ; ++i) {
shjs.exec('true');
if ((i / 10 | 0) == i / 10) {
console.log('went ' + i + ' times');
}
if (i == 100) {
process.exit(0);
}
}
child_processtest.js
var child = require('child_process');
var i = 0;
function go() {
child.exec('true', function() {
++i;
if ((i / 10 | 0) == i / 10) {
console.log('went ' + i + ' times');
}
if (i == 100) {
process.exit(0);
}
go();
});
}
go();
Re: [CLI,Android] Removing FileTransfer plugin fails with ENOENT
+1, let's file it as an issue On 8/6/13 7:01 AM, Andrew Grieve agri...@chromium.org wrote: The path where it was looking for the file looks correct to me. Note that plugins get copied into your project in *two* spots: 1. within plugins/ 2. within platforms/ I think the bug here is that we should ignore when files we're trying to delete are already gone. On Sat, Aug 3, 2013 at 8:32 PM, Brian M Dube bd...@apache.org wrote: On 08/03/2013 02:51 PM, Don Coleman wrote: This is probably and issue, plugman doesn't work well when files are missing Usually you can touch the missing files and then uninstall Thanks, Don. This works around the issue if I touch each source file that is expected to be found during plugin removal. Tedious, but it works. The issue, I think, is not that the files are 'missing' but that they exist somewhere else. Why does the removal step expect to find them somewhere other than where the installation step dropped them? $ touch /home/bdube/workspace/DropIt/platforms/android/src/org/ apac he/cordova/core/FileTransfer.java $ cordova -d plugin rm org.apache.cordova.core.file-transfer Other times it is easier to delete the contents of the plugin directory and re-install all the plugins On Sat, Aug 3, 2013 at 3:05 PM, Brian M Dubebd...@apache.org wrote: I can't tell which piece of the puzzle to massage to make this work. See output below. The path plugman is attempting to unlink is not where the plugin code is installed. Adding and removing the geolocation plugin works for me so I tried to find the difference between the two plugin.xml files. If that's where the answer lies, I've missed it. Am I doing this all wrong? If I should file an issue, which component? $ pwd /home/bdube/workspace/DropIt $ cordova -v 3.0.4 $ cordova plugin ls [ 'org.apache.cordova.core.file-transfer' ] $ cordova -d plugin rm org.apache.cordova.core.file-transfer Calling plugman.uninstall on plugin org.apache.cordova.core.file-** **transfer for platform android Uninstalling org.apache.cordova.core.file-transfer... Beginning processing of action stack for android project... Parsing android project files... Error during processing of action! Attempting to revert... Error: Uh oh! ENOENT, no such file or directory '/home/bdube/workspace/DropIt/ platforms/android/src/org/apache/cordova/core/FileTransfer.java ' at Object.fs.unlinkSync (fs.js:760:18) at Object.module.exports.deleteJava (/home/bdube/lib/node-v0.10.** 10-linux-x64/lib/node_modules/cordova/node_modules/**plugman/** src/platforms/common.js:44:12) at module.exports.source-file.uninstall (/home/bdube/lib/node-v0.10. **10-linux-x64/lib/node_**modules/**cordova/node_**modules/plugman/** src/platforms/android.js:44:20) at Object.ActionStack.process (/home/bdube/lib/node-v0.10.** 10-linux-x64/lib/node_modules/cordova/node_modules/**plugman/** src/util/action-stack.js:61:25) at handleUninstall (/home/bdube/lib/node-v0.10.** 10-linux-x64/lib/node_modules/cordova/node_modules/**plugman/** src/uninstall.js:159:13) at runUninstall (/home/bdube/lib/node-v0.10.** 10-linux-x64/lib/node_modules/cordova/node_modules/**plugman/** src/uninstall.js:120:9) at Function.module.exports.uninstallPlatform (/home/bdube/lib/node-v0.10.10-linux-x64/lib/node_modules/ cordova/node_modules/plugman/src/uninstall.js:42:5) at /home/bdube/lib/node-v0.10.10-linux-x64/lib/node_modules/*** * cordova/src/plugin.js:193:51 at Array.forEach (native) at /home/bdube/lib/node-v0.10.10-linux-x64/lib/node_modules/*** * cordova/src/plugin.js:189:42
Re: w3c Working Groups
I am a member of the sys apps working group: http://www.w3.org/2012/sysapps/ Mozilla (FxOS) and samsung+intel (Tizen) lead a lot of the discussions there and IMO the work done in this group better represents cordova's interests. We used to track the DAP, though. On 8/5/13 12:02 PM, Lisa Seacat DeLuca ldel...@us.ibm.com wrote: I'm curious if anyone here is involved in any of the w3c working groups. Particularly the Device APIs Working Group. It appears to have a lot of overlap with what we are doing with Cordova: http://www.w3.org/2009/dap Lisa Seacat DeLuca Emerging Mobile Software Engineer - IBM Master Inventor SWG Emerging Internet Standards Phone: 1-410-332-2128 | Mobile: 1-415-787-4589 E-mail: ldel...@us.ibm.com personal website: lisaseacat.com http://lisaseacat.com/ Chat: ldel...@us.ibm.com Find me on: http://www.linkedin.com/in/lisaseacat https://twitter.com/IBMlisaand within IBM on: https://w3-connections.ibm.com/profiles/html/profileView.do?key=2e1afd56- daa9-428e-8f4a-2fa7516940c0 100 East Pratt St 21-2212 Baltimore, MD 21202-1009 United States
Re: CLI downloads
:o On 8/2/13 2:39 PM, Anis KADRI anis.ka...@gmail.com wrote: http://npm-stat.vorb.de/charts.html?package=cordova
Re: Posting Blog Posts
I'de like to make a proposal about how we go about publishing certain blog posts. I think this is a good practice for Organizational-type blogs to clearly identify posts which are (1) genuinely origination from the organization, vs (2) those which are just being curated from within the community. This is already widely accepted practice on many other blogs as well as on Twitter, and I think already the strategy that PhoneGap blog uses. Basically: (1) If the content has to do with cordova-core, i.e. announcing releases, or publishing guides, etc., we should publish the full text directly on the cordova Blog (by whichever author), as-if written by the organization. (2) If the content was written by a contributor and is worth curating for the whole community, but is not really core ie. non-core plugins, dev tips, research, opinion-pieces, statistics, etc., post a short description, perhaps adding a document-snippet, but then link to the externally hosted content, making it clearly not written by the organization. I think this makes it both easier to identify those posts which are really organizationally important, as well as giving us a way to post things that otherwise maybe would not have made the cut. WDYT? -Michal On Tue, Aug 6, 2013 at 10:41 AM, Andrew Grieve agri...@chromium.org wrote: Here's a draft of a how to write a blog post. I intend to add this to the website's README.md. Wanted to get some feedback / +1 since this is a process. Writting a Blog Post Blog posts live in `www/_posts`. To create a new post: 1. Copy one of the existing posts into a new file (changing the name appropriately). 2. Run rake serve in the background. 3. Draft your post. 4. Get your post reviewed by at least one other committer 1. via http://reviews.apache.org. 2. Should be able to do this by running the post-review tool. If the tool is not working, upload the diff manually (via svn diff file, and be sure to add the cordova group to the review request). 5. Update the file name to reflect the commit date (if necessary) 6. Run rake build 7. svn commit *Post guidelines:* * Use the post title as the first header. Including a header as well makes the snippet on the front page look really bad. * Use `rake serve` and refresh frequently. Jekyll does not do a good job at telling you where errors are made. * Review your post yourself before asking for a review. This includes spell-check :).
Re: Posting Blog Posts
+1 for Michals approach On Tue, Aug 6, 2013 at 1:27 PM, Michal Mocny mmo...@chromium.org wrote: I'de like to make a proposal about how we go about publishing certain blog posts. I think this is a good practice for Organizational-type blogs to clearly identify posts which are (1) genuinely origination from the organization, vs (2) those which are just being curated from within the community. This is already widely accepted practice on many other blogs as well as on Twitter, and I think already the strategy that PhoneGap blog uses. Basically: (1) If the content has to do with cordova-core, i.e. announcing releases, or publishing guides, etc., we should publish the full text directly on the cordova Blog (by whichever author), as-if written by the organization. (2) If the content was written by a contributor and is worth curating for the whole community, but is not really core ie. non-core plugins, dev tips, research, opinion-pieces, statistics, etc., post a short description, perhaps adding a document-snippet, but then link to the externally hosted content, making it clearly not written by the organization. I think this makes it both easier to identify those posts which are really organizationally important, as well as giving us a way to post things that otherwise maybe would not have made the cut. WDYT? -Michal On Tue, Aug 6, 2013 at 10:41 AM, Andrew Grieve agri...@chromium.org wrote: Here's a draft of a how to write a blog post. I intend to add this to the website's README.md. Wanted to get some feedback / +1 since this is a process. Writting a Blog Post Blog posts live in `www/_posts`. To create a new post: 1. Copy one of the existing posts into a new file (changing the name appropriately). 2. Run rake serve in the background. 3. Draft your post. 4. Get your post reviewed by at least one other committer 1. via http://reviews.apache.org. 2. Should be able to do this by running the post-review tool. If the tool is not working, upload the diff manually (via svn diff file, and be sure to add the cordova group to the review request). 5. Update the file name to reflect the commit date (if necessary) 6. Run rake build 7. svn commit *Post guidelines:* * Use the post title as the first header. Including a header as well makes the snippet on the front page look really bad. * Use `rake serve` and refresh frequently. Jekyll does not do a good job at telling you where errors are made. * Review your post yourself before asking for a review. This includes spell-check :).
Re: Posting Blog Posts
+1. That's a good approach to separating them, and should encourage third-party authors to submit pieces -- knowing that Apache will drive traffic to their site. On Tue, Aug 6, 2013 at 1:35 PM, David Kemp drk...@google.com wrote: +1 for Michals approach On Tue, Aug 6, 2013 at 1:27 PM, Michal Mocny mmo...@chromium.org wrote: I'de like to make a proposal about how we go about publishing certain blog posts. I think this is a good practice for Organizational-type blogs to clearly identify posts which are (1) genuinely origination from the organization, vs (2) those which are just being curated from within the community. This is already widely accepted practice on many other blogs as well as on Twitter, and I think already the strategy that PhoneGap blog uses. Basically: (1) If the content has to do with cordova-core, i.e. announcing releases, or publishing guides, etc., we should publish the full text directly on the cordova Blog (by whichever author), as-if written by the organization. (2) If the content was written by a contributor and is worth curating for the whole community, but is not really core ie. non-core plugins, dev tips, research, opinion-pieces, statistics, etc., post a short description, perhaps adding a document-snippet, but then link to the externally hosted content, making it clearly not written by the organization. I think this makes it both easier to identify those posts which are really organizationally important, as well as giving us a way to post things that otherwise maybe would not have made the cut. WDYT? -Michal On Tue, Aug 6, 2013 at 10:41 AM, Andrew Grieve agri...@chromium.org wrote: Here's a draft of a how to write a blog post. I intend to add this to the website's README.md. Wanted to get some feedback / +1 since this is a process. Writting a Blog Post Blog posts live in `www/_posts`. To create a new post: 1. Copy one of the existing posts into a new file (changing the name appropriately). 2. Run rake serve in the background. 3. Draft your post. 4. Get your post reviewed by at least one other committer 1. via http://reviews.apache.org. 2. Should be able to do this by running the post-review tool. If the tool is not working, upload the diff manually (via svn diff file, and be sure to add the cordova group to the review request). 5. Update the file name to reflect the commit date (if necessary) 6. Run rake build 7. svn commit *Post guidelines:* * Use the post title as the first header. Including a header as well makes the snippet on the front page look really bad. * Use `rake serve` and refresh frequently. Jekyll does not do a good job at telling you where errors are made. * Review your post yourself before asking for a review. This includes spell-check :).
Re: Posting Blog Posts
+1 from me as well. I like the idea of official posts looking official as well as the side effect of third party posts getting the traffic benefits. - tommy On 7 Aug 2013 03:44, Ian Clelland iclell...@chromium.org wrote: +1. That's a good approach to separating them, and should encourage third-party authors to submit pieces -- knowing that Apache will drive traffic to their site. On Tue, Aug 6, 2013 at 1:35 PM, David Kemp drk...@google.com wrote: +1 for Michals approach On Tue, Aug 6, 2013 at 1:27 PM, Michal Mocny mmo...@chromium.org wrote: I'de like to make a proposal about how we go about publishing certain blog posts. I think this is a good practice for Organizational-type blogs to clearly identify posts which are (1) genuinely origination from the organization, vs (2) those which are just being curated from within the community. This is already widely accepted practice on many other blogs as well as on Twitter, and I think already the strategy that PhoneGap blog uses. Basically: (1) If the content has to do with cordova-core, i.e. announcing releases, or publishing guides, etc., we should publish the full text directly on the cordova Blog (by whichever author), as-if written by the organization. (2) If the content was written by a contributor and is worth curating for the whole community, but is not really core ie. non-core plugins, dev tips, research, opinion-pieces, statistics, etc., post a short description, perhaps adding a document-snippet, but then link to the externally hosted content, making it clearly not written by the organization. I think this makes it both easier to identify those posts which are really organizationally important, as well as giving us a way to post things that otherwise maybe would not have made the cut. WDYT? -Michal On Tue, Aug 6, 2013 at 10:41 AM, Andrew Grieve agri...@chromium.org wrote: Here's a draft of a how to write a blog post. I intend to add this to the website's README.md. Wanted to get some feedback / +1 since this is a process. Writting a Blog Post Blog posts live in `www/_posts`. To create a new post: 1. Copy one of the existing posts into a new file (changing the name appropriately). 2. Run rake serve in the background. 3. Draft your post. 4. Get your post reviewed by at least one other committer 1. via http://reviews.apache.org. 2. Should be able to do this by running the post-review tool. If the tool is not working, upload the diff manually (via svn diff file, and be sure to add the cordova group to the review request). 5. Update the file name to reflect the commit date (if necessary) 6. Run rake build 7. svn commit *Post guidelines:* * Use the post title as the first header. Including a header as well makes the snippet on the front page look really bad. * Use `rake serve` and refresh frequently. Jekyll does not do a good job at telling you where errors are made. * Review your post yourself before asking for a review. This includes spell-check :).
Re: Posting Blog Posts
+1 Sent from my BlackBerry® wireless device -Original Message- From: Tommy Williams to...@devgeeks.org Date: Tue, 6 Aug 2013 10:46:15 To: dev@cordova.apache.org Reply-To: dev@cordova.apache.org Subject: Re: Posting Blog Posts +1 from me as well. I like the idea of official posts looking official as well as the side effect of third party posts getting the traffic benefits. - tommy On 7 Aug 2013 03:44, Ian Clelland iclell...@chromium.org wrote: +1. That's a good approach to separating them, and should encourage third-party authors to submit pieces -- knowing that Apache will drive traffic to their site. On Tue, Aug 6, 2013 at 1:35 PM, David Kemp drk...@google.com wrote: +1 for Michals approach On Tue, Aug 6, 2013 at 1:27 PM, Michal Mocny mmo...@chromium.org wrote: I'de like to make a proposal about how we go about publishing certain blog posts. I think this is a good practice for Organizational-type blogs to clearly identify posts which are (1) genuinely origination from the organization, vs (2) those which are just being curated from within the community. This is already widely accepted practice on many other blogs as well as on Twitter, and I think already the strategy that PhoneGap blog uses. Basically: (1) If the content has to do with cordova-core, i.e. announcing releases, or publishing guides, etc., we should publish the full text directly on the cordova Blog (by whichever author), as-if written by the organization. (2) If the content was written by a contributor and is worth curating for the whole community, but is not really core ie. non-core plugins, dev tips, research, opinion-pieces, statistics, etc., post a short description, perhaps adding a document-snippet, but then link to the externally hosted content, making it clearly not written by the organization. I think this makes it both easier to identify those posts which are really organizationally important, as well as giving us a way to post things that otherwise maybe would not have made the cut. WDYT? -Michal On Tue, Aug 6, 2013 at 10:41 AM, Andrew Grieve agri...@chromium.org wrote: Here's a draft of a how to write a blog post. I intend to add this to the website's README.md. Wanted to get some feedback / +1 since this is a process. Writting a Blog Post Blog posts live in `www/_posts`. To create a new post: 1. Copy one of the existing posts into a new file (changing the name appropriately). 2. Run rake serve in the background. 3. Draft your post. 4. Get your post reviewed by at least one other committer 1. via http://reviews.apache.org. 2. Should be able to do this by running the post-review tool. If the tool is not working, upload the diff manually (via svn diff file, and be sure to add the cordova group to the review request). 5. Update the file name to reflect the commit date (if necessary) 6. Run rake build 7. svn commit *Post guidelines:* * Use the post title as the first header. Including a header as well makes the snippet on the front page look really bad. * Use `rake serve` and refresh frequently. Jekyll does not do a good job at telling you where errors are made. * Review your post yourself before asking for a review. This includes spell-check :).
Re: Posting Blog Posts
Will this mean we will be discussing blog post curation stuff on dev@cordova.apache.org ? On 8/6/13 10:46 AM, Tommy Williams to...@devgeeks.org wrote: +1 from me as well. I like the idea of official posts looking official as well as the side effect of third party posts getting the traffic benefits. - tommy On 7 Aug 2013 03:44, Ian Clelland iclell...@chromium.org wrote: +1. That's a good approach to separating them, and should encourage third-party authors to submit pieces -- knowing that Apache will drive traffic to their site. On Tue, Aug 6, 2013 at 1:35 PM, David Kemp drk...@google.com wrote: +1 for Michals approach On Tue, Aug 6, 2013 at 1:27 PM, Michal Mocny mmo...@chromium.org wrote: I'de like to make a proposal about how we go about publishing certain blog posts. I think this is a good practice for Organizational-type blogs to clearly identify posts which are (1) genuinely origination from the organization, vs (2) those which are just being curated from within the community. This is already widely accepted practice on many other blogs as well as on Twitter, and I think already the strategy that PhoneGap blog uses. Basically: (1) If the content has to do with cordova-core, i.e. announcing releases, or publishing guides, etc., we should publish the full text directly on the cordova Blog (by whichever author), as-if written by the organization. (2) If the content was written by a contributor and is worth curating for the whole community, but is not really core ie. non-core plugins, dev tips, research, opinion-pieces, statistics, etc., post a short description, perhaps adding a document-snippet, but then link to the externally hosted content, making it clearly not written by the organization. I think this makes it both easier to identify those posts which are really organizationally important, as well as giving us a way to post things that otherwise maybe would not have made the cut. WDYT? -Michal On Tue, Aug 6, 2013 at 10:41 AM, Andrew Grieve agri...@chromium.org wrote: Here's a draft of a how to write a blog post. I intend to add this to the website's README.md. Wanted to get some feedback / +1 since this is a process. Writting a Blog Post Blog posts live in `www/_posts`. To create a new post: 1. Copy one of the existing posts into a new file (changing the name appropriately). 2. Run rake serve in the background. 3. Draft your post. 4. Get your post reviewed by at least one other committer 1. via http://reviews.apache.org. 2. Should be able to do this by running the post-review tool. If the tool is not working, upload the diff manually (via svn diff file, and be sure to add the cordova group to the review request). 5. Update the file name to reflect the commit date (if necessary) 6. Run rake build 7. svn commit *Post guidelines:* * Use the post title as the first header. Including a header as well makes the snippet on the front page look really bad. * Use `rake serve` and refresh frequently. Jekyll does not do a good job at telling you where errors are made. * Review your post yourself before asking for a review. This includes spell-check :).
Re: Posting Blog Posts
+1 as well. I plan to write some posts on BlackBerry and Cordova and a method to link would be great. Sent from my BlackBerry 10 smartphone on the Bell network. From: dguald...@gmail.com Sent: Tuesday, August 6, 2013 1:48 PM To: dev@cordova.apache.org Reply To: dev@cordova.apache.org Subject: Re: Posting Blog Posts +1 Sent from my BlackBerry® wireless device -Original Message- From: Tommy Williams to...@devgeeks.org Date: Tue, 6 Aug 2013 10:46:15 To: dev@cordova.apache.org Reply-To: dev@cordova.apache.org Subject: Re: Posting Blog Posts +1 from me as well. I like the idea of official posts looking official as well as the side effect of third party posts getting the traffic benefits. - tommy On 7 Aug 2013 03:44, Ian Clelland iclell...@chromium.org wrote: +1. That's a good approach to separating them, and should encourage third-party authors to submit pieces -- knowing that Apache will drive traffic to their site. On Tue, Aug 6, 2013 at 1:35 PM, David Kemp drk...@google.com wrote: +1 for Michals approach On Tue, Aug 6, 2013 at 1:27 PM, Michal Mocny mmo...@chromium.org wrote: I'de like to make a proposal about how we go about publishing certain blog posts. I think this is a good practice for Organizational-type blogs to clearly identify posts which are (1) genuinely origination from the organization, vs (2) those which are just being curated from within the community. This is already widely accepted practice on many other blogs as well as on Twitter, and I think already the strategy that PhoneGap blog uses. Basically: (1) If the content has to do with cordova-core, i.e. announcing releases, or publishing guides, etc., we should publish the full text directly on the cordova Blog (by whichever author), as-if written by the organization. (2) If the content was written by a contributor and is worth curating for the whole community, but is not really core ie. non-core plugins, dev tips, research, opinion-pieces, statistics, etc., post a short description, perhaps adding a document-snippet, but then link to the externally hosted content, making it clearly not written by the organization. I think this makes it both easier to identify those posts which are really organizationally important, as well as giving us a way to post things that otherwise maybe would not have made the cut. WDYT? -Michal On Tue, Aug 6, 2013 at 10:41 AM, Andrew Grieve agri...@chromium.org wrote: Here's a draft of a how to write a blog post. I intend to add this to the website's README.md. Wanted to get some feedback / +1 since this is a process. Writting a Blog Post Blog posts live in `www/_posts`. To create a new post: 1. Copy one of the existing posts into a new file (changing the name appropriately). 2. Run rake serve in the background. 3. Draft your post. 4. Get your post reviewed by at least one other committer 1. via http://reviews.apache.org. 2. Should be able to do this by running the post-review tool. If the tool is not working, upload the diff manually (via svn diff file, and be sure to add the cordova group to the review request). 5. Update the file name to reflect the commit date (if necessary) 6. Run rake build 7. svn commit *Post guidelines:* * Use the post title as the first header. Including a header as well makes the snippet on the front page look really bad. * Use `rake serve` and refresh frequently. Jekyll does not do a good job at telling you where errors are made. * Review your post yourself before asking for a review. This includes spell-check :). - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
Re: Posting Blog Posts
On Tue, Aug 6, 2013 at 2:01 PM, Filip Maj f...@adobe.com wrote: Will this mean we will be discussing blog post curation stuff on dev@cordova.apache.org ? I hope that we can avoid a lot of that -- I'd hate for every potential external contribution to come down to a discussion and vote on the mailing list. It might be good to have one person in charge of that section of the site -- someone responsible whom authors could email for exposure on the Cordova home page. If that's not possible, then I would suggest that anyone who currently has access to update the blog would also be able to publish external postings. If any problems arise, we can deal with them at the time. Obviously if someone has a concern before publishing (is this legit?, is this spam disguised as a blog post?), then they could certainly run it past the mailing list, but it shouldn't be a requirement most of the time. Ian
Re: Posting Blog Posts
I like Ians suggestion. I'm happy to trust that contributors know what constitutes good/bad content and what is/isn't worth sharing, and that we can go to the lists for the few times where confirmation is needed. Fil, that okay with you? Another question, though: should we have templates for these types of posts? -Michal On Tue, Aug 6, 2013 at 2:48 PM, Ian Clelland iclell...@chromium.org wrote: On Tue, Aug 6, 2013 at 2:01 PM, Filip Maj f...@adobe.com wrote: Will this mean we will be discussing blog post curation stuff on dev@cordova.apache.org ? I hope that we can avoid a lot of that -- I'd hate for every potential external contribution to come down to a discussion and vote on the mailing list. It might be good to have one person in charge of that section of the site -- someone responsible whom authors could email for exposure on the Cordova home page. If that's not possible, then I would suggest that anyone who currently has access to update the blog would also be able to publish external postings. If any problems arise, we can deal with them at the time. Obviously if someone has a concern before publishing (is this legit?, is this spam disguised as a blog post?), then they could certainly run it past the mailing list, but it shouldn't be a requirement most of the time. Ian
Re: Post 3.0 release committer and community meeting
Want to get the ball rolling on this. Please fill out this doodle so we can pick a day: http://www.doodle.com/i4u89n2k52yne4zt AFAIK, the *best* timezone-friendly time is 4:30PM PST How to meet? - Hangouts have a max 10 person limit, but I've found that VC meetings get a bit unwieldy anyways when there are more than 10 sites. I'm hoping that co-located people can share computers so that we can keep the number of connections down. Attendees: If you plan to attend, could you add your name to this list (inline so that the list grows) and say whether you plan to be co-located: agrieve, co-location=Google Waterloo Agenda (feel free to add items inline): - release artifacts and process redux - Should platform releases still be coupled? - Does semver make more sense to us now that components are more decoupled? - Deprecation policy improvements? - Can we use cordova-registry to allow older versions of things when APIs are removed? - Can we have our plugin API surface versioned separately from our component versions? - Shortterm plans for Medic - Buildbot? - Should mobile-spec autotests be pulled out? - 4.0 goals, timeline, and priorities - Platforms as build artifacts - Is this our goal? what's big hurdles remain? - Apps Plugins to have the same feature set (dependencies, merges/, etc) On Wed, Jul 17, 2013 at 9:47 AM, Andrew Grieve agri...@chromium.org wrote: That week's good for me! On Tue, Jul 16, 2013 at 3:59 AM, Ally Ogilvie aogil...@wizcorp.jp wrote: Sensible timezone for Asia/Aus please :) On Tue, Jul 16, 2013 at 4:22 PM, Filip Maj f...@adobe.com wrote: Sounds good On 7/16/13 12:10 AM, David Pfahler da...@excellenteasy.com wrote: Count me in for the hangouts etc. On Tue, Jul 16, 2013 at 12:22 AM, Ken Wallis kwal...@blackberry.com wrote: Definitely a good idea. Sent from my BlackBerry 10 smartphone. From: Brian LeRoux Sent: Monday, July 15, 2013 5:45 PM To: dev@cordova.apache.org Reply To: dev@cordova.apache.org Subject: Post 3.0 release committer and community meeting Hey everyone, we're in the final stretch to releasing 3.0 and I think long past due to have an open discussion w/ the committership and larger community. I think we should let the dust settle from 3.0 for a couple of weeks before having this meeting. I'd like to propose the week of August 12th. If that all sounds good, we could setup a Google Hangout, and get an agenda started: - release artifacts and process redux - 4.0 goals, timeline, and priorities Comments pls! - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. -- http://www.wizcorp.jp/Ally Ogilvie Lead Developer - MobDev. | Wizcorp Inc. http://www.wizcorp.jp/ -- TECH . GAMING . OPEN-SOURCE WIZARDS+ 81 (0)3-4550-1448 | Websitehttp://www.wizcorp.jp/ | Twitter https://twitter.com/Wizcorp | Facebookhttp://www.facebook.com/Wizcorp | LinkedIn http://www.linkedin.com/company/wizcorp
Re: Post 3.0 release committer and community meeting
We'll need 2 locations for the Cordova team at Adobe: Attendees: If you plan to attend, could you add your name to this list (inline so that the list grows) and say whether you plan to be co-located: agrieve, co-location=Google Waterloo aharding, co-location=Adobe Vancouver stevegill, co-location=Adobe San Francisco On Tue, Aug 6, 2013 at 12:33 PM, Andrew Grieve agri...@chromium.org wrote: Want to get the ball rolling on this. Please fill out this doodle so we can pick a day: http://www.doodle.com/i4u89n2k52yne4zt AFAIK, the *best* timezone-friendly time is 4:30PM PST How to meet? - Hangouts have a max 10 person limit, but I've found that VC meetings get a bit unwieldy anyways when there are more than 10 sites. I'm hoping that co-located people can share computers so that we can keep the number of connections down. Attendees: If you plan to attend, could you add your name to this list (inline so that the list grows) and say whether you plan to be co-located: agrieve, co-location=Google Waterloo Agenda (feel free to add items inline): - release artifacts and process redux - Should platform releases still be coupled? - Does semver make more sense to us now that components are more decoupled? - Deprecation policy improvements? - Can we use cordova-registry to allow older versions of things when APIs are removed? - Can we have our plugin API surface versioned separately from our component versions? - Shortterm plans for Medic - Buildbot? - Should mobile-spec autotests be pulled out? - 4.0 goals, timeline, and priorities - Platforms as build artifacts - Is this our goal? what's big hurdles remain? - Apps Plugins to have the same feature set (dependencies, merges/, etc) On Wed, Jul 17, 2013 at 9:47 AM, Andrew Grieve agri...@chromium.org wrote: That week's good for me! On Tue, Jul 16, 2013 at 3:59 AM, Ally Ogilvie aogil...@wizcorp.jp wrote: Sensible timezone for Asia/Aus please :) On Tue, Jul 16, 2013 at 4:22 PM, Filip Maj f...@adobe.com wrote: Sounds good On 7/16/13 12:10 AM, David Pfahler da...@excellenteasy.com wrote: Count me in for the hangouts etc. On Tue, Jul 16, 2013 at 12:22 AM, Ken Wallis kwal...@blackberry.com wrote: Definitely a good idea. Sent from my BlackBerry 10 smartphone. From: Brian LeRoux Sent: Monday, July 15, 2013 5:45 PM To: dev@cordova.apache.org Reply To: dev@cordova.apache.org Subject: Post 3.0 release committer and community meeting Hey everyone, we're in the final stretch to releasing 3.0 and I think long past due to have an open discussion w/ the committership and larger community. I think we should let the dust settle from 3.0 for a couple of weeks before having this meeting. I'd like to propose the week of August 12th. If that all sounds good, we could setup a Google Hangout, and get an agenda started: - release artifacts and process redux - 4.0 goals, timeline, and priorities Comments pls! - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. -- http://www.wizcorp.jp/Ally Ogilvie Lead Developer - MobDev. | Wizcorp Inc. http://www.wizcorp.jp/ -- TECH . GAMING . OPEN-SOURCE WIZARDS+ 81 (0)3-4550-1448 | Websitehttp://www.wizcorp.jp/ | Twitter https://twitter.com/Wizcorp | Facebookhttp://www.facebook.com/Wizcorp | LinkedIn http://www.linkedin.com/company/wizcorp
Re: Post 3.0 release committer and community meeting
On Tue, Aug 6, 2013 at 3:33 PM, Andrew Grieve agri...@chromium.org wrote: Want to get the ball rolling on this. Please fill out this doodle so we can pick a day: http://www.doodle.com/i4u89n2k52yne4zt AFAIK, the *best* timezone-friendly time is 4:30PM PST How to meet? - Hangouts have a max 10 person limit, but I've found that VC meetings get a bit unwieldy anyways when there are more than 10 sites. I'm hoping that co-located people can share computers so that we can keep the number of connections down. Suggestion: Hangouts on air appears to have the same 10 people limit, yet allows viewing-only for very many people via youtube. Suggest we only allow contributors to join the hangouts via invite, and publish the link for live viewing if anyone is interested. I think this also enable us to record and share the video and other such cool benefits. Attendees: If you plan to attend, could you add your name to this list (inline so that the list grows) and say whether you plan to be co-located: agrieve, co-location=Google Waterloo mmocny, co-location=Google Waterloo Agenda (feel free to add items inline): - release artifacts and process redux - Should platform releases still be coupled? - Does semver make more sense to us now that components are more decoupled? - Deprecation policy improvements? - Can we use cordova-registry to allow older versions of things when APIs are removed? - Can we have our plugin API surface versioned separately from our component versions? - Shortterm plans for Medic - Buildbot? - Should mobile-spec autotests be pulled out? - 4.0 goals, timeline, and priorities - Platforms as build artifacts - Is this our goal? what's big hurdles remain? - Apps Plugins to have the same feature set (dependencies, merges/, etc) On Wed, Jul 17, 2013 at 9:47 AM, Andrew Grieve agri...@chromium.org wrote: That week's good for me! On Tue, Jul 16, 2013 at 3:59 AM, Ally Ogilvie aogil...@wizcorp.jp wrote: Sensible timezone for Asia/Aus please :) On Tue, Jul 16, 2013 at 4:22 PM, Filip Maj f...@adobe.com wrote: Sounds good On 7/16/13 12:10 AM, David Pfahler da...@excellenteasy.com wrote: Count me in for the hangouts etc. On Tue, Jul 16, 2013 at 12:22 AM, Ken Wallis kwal...@blackberry.com wrote: Definitely a good idea. Sent from my BlackBerry 10 smartphone. From: Brian LeRoux Sent: Monday, July 15, 2013 5:45 PM To: dev@cordova.apache.org Reply To: dev@cordova.apache.org Subject: Post 3.0 release committer and community meeting Hey everyone, we're in the final stretch to releasing 3.0 and I think long past due to have an open discussion w/ the committership and larger community. I think we should let the dust settle from 3.0 for a couple of weeks before having this meeting. I'd like to propose the week of August 12th. If that all sounds good, we could setup a Google Hangout, and get an agenda started: - release artifacts and process redux - 4.0 goals, timeline, and priorities Comments pls! - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. -- http://www.wizcorp.jp/Ally Ogilvie Lead Developer - MobDev. | Wizcorp Inc. http://www.wizcorp.jp/ -- TECH . GAMING . OPEN-SOURCE WIZARDS+ 81 (0)3-4550-1448 | Websitehttp://www.wizcorp.jp/ | Twitter https://twitter.com/Wizcorp | Facebookhttp://www.facebook.com/Wizcorp | LinkedIn http://www.linkedin.com/company/wizcorp
Re: Post 3.0 release committer and community meeting
Added my name + location inline below On 8/6/13 12:33 PM, Andrew Grieve agri...@chromium.org wrote: Want to get the ball rolling on this. Please fill out this doodle so we can pick a day: http://www.doodle.com/i4u89n2k52yne4zt AFAIK, the *best* timezone-friendly time is 4:30PM PST How to meet? - Hangouts have a max 10 person limit, but I've found that VC meetings get a bit unwieldy anyways when there are more than 10 sites. I'm hoping that co-located people can share computers so that we can keep the number of connections down. Attendees: If you plan to attend, could you add your name to this list (inline so that the list grows) and say whether you plan to be co-located: agrieve, co-location=Google Waterloo filmaj, co-location=Adobe Vancouver Agenda (feel free to add items inline): - release artifacts and process redux - Should platform releases still be coupled? - Does semver make more sense to us now that components are more decoupled? - Deprecation policy improvements? - Can we use cordova-registry to allow older versions of things when APIs are removed? - Can we have our plugin API surface versioned separately from our component versions? - Shortterm plans for Medic - Buildbot? - Should mobile-spec autotests be pulled out? - 4.0 goals, timeline, and priorities - Platforms as build artifacts - Is this our goal? what's big hurdles remain? - Apps Plugins to have the same feature set (dependencies, merges/, etc) On Wed, Jul 17, 2013 at 9:47 AM, Andrew Grieve agri...@chromium.org wrote: That week's good for me! On Tue, Jul 16, 2013 at 3:59 AM, Ally Ogilvie aogil...@wizcorp.jp wrote: Sensible timezone for Asia/Aus please :) On Tue, Jul 16, 2013 at 4:22 PM, Filip Maj f...@adobe.com wrote: Sounds good On 7/16/13 12:10 AM, David Pfahler da...@excellenteasy.com wrote: Count me in for the hangouts etc. On Tue, Jul 16, 2013 at 12:22 AM, Ken Wallis kwal...@blackberry.com wrote: Definitely a good idea. Sent from my BlackBerry 10 smartphone. From: Brian LeRoux Sent: Monday, July 15, 2013 5:45 PM To: dev@cordova.apache.org Reply To: dev@cordova.apache.org Subject: Post 3.0 release committer and community meeting Hey everyone, we're in the final stretch to releasing 3.0 and I think long past due to have an open discussion w/ the committership and larger community. I think we should let the dust settle from 3.0 for a couple of weeks before having this meeting. I'd like to propose the week of August 12th. If that all sounds good, we could setup a Google Hangout, and get an agenda started: - release artifacts and process redux - 4.0 goals, timeline, and priorities Comments pls! - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. -- http://www.wizcorp.jp/Ally Ogilvie Lead Developer - MobDev. | Wizcorp Inc. http://www.wizcorp.jp/ -- TECH . GAMING . OPEN-SOURCE WIZARDS+ 81 (0)3-4550-1448 | Websitehttp://www.wizcorp.jp/ | Twitter https://twitter.com/Wizcorp | Facebookhttp://www.facebook.com/Wizcorp | LinkedIn http://www.linkedin.com/company/wizcorp
Re: Posting Blog Posts
SGTM On 8/6/13 11:57 AM, Michal Mocny mmo...@chromium.org wrote: I like Ians suggestion. I'm happy to trust that contributors know what constitutes good/bad content and what is/isn't worth sharing, and that we can go to the lists for the few times where confirmation is needed. Fil, that okay with you? Another question, though: should we have templates for these types of posts? -Michal On Tue, Aug 6, 2013 at 2:48 PM, Ian Clelland iclell...@chromium.org wrote: On Tue, Aug 6, 2013 at 2:01 PM, Filip Maj f...@adobe.com wrote: Will this mean we will be discussing blog post curation stuff on dev@cordova.apache.org ? I hope that we can avoid a lot of that -- I'd hate for every potential external contribution to come down to a discussion and vote on the mailing list. It might be good to have one person in charge of that section of the site -- someone responsible whom authors could email for exposure on the Cordova home page. If that's not possible, then I would suggest that anyone who currently has access to update the blog would also be able to publish external postings. If any problems arise, we can deal with them at the time. Obviously if someone has a concern before publishing (is this legit?, is this spam disguised as a blog post?), then they could certainly run it past the mailing list, but it shouldn't be a requirement most of the time. Ian
Re: Post 3.0 release committer and community meeting
If we're planning on attending from a community standpoint, but aren't planning on talking, is there going to be an easy way to do that or do we need to add our names to the list? And I'm assuming this is open to non-committers based on the subject, but correct me if that's wrong. =Ryan On 8/6/13 12:48 PM, Al Harding alharding...@gmail.com wrote: We'll need 2 locations for the Cordova team at Adobe: Attendees: If you plan to attend, could you add your name to this list (inline so that the list grows) and say whether you plan to be co-located: agrieve, co-location=Google Waterloo aharding, co-location=Adobe Vancouver stevegill, co-location=Adobe San Francisco On Tue, Aug 6, 2013 at 12:33 PM, Andrew Grieve agri...@chromium.org wrote: Want to get the ball rolling on this. Please fill out this doodle so we can pick a day: http://www.doodle.com/i4u89n2k52yne4zt AFAIK, the *best* timezone-friendly time is 4:30PM PST How to meet? - Hangouts have a max 10 person limit, but I've found that VC meetings get a bit unwieldy anyways when there are more than 10 sites. I'm hoping that co-located people can share computers so that we can keep the number of connections down. Attendees: If you plan to attend, could you add your name to this list (inline so that the list grows) and say whether you plan to be co-located: agrieve, co-location=Google Waterloo Agenda (feel free to add items inline): - release artifacts and process redux - Should platform releases still be coupled? - Does semver make more sense to us now that components are more decoupled? - Deprecation policy improvements? - Can we use cordova-registry to allow older versions of things when APIs are removed? - Can we have our plugin API surface versioned separately from our component versions? - Shortterm plans for Medic - Buildbot? - Should mobile-spec autotests be pulled out? - 4.0 goals, timeline, and priorities - Platforms as build artifacts - Is this our goal? what's big hurdles remain? - Apps Plugins to have the same feature set (dependencies, merges/, etc) On Wed, Jul 17, 2013 at 9:47 AM, Andrew Grieve agri...@chromium.org wrote: That week's good for me! On Tue, Jul 16, 2013 at 3:59 AM, Ally Ogilvie aogil...@wizcorp.jp wrote: Sensible timezone for Asia/Aus please :) On Tue, Jul 16, 2013 at 4:22 PM, Filip Maj f...@adobe.com wrote: Sounds good On 7/16/13 12:10 AM, David Pfahler da...@excellenteasy.com wrote: Count me in for the hangouts etc. On Tue, Jul 16, 2013 at 12:22 AM, Ken Wallis kwal...@blackberry.com wrote: Definitely a good idea. Sent from my BlackBerry 10 smartphone. From: Brian LeRoux Sent: Monday, July 15, 2013 5:45 PM To: dev@cordova.apache.org Reply To: dev@cordova.apache.org Subject: Post 3.0 release committer and community meeting Hey everyone, we're in the final stretch to releasing 3.0 and I think long past due to have an open discussion w/ the committership and larger community. I think we should let the dust settle from 3.0 for a couple of weeks before having this meeting. I'd like to propose the week of August 12th. If that all sounds good, we could setup a Google Hangout, and get an agenda started: - release artifacts and process redux - 4.0 goals, timeline, and priorities Comments pls! - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. -- http://www.wizcorp.jp/Ally Ogilvie Lead Developer - MobDev. | Wizcorp Inc. http://www.wizcorp.jp/ -- TECH . GAMING . OPEN-SOURCE WIZARDS+ 81 (0)3-4550-1448 | Websitehttp://www.wizcorp.jp/ | Twitter https://twitter.com/Wizcorp | Facebookhttp://www.facebook.com/Wizcorp | LinkedIn http://www.linkedin.com/company/wizcorp
Re: Post 3.0 release committer and community meeting
agrieve, co-location=Google Waterloo mmocny, co-location=Google Waterloo maxw, co-location=Google Waterloo aharding, co-location=Adobe Vancouver filmaj, co-location=Adobe Vancouver stevegill, co-location=Adobe San Francisco On Tue, Aug 6, 2013 at 3:50 PM, Filip Maj f...@adobe.com wrote: Added my name + location inline below On 8/6/13 12:33 PM, Andrew Grieve agri...@chromium.org wrote: Want to get the ball rolling on this. Please fill out this doodle so we can pick a day: http://www.doodle.com/i4u89n2k52yne4zt AFAIK, the *best* timezone-friendly time is 4:30PM PST How to meet? - Hangouts have a max 10 person limit, but I've found that VC meetings get a bit unwieldy anyways when there are more than 10 sites. I'm hoping that co-located people can share computers so that we can keep the number of connections down. Attendees: If you plan to attend, could you add your name to this list (inline so that the list grows) and say whether you plan to be co-located: agrieve, co-location=Google Waterloo filmaj, co-location=Adobe Vancouver Agenda (feel free to add items inline): - release artifacts and process redux - Should platform releases still be coupled? - Does semver make more sense to us now that components are more decoupled? - Deprecation policy improvements? - Can we use cordova-registry to allow older versions of things when APIs are removed? - Can we have our plugin API surface versioned separately from our component versions? - Shortterm plans for Medic - Buildbot? - Should mobile-spec autotests be pulled out? - 4.0 goals, timeline, and priorities - Platforms as build artifacts - Is this our goal? what's big hurdles remain? - Apps Plugins to have the same feature set (dependencies, merges/, etc) On Wed, Jul 17, 2013 at 9:47 AM, Andrew Grieve agri...@chromium.org wrote: That week's good for me! On Tue, Jul 16, 2013 at 3:59 AM, Ally Ogilvie aogil...@wizcorp.jp wrote: Sensible timezone for Asia/Aus please :) On Tue, Jul 16, 2013 at 4:22 PM, Filip Maj f...@adobe.com wrote: Sounds good On 7/16/13 12:10 AM, David Pfahler da...@excellenteasy.com wrote: Count me in for the hangouts etc. On Tue, Jul 16, 2013 at 12:22 AM, Ken Wallis kwal...@blackberry.com wrote: Definitely a good idea. Sent from my BlackBerry 10 smartphone. From: Brian LeRoux Sent: Monday, July 15, 2013 5:45 PM To: dev@cordova.apache.org Reply To: dev@cordova.apache.org Subject: Post 3.0 release committer and community meeting Hey everyone, we're in the final stretch to releasing 3.0 and I think long past due to have an open discussion w/ the committership and larger community. I think we should let the dust settle from 3.0 for a couple of weeks before having this meeting. I'd like to propose the week of August 12th. If that all sounds good, we could setup a Google Hangout, and get an agenda started: - release artifacts and process redux - 4.0 goals, timeline, and priorities Comments pls! - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. -- http://www.wizcorp.jp/Ally Ogilvie Lead Developer - MobDev. | Wizcorp Inc. http://www.wizcorp.jp/ -- TECH . GAMING . OPEN-SOURCE WIZARDS+ 81 (0)3-4550-1448 | Websitehttp://www.wizcorp.jp/ | Twitter https://twitter.com/Wizcorp | Facebookhttp://www.facebook.com/Wizcorp | LinkedIn http://www.linkedin.com/company/wizcorp
Re: Post 3.0 release committer and community meeting
Ryan come up to the Vancouver office? On Tue, Aug 6, 2013 at 12:51 PM, Ryan Stewart rstew...@adobe.com wrote: If we're planning on attending from a community standpoint, but aren't planning on talking, is there going to be an easy way to do that or do we need to add our names to the list? And I'm assuming this is open to non-committers based on the subject, but correct me if that's wrong. =Ryan On 8/6/13 12:48 PM, Al Harding alharding...@gmail.com wrote: We'll need 2 locations for the Cordova team at Adobe: Attendees: If you plan to attend, could you add your name to this list (inline so that the list grows) and say whether you plan to be co-located: agrieve, co-location=Google Waterloo aharding, co-location=Adobe Vancouver stevegill, co-location=Adobe San Francisco On Tue, Aug 6, 2013 at 12:33 PM, Andrew Grieve agri...@chromium.org wrote: Want to get the ball rolling on this. Please fill out this doodle so we can pick a day: http://www.doodle.com/i4u89n2k52yne4zt AFAIK, the *best* timezone-friendly time is 4:30PM PST How to meet? - Hangouts have a max 10 person limit, but I've found that VC meetings get a bit unwieldy anyways when there are more than 10 sites. I'm hoping that co-located people can share computers so that we can keep the number of connections down. Attendees: If you plan to attend, could you add your name to this list (inline so that the list grows) and say whether you plan to be co-located: agrieve, co-location=Google Waterloo Agenda (feel free to add items inline): - release artifacts and process redux - Should platform releases still be coupled? - Does semver make more sense to us now that components are more decoupled? - Deprecation policy improvements? - Can we use cordova-registry to allow older versions of things when APIs are removed? - Can we have our plugin API surface versioned separately from our component versions? - Shortterm plans for Medic - Buildbot? - Should mobile-spec autotests be pulled out? - 4.0 goals, timeline, and priorities - Platforms as build artifacts - Is this our goal? what's big hurdles remain? - Apps Plugins to have the same feature set (dependencies, merges/, etc) On Wed, Jul 17, 2013 at 9:47 AM, Andrew Grieve agri...@chromium.org wrote: That week's good for me! On Tue, Jul 16, 2013 at 3:59 AM, Ally Ogilvie aogil...@wizcorp.jp wrote: Sensible timezone for Asia/Aus please :) On Tue, Jul 16, 2013 at 4:22 PM, Filip Maj f...@adobe.com wrote: Sounds good On 7/16/13 12:10 AM, David Pfahler da...@excellenteasy.com wrote: Count me in for the hangouts etc. On Tue, Jul 16, 2013 at 12:22 AM, Ken Wallis kwal...@blackberry.com wrote: Definitely a good idea. Sent from my BlackBerry 10 smartphone. From: Brian LeRoux Sent: Monday, July 15, 2013 5:45 PM To: dev@cordova.apache.org Reply To: dev@cordova.apache.org Subject: Post 3.0 release committer and community meeting Hey everyone, we're in the final stretch to releasing 3.0 and I think long past due to have an open discussion w/ the committership and larger community. I think we should let the dust settle from 3.0 for a couple of weeks before having this meeting. I'd like to propose the week of August 12th. If that all sounds good, we could setup a Google Hangout, and get an agenda started: - release artifacts and process redux - 4.0 goals, timeline, and priorities Comments pls! - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. -- http://www.wizcorp.jp/Ally Ogilvie Lead Developer - MobDev. | Wizcorp Inc. http://www.wizcorp.jp/ -- TECH . GAMING . OPEN-SOURCE WIZARDS+ 81 (0)3-4550-1448 | Websitehttp://www.wizcorp.jp/ | Twitter https://twitter.com/Wizcorp | Facebookhttp://www.facebook.com/Wizcorp | LinkedIn http://www.linkedin.com/company/wizcorp
Re: [Vote] Transifex Translation : please vote
Finally getting around to this. I think the workflow that you describe sounds great! The project link didn't work for me... maybe I was too slow :(. On Tue, Jul 30, 2013 at 5:24 PM, Anis KADRI anis.ka...@gmail.com wrote: I vote yes. I am a bit worried about translations though. I feel like people who translate and are not involved in the project tend to produce poor translations. But translation is better than no translation. So +1. -a On Tue, Jul 30, 2013 at 2:02 PM, Lisa Seacat DeLuca ldel...@us.ibm.com wrote: I sent a note out about a month ago about using Transifex for translation of the Cordova docs. Everyone was preparing for the 3.0 release and phonegap day so I didn't receive much of a response. So I'm reopening the discussion. I have created a project within Transifex for cordova here: https://www.transifex.com/projects/p/cordova The way it works is: 1. files are upload to the Transifex system. Transifex does not have markdown files as one of the options for file type to import but they do have html and plain text. I have chosen plain text for testing and it appears to work great. I setup a preferences for the resource to be pulled from github on a daily basis with the latest version of the file. 2. Users may come in and provide translation or all or part of a file. 3. A maintainer or language expert is assigned to each language and approves the translations 4. progress information and status can be shown per file/project. Once complete, the translated file can be uploaded back into github under the specific language. This part is a manual process Other open source projects use Transifex, for example, OpenStack. I propose we do the following: Use Transifex for each major release starting with 3.0. If it is relatively easy to translate for minor releases we can vote to do so with each. Assign a language maintainer for each supported language to monitor translations. I suggest we start with Spanish and French since those are the languages our group of committers can best contribute to at this time. (If we have a consensus to use Transfix, please volunteer if you'd like to be the maintainer for a specific language). Once a section of the documentation is approved by the language moderator, we push the updates to GitHub. I created a new JIRA issue related to globalization so we can track comments outside of the mailing list as well. https://issues.apache.org/jira/browse/CB-4461 Another thing to think about, Transifex offers automatic translation for faster translation using google translation services or microsoft's which require an api key and a paid subscription. I don't know if either of those companies offer a free key for open source needs. I know we have a few representatives from those companies that might be able to give us more information. Why we should be worried about translation? Globalization! If we can attract more developers to Cordova and make it easier for those developers to get up and running with cordova by providing documentation in their native languages, cordova will continue to grow in popularity globally. Please vote if you are okay with moving forward with Transifex as a solution to our translation needs. Lisa ldel...@us.ibm.com @IBMLisa From: Lisa Seacat DeLuca/San Francisco/IBM To: dev@cordova.apache.org, Date: 07/17/2013 10:23 AM Subject:Transifex I have been doing some research into translation services available and ran into a group that has been working on a solution for Open Stack using Transifex. Lets face it, the cordova translation story is just not where it could be. It looks like the Transifex service is free for open source projects. Does anyone have a strong opinion one way or another on whether or not we could utilize Transifex for cordova? Transifex website: http://www.transifex.com Supported File Formats: http://support.transifex.com/customer/portal/articles/971979-supported-file-formats cordova project I created on transifex: https://www.transifex.com/projects/p/cordova I uploaded the overview file ( https://www.transifex.com/projects/p/cordova/resource/guide_overview_indexmdhtml/ ) to give the service a try and see what we can expect. It would be interesting to build this into our release cycle, especially during major releases when the getting started guides, plugin guides, etc. change drastically. Lisa ldel...@us.ibm.com
Re: Post 3.0 release committer and community meeting
That could be an ideal solution to that :). Thanks all, =Ryan On 8/6/13 12:53 PM, Al Harding alharding...@gmail.com wrote: Ryan come up to the Vancouver office? On Tue, Aug 6, 2013 at 12:51 PM, Ryan Stewart rstew...@adobe.com wrote: If we're planning on attending from a community standpoint, but aren't planning on talking, is there going to be an easy way to do that or do we need to add our names to the list? And I'm assuming this is open to non-committers based on the subject, but correct me if that's wrong. =Ryan On 8/6/13 12:48 PM, Al Harding alharding...@gmail.com wrote: We'll need 2 locations for the Cordova team at Adobe: Attendees: If you plan to attend, could you add your name to this list (inline so that the list grows) and say whether you plan to be co-located: agrieve, co-location=Google Waterloo aharding, co-location=Adobe Vancouver stevegill, co-location=Adobe San Francisco On Tue, Aug 6, 2013 at 12:33 PM, Andrew Grieve agri...@chromium.org wrote: Want to get the ball rolling on this. Please fill out this doodle so we can pick a day: http://www.doodle.com/i4u89n2k52yne4zt AFAIK, the *best* timezone-friendly time is 4:30PM PST How to meet? - Hangouts have a max 10 person limit, but I've found that VC meetings get a bit unwieldy anyways when there are more than 10 sites. I'm hoping that co-located people can share computers so that we can keep the number of connections down. Attendees: If you plan to attend, could you add your name to this list (inline so that the list grows) and say whether you plan to be co-located: agrieve, co-location=Google Waterloo Agenda (feel free to add items inline): - release artifacts and process redux - Should platform releases still be coupled? - Does semver make more sense to us now that components are more decoupled? - Deprecation policy improvements? - Can we use cordova-registry to allow older versions of things when APIs are removed? - Can we have our plugin API surface versioned separately from our component versions? - Shortterm plans for Medic - Buildbot? - Should mobile-spec autotests be pulled out? - 4.0 goals, timeline, and priorities - Platforms as build artifacts - Is this our goal? what's big hurdles remain? - Apps Plugins to have the same feature set (dependencies, merges/, etc) On Wed, Jul 17, 2013 at 9:47 AM, Andrew Grieve agri...@chromium.org wrote: That week's good for me! On Tue, Jul 16, 2013 at 3:59 AM, Ally Ogilvie aogil...@wizcorp.jp wrote: Sensible timezone for Asia/Aus please :) On Tue, Jul 16, 2013 at 4:22 PM, Filip Maj f...@adobe.com wrote: Sounds good On 7/16/13 12:10 AM, David Pfahler da...@excellenteasy.com wrote: Count me in for the hangouts etc. On Tue, Jul 16, 2013 at 12:22 AM, Ken Wallis kwal...@blackberry.com wrote: Definitely a good idea. Sent from my BlackBerry 10 smartphone. From: Brian LeRoux Sent: Monday, July 15, 2013 5:45 PM To: dev@cordova.apache.org Reply To: dev@cordova.apache.org Subject: Post 3.0 release committer and community meeting Hey everyone, we're in the final stretch to releasing 3.0 and I think long past due to have an open discussion w/ the committership and larger community. I think we should let the dust settle from 3.0 for a couple of weeks before having this meeting. I'd like to propose the week of August 12th. If that all sounds good, we could setup a Google Hangout, and get an agenda started: - release artifacts and process redux - 4.0 goals, timeline, and priorities Comments pls! - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. -- http://www.wizcorp.jp/Ally Ogilvie Lead Developer - MobDev. | Wizcorp Inc. http://www.wizcorp.jp/ -- TECH . GAMING . OPEN-SOURCE WIZARDS+ 81 (0)3-4550-1448 | Websitehttp://www.wizcorp.jp/ | Twitter https://twitter.com/Wizcorp | Facebookhttp://www.facebook.com/Wizcorp | LinkedIn http://www.linkedin.com/company/wizcorp
Re: Post 3.0 release committer and community meeting
definitely +1 for viewing-only via youtube but pretty sure the recorded version might get some audience too Richard -- Sent from my mobile Original Message From: Michal Mocny mmo...@chromium.org Sent: Wed Aug 07 07:49:55 NZST 2013 To: dev dev@cordova.apache.org Cc: Andrew Grieve agri...@chromium.org Subject: Re: Post 3.0 release committer and community meeting On Tue, Aug 6, 2013 at 3:33 PM, Andrew Grieve agri...@chromium.org wrote: Want to get the ball rolling on this. Please fill out this doodle so we can pick a day: http://www.doodle.com/i4u89n2k52yne4zt AFAIK, the *best* timezone-friendly time is 4:30PM PST How to meet? - Hangouts have a max 10 person limit, but I've found that VC meetings get a bit unwieldy anyways when there are more than 10 sites. I'm hoping that co-located people can share computers so that we can keep the number of connections down. Suggestion: Hangouts on air appears to have the same 10 people limit, yet allows viewing-only for very many people via youtube. Suggest we only allow contributors to join the hangouts via invite, and publish the link for live viewing if anyone is interested. I think this also enable us to record and share the video and other such cool benefits. Attendees: If you plan to attend, could you add your name to this list (inline so that the list grows) and say whether you plan to be co-located: agrieve, co-location=Google Waterloo mmocny, co-location=Google Waterloo Agenda (feel free to add items inline): - release artifacts and process redux - Should platform releases still be coupled? - Does semver make more sense to us now that components are more decoupled? - Deprecation policy improvements? - Can we use cordova-registry to allow older versions of things when APIs are removed? - Can we have our plugin API surface versioned separately from our component versions? - Shortterm plans for Medic - Buildbot? - Should mobile-spec autotests be pulled out? - 4.0 goals, timeline, and priorities - Platforms as build artifacts - Is this our goal? what's big hurdles remain? - Apps Plugins to have the same feature set (dependencies, merges/, etc) On Wed, Jul 17, 2013 at 9:47 AM, Andrew Grieve agri...@chromium.org wrote: That week's good for me! On Tue, Jul 16, 2013 at 3:59 AM, Ally Ogilvie aogil...@wizcorp.jp wrote: Sensible timezone for Asia/Aus please :) On Tue, Jul 16, 2013 at 4:22 PM, Filip Maj f...@adobe.com wrote: Sounds good On 7/16/13 12:10 AM, David Pfahler da...@excellenteasy.com wrote: Count me in for the hangouts etc. On Tue, Jul 16, 2013 at 12:22 AM, Ken Wallis kwal...@blackberry.com wrote: Definitely a good idea. Sent from my BlackBerry 10 smartphone. From: Brian LeRoux Sent: Monday, July 15, 2013 5:45 PM To: dev@cordova.apache.org Reply To: dev@cordova.apache.org Subject: Post 3.0 release committer and community meeting Hey everyone, we're in the final stretch to releasing 3.0 and I think long past due to have an open discussion w/ the committership and larger community. I think we should let the dust settle from 3.0 for a couple of weeks before having this meeting. I'd like to propose the week of August 12th. If that all sounds good, we could setup a Google Hangout, and get an agenda started: - release artifacts and process redux - 4.0 goals, timeline, and priorities Comments pls! - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. -- http://www.wizcorp.jp/Ally Ogilvie Lead Developer - MobDev. | Wizcorp Inc. http://www.wizcorp.jp/ -- TECH . GAMING . OPEN-SOURCE WIZARDS+ 81 (0)3-4550-1448 | Websitehttp://www.wizcorp.jp/ | Twitter https://twitter.com/Wizcorp | Facebookhttp://www.facebook.com/Wizcorp | LinkedIn http://www.linkedin.com/company/wizcorp
Re: Post 3.0 release committer and community meeting
Michal I did a test run with the hang-outs on air and it seemed to work really well! We'll give it a try :) No need to fill out your info if you don't plan on talking. On Tue, Aug 6, 2013 at 4:04 PM, Richard Sentino rich...@mindginative.comwrote: definitely +1 for viewing-only via youtube but pretty sure the recorded version might get some audience too Richard -- Sent from my mobile Original Message From: Michal Mocny mmo...@chromium.org Sent: Wed Aug 07 07:49:55 NZST 2013 To: dev dev@cordova.apache.org Cc: Andrew Grieve agri...@chromium.org Subject: Re: Post 3.0 release committer and community meeting On Tue, Aug 6, 2013 at 3:33 PM, Andrew Grieve agri...@chromium.org wrote: Want to get the ball rolling on this. Please fill out this doodle so we can pick a day: http://www.doodle.com/i4u89n2k52yne4zt AFAIK, the *best* timezone-friendly time is 4:30PM PST How to meet? - Hangouts have a max 10 person limit, but I've found that VC meetings get a bit unwieldy anyways when there are more than 10 sites. I'm hoping that co-located people can share computers so that we can keep the number of connections down. Suggestion: Hangouts on air appears to have the same 10 people limit, yet allows viewing-only for very many people via youtube. Suggest we only allow contributors to join the hangouts via invite, and publish the link for live viewing if anyone is interested. I think this also enable us to record and share the video and other such cool benefits. Attendees: If you plan to attend, could you add your name to this list (inline so that the list grows) and say whether you plan to be co-located: agrieve, co-location=Google Waterloo mmocny, co-location=Google Waterloo Agenda (feel free to add items inline): - release artifacts and process redux - Should platform releases still be coupled? - Does semver make more sense to us now that components are more decoupled? - Deprecation policy improvements? - Can we use cordova-registry to allow older versions of things when APIs are removed? - Can we have our plugin API surface versioned separately from our component versions? - Shortterm plans for Medic - Buildbot? - Should mobile-spec autotests be pulled out? - 4.0 goals, timeline, and priorities - Platforms as build artifacts - Is this our goal? what's big hurdles remain? - Apps Plugins to have the same feature set (dependencies, merges/, etc) On Wed, Jul 17, 2013 at 9:47 AM, Andrew Grieve agri...@chromium.org wrote: That week's good for me! On Tue, Jul 16, 2013 at 3:59 AM, Ally Ogilvie aogil...@wizcorp.jp wrote: Sensible timezone for Asia/Aus please :) On Tue, Jul 16, 2013 at 4:22 PM, Filip Maj f...@adobe.com wrote: Sounds good On 7/16/13 12:10 AM, David Pfahler da...@excellenteasy.com wrote: Count me in for the hangouts etc. On Tue, Jul 16, 2013 at 12:22 AM, Ken Wallis kwal...@blackberry.com wrote: Definitely a good idea. Sent from my BlackBerry 10 smartphone. From: Brian LeRoux Sent: Monday, July 15, 2013 5:45 PM To: dev@cordova.apache.org Reply To: dev@cordova.apache.org Subject: Post 3.0 release committer and community meeting Hey everyone, we're in the final stretch to releasing 3.0 and I think long past due to have an open discussion w/ the committership and larger community. I think we should let the dust settle from 3.0 for a couple of weeks before having this meeting. I'd like to propose the week of August 12th. If that all sounds good, we could setup a Google Hangout, and get an agenda started: - release artifacts and process redux - 4.0 goals, timeline, and priorities Comments pls! - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. -- http://www.wizcorp.jp/Ally Ogilvie Lead Developer - MobDev. | Wizcorp Inc. http://www.wizcorp.jp/ -- TECH . GAMING . OPEN-SOURCE WIZARDS+ 81 (0)3-4550-1448 | Websitehttp://www.wizcorp.jp/ | Twitter https://twitter.com/Wizcorp |
Re: Post 3.0 release committer and community meeting
agrieve, co-location=Google Waterloo mmocny, co-location=Google Waterloo maxw, co-location=Google Waterloo aharding, co-location=Adobe Vancouver filmaj, co-location=Adobe Vancouver stevegill, co-location=Adobe San Francisco bhiggins, co-location=BlackBerry Toronto jheifetz, co-location=BlackBerry Toronto On Tue, Aug 6, 2013 at 4:04 PM, Richard Sentino rich...@mindginative.comwrote: definitely +1 for viewing-only via youtube but pretty sure the recorded version might get some audience too Richard -- Sent from my mobile Original Message From: Michal Mocny mmo...@chromium.org Sent: Wed Aug 07 07:49:55 NZST 2013 To: dev dev@cordova.apache.org Cc: Andrew Grieve agri...@chromium.org Subject: Re: Post 3.0 release committer and community meeting On Tue, Aug 6, 2013 at 3:33 PM, Andrew Grieve agri...@chromium.org wrote: Want to get the ball rolling on this. Please fill out this doodle so we can pick a day: http://www.doodle.com/i4u89n2k52yne4zt AFAIK, the *best* timezone-friendly time is 4:30PM PST How to meet? - Hangouts have a max 10 person limit, but I've found that VC meetings get a bit unwieldy anyways when there are more than 10 sites. I'm hoping that co-located people can share computers so that we can keep the number of connections down. Suggestion: Hangouts on air appears to have the same 10 people limit, yet allows viewing-only for very many people via youtube. Suggest we only allow contributors to join the hangouts via invite, and publish the link for live viewing if anyone is interested. I think this also enable us to record and share the video and other such cool benefits. Attendees: If you plan to attend, could you add your name to this list (inline so that the list grows) and say whether you plan to be co-located: agrieve, co-location=Google Waterloo mmocny, co-location=Google Waterloo Agenda (feel free to add items inline): - release artifacts and process redux - Should platform releases still be coupled? - Does semver make more sense to us now that components are more decoupled? - Deprecation policy improvements? - Can we use cordova-registry to allow older versions of things when APIs are removed? - Can we have our plugin API surface versioned separately from our component versions? - Shortterm plans for Medic - Buildbot? - Should mobile-spec autotests be pulled out? - 4.0 goals, timeline, and priorities - Platforms as build artifacts - Is this our goal? what's big hurdles remain? - Apps Plugins to have the same feature set (dependencies, merges/, etc) On Wed, Jul 17, 2013 at 9:47 AM, Andrew Grieve agri...@chromium.org wrote: That week's good for me! On Tue, Jul 16, 2013 at 3:59 AM, Ally Ogilvie aogil...@wizcorp.jp wrote: Sensible timezone for Asia/Aus please :) On Tue, Jul 16, 2013 at 4:22 PM, Filip Maj f...@adobe.com wrote: Sounds good On 7/16/13 12:10 AM, David Pfahler da...@excellenteasy.com wrote: Count me in for the hangouts etc. On Tue, Jul 16, 2013 at 12:22 AM, Ken Wallis kwal...@blackberry.com wrote: Definitely a good idea. Sent from my BlackBerry 10 smartphone. From: Brian LeRoux Sent: Monday, July 15, 2013 5:45 PM To: dev@cordova.apache.org Reply To: dev@cordova.apache.org Subject: Post 3.0 release committer and community meeting Hey everyone, we're in the final stretch to releasing 3.0 and I think long past due to have an open discussion w/ the committership and larger community. I think we should let the dust settle from 3.0 for a couple of weeks before having this meeting. I'd like to propose the week of August 12th. If that all sounds good, we could setup a Google Hangout, and get an agenda started: - release artifacts and process redux - 4.0 goals, timeline, and priorities Comments pls! - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. -- http://www.wizcorp.jp/Ally Ogilvie Lead Developer - MobDev. | Wizcorp Inc. http://www.wizcorp.jp/ -- TECH . GAMING . OPEN-SOURCE
Re: Post 3.0 release committer and community meeting
On Tue, Aug 6, 2013 at 4:15 PM, Bryan Higgins br...@bryanhiggins.netwrote: agrieve, co-location=Google Waterloo mmocny, co-location=Google Waterloo maxw, co-location=Google Waterloo aharding, co-location=Adobe Vancouver filmaj, co-location=Adobe Vancouver stevegill, co-location=Adobe San Francisco bhiggins, co-location=BlackBerry Toronto jheifetz, co-location=BlackBerry Toronto drkemp, co-location=Google Waterloo On Tue, Aug 6, 2013 at 4:04 PM, Richard Sentino rich...@mindginative.com wrote: definitely +1 for viewing-only via youtube but pretty sure the recorded version might get some audience too Richard -- Sent from my mobile Original Message From: Michal Mocny mmo...@chromium.org Sent: Wed Aug 07 07:49:55 NZST 2013 To: dev dev@cordova.apache.org Cc: Andrew Grieve agri...@chromium.org Subject: Re: Post 3.0 release committer and community meeting On Tue, Aug 6, 2013 at 3:33 PM, Andrew Grieve agri...@chromium.org wrote: Want to get the ball rolling on this. Please fill out this doodle so we can pick a day: http://www.doodle.com/i4u89n2k52yne4zt AFAIK, the *best* timezone-friendly time is 4:30PM PST How to meet? - Hangouts have a max 10 person limit, but I've found that VC meetings get a bit unwieldy anyways when there are more than 10 sites. I'm hoping that co-located people can share computers so that we can keep the number of connections down. Suggestion: Hangouts on air appears to have the same 10 people limit, yet allows viewing-only for very many people via youtube. Suggest we only allow contributors to join the hangouts via invite, and publish the link for live viewing if anyone is interested. I think this also enable us to record and share the video and other such cool benefits. Attendees: If you plan to attend, could you add your name to this list (inline so that the list grows) and say whether you plan to be co-located: agrieve, co-location=Google Waterloo mmocny, co-location=Google Waterloo Agenda (feel free to add items inline): - release artifacts and process redux - Should platform releases still be coupled? - Does semver make more sense to us now that components are more decoupled? - Deprecation policy improvements? - Can we use cordova-registry to allow older versions of things when APIs are removed? - Can we have our plugin API surface versioned separately from our component versions? - Shortterm plans for Medic - Buildbot? - Should mobile-spec autotests be pulled out? - 4.0 goals, timeline, and priorities - Platforms as build artifacts - Is this our goal? what's big hurdles remain? - Apps Plugins to have the same feature set (dependencies, merges/, etc) On Wed, Jul 17, 2013 at 9:47 AM, Andrew Grieve agri...@chromium.org wrote: That week's good for me! On Tue, Jul 16, 2013 at 3:59 AM, Ally Ogilvie aogil...@wizcorp.jp wrote: Sensible timezone for Asia/Aus please :) On Tue, Jul 16, 2013 at 4:22 PM, Filip Maj f...@adobe.com wrote: Sounds good On 7/16/13 12:10 AM, David Pfahler da...@excellenteasy.com wrote: Count me in for the hangouts etc. On Tue, Jul 16, 2013 at 12:22 AM, Ken Wallis kwal...@blackberry.com wrote: Definitely a good idea. Sent from my BlackBerry 10 smartphone. From: Brian LeRoux Sent: Monday, July 15, 2013 5:45 PM To: dev@cordova.apache.org Reply To: dev@cordova.apache.org Subject: Post 3.0 release committer and community meeting Hey everyone, we're in the final stretch to releasing 3.0 and I think long past due to have an open discussion w/ the committership and larger community. I think we should let the dust settle from 3.0 for a couple of weeks before having this meeting. I'd like to propose the week of August 12th. If that all sounds good, we could setup a Google Hangout, and get an agenda started: - release artifacts and process redux - 4.0 goals, timeline, and priorities Comments pls! - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of
Removing onNativeReady channel
All of the JS platforms fire onNativeReady in their platform.bootstrap function (used to be bootstrap-$platform.js). Might as well just delete this channel, yes?
Re: Removing onNativeReady channel
I think the onCordovaReady event does what onNativeReady intends to do.. If that makes sense. So removal sounds good to me. Are there cases out there where third party plugins attach to onNativeReady? On 8/6/13 1:21 PM, Andrew Grieve agri...@chromium.org wrote: All of the JS platforms fire onNativeReady in their platform.bootstrap function (used to be bootstrap-$platform.js). Might as well just delete this channel, yes?
Re: WP8 'Plugin interface' and 'Splash screen' support
Sergey, `cordova plugin *` commands all invoke plugman. On 8/1/13 12:26 AM, Sergey Grebnov (Akvelon) v-seg...@microsoft.com wrote: Thanks Benn, regarding WP8 and plugman support: Does this mean cli command cordova plugin add ... use different mechanism (not plugman)? I run the following commands and got added plugin worked. cordova plugin add somepluginuri cordova build wp8 cordova emulate wp8 Thx!! Sergey -Original Message- From: Benn Mapes [mailto:benn.ma...@gmail.com] Sent: Wednesday, July 31, 2013 10:42 PM To: dev@cordova.apache.org Subject: Re: WP8 'Plugin interface' and 'Splash screen' support Windows Phone 7+8 support the SpashScreen plugin, if there are any issues with it please file a bug in jira but the plugin should work. Windows Phone 8 does support the plugin interface (plugman + cli). File Transfer plugin has some issues though on windows phone. These should be changed. ~Benn On Wed, Jul 31, 2013 at 9:53 AM, Bryan Higgins br...@bryanhiggins.netwrote: Thanks Fil! There is a README in that repo for BB10 stating this is supported OOTB. I'll validate it still works in 3.0. Mike - this can be marked as supported https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-device-orient ation.git;h=75ae8b8 On Wed, Jul 31, 2013 at 12:09 PM, Filip Maj f...@adobe.com wrote: That's the device orientation plugin: https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-device-orient ation .git; On 7/31/13 8:18 AM, Bryan Higgins br...@bryanhiggins.net wrote: BB10 CLI will work on Linux, BBOS has no CLI support I'm having trouble tracking down where the compass plugin is hosted. If BB10 doesn't support this right now, we should be able to add it quickly On Wed, Jul 31, 2013 at 10:41 AM, Jeffrey Heifetz jheif...@blackberry.comwrote: BlackBerry10 supports both Media and SplashScreen but not Globalization On 13-07-31 9:52 AM, Michael Sierra msie...@adobe.com wrote: I can see another couple of problems that need to be fixed. Please take a moment to review this table for any platform you're particularly familiar with. Thanks, --Mike Sierra From: Sergey Grebnov (Akvelon) [v-seg...@microsoft.com] Sent: Wednesday, July 31, 2013 5:13 AM To: dev@cordova.apache.org Subject: WP8 'Plugin interface' and 'Splash screen' support Hi, on the platform support overview page below there is information that WP8 does not support 'Plugin interface' and 'Splash screen' plugin http://docs.phonegap.com/en/edge/guide_overview_index.md.html#Overview _pl a tform_support Is it really true, could someone clarify this information? Plugins - we supported this previously and there is also special Windows Phone Plugins guideline available http://docs.phonegap.com/en/3.0.0/guide_platforms_wp8_plugin.md.html#W ind o ws%20Phone%20Plugins Somehow related to CB-4453 ? Splash Screen plugin - there is some wp8 implementation here https://github.com/apache/cordova-plugin-splashscreen/blob/master/src/ wp/ S plashScreen.cs Jira: does not see any open issue related to splash screen plugin under [wp8] tag Thank you, -Sergey Grebnov -- --- This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
Re: [Vote] Transifex Translation : please vote
Andrew, not too late. I started a JIRA issue related to translation here: https://issues.apache.org/jira/browse/CB-4461 Basically I ended up going with Crowdin instead of Transifex because Crowdin supports markdown file times making it a LOT easier on our flow. The customer support has been incredible as well and they have machine translations built into their tooling. Here's the crowdin project team area: http://crowdin.net/project/cordova I've been posting a few comments on Twitter to try to attract translators but so far it's just me and one other person. If anyone is interested please feel free to join in. Which reminds me, this might be a good topic for a blog post! Lisa Seacat DeLuca ldel...@us.ibm.com - Message from Andrew Grieve agri...@chromium.org on Tue, 6 Aug 2013 15:55:23 -0400 - To: dev dev@cordova.apache.org Subject: Re: [Vote] Transifex Translation : please vote Finally getting around to this. I think the workflow that you describe sounds great! The project link didn't work for me... maybe I was too slow :(. On Tue, Jul 30, 2013 at 5:24 PM, Anis KADRI anis.ka...@gmail.com wrote: I vote yes. I am a bit worried about translations though. I feel like people who translate and are not involved in the project tend to produce poor translations. But translation is better than no translation. So +1. -a On Tue, Jul 30, 2013 at 2:02 PM, Lisa Seacat DeLuca ldel...@us.ibm.com wrote: I sent a note out about a month ago about using Transifex for translation of the Cordova docs. Everyone was preparing for the 3.0 release and phonegap day so I didn't receive much of a response. So I'm reopening the discussion. I have created a project within Transifex for cordova here: https://www.transifex.com/projects/p/cordova The way it works is: 1. files are upload to the Transifex system. Transifex does not have markdown files as one of the options for file type to import but they do have html and plain text. I have chosen plain text for testing and it appears to work great. I setup a preferences for the resource to be pulled from github on a daily basis with the latest version of the file. 2. Users may come in and provide translation or all or part of a file. 3. A maintainer or language expert is assigned to each language and approves the translations 4. progress information and status can be shown per file/project. Once complete, the translated file can be uploaded back into github under the specific language. This part is a manual process Other open source projects use Transifex, for example, OpenStack. I propose we do the following: Use Transifex for each major release starting with 3.0. If it is relatively easy to translate for minor releases we can vote to do so with each. Assign a language maintainer for each supported language to monitor translations. I suggest we start with Spanish and French since those are the languages our group of committers can best contribute to at this time. (If we have a consensus to use Transfix, please volunteer if you'd like to be the maintainer for a specific language). Once a section of the documentation is approved by the language moderator, we push the updates to GitHub. I created a new JIRA issue related to globalization so we can track comments outside of the mailing list as well. https://issues.apache.org/jira/browse/CB-4461 Another thing to think about, Transifex offers automatic translation for faster translation using google translation services or microsoft's which require an api key and a paid subscription. I don't know if either of those companies offer a free key for open source needs. I know we have a few representatives from those companies that might be able to give us more information. Why we should be worried about translation? Globalization! If we can attract more developers to Cordova and make it easier for those developers to get up and running with cordova by providing documentation in their native languages, cordova will continue to grow in popularity globally. Please vote if you are okay with moving forward with Transifex as a solution to our translation needs. Lisa ldel...@us.ibm.com @IBMLisa From: Lisa Seacat DeLuca/San Francisco/IBM To: dev@cordova.apache.org, Date: 07/17/2013 10:23 AM Subject:Transifex I have been doing some research into translation services available and ran into a group that has been working on a solution for Open Stack using Transifex. Lets face it, the cordova translation story is just not where it could be. It looks like the Transifex service is free for open source projects. Does anyone have a strong opinion one way or another on whether or not we could utilize Transifex for cordova? Transifex website: http://www.transifex.com Supported File Formats:
Releases in a 3.0 World
Want to have this as a discussion starter. We've previously established that: 1. Releases for plugman CLI will not be tied to platform releases 2. Releases to plugins will not be tied to platform releases That's not to say we shouldn't sometime co-ordinate them with platform releases, but I think there would need to be a compelling reason to couple them. I'm wondering if it makes sense to not tie platform releases together either? E.g. Allow an update to cordova-ios separately from cordova-blackberry10. Possible Advantages: - Releases will (hopefully) occur more frequently. Don't need to wait for synchronization with other platforms to do a release. Possible Disadvantages: - Might make for too many releases spam our users with release notes too often - Might make us lazy and release platforms too infrequently - Might make version numbers for platforms not correspond date-wise with version numbers of other platforms (e.g. 3.1 ios != 3.1 android) Other considerations: cordova-js is a common piece here. Perhaps that could be pulled out as well? Option 1: Bundle the exec bridge, platform bootstrap plugin loader with the platform, and have the rest available as a plugin. Option 2: Bundle exec bridge + platform bootstrap with the platform, bundle the plugin loader with plugman, put the rest in a plugin For reference, the only non-exec-bridge / start-up code I can see is: ./cordova.js --- hooks addEventListener + has exec bridge logic ./common/argscheck.js --- strictly a helper for plugins ./common/base64.js --- exec bridge depends on this ./common/builder.js --- should be folded into modulemapper.js ./common/channel.js --- start-up code needs this ./common/init.js --- start-up code ./common/modulemapper.js --- start-up code ./common/pluginloader.js --- loads plugins on start-up ./common/urlutil.js --- recently added helper for plugins ./common/utils.js --- mostly misc stuff that may be mostly unused? There's also: ./windows8/windows8/commandProxy.js which I assume is exec bridge releated. I think that argscheck urlutil would be well-suited as stand-alone plugins that other plugins depend on.
Re: Removing onNativeReady channel
I think that's a good idea. If there are no platforms actually using this signal to indicate anything useful, then nobody should be listening for it to fire. Deleting it now means that nobody ends up in a situation where they're implicitly depending on a feature that we don't support, don't test, and which will probably break in the future without anyone noticing. On Tue, Aug 6, 2013 at 4:21 PM, Andrew Grieve agri...@chromium.org wrote: All of the JS platforms fire onNativeReady in their platform.bootstrap function (used to be bootstrap-$platform.js). Might as well just delete this channel, yes?
Re: add about command to CLI
So i've done a little work on this here: https://github.com/lholmquist/cordova-cli/tree/CB-2234 atm i've only added the iOS and Android platforms. And it doesn't currently get your command history. i have it outputting to the console as well as writing to a file, info.txt , eventually maybe just go with the file. wanted to get some feedback before i sent the PR in On Aug 5, 2013, at 3:42 PM, Lucas Holmquist lholm...@redhat.com wrote: On Aug 5, 2013, at 3:38 PM, Anis KADRI anis.ka...@gmail.com wrote: Do it! :) i will, looks like i can't assign to myself however, commented in the JIRA On Mon, Aug 5, 2013 at 12:36 PM, Lucas Holmquist lholm...@redhat.com wrote: https://issues.apache.org/jira/browse/CB-2234 has there been any work done on this? I would like to take this one. I've been meaning to start contributing, but things keep coming up, so i figured this would be a good step to start with -Luke
Re: add about command to CLI
oh yea, and the command is cordova -i or cordova -info On Aug 6, 2013, at 5:10 PM, Lucas Holmquist lholm...@redhat.com wrote: So i've done a little work on this here: https://github.com/lholmquist/cordova-cli/tree/CB-2234 atm i've only added the iOS and Android platforms. And it doesn't currently get your command history. i have it outputting to the console as well as writing to a file, info.txt , eventually maybe just go with the file. wanted to get some feedback before i sent the PR in On Aug 5, 2013, at 3:42 PM, Lucas Holmquist lholm...@redhat.com wrote: On Aug 5, 2013, at 3:38 PM, Anis KADRI anis.ka...@gmail.com wrote: Do it! :) i will, looks like i can't assign to myself however, commented in the JIRA On Mon, Aug 5, 2013 at 12:36 PM, Lucas Holmquist lholm...@redhat.com wrote: https://issues.apache.org/jira/browse/CB-2234 has there been any work done on this? I would like to take this one. I've been meaning to start contributing, but things keep coming up, so i figured this would be a good step to start with -Luke
Re: Removing onNativeReady channel
WP code:
string nativeReady = (function(){
cordova.require('cordova/channel').onNativeReady.fire()})();;
@purplecabbage
risingj.com
On Tue, Aug 6, 2013 at 1:45 PM, Ian Clelland iclell...@chromium.org wrote:
I think that's a good idea. If there are no platforms actually using this
signal to indicate anything useful, then nobody should be listening for it
to fire.
Deleting it now means that nobody ends up in a situation where they're
implicitly depending on a feature that we don't support, don't test, and
which will probably break in the future without anyone noticing.
On Tue, Aug 6, 2013 at 4:21 PM, Andrew Grieve agri...@chromium.org
wrote:
All of the JS platforms fire onNativeReady in their platform.bootstrap
function (used to be bootstrap-$platform.js).
Might as well just delete this channel, yes?
PROPOSAL: platform-spec
I would like to propose adding a new repository to cordova called platform-spec. It would be a set of tests that would be run against a cordova-* platform implementation's bin/ folder, testing all of the platform scripts that we have started / attempted to standardize [1]. Reason: I already see divergence across platform implementations, and for tools that rely on these scripts (ahem, cordova-cli), it would be a big bonus :) It would be nice to introduce running these tests into our testing process. At the minimum, we would control script regressions that have burned us in the past. [1] https://wiki.apache.org/cordova/CommandLineToolingDesign
Re: PROPOSAL: platform-spec
Bonus: no longer need to update the wiki article linked-to below and instead can update the tests. At least this way platform maintainers will get a bit more tangible feedback on those scripts, and possibly higher chance that the scripts get updated :) On 8/6/13 3:07 PM, Filip Maj f...@adobe.com wrote: I would like to propose adding a new repository to cordova called platform-spec. It would be a set of tests that would be run against a cordova-* platform implementation's bin/ folder, testing all of the platform scripts that we have started / attempted to standardize [1]. Reason: I already see divergence across platform implementations, and for tools that rely on these scripts (ahem, cordova-cli), it would be a big bonus :) It would be nice to introduce running these tests into our testing process. At the minimum, we would control script regressions that have burned us in the past. [1] https://wiki.apache.org/cordova/CommandLineToolingDesign
PROPOSAL: node.js all the script things
I would like to introduce node.js as a dependency for the platform libraries, so that the platform scripts (bin/create, cordova/run, etc) are written in node. Pros: - For multi-OS platforms (Android, BlackBerry), this reduces committer cognitive load as the scripts do not need to be authored in two different script languages (I.e. Shell for unix-y Oses, Wscript for Windows) - consistency in tool/script language. Cordova-js, coho, cli and plugman are all written on top of node.js. Cons: - Introducing a new dependency NB: This is separate from platform-spec; I would like to see platform-spec created/used regardless of the outcome of this thread.
Re: PROPOSAL: node.js all the script things
I only think this should be done for the multi-OS platforms. Elsewhere it is just a make work project IMHO. I have spent a lot of time ensuring that I was not introducing dependencies, then we add node, and we get 600 deps. @purplecabbage risingj.com On Tue, Aug 6, 2013 at 3:14 PM, Filip Maj f...@adobe.com wrote: I would like to introduce node.js as a dependency for the platform libraries, so that the platform scripts (bin/create, cordova/run, etc) are written in node. Pros: - For multi-OS platforms (Android, BlackBerry), this reduces committer cognitive load as the scripts do not need to be authored in two different script languages (I.e. Shell for unix-y Oses, Wscript for Windows) - consistency in tool/script language. Cordova-js, coho, cli and plugman are all written on top of node.js. Cons: - Introducing a new dependency NB: This is separate from platform-spec; I would like to see platform-spec created/used regardless of the outcome of this thread.
Re: PROPOSAL: platform-spec
Can't this be done vicariously through the cordova-cli tests? @purplecabbage risingj.com On Tue, Aug 6, 2013 at 3:10 PM, Filip Maj f...@adobe.com wrote: Bonus: no longer need to update the wiki article linked-to below and instead can update the tests. At least this way platform maintainers will get a bit more tangible feedback on those scripts, and possibly higher chance that the scripts get updated :) On 8/6/13 3:07 PM, Filip Maj f...@adobe.com wrote: I would like to propose adding a new repository to cordova called platform-spec. It would be a set of tests that would be run against a cordova-* platform implementation's bin/ folder, testing all of the platform scripts that we have started / attempted to standardize [1]. Reason: I already see divergence across platform implementations, and for tools that rely on these scripts (ahem, cordova-cli), it would be a big bonus :) It would be nice to introduce running these tests into our testing process. At the minimum, we would control script regressions that have burned us in the past. [1] https://wiki.apache.org/cordova/CommandLineToolingDesign
Re: PROPOSAL: node.js all the script things
That's a fair answer! I concur. The main win for me is in android + BB land, for the reason you name, Jesse. On 8/6/13 3:24 PM, Jesse purplecabb...@gmail.com wrote: I only think this should be done for the multi-OS platforms. Elsewhere it is just a make work project IMHO. I have spent a lot of time ensuring that I was not introducing dependencies, then we add node, and we get 600 deps. @purplecabbage risingj.com On Tue, Aug 6, 2013 at 3:14 PM, Filip Maj f...@adobe.com wrote: I would like to introduce node.js as a dependency for the platform libraries, so that the platform scripts (bin/create, cordova/run, etc) are written in node. Pros: - For multi-OS platforms (Android, BlackBerry), this reduces committer cognitive load as the scripts do not need to be authored in two different script languages (I.e. Shell for unix-y Oses, Wscript for Windows) - consistency in tool/script language. Cordova-js, coho, cli and plugman are all written on top of node.js. Cons: - Introducing a new dependency NB: This is separate from platform-spec; I would like to see platform-spec created/used regardless of the outcome of this thread.
Re: PROPOSAL: platform-spec
This will also be a great addition to the min requirements of being a supported platform. +1 On Tue, Aug 6, 2013 at 3:10 PM, Filip Maj f...@adobe.com wrote: Bonus: no longer need to update the wiki article linked-to below and instead can update the tests. At least this way platform maintainers will get a bit more tangible feedback on those scripts, and possibly higher chance that the scripts get updated :) On 8/6/13 3:07 PM, Filip Maj f...@adobe.com wrote: I would like to propose adding a new repository to cordova called platform-spec. It would be a set of tests that would be run against a cordova-* platform implementation's bin/ folder, testing all of the platform scripts that we have started / attempted to standardize [1]. Reason: I already see divergence across platform implementations, and for tools that rely on these scripts (ahem, cordova-cli), it would be a big bonus :) It would be nice to introduce running these tests into our testing process. At the minimum, we would control script regressions that have burned us in the past. [1] https://wiki.apache.org/cordova/CommandLineToolingDesign
Re: PROPOSAL: platform-spec
You mean, can't the tests exist as part of the cordova-cli tests? I suppose they could. The unit tests in cordova-cli are just that: unit tests. They do not actually shell out to the platform scripts. This keeps the tests focussed and light (run in 1 second). A good thing if you're developing on that project. Related, Jeff from BlackBerry recently added an integration test to cordova-cli to actually shell out to certain cordova-cli commands and inspect output, but this is brittle: timeouts are usually not met and are very system-dependent (having an SSD vs. not is the difference between a failing and passing test). If we broke out the integration tests for the platform scripts, and not have them run automatically when you invoke `npm test` within cordova-cli, I think it'd be fine. I don't really care where the tests exist, as long as a) they exist and b) running them becomes part of the Sanctioned Testing And Release Process© (aka STARP) On 8/6/13 3:27 PM, Jesse purplecabb...@gmail.com wrote: Can't this be done vicariously through the cordova-cli tests? @purplecabbage risingj.com On Tue, Aug 6, 2013 at 3:10 PM, Filip Maj f...@adobe.com wrote: Bonus: no longer need to update the wiki article linked-to below and instead can update the tests. At least this way platform maintainers will get a bit more tangible feedback on those scripts, and possibly higher chance that the scripts get updated :) On 8/6/13 3:07 PM, Filip Maj f...@adobe.com wrote: I would like to propose adding a new repository to cordova called platform-spec. It would be a set of tests that would be run against a cordova-* platform implementation's bin/ folder, testing all of the platform scripts that we have started / attempted to standardize [1]. Reason: I already see divergence across platform implementations, and for tools that rely on these scripts (ahem, cordova-cli), it would be a big bonus :) It would be nice to introduce running these tests into our testing process. At the minimum, we would control script regressions that have burned us in the past. [1] https://wiki.apache.org/cordova/CommandLineToolingDesign
Re: Post 3.0 release committer and community meeting
+1 for sane Asia/Aus time. On 16/07/2013, at 5:59 PM, Ally Ogilvie aogil...@wizcorp.jp wrote: Sensible timezone for Asia/Aus please :) On Tue, Jul 16, 2013 at 4:22 PM, Filip Maj f...@adobe.com wrote: Sounds good On 7/16/13 12:10 AM, David Pfahler da...@excellenteasy.com wrote: Count me in for the hangouts etc. On Tue, Jul 16, 2013 at 12:22 AM, Ken Wallis kwal...@blackberry.com wrote: Definitely a good idea. Sent from my BlackBerry 10 smartphone. From: Brian LeRoux Sent: Monday, July 15, 2013 5:45 PM To: dev@cordova.apache.org Reply To: dev@cordova.apache.org Subject: Post 3.0 release committer and community meeting Hey everyone, we're in the final stretch to releasing 3.0 and I think long past due to have an open discussion w/ the committership and larger community. I think we should let the dust settle from 3.0 for a couple of weeks before having this meeting. I'd like to propose the week of August 12th. If that all sounds good, we could setup a Google Hangout, and get an agenda started: - release artifacts and process redux - 4.0 goals, timeline, and priorities Comments pls! - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. -- http://www.wizcorp.jp/Ally Ogilvie Lead Developer - MobDev. | Wizcorp Inc. http://www.wizcorp.jp/ -- TECH . GAMING . OPEN-SOURCE WIZARDS+ 81 (0)3-4550-1448 | Websitehttp://www.wizcorp.jp/ | Twitter https://twitter.com/Wizcorp | Facebookhttp://www.facebook.com/Wizcorp | LinkedIn http://www.linkedin.com/company/wizcorp
Re: PROPOSAL: platform-spec
I am a +1 either way, not sure which is best. @purplecabbage risingj.com On Tue, Aug 6, 2013 at 3:40 PM, Filip Maj f...@adobe.com wrote: You mean, can't the tests exist as part of the cordova-cli tests? I suppose they could. The unit tests in cordova-cli are just that: unit tests. They do not actually shell out to the platform scripts. This keeps the tests focussed and light (run in 1 second). A good thing if you're developing on that project. Related, Jeff from BlackBerry recently added an integration test to cordova-cli to actually shell out to certain cordova-cli commands and inspect output, but this is brittle: timeouts are usually not met and are very system-dependent (having an SSD vs. not is the difference between a failing and passing test). If we broke out the integration tests for the platform scripts, and not have them run automatically when you invoke `npm test` within cordova-cli, I think it'd be fine. I don't really care where the tests exist, as long as a) they exist and b) running them becomes part of the Sanctioned Testing And Release Process© (aka STARP) On 8/6/13 3:27 PM, Jesse purplecabb...@gmail.com wrote: Can't this be done vicariously through the cordova-cli tests? @purplecabbage risingj.com On Tue, Aug 6, 2013 at 3:10 PM, Filip Maj f...@adobe.com wrote: Bonus: no longer need to update the wiki article linked-to below and instead can update the tests. At least this way platform maintainers will get a bit more tangible feedback on those scripts, and possibly higher chance that the scripts get updated :) On 8/6/13 3:07 PM, Filip Maj f...@adobe.com wrote: I would like to propose adding a new repository to cordova called platform-spec. It would be a set of tests that would be run against a cordova-* platform implementation's bin/ folder, testing all of the platform scripts that we have started / attempted to standardize [1]. Reason: I already see divergence across platform implementations, and for tools that rely on these scripts (ahem, cordova-cli), it would be a big bonus :) It would be nice to introduce running these tests into our testing process. At the minimum, we would control script regressions that have burned us in the past. [1] https://wiki.apache.org/cordova/CommandLineToolingDesign
Re: Post 3.0 release committer and community meeting
On 07/08/2013, at 6:15 AM, Bryan Higgins br...@bryanhiggins.net wrote: agrieve, co-location=Google Waterloo mmocny, co-location=Google Waterloo maxw, co-location=Google Waterloo aharding, co-location=Adobe Vancouver filmaj, co-location=Adobe Vancouver stevegill, co-location=Adobe San Francisco bhiggins, co-location=BlackBerry Toronto jheifetz, co-location=BlackBerry Toronto devgeeks, co-location=n/a Melbourne, Australia On Tue, Aug 6, 2013 at 4:04 PM, Richard Sentino rich...@mindginative.comwrote: definitely +1 for viewing-only via youtube but pretty sure the recorded version might get some audience too Richard -- Sent from my mobile Original Message From: Michal Mocny mmo...@chromium.org Sent: Wed Aug 07 07:49:55 NZST 2013 To: dev dev@cordova.apache.org Cc: Andrew Grieve agri...@chromium.org Subject: Re: Post 3.0 release committer and community meeting On Tue, Aug 6, 2013 at 3:33 PM, Andrew Grieve agri...@chromium.org wrote: Want to get the ball rolling on this. Please fill out this doodle so we can pick a day: http://www.doodle.com/i4u89n2k52yne4zt AFAIK, the *best* timezone-friendly time is 4:30PM PST How to meet? - Hangouts have a max 10 person limit, but I've found that VC meetings get a bit unwieldy anyways when there are more than 10 sites. I'm hoping that co-located people can share computers so that we can keep the number of connections down. Suggestion: Hangouts on air appears to have the same 10 people limit, yet allows viewing-only for very many people via youtube. Suggest we only allow contributors to join the hangouts via invite, and publish the link for live viewing if anyone is interested. I think this also enable us to record and share the video and other such cool benefits. Attendees: If you plan to attend, could you add your name to this list (inline so that the list grows) and say whether you plan to be co-located: agrieve, co-location=Google Waterloo mmocny, co-location=Google Waterloo Agenda (feel free to add items inline): - release artifacts and process redux - Should platform releases still be coupled? - Does semver make more sense to us now that components are more decoupled? - Deprecation policy improvements? - Can we use cordova-registry to allow older versions of things when APIs are removed? - Can we have our plugin API surface versioned separately from our component versions? - Shortterm plans for Medic - Buildbot? - Should mobile-spec autotests be pulled out? - 4.0 goals, timeline, and priorities - Platforms as build artifacts - Is this our goal? what's big hurdles remain? - Apps Plugins to have the same feature set (dependencies, merges/, etc) On Wed, Jul 17, 2013 at 9:47 AM, Andrew Grieve agri...@chromium.org wrote: That week's good for me! On Tue, Jul 16, 2013 at 3:59 AM, Ally Ogilvie aogil...@wizcorp.jp wrote: Sensible timezone for Asia/Aus please :) On Tue, Jul 16, 2013 at 4:22 PM, Filip Maj f...@adobe.com wrote: Sounds good On 7/16/13 12:10 AM, David Pfahler da...@excellenteasy.com wrote: Count me in for the hangouts etc. On Tue, Jul 16, 2013 at 12:22 AM, Ken Wallis kwal...@blackberry.com wrote: Definitely a good idea. Sent from my BlackBerry 10 smartphone. From: Brian LeRoux Sent: Monday, July 15, 2013 5:45 PM To: dev@cordova.apache.org Reply To: dev@cordova.apache.org Subject: Post 3.0 release committer and community meeting Hey everyone, we're in the final stretch to releasing 3.0 and I think long past due to have an open discussion w/ the committership and larger community. I think we should let the dust settle from 3.0 for a couple of weeks before having this meeting. I'd like to propose the week of August 12th. If that all sounds good, we could setup a Google Hangout, and get an agenda started: - release artifacts and process redux - 4.0 goals, timeline, and priorities Comments pls! - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. -- http://www.wizcorp.jp/Ally Ogilvie Lead Developer - MobDev. | Wizcorp Inc. http://www.wizcorp.jp/ -- TECH . GAMING . OPEN-SOURCE WIZARDS+ 81 (0)3-4550-1448 | Websitehttp://www.wizcorp.jp/ | Twitter https://twitter.com/Wizcorp |
Re: PROPOSAL: platform-spec
I wrote some tests for Android back when I was writing those bin/ thingies. I think it makes sense to have some higher level blind tests that run against each platform's bin folder. I'd like it be part of cordova-cli though. We already have 40+ repositories. On Tue, Aug 6, 2013 at 3:52 PM, Jesse purplecabb...@gmail.com wrote: I am a +1 either way, not sure which is best. @purplecabbage risingj.com On Tue, Aug 6, 2013 at 3:40 PM, Filip Maj f...@adobe.com wrote: You mean, can't the tests exist as part of the cordova-cli tests? I suppose they could. The unit tests in cordova-cli are just that: unit tests. They do not actually shell out to the platform scripts. This keeps the tests focussed and light (run in 1 second). A good thing if you're developing on that project. Related, Jeff from BlackBerry recently added an integration test to cordova-cli to actually shell out to certain cordova-cli commands and inspect output, but this is brittle: timeouts are usually not met and are very system-dependent (having an SSD vs. not is the difference between a failing and passing test). If we broke out the integration tests for the platform scripts, and not have them run automatically when you invoke `npm test` within cordova-cli, I think it'd be fine. I don't really care where the tests exist, as long as a) they exist and b) running them becomes part of the Sanctioned Testing And Release Process© (aka STARP) On 8/6/13 3:27 PM, Jesse purplecabb...@gmail.com wrote: Can't this be done vicariously through the cordova-cli tests? @purplecabbage risingj.com On Tue, Aug 6, 2013 at 3:10 PM, Filip Maj f...@adobe.com wrote: Bonus: no longer need to update the wiki article linked-to below and instead can update the tests. At least this way platform maintainers will get a bit more tangible feedback on those scripts, and possibly higher chance that the scripts get updated :) On 8/6/13 3:07 PM, Filip Maj f...@adobe.com wrote: I would like to propose adding a new repository to cordova called platform-spec. It would be a set of tests that would be run against a cordova-* platform implementation's bin/ folder, testing all of the platform scripts that we have started / attempted to standardize [1]. Reason: I already see divergence across platform implementations, and for tools that rely on these scripts (ahem, cordova-cli), it would be a big bonus :) It would be nice to introduce running these tests into our testing process. At the minimum, we would control script regressions that have burned us in the past. [1] https://wiki.apache.org/cordova/CommandLineToolingDesign
Re: Releases in a 3.0 World
Another disadvantage is, this may cause downstream distributions of Cordova to get fragmented. -- Gorkem On Tue, Aug 6, 2013 at 4:43 PM, Andrew Grieve agri...@chromium.org wrote: Want to have this as a discussion starter. We've previously established that: 1. Releases for plugman CLI will not be tied to platform releases 2. Releases to plugins will not be tied to platform releases That's not to say we shouldn't sometime co-ordinate them with platform releases, but I think there would need to be a compelling reason to couple them. I'm wondering if it makes sense to not tie platform releases together either? E.g. Allow an update to cordova-ios separately from cordova-blackberry10. Possible Advantages: - Releases will (hopefully) occur more frequently. Don't need to wait for synchronization with other platforms to do a release. Possible Disadvantages: - Might make for too many releases spam our users with release notes too often - Might make us lazy and release platforms too infrequently - Might make version numbers for platforms not correspond date-wise with version numbers of other platforms (e.g. 3.1 ios != 3.1 android) Other considerations: cordova-js is a common piece here. Perhaps that could be pulled out as well? Option 1: Bundle the exec bridge, platform bootstrap plugin loader with the platform, and have the rest available as a plugin. Option 2: Bundle exec bridge + platform bootstrap with the platform, bundle the plugin loader with plugman, put the rest in a plugin For reference, the only non-exec-bridge / start-up code I can see is: ./cordova.js --- hooks addEventListener + has exec bridge logic ./common/argscheck.js --- strictly a helper for plugins ./common/base64.js --- exec bridge depends on this ./common/builder.js --- should be folded into modulemapper.js ./common/channel.js --- start-up code needs this ./common/init.js --- start-up code ./common/modulemapper.js --- start-up code ./common/pluginloader.js --- loads plugins on start-up ./common/urlutil.js --- recently added helper for plugins ./common/utils.js --- mostly misc stuff that may be mostly unused? There's also: ./windows8/windows8/commandProxy.js which I assume is exec bridge releated. I think that argscheck urlutil would be well-suited as stand-alone plugins that other plugins depend on.
Re: PROPOSAL: node.js all the script things
+1 if we can somehow automate a user-level node installation (or package it somehow). On Tue, Aug 6, 2013 at 3:28 PM, Filip Maj f...@adobe.com wrote: That's a fair answer! I concur. The main win for me is in android + BB land, for the reason you name, Jesse. On 8/6/13 3:24 PM, Jesse purplecabb...@gmail.com wrote: I only think this should be done for the multi-OS platforms. Elsewhere it is just a make work project IMHO. I have spent a lot of time ensuring that I was not introducing dependencies, then we add node, and we get 600 deps. @purplecabbage risingj.com On Tue, Aug 6, 2013 at 3:14 PM, Filip Maj f...@adobe.com wrote: I would like to introduce node.js as a dependency for the platform libraries, so that the platform scripts (bin/create, cordova/run, etc) are written in node. Pros: - For multi-OS platforms (Android, BlackBerry), this reduces committer cognitive load as the scripts do not need to be authored in two different script languages (I.e. Shell for unix-y Oses, Wscript for Windows) - consistency in tool/script language. Cordova-js, coho, cli and plugman are all written on top of node.js. Cons: - Introducing a new dependency NB: This is separate from platform-spec; I would like to see platform-spec created/used regardless of the outcome of this thread.
Re: add about command to CLI
Just tried it and it works. I have a couple of comments. - I think it would be better to have a separate template and then use util.format() to add all the values. Kinda like we do help() - I think you should add some tests ;-} On Tue, Aug 6, 2013 at 2:11 PM, Lucas Holmquist lholm...@redhat.com wrote: oh yea, and the command is cordova -i or cordova -info On Aug 6, 2013, at 5:10 PM, Lucas Holmquist lholm...@redhat.com wrote: So i've done a little work on this here: https://github.com/lholmquist/cordova-cli/tree/CB-2234 atm i've only added the iOS and Android platforms. And it doesn't currently get your command history. i have it outputting to the console as well as writing to a file, info.txt , eventually maybe just go with the file. wanted to get some feedback before i sent the PR in On Aug 5, 2013, at 3:42 PM, Lucas Holmquist lholm...@redhat.com wrote: On Aug 5, 2013, at 3:38 PM, Anis KADRI anis.ka...@gmail.com wrote: Do it! :) i will, looks like i can't assign to myself however, commented in the JIRA On Mon, Aug 5, 2013 at 12:36 PM, Lucas Holmquist lholm...@redhat.com wrote: https://issues.apache.org/jira/browse/CB-2234 has there been any work done on this? I would like to take this one. I've been meaning to start contributing, but things keep coming up, so i figured this would be a good step to start with -Luke
RE: Post 3.0 release committer and community meeting
Ally, co-location=n/a Tokyo, Japan. Sent from my Windows Phone From: Tommy-Carlos Williams Sent: 07/08/2013 07:53 To: dev@cordova.apache.org Subject: Re: Post 3.0 release committer and community meeting On 07/08/2013, at 6:15 AM, Bryan Higgins br...@bryanhiggins.net wrote: agrieve, co-location=Google Waterloo mmocny, co-location=Google Waterloo maxw, co-location=Google Waterloo aharding, co-location=Adobe Vancouver filmaj, co-location=Adobe Vancouver stevegill, co-location=Adobe San Francisco bhiggins, co-location=BlackBerry Toronto jheifetz, co-location=BlackBerry Toronto devgeeks, co-location=n/a Melbourne, Australia On Tue, Aug 6, 2013 at 4:04 PM, Richard Sentino rich...@mindginative.comwrote: definitely +1 for viewing-only via youtube but pretty sure the recorded version might get some audience too Richard -- Sent from my mobile Original Message From: Michal Mocny mmo...@chromium.org Sent: Wed Aug 07 07:49:55 NZST 2013 To: dev dev@cordova.apache.org Cc: Andrew Grieve agri...@chromium.org Subject: Re: Post 3.0 release committer and community meeting On Tue, Aug 6, 2013 at 3:33 PM, Andrew Grieve agri...@chromium.org wrote: Want to get the ball rolling on this. Please fill out this doodle so we can pick a day: http://www.doodle.com/i4u89n2k52yne4zt AFAIK, the *best* timezone-friendly time is 4:30PM PST How to meet? - Hangouts have a max 10 person limit, but I've found that VC meetings get a bit unwieldy anyways when there are more than 10 sites. I'm hoping that co-located people can share computers so that we can keep the number of connections down. Suggestion: Hangouts on air appears to have the same 10 people limit, yet allows viewing-only for very many people via youtube. Suggest we only allow contributors to join the hangouts via invite, and publish the link for live viewing if anyone is interested. I think this also enable us to record and share the video and other such cool benefits. Attendees: If you plan to attend, could you add your name to this list (inline so that the list grows) and say whether you plan to be co-located: agrieve, co-location=Google Waterloo mmocny, co-location=Google Waterloo Agenda (feel free to add items inline): - release artifacts and process redux - Should platform releases still be coupled? - Does semver make more sense to us now that components are more decoupled? - Deprecation policy improvements? - Can we use cordova-registry to allow older versions of things when APIs are removed? - Can we have our plugin API surface versioned separately from our component versions? - Shortterm plans for Medic - Buildbot? - Should mobile-spec autotests be pulled out? - 4.0 goals, timeline, and priorities - Platforms as build artifacts - Is this our goal? what's big hurdles remain? - Apps Plugins to have the same feature set (dependencies, merges/, etc) On Wed, Jul 17, 2013 at 9:47 AM, Andrew Grieve agri...@chromium.org wrote: That week's good for me! On Tue, Jul 16, 2013 at 3:59 AM, Ally Ogilvie aogil...@wizcorp.jp wrote: Sensible timezone for Asia/Aus please :) On Tue, Jul 16, 2013 at 4:22 PM, Filip Maj f...@adobe.com wrote: Sounds good On 7/16/13 12:10 AM, David Pfahler da...@excellenteasy.com wrote: Count me in for the hangouts etc. On Tue, Jul 16, 2013 at 12:22 AM, Ken Wallis kwal...@blackberry.com wrote: Definitely a good idea. Sent from my BlackBerry 10 smartphone. From: Brian LeRoux Sent: Monday, July 15, 2013 5:45 PM To: dev@cordova.apache.org Reply To: dev@cordova.apache.org Subject: Post 3.0 release committer and community meeting Hey everyone, we're in the final stretch to releasing 3.0 and I think long past due to have an open discussion w/ the committership and larger community. I think we should let the dust settle from 3.0 for a couple of weeks before having this meeting. I'd like to propose the week of August 12th. If that all sounds good, we could setup a Google Hangout, and get an agenda started: - release artifacts and process redux - 4.0 goals, timeline, and priorities Comments pls! - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. -- http://www.wizcorp.jp/Ally Ogilvie Lead Developer - MobDev. | Wizcorp Inc. http://www.wizcorp.jp/
Re: add about command to CLI
On Aug 6, 2013, at 7:45 PM, Anis KADRI anis.ka...@gmail.com wrote: Just tried it and it works. I have a couple of comments. - I think it would be better to have a separate template and then use util.format() to add all the values. Kinda like we do help() thanks for the feedback, i figured there was an easier way - I think you should add some tests ;-} tests? what are tests? ;) On Tue, Aug 6, 2013 at 2:11 PM, Lucas Holmquist lholm...@redhat.com wrote: oh yea, and the command is cordova -i or cordova -info On Aug 6, 2013, at 5:10 PM, Lucas Holmquist lholm...@redhat.com wrote: So i've done a little work on this here: https://github.com/lholmquist/cordova-cli/tree/CB-2234 atm i've only added the iOS and Android platforms. And it doesn't currently get your command history. i have it outputting to the console as well as writing to a file, info.txt , eventually maybe just go with the file. wanted to get some feedback before i sent the PR in On Aug 5, 2013, at 3:42 PM, Lucas Holmquist lholm...@redhat.com wrote: On Aug 5, 2013, at 3:38 PM, Anis KADRI anis.ka...@gmail.com wrote: Do it! :) i will, looks like i can't assign to myself however, commented in the JIRA On Mon, Aug 5, 2013 at 12:36 PM, Lucas Holmquist lholm...@redhat.com wrote: https://issues.apache.org/jira/browse/CB-2234 has there been any work done on this? I would like to take this one. I've been meaning to start contributing, but things keep coming up, so i figured this would be a good step to start with -Luke
Re: Post 3.0 release committer and community meeting
Sorry, I buggered up the list. Full list copied below... Attendees: If you plan to attend, could you add your name to this list (inline so that the list grows) and say whether you plan to be co-located: agrieve, co-location=Google Waterloo mmocny, co-location=Google Waterloo maxw, co-location=Google Waterloo aharding, co-location=Adobe Vancouver filmaj, co-location=Adobe Vancouver stevegill, co-location=Adobe San Francisco bhiggins, co-location=BlackBerry Toronto jheifetz, co-location=BlackBerry Toronto drkemp, co-location=Google Waterloo devgeeks, co-location=n/a Melbourne, Australia aogilvie, co-location=n/a Tokyo, Japan. Agenda (feel free to add items inline): - Release artifacts and process redux - Should platform releases still be coupled? - Does semver make more sense to us now that components are more decoupled? - Deprecation policy improvements? - Can we use cordova-registry to allow older versions of things when APIs are removed? - Can we have our plugin API surface versioned separately from our component versions? - Shortterm plans for Medic - Buildbot? - Should mobile-spec autotests be pulled out? - 4.0 goals, timeline, and priorities - Platforms as build artifacts - Is this our goal? what's big hurdles remain? - Apps Plugins to have the same feature set (dependencies, merges/, etc) On Wed, Aug 7, 2013 at 10:09 AM, Ally Ogilvie aogil...@wizcorp.jp wrote: Ally, co-location=n/a Tokyo, Japan. Sent from my Windows Phone From: Tommy-Carlos Williams Sent: 07/08/2013 07:53 To: dev@cordova.apache.org Subject: Re: Post 3.0 release committer and community meeting On 07/08/2013, at 6:15 AM, Bryan Higgins br...@bryanhiggins.net wrote: agrieve, co-location=Google Waterloo mmocny, co-location=Google Waterloo maxw, co-location=Google Waterloo aharding, co-location=Adobe Vancouver filmaj, co-location=Adobe Vancouver stevegill, co-location=Adobe San Francisco bhiggins, co-location=BlackBerry Toronto jheifetz, co-location=BlackBerry Toronto devgeeks, co-location=n/a Melbourne, Australia On Tue, Aug 6, 2013 at 4:04 PM, Richard Sentino rich...@mindginative.comwrote: definitely +1 for viewing-only via youtube but pretty sure the recorded version might get some audience too Richard -- Sent from my mobile Original Message From: Michal Mocny mmo...@chromium.org Sent: Wed Aug 07 07:49:55 NZST 2013 To: dev dev@cordova.apache.org Cc: Andrew Grieve agri...@chromium.org Subject: Re: Post 3.0 release committer and community meeting On Tue, Aug 6, 2013 at 3:33 PM, Andrew Grieve agri...@chromium.org wrote: Want to get the ball rolling on this. Please fill out this doodle so we can pick a day: http://www.doodle.com/i4u89n2k52yne4zt AFAIK, the *best* timezone-friendly time is 4:30PM PST How to meet? - Hangouts have a max 10 person limit, but I've found that VC meetings get a bit unwieldy anyways when there are more than 10 sites. I'm hoping that co-located people can share computers so that we can keep the number of connections down. Suggestion: Hangouts on air appears to have the same 10 people limit, yet allows viewing-only for very many people via youtube. Suggest we only allow contributors to join the hangouts via invite, and publish the link for live viewing if anyone is interested. I think this also enable us to record and share the video and other such cool benefits. Attendees: If you plan to attend, could you add your name to this list (inline so that the list grows) and say whether you plan to be co-located: agrieve, co-location=Google Waterloo mmocny, co-location=Google Waterloo Agenda (feel free to add items inline): - release artifacts and process redux - Should platform releases still be coupled? - Does semver make more sense to us now that components are more decoupled? - Deprecation policy improvements? - Can we use cordova-registry to allow older versions of things when APIs are removed? - Can we have our plugin API surface versioned separately from our component versions? - Shortterm plans for Medic - Buildbot? - Should mobile-spec autotests be pulled out? - 4.0 goals, timeline, and priorities - Platforms as build artifacts - Is this our goal? what's big hurdles remain? - Apps Plugins to have the same feature set (dependencies, merges/, etc) On Wed, Jul 17, 2013 at 9:47 AM, Andrew Grieve agri...@chromium.org wrote: That week's good for me! On Tue, Jul 16, 2013 at 3:59 AM, Ally Ogilvie aogil...@wizcorp.jp wrote: Sensible timezone for Asia/Aus please :) On Tue, Jul 16, 2013 at 4:22 PM, Filip Maj f...@adobe.com wrote: Sounds good On 7/16/13 12:10 AM, David Pfahler da...@excellenteasy.com wrote: Count me in for the hangouts etc. On Tue, Jul 16, 2013 at 12:22 AM, Ken Wallis kwal...@blackberry.com
