I vote +1
-Original Message-
From: Chris Brody
Sent: Wednesday, June 6, 2018 2:50 PM
To: dev@cordova.apache.org
Subject: Re: [VOTE] cordova-serve release
+1
Thanks Darryl for the quick turnaround!
On Wed, Jun 6, 2018 at 5:40 PM, Darryl Pogue wrote:
> Please review and vote on this T
Sorry, with the Christmas break I forgot to follow up on this. The vote has now
well and truly closed. The results are:
Positive binding votes: 3
Tim Barham
Alexander Sorokin
Vladimir Kotikov
The vote has passed.
-Original Message-
From: Vladimir Kotikov (Akvelon) [mailto:v-vlk
Please review and vote on this Tools Release by replying to this email (and
keep discussion on the DISCUSS thread)
Release issue: https://issues.apache.org/jira/browse/CB-12289
The release has been published to dist/dev:
https://dist.apache.org/repos/dist/dev/cordova/CB-12289/. It has also been
I'd like to do a cordova-serve 1.0.1 release that just cherry picks a single
commit
(https://github.com/apache/cordova-lib/commit/84fa8e39b22252381ed4baa6868ff6f22b7a48e2).
Anyone have any concerns with that?
(the reasoning behind just taking that single commit is that we'd like to take
that f
It seems to me it would be bad form to simply change the default behavior back
to copy, if that will break existing plugins that rely on the current behavior.
While it would be inconsistent with other platforms, perhaps we should leave
the current default behavior as-is and add an attribute to s
I vote +1:
* Verified license headers with 'coho audit-license-headers'
* Verified dependency licenses with 'coho check-license'
* Built and ran basic Windows app
* Verified fixes cordova-windows build issues under Visual Studio "15" new
install experience
-Original Message-
From: Vladimi
It's been a long time since we did a cordova-browser release, and there have
been many improvements since then. Should we get a release out before the next
tools release?
If so, what should the version be? Proper npm versioning would suggest we go
with 4.1.0 (since it is more than just bug fixe
Oh yes please :).
-Original Message-
From: Anis KADRI [mailto:anis.ka...@gmail.com]
Sent: Thursday, December 3, 2015 5:58 AM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] Deprecate cordova-wp8
+1
On Wed, Dec 2, 2015 at 11:32 AM Steven Gill wrote:
> +1
>
> On Wed, Dec 2, 2015 at 11
I have no opinion regarding removing or not, but WTFPL is fine
(http://www.apache.org/legal/resolved.html#category-a).
Tim
-Original Message-
From: Jesse [mailto:purplecabb...@gmail.com]
Sent: Friday, October 30, 2015 12:00 PM
To: dev@cordova.apache.org
Subject: Re: CB-9901 cordova plug
> However tests are still failing locally, but this seems to be a
> problem with tests, not LIB/Android. Alex Sorokin is looking into this.
>
> -
> Best regards, Vladimir
>
> -Original Message-
> From: Tim Barham [mailto:tim.bar...@microsoft.com]
> Sent: Tuesday
+1
-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com]
Sent: Tuesday, October 27, 2015 5:11 PM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] Removal of unused iOS bridges
+1
On Tue, Oct 27, 2015 at 5:05 PM, Shazron wrote:
> Filed
> https://na01.safelinks.protecti
This appears to be a cordova-android issue (I followed the steps in that test
and filed https://issues.apache.org/jira/browse/CB-9880). Although I agree we
should fix the cordova-android issue and get cordova-lib green before
proceeding.
-Original Message-
From: Steven Gill [mailto:stev
Thanks all. The vote has now closed. The results are:
Positive binding votes: 3
Tim Barham
Sergey Grebnov
Vladimir Kotikov
The vote has passed. I will publish it to dist and set it as latest on npm.
We'll reference the changes in the blog post for the next tools release.
-Original Me
> Now we are planning to add express as new npm dependency to cordova-cli,
> brining with it 43 npm packages for us to clear on the next release of our
> product.
Heh, sorry about that :). At least the good news is they all have well
documented licenses (apart from the one where you have to look
t of Express (or very closely related to it).
Tim
-----Original Message-
From: Tim Barham
Sent: Monday, October 5, 2015 7:15 PM
To: 'dev@cordova.apache.org'
Subject: RE: [DISCUSS] cordova-serve 0.2.0 release
Yeah... This is a philosophy of the Express guys - they keep packages reall
able file size to
cordova-cli I check and it's small 1.7mb, so no problem there.
⛄ $ du -sh node_modules/express/
1.7M node_modules/express/
On Mon, Oct 5, 2015 at 1:29 PM Steven Gill wrote:
> I'd rather we bump the major and get out of 0.x.x land.
> On Oct 5, 2015 9:58 AM, &q
Please review and vote on this 1.0.0 release of cordova-serve by replying to
this email (and keep discussion on the DISCUSS thread).
Release issue: https://issues.apache.org/jira/browse/CB-9748
The archive has been published to dist/dev:
https://dist.apache.org/repos/dist/dev/cordova/CB-9748/
:stevengil...@gmail.com]
Sent: Monday, October 5, 2015 9:01 AM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] cordova-serve 0.2.0 release
Why not 1.0.0 if it is breaking
On Oct 4, 2015 5:22 PM, "Tim Barham" wrote:
> Hi all... Yesterday I submitted a PR that was a bit of a rew
Hi all... Yesterday I submitted a PR that was a bit of a rework to
cordova-serve - previously it had essentially been a direct port of what was in
cordova-lib's 'serve' command and cordova-browser, with a couple of hooks to
customize functionality. Yesterday's PR changes it to use ExpressJS for
+1
* Verified tags with coho verify-tags
* Verified signature and hashes with coho verify-archive
* Verified package contents match git repo at tag
* Installed Cordova
* Built and ran blank app for Windows, Android, Browser
* Verified blank app launches without error in Ripple
-Original Messa
rrect. I forgot to run svn commit. Updated RC's are now there.
You can also test using npm install -g cordova@rc
On Aug 30, 2015 10:01 PM, "Tim Barham" wrote:
> Hey Steve - you mention version bumps for lib, cli and plugman, but that
> doesn't seem to be what's in
Hey Steve - you mention version bumps for lib, cli and plugman, but that
doesn't seem to be what's in dist/dev... There we have lib 5.3.0, cli 5.3.0 and
plugman 1.01, but in the vote email you refer to lib 5.3.1, cli 5.3.1 and
plugman 1.0.2. Did you miss updating dist/dev?
-Original Message
Thanks for this info, Tammo - this is all great stuff, and it sounds like the
German Cordova community owes you a lot! I have a couple of comments:
1. In the Cordova community (or any Apache community), nobody should consider
themselves a small person :). Individual contributions are what Apache
Oops... Sorry for apparently counting one of us as 2 people. There were, of
course, actually 3 positive binding votes.
-Original Message-
From: Tim Barham [mailto:tim.bar...@microsoft.com]
Sent: Thursday, August 27, 2015 10:33 AM
To: dev@cordova.apache.org
Subject: RE: [VOTE] Windows
Rob is OOF, so I'll take over getting this out.
The vote has now closed. The results are:
Positive Binding Votes: 4
Rob Paveza
Jesse MacFadyen
Tim Barham
The vote has passed. I will publish it to dist and npm.
-Original Message-
From: Tim Barham [mailto:tim.bar...@microsoft.com]
Thanks all. The vote has now closed. The results are:
Positive Binding Votes: 4
Tim Barham
Sergey Grebnov
Jesse MacFadyen
Carlos Santana
The vote has passed. I will publish it to dist and set it as latest on npm.
We'll reference the changes in the blog post for the next tools re
+1
* Verified archives with 'coho verify-archive'.
* Verified license headers with 'coho audit-license-headers'.
* Verified tag with 'coho verify-tags'.
* Built and ran Hello World app with Windows platform.
* Verified tests were green.
-Original Message-
From: Jesse [mailto:purplecabb...
Please review and vote on this 0.1.3 release of cordova-serve by replying to
this email (and keep discussion on the DISCUSS thread).
Release issue: https://issues.apache.org/jira/browse/CB-9547
The archive has been published to dist/dev:
https://dist.apache.org/repos/dist/dev/cordova/CB-9547
S
If no-one has any objections, I'd like to do a cordova-serve release. It has a
few changes I'd like to take advantage of in some downstream stuff I'm working
on.
For those interested, here's the list of changes since the last release:
* Clean up cordova-serve console output (simplifies output,
al Message-----
From: Tim Barham [mailto:tim.bar...@microsoft.com]
Sent: Friday, August 7, 2015 11:34 AM
To: dev@cordova.apache.org
Subject: RE: [DISCUSS] Upcoming Releases
Hah, of course... I use my Mac to do releases for two reasons:
1. It is the only machine I have set up for doing that.
back, I will help with reviewing and voting.
- Carlos
Sent from my iPhone
> On Aug 6, 2015, at 3:36 AM, Tim Barham wrote:
>
> Ok, sounds good. I'll do this tomorrow (don't have access to my Mac until
> then :) ).
>
> -Original Message-
> From: Carlos
t; > >> >>
> > >> >> On Wed, Jul 22, 2015 at 6:24 PM Steven Gill <
> stevengil...@gmail.com>
> > >> >> wrote:
> > >> >>
> > >> >>> Sounds reasonable. I'll further shorten it a
d a you do Browser and I will do Firefox since I'm not familiar
with latest changes in Browser.
I'm familiar with Firefox and have a Firefox phone for testing.
- Carlos
Sent from my iPhone
> On Aug 5, 2015, at 10:57 PM, Tim Barham wrote:
>
> I was going to do a browser
I was going to do a browser release, but I'm happy to let you do it Carlos for
practice :).
-Original Message-
From: Carlos Santana [mailto:csantan...@gmail.com]
Sent: Wednesday, August 5, 2015 12:34 PM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] Upcoming Releases
I will help out
n the changes that have gone in since 3.6.0
compared to semvers requirements. Launching from a server seems like a pretty
big change. Might be 4.0 worthy.
On Tue, Jul 28, 2015 at 5:39 PM, Tim Barham
wrote:
> It seems to me like it would be good to get a cordova-browser release out.
> There
It seems to me like it would be good to get a cordova-browser release out.
There have been a few changes since the last release - most significantly
launching from a server rather than the local file system, which I think is an
important change to release.
Any objections? Would 3.7.0 be the app
I'd love it if it could be between Sept 21 and Oct 30 - I'll be in Redmond over
that period.
From: Steven Gill
Sent: Thursday, July 23, 2015 7:12 AM
To: dev@cordova.apache.org
Subject: Re: Cordova Face to Face meeting
Redmond sounds good to me. Guess we
Doesn't look like Nikhil has published this to npm, so that shouldn't be a
problem, right?
-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com]
Sent: Wednesday, July 22, 2015 11:41 AM
To: dev@cordova.apache.org
Subject: Re: [VOTE] cordova-android 4.1.0 release
Because rc
The vote has now closed. The results are:
Positive binding votes: 4
Tim Barham
Vladimir Kotikov
Steven Gill
Jesse MacFadyen
The vote has passed. Thanks all!
I will publish to dist and npm.
Question: Does a release like this require a blog post?
Thanks,
Tim
-Original Message-
From
Please review and vote on this Cordova Serve Release by replying to this email.
Release issue: https://issues.apache.org/jira/browse/CB-9181
Package has been published to dist/dev:
https://dist.apache.org/repos/dist/dev/cordova/CB-9181/
I have uploaded the package to npm under the RC tag for tes
se headers.
>
> On Mon, Jun 8, 2015 at 11:21 AM, Tim Barham
> wrote:
>
> > Currently these files are flagged by RAT. We should either add
> > license headers or exclude them (from RAT) to clean up the noise.
> > They're small pieces of template code used by plugm
07 AM, Mefire O. wrote:
> +1 for moving towards consistency, following the same strategy as
> platforms that we pin down.
>
> Thanks,
> Mefire
>
> -----Original Message-
> From: Tim Barham [mailto:tim.bar...@microsoft.com]
> Sent: Thursday, June 11, 2015 8:23 AM
> To:
When we implemented --save for platforms and plugins, we decided to save
versions as caret ranges to be consistent with current npm behavior. However,
when we made our pinned platforms more flexible we decided to go with tilde
ranges rather than caret ranges to keep things a bit more locked down
If nobody has an objections (and I can't imagine why there would be any :) )
I'd like to get a release of cordova-serve underway (so I can then update
cordova-lib and cordova-browser to use it).
I'm pretty sure there are no pending PRs that should go in first :).
Thanks!
Tim
-
Currently these files are flagged by RAT. We should either add license headers
or exclude them (from RAT) to clean up the noise. They're small pieces of
template code used by plugman. The Apache rules for whether a file needs to
have a license header [1] specifies:
> What files in an Apache rel
I vote +1
Verified:
* cordova verify-tags (note this failed for cordova-lib as my origin is github
which still shows 5.1.1 tag on ffb02197e9, but I verified manually on
apache.org).
* cordova audit-license-headers.
* Verified builds are green.
* Created and ran blank app on Android and Windows.
If we need a blog post for this one, I have one here for review:
https://github.com/cordova/apache-blog-posts/blob/c1d53b7a3731a15c40101fe4b2f39041724252c3/2015-06-04-tools-release.md
Thanks,
Tim
-Original Message-
From: Tim Barham [mailto:tim.bar...@microsoft.com]
Sent: Thursday
The vote has now closed. The results are:
Positive binding votes:
- Murat Sutunc
- Nikhil Khandelwal
- Tim Barham
No negative votes.
The vote has passed.
Thanks,
Tim
-Original Message-
From: Murat Sutunc [mailto:mura...@microsoft.com]
Sent: Thursday, June 4, 2015 10:16 AM
To: dev
s in one repo. It would only affect use cases where you are
grabbing the modules from git instead of npm.
Alternative:
request a new repo from infra for cordova-serve.
Since the module will live at Apache, we would have to vote on it like we do
with all of our other releases.
On Thu, May 28,
Please review and vote on this partial Tools Release (lib and cli only)
by replying to this email (and keep discussion on the DISCUSS thread)
This release is to provide a 4.3.1 patch that pins Android 3.7.2 (a security
release).
Release issue: https://issues.apache.org/jira/browse/CB-9103
The p
ols release 4.3.1
Sounds good.
P. S. Obviously I meant cordova platform add not plugin add
On Jun 1, 2015 11:55 AM, "Tim Barham" wrote:
> Thanks Steve... The use case here is for people not using the CLI
> directly, but working with tools like Visual Studio. If they want to be on
er that to
> pin this Windows release. I'm not sure if there is a guideline around
> this - and wonder if it makes sense to combine the two TOOLS releases.
>
> Thanks,
> Nikhil
>
>
> -Original Message-
> From: Tim Barham [mailto:tim.bar...@microsoft.com]
just feels like overkill to me. People on the 4series can easily cordova
plugin add android@3.7.2.
I won't block you though if you decide to proceed.
On Jun 1, 2015 10:06 AM, "Tim Barham" wrote:
> I'd like to propose a 4.3.1 Cordova Tools release to pin cordova-android
I'd like to propose a 4.3.1 Cordova Tools release to pin cordova-android 3.7.2
(security release - see
http://cordova.apache.org/announcements/2015/05/26/android-402.html).
Is anyone aware of any reasons not to proceed with this? If not, I'll proceed
with it later today.
Thanks!
Tim
A while back we duplicated a bunch of 'cordova serve' code in cordova-browser
so that 'cordova run browser' launched from a server rather than the local file
system. At the time, the desire was expressed that ultimately we should avoid
the duplicated code and have a separate 'cordova-serve' modu
://issues.apache.org/jira/browse/CB-9075
On Tue, May 26, 2015 at 4:07 PM, Tim Barham
wrote:
> Couple of things...
>
> * The pinned version for 'windows' platform needs to be updated to
> 3.8.2 ('windows8' got updated, but not 'windows').
> * It would perhaps
Couple of things...
* The pinned version for 'windows' platform needs to be updated to 3.8.2
('windows8' got updated, but not 'windows').
* It would perhaps be good to make the change to allow platform patch updates
(using tilde versions) with this release. I was planning on doing that today
(b
latform
> releases, we would have to test it with the oldest version of the CLI
> that could potentially pull it down.
>
> What do others think?
>
>
>
>
>
>
> On Tue, May 12, 2015 at 6:36 AM, Tim Barham
> wrote:
>
>> ?Currently our pinned platforms are a
No, you were correct - any sort of pre-release identifier makes the version
less than the version without the pre-release identifier (since it signifies a
pre-release).
Hence '4.0.0-dev', '4.0.0-alpha', '4.0.0-0.0.1' and
'4.0.0-iwishiwasarealreease' are all < 4.0.0.
It seems to me the problem
?Currently our pinned platforms are all in the form "1.2.3", which I expect
means we'll always get that exact version. Should we instead use the form
"1.2.x" to allow for patches without having to do a tools release?
BTW... When you add a platform, and we use the pinned version of, say, '1.2.3'
o me.
On Wed, May 6, 2015 at 3:28 PM, Tim Barham wrote:
> Sounds good to me. Once this is done, will we need to do a tools release
> to update pinned platforms (which makes me wonder - should we set the
> version of pinned platforms to something like "4.0.x" so we don't
I vote +1
* Verified archive sigs and hashes ('coho verify-archive').
* Verified tag sha1s ('coho verify-tags').
* Verified can build and run blank app for each platform.
* Verified tests were green (windows and wp8).
* Verified android platform now works in Ripple.
Thanks,
Tim
Sounds good to me. Once this is done, will we need to do a tools release to
update pinned platforms (which makes me wonder - should we set the version of
pinned platforms to something like "4.0.x" so we don't need to update tools
when we do a platform patch release)?
ll platforms that included cordova-js
> >3.8.2 ?
> This will be a 3.9.2 cordova-js release I think, and appropriately enough
> has a ripple effect into platforms and tools.
>
> @purplecabbage
> risingj.com
>
> On Mon, May 4, 2015 at 7:30 PM, Tim Barham
> wrote:
>
&g
lease fanfare in the morning, as a minor release
directly from the last release and a minor bump with no other changes
coming in.
Let me know if there are still issues in cordova-js, and I'll look later
tonite.
Cheers,
Jesse
@purplecabbage
risingj.com
On Mon, May 4, 2015 at 5:23 PM, Tim
xec/proxy or some
cordova apis that we purposely publish, which is what I plan to look into
this week. Or we can consider moving to a model where we do define a way to
override the entire cordova object, and document it.
@purplecabbage
risingj.com
On Mon, May 4, 2015 at 3:56 PM, Tim Barham wro
2015 2:28 AM
To: dev@cordova.apache.org
Subject: Re: Cordova 5.0.0 "duplicate cordova" check breaks Ripple
I think ripple will need to change, I'll have a look and see if there is a more
elegant way to implement honeypot.
> On Apr 30, 2015, at 7:06 PM, Tim Barham wrote:
&
Hey everyone - a bug was filed today against Ripple that it is broken with
Cordova 5.0.0. The issue is that Ripple triggers the new "duplicate cordova"
check:
cordova-js/src/cordova.js line 22:
if ("cordova" in window) { throw new Error("cordova already defined"); };
Ripple patches co
@gorkem - are you ok for this to be merged, or do you feel strongly we should
stick with 'version'?
Thanks,
Tim
____
From: Tim Barham
Sent: Tuesday, April 7, 2015 8:18 AM
To: dev@cordova.apache.org
Subject: Re: Question about plugin/platform --sa
he version of sem-ver?
@purplecabbage
risingj.com
On Mon, Apr 6, 2015 at 7:28 AM, Tim Barham wrote:
> Ok, so... Jesse's ok with 'spec', but prefers 'src'. Gorkem prefers
> 'version'. Glad we at least agree we need something :).
>
> So, because
x27;spec'
However; I had always thought we would jam the new single attribute
into 'src' which is much more generic than 'version', and I think is
still close enough in meaning.
I have been looking at this more from the perspective of added
plugins, but I think even the
01, 2015 3:59 AM
To: dev@cordova.apache.org
Subject: Re: Question about plugin/platform --save: src vs version?
On 31 Mar 2015, at 8:44, Tim Barham wrote:
> So... I agree that:
>
> a) if we don't find it in the specified location, we should fail, and
> b) storing the version is r
om one customer who develops apps
> for
> > a living. For less technical customers a prototype of an app he would
> > build running in the XDK Device Emulator to show what the app would feel
> > like. We lose this capability if we entrust the device emulation problem
> &
h for the case where restoring from src
> > fails. For example, if the path to a local folder no longer exists, what
> do
> > you use to restore? In that case you could use the version as a fallback?
> >
> > Thanks,
> > Edna Morales
> >
> > [image: Inactiv
Hi - I'm looking for input on this issue: For the plugin/platform --save
feature, there's currently an inconsistency between how we store the
information in config.xml for platforms vs plugins.
For platforms, we have a 'version' attribute where we store either the source
location or the versi
Just an FYI - I've been struggling with GitHub most of my day. Turns out
there's been an ongoing DDoS attack.
https://status.github.com/messages
Tim
On Wed, Mar 25, 2015 at 12:00 AM, Michal Mocny wrote:
> ..Also with the move to put plugins in npm, I think we would be directly
> using npm's resolution of the version?
>
> On Tue, Mar 24, 2015 at 8:48 PM, Andrew Grieve
> wrote:
>
> > On Tue, Mar 24, 2015 at
oes not appear to impact cordova, just supplement it,
> you should probably just go for it. Fixing cordova-serve and getting
> cordova-browser to use it are already in discussions, so moving
> forward with another module 'cordova-platform-sim'? sounds good to me.
>
> Che
+1 from me too (always save version, and allow automatic minor version
upgrades).
Gorkem - I'm currently doing some work in this area - I'm happy to make this
change while I'm there.
From: Steven Gill [stevengil...@gmail.com]
Sent: Wednesday, March 25, 2
and be added
independently.
There is a lengthy discussion on browser vs ripple here [2]
[1] https://github.com/apache/incubator-ripple
[2] http://callback.markmail.org/thread/mxwnjp4lnz7kfzrr
@purplecabbage
risingj.com
On Wed, Mar 18, 2015 at 2:04 AM, Tim Barham
wrote:
> Hey everyone...
Jesse - we couldn't use `target` for ``, because there was already
a `target` attribute that had a different meaning. So it was decided to go with
`device-target`. I requested Rob change the equivalent `target` attribute on
`` and `` so that it was consistent across elements.
---
Hey everyone... I would like to introduce a proposal and proof-of-concept
prototype that we have been working on. The proposal is to provide a
tool/feature that allows you to simulate Cordova plugins and device
capabilities when a Cordova app is launched in your desktop browser.
The goals for t
Thanks Jesse!
From: Jesse [purplecabb...@gmail.com]
Sent: Saturday, March 14, 2015 5:22 PM
To: dev@cordova.apache.org
Subject: Re: Assigning JIRA issues to myself...
Done, you're in Tim!
@purplecabbage
risingj.com
On Fri, Mar 13, 2015 at 5:46 PM
Hey Jesse (or someone else with rights)... Could you give me rights in JIRA so
I can assign bugs to myself?
Thanks!
Tim
From: Jesse [purplecabb...@gmail.com]
Sent: Saturday, March 14, 2015 8:14 AM
To: dev@cordova.apache.org
Subject: Re: Introduction for
Welcome Julian!
From: Horn, Julian C [julian.c.h...@intel.com]
Sent: Saturday, March 14, 2015 7:20 AM
To: dev@cordova.apache.org
Subject: Introduction for Julian Horn
Hello! I am Julian Horn. I'm a software engineer in the Intel XDK team. I am
the team
Looks good to me!
-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com]
Sent: Thursday, March 5, 2015 11:03 AM
To: dev@cordova.apache.org
Subject: Re: [REVIEW] NPM Registry integration for fetching plugins and plugin
rm
I have updated the PR based on feedback. Take a look
nning MacOS, so it is
probably just related to path separators.
@purplecabbage
risingj.com
On Thu, Jan 29, 2015 at 11:27 AM, Tim Barham
wrote:
> Thanks Jesse. Do you have any thoughts on the test failures? The failures
> appear to be related to my directory renaming - but the tests pa
Thanks Jesse. Do you have any thoughts on the test failures? The failures
appear to be related to my directory renaming - but the tests pass locally, and
the commits look good (and identical to what I have locally).
-Original Message-
From: purplecabbage [mailto:g...@git.apache.org]
Sen
in cordova-lib/pull/121. Thanks!
Cheers,
Jesse
@purplecabbage
risingj.com
On Thu, Nov 20, 2014 at 11:18 AM, Lorin Beer wrote:
> welcome Tim!
>
> On Thu, Nov 20, 2014 at 11:16 AM, Shazron wrote:
>
> > Welcome aboard Tim!
> >
> > On Thu, Nov 20, 2014 at 11:13
Hi all,
My name is Tim Barham, and I'm on the Visual Studio team at Microsoft. I have
been a part of the team that has been working on Cordova support for Visual
Studio, and now I would like to contribute directly to Cordova, so hopefully
you'll be seeing more of me around here!
90 matches
Mail list logo
