Re: Nomination for a new chair for Apache Cordova

[gandhi rajan]

+1 for Bryan Ellis nomination. He is very active in the community as well.

Thanks Jesse and team for all the support.

On Thu, 30 Nov 2023 at 21:08, Niklas Merz  wrote:

> +1 for nominating Bryan Ellis as the new chair
>
> Bryan is a great choice as he has been doing lots of important work for
> a very long time.
>
> Thanks Jesse for being chair of this PMC for those 5 years. It's great
> to have you around if we need advice from someone who knows the
> internals and history of Cordova.
>
> On November 30, 2023, Jesse  wrote:
> > Hello friends! I have been the chair of Apache Cordova since around
> > December of 2018, roughly 5 years. My duties of late have been mostly
> > administrative: board reports, PMC management etc. Some of it is
> > listed
> > here in the README: https://github.com/apache/cordova-apache-board-
> > reports
> > I think it is time for new leadership and I have decided to resign my
> > duties as the Apache Cordova chair. I formally nominate Bryan Ellis as
> > the
> > next chair.
> > Bryan has been a consistently motivated contributor to the project and
> > has
> > been diligently pushing through many of our releases over the last
> > several
> > years. I believe Bryan will be great in this new role and I will do my
> > best to help him. Bryan is very familiar with and helps uphold 'The
> > Apache
> > Way'
> > (https://www.apache.org/foundation/how-it-works.html) and he will be a
> > great liaison with the Board. I won't be far, I plan to remain in the
> > community and will always be reachable, though I am going to be more
> > focused on personal goals. I am always available to answer questions
> > and
> > help sort issues. Cheers,
> >  Jesse
>


-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Re: Plans for Cordova user & contributor survey

[gandhi rajan]

+1

On Sat, 18 Nov 2023 at 18:00, Niklas Merz  wrote:

> Hey everyone,
>
> As discussed I started building a survey using Google forms. This is the
> current version: https://forms.gle/2HKWATLcRQdw85mE6 .The results are
> stored in a Google Sheet and I can invite you as editors if you want.
>
> I will only continue this effort if at least 3 other PMC members share
> their consensus with a +1 vote.
>
> I also drafted an announcement for the blog as a PR. Feel free to review
> or just edit it there: https://github.com/apache/cordova-docs/pull/1341
>
> For the timeline I suggest the following:
>
> Announcement via blog, mailing list and social media: November 24th 2023
> Closing: December 24th 2023
> Sharing results: End of 2023 (I would prepare another blog post and
> email with numbers)
> Online Hangout to discuss results and conclusions: Start of 2024
>
> What do you think? Let me know your honest opinion on the questions,
> communication and timeline.
>
> Personally I'm really interested in the results and I would love to get
> clearer picture about what we should work on and what users actually do.
>
> Kind regards
> Niklas
>


-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Re: [DISCUSS] Enable github discussions

[gandhi rajan]

+ 1

Github discussions help in easy and transparent interactions.

On Sun, 20 Nov 2022 at 14:26, Jesse  wrote:

> Hello all,
>
> github discussions are a great way of keeping code conversations very close
> to the actual code and I think would suit our project better than our use
> of #slack
>
> The apache airflow project switched to use discussions [1]
> This is not configurable via asf.yml [2] and requires an infra ticket
> linking a consensus reaching discussion. [3]
>
> I propose that we enable discussions on the apache/cordova repo [4] to
> evaluate, and we can possibly make a decision to include other repos later.
>
> What do you think?
>
> Cheers,
>   Jesse
>
> [1]
>
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=191332632#GitHubIssues/Discussions-GithubIssuesandDiscussions
> [2]
> https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features
> [3]
>
> https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-GitHubDiscussions
> [4] https://github.com/apache/cordova
>


-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Re: vote: PR merge convention

[gandhi rajan]

+ 1 for squash and merge as it makes the repo history cleaner.

On Sat, Oct 5, 2019 at 8:34 PM  wrote:

> +1 for "Squash and merge" as the default strategy
>
> Regarding "Create a merge commit":
> At times, I find this option valuable too. Consider a PR that cleans up a
> test suite. As part of that cleanup I might re-order the test cases. As
> re-ordering produces a noisy diff, I usually isolate it in its own commit.
> I would not want to merge this commit with the others as that would lead to
> a commit with a very incomprehensible diff. So in this case I would favor
> leaving the commits separate and doing an actual merge to group them
> together in the global history.
>
> Am Fr., 4. Okt. 2019 um 17:03 Uhr schrieb julio cesar sanchez <
> jcesarmob...@gmail.com>:
>
> > Sorry if it wasn't clear, I said I was leaving the protecting master
> branch
> > out of the vote.
> >
> > Looks like we all agree on using "Squash and merge" as default, unless it
> > makes more sense to use one of the other options.
> >
> > El jue., 3 oct. 2019 a las 3:43, Bryan Ellis ()
> > escribió:
> >
> > > -1 for protected master branches.
> > > Protecting a branch is a great idea except it does not work with our
> > > current workflow process. COHO commits directly onto the master branch
> > for
> > > releases. We would have to spend more time planning and changing our
> > entire
> > > current workflow process to eliminate direct commits if we wanted to
> > > protect branches. There is alternative such keeping master open for
> > direct
> > > commits and development while creating a protected "production" branch.
> > > Anyways this part of the discussion is off-topic and could be another
> > > discussion... Anyways, stated above I am downvoting protected branches
> > for
> > > now.
> > >
> > > +1 for "Squash and merge"
> > > Makes a nice single commit with the PR number and without the extra
> merge
> > > commit.
> > >
> > > +1 for "Rebase and merge"
> > > There are use cases where this can work perfectly.
> > > For example, Cordova-Electron has a `draft-2.0.0` branch which is
> > targeting
> > > the next major release. Major PRs were merged into that branch with
> > "Squash
> > > and merge". This means all PRs have nice PR# information in the title.
> > > A PR will later be created to merge this branch onto master. "Rebase
> and
> > > merge" will be used and will not create the merge commit message and
> will
> > > not squash.
> > >
> > > -1 for "Create a merge commit"
> > > Not in favor of the extra merge commit. I think in most cases one PR
> > should
> > > focus on one task so that means it could be squashed when there are
> > > multiple commits. If "Create a merge commit" is used, each commit will
> be
> > > merged and does not contain the PR# in the title. When creating release
> > > notes, I need to manually review those commits to identify what PR it
> > came
> > > from to include the PR linking. Some times, depending on if they are
> all
> > > related commits, I need to manually group them and create a meaningful
> > > title for the release notes which I would prefer to have been done
> > > beforehand.
> > >
> > >
> > > On Wed, Oct 2, 2019 at 12:51 AM Jesse  wrote:
> > >
> > > > -1 for protected master branches, we are a small group of committers
> > and
> > > > don't need rules to keep us honest.
> > > > Protecting master would involve infra, as we cannot manage the
> minutia
> > in
> > > > github.  I think we all do this anyway except for rare occasions.
> > > >
> > > > +1 for squash and merge, as long as the meaningful individual commit
> > > > messages get consolidated into the 1 commit.
> > > >
> > > > On Tue, Oct 1, 2019 at 8:36 AM Norman Breau 
> > > > wrote:
> > > >
> > > > > +1 to protect the master branch.
> > > > >
> > > > > Forcing PR will help organize commits if we need to go back in
> > > > > time to determine the reason why a change was made as the
> > > > > commit in github will show the corresponding PR. Which will
> > > > > (hopefully) be properly filled out with context and motivation,
> > > > > as well as the issues that the PR resolves.
> > > > >
> > > > > +1 for "squash + merge" as a default strategy.
> > > > >
> > > > > I feel like most of the time having all the individual commits that
> > > > > makes up a PR is not really necessary. Most of the time it's
> > > > > bloated with tweaks fixing errors that was introduced during the
> > > > > development of the PR or perhaps refactoring for code style, etc.
> > > > > If there are instances where squash shouldn't be used, that can
> > > > > be decided on a per-case basis in my opinion.
> > > > >
> > > > > On 2019-10-01 10:37 a.m., Chris Brody wrote:
> > > > > > I would agree that "squash + merge" should be used in *most*
> cases,
> > > > > > and I think there is no dispute on this point.
> > > > > >
> > > > > > In the few cases where there are too many things for a "squash +
> > > > > > merge" commit, and we have the changes down to a limited number
> o

Re: [BOARD REPORT DRAFT] September 2019 Cordova Board Report

[gandhi rajan]

Looks perfect.

On Wednesday, September 11, 2019, Jesse  wrote:

> Please review and comment here.
>
> https://github.com/apache/cordova-apache-board-reports/
> blob/master/2019/2019-09.md
>
> Sorry for the lateness of this email, the report is due today.
>
> Cheers,
>  Jesse
>


-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Re: [Cordova dev] info needed label

[gandhi rajan]

+1 Makes sense.

On Tuesday, July 16, 2019, Chris Brody  wrote:

> We receive a number of support issues where I think we need an
> explicit label such as “info needed”, to make it clear that more
> information is needed before we can provide any support. I think we
> need to add this label to a number of repos such as apache/cordova,
> cordova-android, cordova-ios, etc.
>
> Any objections if I would add this label to some of the repos on GitHub?
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Re: how to add and use admob for app phonegap-vue

[gandhi rajan]

Hi,

I suggest you to ask your clarification in https://stackoverflow.com/ under
Cordova tag as this mailing list is meant for Cordova developers

On Monday, July 8, 2019, dam manh duc  wrote:

> Hello Apache Cordova Team!
> I am using phonegap and vue  for
> my
> app. but i don't know how to add and use addmob.
> If only using phonegap(not use vue), I usually use plugin phonegap-admob
>  to display admob ads. But
> combined with vue, I don't know how to do it.
> When i run command npm install phonegap-admob. And then add 'import admob
> from phonegap-admob' to file. it show error
>
> Please help me.
>
> --
> 
> ---   DUCDM87   ---
> 
>
> -- Many thanks and best regards!
>
> *Mobile*: *0979390590*
> *Email*: ducd...@gmail.com
>


-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Re: [DISCUSS] non-global Cordova installs

[gandhi rajan]

Hi Dmitry,

I second you on this.

On Tuesday, May 14, 2019, Dmitry Blotsky  wrote:

> I'm really glad this discussion lit up, because it clearly shows that this
> issue isn't settled.
>
> I personally have few opinions about the "best" solution here, but I
> firmly believe that npx is a non-starter for these 2 reasons:
> 1. It is strictly less secure than the status quo, and all alternatives.
> It is literally downloading code from hundreds of untrusted parties and
> immediately running it. It's worse than piping a curl command into bash (at
> least you can check the curl command's URL, or checksum the downloaded
> script).
> 2. It is strictly less stable than a local installation because now every
> call to Cordova goes through an opaque dependency.
>
> Unless both of those can be addressed, I think we shouldn't consider npx.
>
> Dmitry
>
> > On May 10, 2019, at 4:31 PM, Oliver Salzburg 
> wrote:
> >
> > Our DX is not good and this proposal would have the potential to have a
> > positive impact on that. I'm sorry that you're not convinced yet.
> >
> > Because I don't want to skip back and forth between GitHub and the
> > mailing list, I'll address your points here.
> >
> > - When you start a new project, unless you create a new cordova project
> > every week, you'll download cordova. npx will only help you in
> > downloading the package and if you have downloaded it in the past, it
> > will be pulled from the cache.
> >
> > - Yes, the Cordova CLI behavior can change over time, which is exactly
> > why you would not want to share a single global version with all of your
> > projects. I consider this a pro-local point.
> >
> > - It is 4 more characters to type. Yes. I give you that. But if you want
> > to interact with a local installation of cordova, what exactly is the
> > alternative? Not installing locally? I disagree.
> >
> > - Your suggestion regarding writing a completely new module to initiate
> > a cordova project is completely besides the point here. If you had that
> > module, you'd still want to use it with npx. And using `npx cordova`
> > pulls cordova into the cache where you are going to want to have it
> > anyway. If you had a slimmed down module, you now still need to download
> > cordova.
> >
> > By using npx, given your usage examples, you would have less downloads
> > instead of more.
> >
> > I'm sorry, Brody, I don't see your points and I don't feel like they
> > have been weighed appropriately against the benefits I proposed earlier.
> >
> > I would also appreciate it if we could try to keep the conversation to a
> > single media. The split between mailing list and GitHub is not
> constructive.
> >
> > Almost like putting part of your application in a global context and
> > another part in a local context is not constructive...
> >
> > On 2019-05-10 23:08, Chris Brody wrote:
> >> I am very sorry to say that I am still not convinced about this idea.
> >> I just raised some concerns in a recent comment in:
> >> https://github.com/apache/cordova-docs/issues/838
> >>
> >> And I think I am not the only one right now.
> >>
> >> As I said in cordova-docs#838, I would favor that we mention using
> >> `npx cordova` *as an option* in a limited number of places.
> >>
> >> I would like to express my appreciation to Oliver for the time and
> >> effort has given to improve the documentation, and to contribute a
> >> number of updates and fixes in the past. But I would rather take the
> >> extra time and effort to ensure we keep up the best app DX we can.
> >>
> >> And I don't really follow what you mean about CORDOVA_CMDLINE, would
> >> probably be easiest if we keep it in a separate discussion thread or
> >> issue.
> >>
> >> On Fri, May 10, 2019 at 3:05 PM Oliver Salzburg
> >>  wrote:
> >>>
> >>> I have already started working on a PR to make the necessary changes to
> >>> the documentation, as I was under the impression that consensus
> >>> regarding this issue was already reached:
> >>>
> >>> https://github.com/apache/cordova-docs/pull/987
> >>>
> >>> Specifically this might be of interest:
> >>>
> >>> https://github.com/apache/cordova-docs/blob/
> 04363c2796199f5379fa2b5f99ac8b1a488a/www/docs/en/dev/
> guide/cli/index.md
> >>>
> >>> I believe installing the cordova dependency as a devDependency should
> be
> >>> part of the "create" task. I was planning to propose the necessary
> >>> changes in another PR, but the freshly ignited debate caused me to hold
> >>> on that.
> >>>
> >>> I also brought up another area of concern regarding CORDOVA_CMDLINE in
> >>> hooks. I mentioned this in the PR.
> >>>
> >>>
> >>> On 2019-05-10 20:42, Jesse wrote:
>  Also thanks for the comprehensive write-up Oliver!
> 
>  Yeah, I am good with a move to recommend npx.
>  I just ran thru the steps and everything seems to work fine with it.
> 
>  One other reservation I had was just about network usage, and being
>  sensitive to places where bandwidth during the day is extremely
> costly

Re: [DISCUSS] Node 6.x & 8.x Deprecation & Node 12.x Support

[gandhi rajan]

+1

However waiting till December will be a safe bet I feel.

On Wednesday, April 10, 2019, Bryan Ellis  wrote:

> I would like to start the discussion around Cordova's planning for
> deprecating Node 6.x and Node 8.x as well as starting to support Node 12.x.
>
> Since Node 6.x is being deprecated by the end of this month, I am not
> expecting drastic action.
>
> Additionally, Node 8.x is expected to be deprecated by December.
>
> IMO, we could hold out till December to deprecate both versions and just
> warn users about our recommendation to upgrade in the meantime. These
> notices and warnings can be added in April and September as a patch or
> minor release.
>
> As a side note, I suspect Android Q's release (August?) and possible iOS
> (Sept?) to be out before December. For a major release for these new
> platforms, adding Node will fall in nicely.
>
> Blog Post PR: https://github.com/apache/cordova-docs/pull/965
> GH Issue Ticket: https://github.com/apache/cordova/issues/79



-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Re: [VOTE] cordova-lib@9.0.1 Release

[gandhi rajan]

+1



On Monday, April 1, 2019, Darryl Pogue  wrote:

> Please review and vote on this cordova-lib release by replying to this
> email (and keep discussion on the DISCUSS thread)
>
> Artifacts have been published to dist/dev:
> https://dist.apache.org/repos/dist/dev/cordova/lib901/
>
> The packages were published from their corresponding git tags:
> cordova-lib: 9.0.1 (d4a0938385)
>
> Upon a successful vote I will upload the archives to dist/, and
> publish them to npm. I don't personally think a blog post is needed
> for a patch update to a non-user-facing library, but I'll bring that
> up in the DISCUSS thread.
>
> Voting guidelines:
> https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
>
> Voting will go on for a minimum of 48 hours.
>
> I vote +1:
> * Ran coho audit-license-headers over the relevant repos
> * Ran coho check-license to ensure all dependencies and
> subdependencies have Apache-compatible licenses
> * Ensured continuous build was green when repos were tagged
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Great team work

[gandhi rajan]

Hi All,

It feels really happy to see Apache Cordova in the list of 20 innovative
apache projects - https://opensource.com/article/19/3/apache-projects

Thanks to each and everyone who contributed to the success of this project.
We should feel proud about our team work. Cheers.

Regards,
Gandhi.


-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Re: cordova in appbrowser issue

[gandhi rajan]

As far as I know, inapp browser plugin is for rendering links within the
app. For file download, you may have to use file download plugin.

Regards,
Gandhi

On Thursday, March 21, 2019, Naresh Raju Upendram <
naresh.upend...@compugain.com> wrote:

> Hi Dev Team,
>
>
> I am opening an URL in inappbrowser using cordova and open URL generates
> the pdf file after ticket reservation completes.But i am unable to download
> that file on device.
>
> Could you please let me know? what was issue with this.
>
>
> thanks,
>
> Thanks & Regards,
>
> U.Naresh Raju,
>
> Module Lead-Mobile Development,
>
> CompuGain Solutions India Pvt Ltd,
>
> Tower 2.1 (2nd Floor), TSI Business Parks (Hyd) Pvt. Ltd SEZ,
>
> Nanakramguda, Gachibowli, Hyderabad - 500081, (INDIA).
>
> E-mail: naresh.upend...@compugain.com
>
> Mobile No: +91-6309819887.
>
> Desk Phone:  001-7034540677 | 040-67222777.
>
> Websites: http://www.compugain-solutions.com compugain-solutions.com/>
>
>

-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Re: Contributor Introduction

[gandhi rajan]

Welcome Gedas. Nice to hear from you.

Regards,
Gandhi

On Thursday, March 7, 2019, Gedas Gardauskas 
wrote:

> Hello,
>
> My name is Gedas Gardauskas. Currently, I am working at Monaca as a
> Software Engineer. For the past few months, I have been actively
> contributing to the Cordova framework, mostly Electron platform. Here is
> some of the work I have done so far:
>
> https://github.com/search?q=org%3Aapache+author%3AGedasGa&type=Issues
>
> On top of development, I would like to be more engaged in Cordova’s and
> Apache's workflow. I would like to provide help in any way I can.
>


-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

[dev] some bad press

[gandhi rajan]

I completely agree with Oliver. My personal opinion is when genius like
Nikola Tesla was under rated we need not worry much about popularity. As
long as we feel motivated to contribute to the framework and serve the end
users we should feel proud.

Regards,
Gandhi.

On Friday, January 25, 2019, Oliver Salzburg 
wrote:

> Why do you feel the need to be competitive? Isn't it enough to serve all
> the existing users that appreciate the framework as it is?
>
> Seems fine to me. And popularity is a pretty bad quality indicator IMHO,
> especially when the source is the SO community.
>
> On 2019-01-24 19:31, Chris Brody wrote:
>
>> I recently saw an article about app frameworks, where Cordova sadly
>> shows up as the most dreaded framework in an image near the end:
>> https://medium.com/zerotomastery/tech-trends-showdown-react-
>> vs-angular-vs-vue-61ffaf1d8706
>>
>> and I just raised a minor usability issue:
>> https://github.com/apache/cordova/issues/71
>>
>> And this is just the tip of the iceberg.
>>
>> It makes me pretty sad to see this kind of bad press despite the
>> amount of efforts taken over the years to update and maintain such a
>> widely used framework.
>>
>> I am starting to wonder if it is worth the amount of effort needed for
>> Cordova to remain competitive with alternatives such as Capacitor and
>> React Native.
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
>> For additional commands, e-mail: dev-h...@cordova.apache.org
>>
>>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Re: [VOTE] Cordova Node Xcode 2.0.0 Release

[gandhi rajan]

+1

Ran coho audit-license-headers
Ran coho check-license


On Tuesday, January 15, 2019, Bryan Ellis  wrote:

> Please review and vote on this Cordova Node Xcode 2.0.0 Release
> by replying to this email (and keep discussion on the DISCUSS thread)
>
> DISCUSS thread:
> https://lists.apache.org/thread.html/33faba601f6d624c7b3c69ca863285
> 2c2a52bbbf98a09c27c8180ef5@%3Cdev.cordova.apache.org%3E
>
> Release issue: https://github.com/apache/cordova/issues/10
>
> xcode-2.0.0 have been published to dist/dev:
> https://dist.apache.org/repos/dist/dev/cordova/GH-10/
>
> The packages were published from their corresponding git tags:
>
> cordova-node-xcode: 2.0.0 (1acf05)
>
> Upon a successful vote I will upload the archives to dist/, publish them to
> npm, and post the corresponding blog post.
>
> Voting guidelines:
> https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
>
> Voting will go on for a minimum of 48 hours.
>
> I vote +1:
> * Ran coho audit-license-headers over the relevant repos
> * Ran coho check-license to ensure all dependencies and subdependencies
> have Apache-compatible licenses
> * Ensured continuous build was green when repos were tagged
>


-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Re: Nomination for a new chair for Apache Cordova

[gandhi rajan]

Hi Shazron,

Thanks for all your hard work and we respect your decision.

+1 to Jesse for his responsiveness and willingness to help others.

On Friday, December 7, 2018, Shazron  wrote:

> Hello beloved Community!
> I have been the chair of Apache Cordova since around April 2014 (~4.5
> years).
>
> The duties are mostly administrative: board reports, PMC management
> etc. Some of it is listed here in the README:
> https://github.com/apache/cordova-apache-board-reports
>
> I think it is time for new leadership. I have decided to resign my
> duties as the Apache Cordova chair, hopefully for the upcoming new
> year of 2019.
>
> I nominate Jesse MacFadyen as the next chair. Jesse has been with me
> at the start when Cordova was PhoneGap. Although we didn't give birth
> to it, we helped work on improving Cordova from being an infant to
> adulthood (together with our great team), particularly on cordova-ios.
> 10 years is adulthood in software!
>
> He has also contributed greatly to the other platforms and tooling,
> particularly cordova-windows. He has the most experience with helping
> run the Cordova project out of the remaining active contributors.
>
> As an Apache Member (https://www.apache.org/foundation/members.html)
> he also understands and helps uphold 'The Apache Way'
> (https://www.apache.org/foundation/how-it-works.html) and will be a
> great liaison with the Board.
>
> I'm not going anywhere and I will still contribute to the project in
> my areas of expertise.
>
> Thank you.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Re: [DISCUSS] cordova-android@7.1.4 accelerated hotfix release coming

[gandhi rajan]

Apologies for raising concerns on the same thread. Will try out the
suggestion and let you know.

On Saturday, November 24, 2018, Jan Piotrowski  wrote:

> (You should have create a new thread instead of replying to this old
> one for this. Please do so in the future)
>
> I can recreate that issue when using the current mobilespec
> instructions. I reported it in the CLI repository:
> https://github.com/apache/cordova-cli/issues/362
>
> But I am currently also working through the whole mobilespec project
> (see the thread I created yesterday here) and will create several PRs
> to fix the instructions.
>
> If you _just_ want to have a working mobilespec project, use the
> `--global` argument for `createmobilespec.js`. This uses the global
> `cordova` and downloads the platforms and plugins from NPM, but it
> creates a working app.
>
> -J
> Am Sa., 24. Nov. 2018 um 08:21 Uhr schrieb gandhi rajan
> :
> >
> > Hi Chris and Jan,
> >
> > Recently I was working on mobilespec project for testing android
> platform.
> > But for past two patches I m not able to create mobilespec project
> > successfully which I made it work earlier after discussion with Jan on
> > Slack. While trying to create mobilespec project, I get the error trace
> as
> > mentioned in the link - https://imgur.com/a/jDHIlAB
> >
> > You were able to build the project with latest code without any error?
> Am I
> > missing something? Please let me know
> >
> > On Fri, Nov 23, 2018 at 6:58 PM Chris Brody 
> wrote:
> >
> > > 1-2 more votes on the VOTE thread would be appreciated.
> > >
> > > I updated the mobilespec document as requested and recorded my
> > > findings on mobilespec in https://github.com/apache/cordova/issues/54
> > > On Fri, Nov 23, 2018 at 6:33 AM Jan Piotrowski 
> > > wrote:
> > > >
> > > > Great, please also update mobilespec documentation on how to use this
> > > > - that really needs some refreshing.
> > > > Am Fr., 23. Nov. 2018 um 02:18 Uhr schrieb Chris Brody <
> > > chris.br...@gmail.com>:
> > > > >
> > > > > I just built and ran the mobilespec, with quite a bit of trial and
> > > > > error, will report in issue 54 when I get a chance. I was able to
> get
> > > > > most of the "automatic" mobilespec tests to succeed, but selecting
> 1
> > > > > plugin at a time to run the tests on. I will go ahead with the
> patch
> > > > > release now.
> > > > > On Thu, Nov 22, 2018 at 5:37 PM Jan Piotrowski <
> piotrow...@gmail.com>
> > > wrote:
> > > > > >
> > > > > > I created https://github.com/apache/cordova/issues/54 for the
> work
> > > on
> > > > > > or discussion about this.
> > > > > > Am Do., 22. Nov. 2018 um 23:22 Uhr schrieb julio cesar sanchez
> > > > > > :
> > > > > > >
> > > > > > > Yeah, I agree, we shouldn’t delay because of that, but we
> should
> > > definitely
> > > > > > > figure it out before next major release
> > > > > > >
> > > > > > > El El jue, 22 nov 2018 a las 23:12, Jan Piotrowski <
> > > piotrow...@gmail.com>
> > > > > > > escribió:
> > > > > > >
> > > > > > > > No reason to slow down the release process - anyone can do
> that
> > > for
> > > > > > > > themselves and -1 the release vote if it shows a problem.
> > > > > > > > Am Do., 22. Nov. 2018 um 20:55 Uhr schrieb Chris Brody <
> > > > > > > > chris.br...@gmail.com>:
> > > > > > > > >
> > > > > > > > > I can look into that tomorrow. It would definitely delay
> the
> > > release,
> > > > > > > > > unless someone else wants to pick this up.
> > > > > > > > > On Thu, Nov 22, 2018 at 2:45 PM Darryl Pogue <
> > > dvpdin...@gmail.com>
> > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > Can we please try to figure out how to run mobilespec or
> > > paramedic or
> > > > > > > > > > some sort of regression test against our core plugins
> before
> > > > 

Re: [DISCUSS] cordova-android@7.1.4 accelerated hotfix release coming

[gandhi rajan]

Hi Chris and Jan,

Recently I was working on mobilespec project for testing android platform.
But for past two patches I m not able to create mobilespec project
successfully which I made it work earlier after discussion with Jan on
Slack. While trying to create mobilespec project, I get the error trace as
mentioned in the link - https://imgur.com/a/jDHIlAB

You were able to build the project with latest code without any error? Am I
missing something? Please let me know

On Fri, Nov 23, 2018 at 6:58 PM Chris Brody  wrote:

> 1-2 more votes on the VOTE thread would be appreciated.
>
> I updated the mobilespec document as requested and recorded my
> findings on mobilespec in https://github.com/apache/cordova/issues/54
> On Fri, Nov 23, 2018 at 6:33 AM Jan Piotrowski 
> wrote:
> >
> > Great, please also update mobilespec documentation on how to use this
> > - that really needs some refreshing.
> > Am Fr., 23. Nov. 2018 um 02:18 Uhr schrieb Chris Brody <
> chris.br...@gmail.com>:
> > >
> > > I just built and ran the mobilespec, with quite a bit of trial and
> > > error, will report in issue 54 when I get a chance. I was able to get
> > > most of the "automatic" mobilespec tests to succeed, but selecting 1
> > > plugin at a time to run the tests on. I will go ahead with the patch
> > > release now.
> > > On Thu, Nov 22, 2018 at 5:37 PM Jan Piotrowski 
> wrote:
> > > >
> > > > I created https://github.com/apache/cordova/issues/54 for the work
> on
> > > > or discussion about this.
> > > > Am Do., 22. Nov. 2018 um 23:22 Uhr schrieb julio cesar sanchez
> > > > :
> > > > >
> > > > > Yeah, I agree, we shouldn’t delay because of that, but we should
> definitely
> > > > > figure it out before next major release
> > > > >
> > > > > El El jue, 22 nov 2018 a las 23:12, Jan Piotrowski <
> piotrow...@gmail.com>
> > > > > escribió:
> > > > >
> > > > > > No reason to slow down the release process - anyone can do that
> for
> > > > > > themselves and -1 the release vote if it shows a problem.
> > > > > > Am Do., 22. Nov. 2018 um 20:55 Uhr schrieb Chris Brody <
> > > > > > chris.br...@gmail.com>:
> > > > > > >
> > > > > > > I can look into that tomorrow. It would definitely delay the
> release,
> > > > > > > unless someone else wants to pick this up.
> > > > > > > On Thu, Nov 22, 2018 at 2:45 PM Darryl Pogue <
> dvpdin...@gmail.com>
> > > > > > wrote:
> > > > > > > >
> > > > > > > > Can we please try to figure out how to run mobilespec or
> paramedic or
> > > > > > > > some sort of regression test against our core plugins before
> > > > > > > > releasing?
> > > > > > > >
> > > > > > > > On Thu, Nov 22, 2018 at 11:36 AM Chris Brody <
> chris.br...@gmail.com>
> > > > > > wrote:
> > > > > > > > >
> > > > > > > > > Does anyone have any reason to delay a
> cordova-android@7.1.4
> > > > > > > > > accelerated hotfix release?
> > > > > > > > >
> > > > > > > > > Any outstanding patches to land?
> > > > > > > > >
> > > > > > > > > If not, I will start the release now.
> > > > > > > > >
> > > > > > > > >
> -
> > > > > > > > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > > > > > > > > For additional commands, e-mail:
> dev-h...@cordova.apache.org
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> -
> > > > > > > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > > > > > > > For additional commands, e-mail: dev-h...@cordova.apache.org
> > > > > > > >
> > > > > > >
> > > > > > >
> -
> > > > > > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > > > > > > For additional commands, e-mail: dev-h...@cordova.apache.org
> > > > > > >
> > > > > >
> > > > > >
> -
> > > > > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > > > > > For additional commands, e-mail: dev-h...@cordova.apache.org
> > > > > >
> > > > > >
> > > >
> > > > -
> > > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > > > For additional commands, e-mail: dev-h...@cordova.apache.org
> > > >
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > > For additional commands, e-mail: dev-h...@cordova.apache.org
> > >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > For additional commands, e-mail: dev-h...@cordova.apache.org
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

-- 
Regards,
Gandhi

"The best way to find urself is to lose ur

Re: [VOTE] cordova-android 7.1.3 patch release

[gandhi rajan]

+1

npm audit successful
License check successful
Was able to create new project and add & build Android platform with out
any error.

On Tuesday, November 20, 2018, Darryl Pogue  wrote:

> +1
>
> - npm audit all good
> - ran coho verify-archive over release artifacts
>
> On Mon, Nov 19, 2018 at 3:43 PM Jesse  wrote:
> >
> > +1
> >
> > - npm audit all good
> > - ran coho verify-archive over release artifacts
> > - created a new cordova project, and added cordova-android platform (
> from
> > filesystem ) and build+ran on emulator
> >
> >
> > @purplecabbage
> > risingj.com
> >
> >
> > On Mon, Nov 19, 2018 at 2:17 PM Chris Brody 
> wrote:
> >
> > > Please review and vote on this cordova-android 7.1.3 patch release, by
> > > replying to this email (and keep discussion on the DISCUSS thread)
> > >
> > > Release changes as proposed in:
> > > https://github.com/apache/cordova-android/pull/555
> > >
> > > The archive has been published to dist/dev:
> > > https://dist.apache.org/repos/dist/dev/cordova/GH-555/
> > >
> > > The package was published from its corresponding git tag:
> > > cordova-android: 7.1.3 (e1befaca5a)
> > >
> > > Note that you can test it out via:
> > >
> > > cordova platform add https://github.com/apache/
> cordova-android#7.1.3
> > >
> > > Upon a successful vote I will upload the archive to dist/, publish it
> > > to npm, and post the blog post.
> > >
> > > Voting guidelines:
> > > https://github.com/apache/cordova-coho/blob/master/docs/
> release-voting.md
> > >
> > > Voting will go on for a minimum of 48 hours.
> > >
> > > I vote +1:
> > > * npm audit shows 0 vulnerabilities
> > > * Ran coho audit-license-headers over the relevant repos
> > > * Ran coho check-license to ensure all dependencies and
> > >   subdependencies have Apache-compatible licenses
> > > * Ensured continuous build was green when repo was tagged
> > > * Able to run self test on:
> > >   https://github.com/brodybits/cordova-sqlite-test-app
> > >   with cordova-android version e1befac (7.1.3) from local file system,
> > >   along with cordova-sqlite-storage@2.1.5 (with old plugin JAR & .so
> > > directory mapping)
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > > For additional commands, e-mail: dev-h...@cordova.apache.org
> > >
> > >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Re: [DISCUSS] cordova-android@7.1.3 patch release, any objections?

[gandhi rajan]

Hi Chris and Julio, My bad. Seems to be an issue with npm cache. Cleared
npm cache and retried complete stuff from fresh check out and it worked.
Was able to add test project successfully.

But still couldn't get that mobilespec project created successfully which I
fixed sometime back before this new release. Has someone tried it?

On Wednesday, November 21, 2018, Chris Brody  wrote:

> Can you confirm which version of Cordova CLI you are using?
>
> Am I correct that you are using mac OS 10.13 or 10.14?
>
> Would you mind raising an issue with the information about the
> "cordova-android version check failed" error you encountered?
>
> I already found the "version check failed" in 2 places in cordova-lib (2
> places in src/plugman/install.js). It would be nice if we could reproduce
> and fix it somehow (a Cordova project may really help us). I still don't
> know how to reproduce it myself, so far.
>
> @Gandhi if you could also post the error message, Cordova CLI version, and
> what kind of development platform it could really help us. Demo project
> could also be helpful.
>
> While not a major blocker it would be nice to get this fixed, if possible.
>
> On Tue, Nov 20, 2018 at 2:25 PM Jesse  wrote:
>
> > Installing "cordova-plugin-whitelist" for android
> >
> > cordova-android version check failed
> > ("/Users/jessem/test/android713/platforms/android/cordova/version"),
> > continuing anyways.
> >
> >
> > This plugin is only applicable for versions of cordova-android greater
> than
> > 4.0. If you have a previous platform version, you do *not* need this
> plugin
> > since the whitelist will be built in.
> >
> >
> >
> > Yeah, same I had it backwards.
> >
> > @purplecabbage
> > risingj.com
> >
> >
> > On Tue, Nov 20, 2018 at 10:34 AM julio cesar sanchez <
> > jcesarmob...@gmail.com>
> > wrote:
> >
> > > Yeah, that's not an error, it's an info message and might be a bit
> > > confusing, but what it says it's the opposite of what Jesse said, it
> says
> > > "This plugin is only applicable for versions of
> > > cordova-android greater than 4.0", which is the case, and installs fine
> > on
> > > my computer.
> > >
> > > El mar., 20 nov. 2018 a las 18:59, Jesse ()
> > > escribió:
> > >
> > > > Yes. I will. When I get to the office ;)
> > > >
> > > > > On Nov 20, 2018, at 9:40 AM, Oliver Salzburg <
> > > oliver.salzb...@gmail.com>
> > > > wrote:
> > > > >
> > > > > Maybe it's time to get rid of the warning? It was confusing me as
> > well
> > > > when
> > > > > I first saw it and that was already quite some time ago.
> > > > >
> > > > > On Tue, Nov 20, 2018 at 6:38 PM gandhi rajan <
> > gandhiraja...@gmail.com>
> > > > > wrote:
> > > > >
> > > > >> Ya Jesse. While creating hello world app as mentioned in
> > > > >>
> > > > >>
> > > >
> > >
> > https://github.com/apache/cordova-coho/blob/master/docs/
> platforms-release-process.md#2-hello-world-app-with-cordova-cli
> > > > >> I got the error regarding plugin installation but android platform
> > > > addition
> > > > >> was successful. As you said its not a blocker. But unfortunately
> I m
> > > not
> > > > >> able to provide the details Julio asked for as the setup is in my
> > > office
> > > > >> desktop. Will get back with more details on this.
> > > > >>
> > > > >>> On Tue, Nov 20, 2018 at 11:01 PM Jesse 
> > > > wrote:
> > > > >>>
> > > > >>> There is a reported error in the output, the android template app
> > > > >> includes
> > > > >>> the whitelist plugin, but the plugin itself only supports older
> > > > versions
> > > > >> of
> > > > >>> Cordova-android.
> > > > >>>
> > > > >>> The message is something like ‘failed to install plugin ...
> moving
> > > on’.
> > > > >>> Ultimately not an issue other than the appearance that something
> > has
> > > > gone
> > > > >>> wrong. Not a blocker, imho.
> > > > >>>
> > > > >>>> On Nov 20, 2018, at 9:13 AM, gandhi rajan <

Re: [DISCUSS] cordova-android@7.1.3 patch release, any objections?

[gandhi rajan]

Ya Jesse. While creating hello world app as mentioned in
https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md#2-hello-world-app-with-cordova-cli
I got the error regarding plugin installation but android platform addition
was successful. As you said its not a blocker. But unfortunately I m not
able to provide the details Julio asked for as the setup is in my office
desktop. Will get back with more details on this.

On Tue, Nov 20, 2018 at 11:01 PM Jesse  wrote:

> There is a reported error in the output, the android template app includes
> the whitelist plugin, but the plugin itself only supports older versions of
> Cordova-android.
>
> The message is something like ‘failed to install plugin ... moving on’.
> Ultimately not an issue other than the appearance that something has gone
> wrong. Not a blocker, imho.
>
> > On Nov 20, 2018, at 9:13 AM, gandhi rajan 
> wrote:
> >
> > Hi Julio,
> >
> > Thanks for the response. Will have a check on this tomorrow and get back
> to
> > you on this.
> >
> > On Tue, Nov 20, 2018 at 10:41 PM julio cesar sanchez <
> jcesarmob...@gmail.com>
> > wrote:
> >
> >> What's your CLI version?
> >> What error did you get?
> >> node and npm versions?
> >>
> >> It's installing fine on my computer
> >>
> >> El mar., 20 nov. 2018 a las 17:51, gandhi rajan (<
> gandhiraja...@gmail.com
> >>> )
> >> escribió:
> >>
> >>> Hi All,
> >>>
> >>> While testing Cordova Android 7.1.3, license check and npm audit
> passed.
> >>>
> >>> But while executing "cordova platform add
> >>> https://github.com/apache/cordova-android#7.1.3 " , android platform
> >> added
> >>> successfully but whitelist plugin dint got added and failed with error.
> >> Am
> >>> I missing something?
> >>>
> >>> cordova platform add https://github.com/apache/cordova-android#7.1.3
> >>>
> >>> On Mon, Nov 19, 2018 at 9:33 PM julio cesar sanchez <
> >>> jcesarmob...@gmail.com>
> >>> wrote:
> >>>
> >>>> +1, ship it
> >>>>
> >>>> El dom., 18 nov. 2018 a las 1:51, Chris Brody ( >>> )
> >>>> escribió:
> >>>>
> >>>>> Does anyone have any reason to delay a cordova-_android_ platform
> >>>> release?
> >>>>>
> >>>>> Any outstanding patches to land?
> >>>>>
> >>>>> If not, I will start the release tomorrow.
> >>>>>
> >>>>> -
> >>>>> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> >>>>> For additional commands, e-mail: dev-h...@cordova.apache.org
> >>>>>
> >>>>>
> >>>>
> >>>
> >>>
> >>> --
> >>> Regards,
> >>> Gandhi
> >>>
> >>> "The best way to find urself is to lose urself in the service of others
> >>> !!!"
> >>>
> >>
> >
> >
> > --
> > Regards,
> > Gandhi
> >
> > "The best way to find urself is to lose urself in the service of others
> !!!"
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Re: [DISCUSS] cordova-android@7.1.3 patch release, any objections?

[gandhi rajan]

Hi Julio,

Thanks for the response. Will have a check on this tomorrow and get back to
you on this.

On Tue, Nov 20, 2018 at 10:41 PM julio cesar sanchez 
wrote:

> What's your CLI version?
> What error did you get?
> node and npm versions?
>
> It's installing fine on my computer
>
> El mar., 20 nov. 2018 a las 17:51, gandhi rajan ( >)
> escribió:
>
> > Hi All,
> >
> > While testing Cordova Android 7.1.3, license check and npm audit passed.
> >
> >  But while executing "cordova platform add
> > https://github.com/apache/cordova-android#7.1.3 " , android platform
> added
> > successfully but whitelist plugin dint got added and failed with error.
> Am
> > I missing something?
> >
> > cordova platform add https://github.com/apache/cordova-android#7.1.3
> >
> > On Mon, Nov 19, 2018 at 9:33 PM julio cesar sanchez <
> > jcesarmob...@gmail.com>
> > wrote:
> >
> > > +1, ship it
> > >
> > > El dom., 18 nov. 2018 a las 1:51, Chris Brody ( >)
> > > escribió:
> > >
> > > > Does anyone have any reason to delay a cordova-_android_ platform
> > > release?
> > > >
> > > > Any outstanding patches to land?
> > > >
> > > > If not, I will start the release tomorrow.
> > > >
> > > > -
> > > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > > > For additional commands, e-mail: dev-h...@cordova.apache.org
> > > >
> > > >
> > >
> >
> >
> > --
> > Regards,
> > Gandhi
> >
> > "The best way to find urself is to lose urself in the service of others
> > !!!"
> >
>


-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Re: [DISCUSS] cordova-android@7.1.3 patch release, any objections?

[gandhi rajan]

Hi All,

While testing Cordova Android 7.1.3, license check and npm audit passed.

 But while executing "cordova platform add
https://github.com/apache/cordova-android#7.1.3 " , android platform added
successfully but whitelist plugin dint got added and failed with error. Am
I missing something?

cordova platform add https://github.com/apache/cordova-android#7.1.3

On Mon, Nov 19, 2018 at 9:33 PM julio cesar sanchez 
wrote:

> +1, ship it
>
> El dom., 18 nov. 2018 a las 1:51, Chris Brody ()
> escribió:
>
> > Does anyone have any reason to delay a cordova-_android_ platform
> release?
> >
> > Any outstanding patches to land?
> >
> > If not, I will start the release tomorrow.
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > For additional commands, e-mail: dev-h...@cordova.apache.org
> >
> >
>


-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Re: Facing issue in testing release process of Cordova platforms

[gandhi rajan]

Hi Jan,

Thanks for the response again. Please find my response inline.

On Thu, Nov 1, 2018 at 10:46 PM Jan Piotrowski  wrote:

> The documented command actually is just
> "./cordova-mobile-spec/createmobilespec/createmobilespec.js --android
> --forceplugins", without the "node" in front of it. But I am not sure
> if this is correct or just a bug in the documentation.
>
   *The documented command does not include node but this needs to be
included in order to run the js file in windows OS. As I mentioned earlier,*
*the existing documentation is more macOS oriented.*

>
> Please reply with the full command you are executing and the full
> output you are getting.
>

 *Please find the complete error trace on executing the documented command
and command with node in the link - https://imgur.com/a/tLyEWkq
<https://imgur.com/a/tLyEWkq> *


>
> > I did install cordova-js and cordova-lib modules ...
>
> Where did you run which command exactly to try to fix this?
>

  *I navigated to the respective folders and executed 'npm install'
command *

>
> Best,
> Jan
>
> PS: Yep, mobilespec is heavily underdocumented as most of the testing
> stuff.
>
>
> Am Do., 1. Nov. 2018 um 18:10 Uhr schrieb gandhi rajan
> :
> >
> > Hi Jan,
> >
> > Thanks for your response. I did checkout  all repos using the coho
> command
> > - "coho repo-update -g -r all"
> >
> > While trying to do plugin tests as mentioned in
> >
> https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md#1-plugin-tests-with-cordova-mobile-spec-project
> ,
> > I executed the following command in my windows system:
> >
> > "node ./cordova-mobile-spec/createmobilespec/createmobilespec.js
> --android
> > --forceplugins"
> >
> > I got the following error while executing the above command:
> >
> > "Error: Module cordova-js is not installed at all (direct or npm-linked)
> in
> > cordova-lib"
> >
> > I did install cordova-js and cordova-lib modules but couldn't get away
> from
> > this error. Jesse did pointed out that we dont do this test until we make
> > some breaking changes in platform but just curious to resolve this issue
> as
> > we may encounter this error anytime in future.
> >
> > Let me know your thoughts.
> >
> > On Wed, Oct 31, 2018 at 11:07 PM Jan Piotrowski 
> > wrote:
> >
> > > Gandhi, what exactly did you do until now? Do you have a checkout of
> > > all the Cordova repos created with coho?
> > >
> > > Please reply with the exact command you are running and error/output
> > > you are getting.
> > >
> > > J
> > > Am Sa., 27. Okt. 2018 um 11:02 Uhr schrieb gandhi rajan
> > > :
> > > >
> > > > Hi Raphinesse, Thanks for the Jasmine 3 update. I m now able to
> build and
> > > > install cordova-js module.
> > > >
> > > > @jesse, I tried the steps you mentioned to test platform and it
> works.
> > > But
> > > > I m still not able to create and run mobile-spec project.While
> running
> > > the
> > > > following command - "node
> > > > cordova-mobile-spec\createmobilespec\createmobilespec.js --android
> > > > --forceplugins", I get the following error - Error: Module
> cordova-js is
> > > > not installed at all (direct or npm-linked) in cordova-lib
> > > >
> > > > Any thoughts on this?
> > > >
> > > > On Thu, Oct 25, 2018 at 11:43 PM gandhi rajan <
> gandhiraja...@gmail.com>
> > > > wrote:
> > > >
> > > > > Thanks a lot for the response Jesse and Raphinesse. Will try out
> the
> > > > > suggested steps and check out the merge as well. Will get back with
> > > further
> > > > > updates if I m stuck.
> > > > >
> > > > > On Thursday, October 25, 2018,  wrote:
> > > > >
> > > > >> I already updated cordova-js to use more modern tooling some time
> ago
> > > in
> > > > >> https://github.com/apache/cordova-js/pull/176.  I just had not
> gotten
> > > > >> around to merging it yet. I did so just now.
> > > > >>
> > > > >> Jesse  schrieb am Do., 25. Okt. 2018,
> 10:19:
> > > > >>
> > > > >> > Hi Gandhi,
> > > > >> >
> > > > >> > There is an issue with this repo in that cordova-js uses a
> &g

Re: Facing issue in testing release process of Cordova platforms

[gandhi rajan]

Hi Jan,

Thanks for your response. I did checkout  all repos using the coho command
- "coho repo-update -g -r all"

While trying to do plugin tests as mentioned in
https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md#1-plugin-tests-with-cordova-mobile-spec-project,
I executed the following command in my windows system:

"node ./cordova-mobile-spec/createmobilespec/createmobilespec.js --android
--forceplugins"

I got the following error while executing the above command:

"Error: Module cordova-js is not installed at all (direct or npm-linked) in
cordova-lib"

I did install cordova-js and cordova-lib modules but couldn't get away from
this error. Jesse did pointed out that we dont do this test until we make
some breaking changes in platform but just curious to resolve this issue as
we may encounter this error anytime in future.

Let me know your thoughts.

On Wed, Oct 31, 2018 at 11:07 PM Jan Piotrowski 
wrote:

> Gandhi, what exactly did you do until now? Do you have a checkout of
> all the Cordova repos created with coho?
>
> Please reply with the exact command you are running and error/output
> you are getting.
>
> J
> Am Sa., 27. Okt. 2018 um 11:02 Uhr schrieb gandhi rajan
> :
> >
> > Hi Raphinesse, Thanks for the Jasmine 3 update. I m now able to build and
> > install cordova-js module.
> >
> > @jesse, I tried the steps you mentioned to test platform and it works.
> But
> > I m still not able to create and run mobile-spec project.While running
> the
> > following command - "node
> > cordova-mobile-spec\createmobilespec\createmobilespec.js --android
> > --forceplugins", I get the following error - Error: Module cordova-js is
> > not installed at all (direct or npm-linked) in cordova-lib
> >
> > Any thoughts on this?
> >
> > On Thu, Oct 25, 2018 at 11:43 PM gandhi rajan 
> > wrote:
> >
> > > Thanks a lot for the response Jesse and Raphinesse. Will try out the
> > > suggested steps and check out the merge as well. Will get back with
> further
> > > updates if I m stuck.
> > >
> > > On Thursday, October 25, 2018,  wrote:
> > >
> > >> I already updated cordova-js to use more modern tooling some time ago
> in
> > >> https://github.com/apache/cordova-js/pull/176.  I just had not gotten
> > >> around to merging it yet. I did so just now.
> > >>
> > >> Jesse  schrieb am Do., 25. Okt. 2018, 10:19:
> > >>
> > >> > Hi Gandhi,
> > >> >
> > >> > There is an issue with this repo in that cordova-js uses a
> jasmine-node
> > >> > version that depends on a non-secure version of growl.  This is not
> a
> > >> > trivial fix as moving to the recommended jasmine-node@2.0.1 is a
> > >> breaking
> > >> > change.
> > >> > I am not completely of the mind that updating is the right approach
> > >> here,
> > >> > as I think in many ways the cordova-js project is outdated, and the
> > >> whole
> > >> > process of generating platform specific cordova.js files needs to be
> > >> > rethought.
> > >> >
> > >> > Personally, this does not block me ... I do the following:
> > >> > ⚡ npm i
> > >> > audited 684 packages in 2.085s
> > >> > found 1 critical severity vulnerability
> > >> >   run `npm audit fix` to fix them, or `npm audit` for details
> > >> >
> > >> > ⚡ npx grunt
> > >> > ... succeeds
> > >> >
> > >> > ⚡ npx grunt compile:windows
> > >> > Running "compile:windows" (compile) task
> > >> > generated cordova.windows.js @
> 243e7aac8cee0108927df0253118e36857ab9fc7
> > >> in
> > >> > 5ms
> > >> > Done.
> > >> >
> > >> > The typical way a platform is released is to use cordova-coho.
> > >> > ex. `coho prepare-platform-release-branch -r cordova-android
> --version
> > >> > 9.9.9`
> > >> > This takes care of all the tagging, building/copying of cordova.js
> to
> > >> the
> > >> > correct platform folder.
> > >> >
> > >> > About the mobile-spec workflow, I have not done this is a long time,
> > >> this
> > >> > was more important when we were breaking things a lot.  One
> expectation
> > >> of
> > >> > the tooling that may not be explicitly listed is that all repos are
> &g

Re: Facing issue in testing release process of Cordova platforms

[gandhi rajan]

Hi Raphinesse, Thanks for the Jasmine 3 update. I m now able to build and
install cordova-js module.

@jesse, I tried the steps you mentioned to test platform and it works. But
I m still not able to create and run mobile-spec project.While running the
following command - "node
cordova-mobile-spec\createmobilespec\createmobilespec.js --android
--forceplugins", I get the following error - Error: Module cordova-js is
not installed at all (direct or npm-linked) in cordova-lib

Any thoughts on this?

On Thu, Oct 25, 2018 at 11:43 PM gandhi rajan 
wrote:

> Thanks a lot for the response Jesse and Raphinesse. Will try out the
> suggested steps and check out the merge as well. Will get back with further
> updates if I m stuck.
>
> On Thursday, October 25, 2018,  wrote:
>
>> I already updated cordova-js to use more modern tooling some time ago in
>> https://github.com/apache/cordova-js/pull/176.  I just had not gotten
>> around to merging it yet. I did so just now.
>>
>> Jesse  schrieb am Do., 25. Okt. 2018, 10:19:
>>
>> > Hi Gandhi,
>> >
>> > There is an issue with this repo in that cordova-js uses a jasmine-node
>> > version that depends on a non-secure version of growl.  This is not a
>> > trivial fix as moving to the recommended jasmine-node@2.0.1 is a
>> breaking
>> > change.
>> > I am not completely of the mind that updating is the right approach
>> here,
>> > as I think in many ways the cordova-js project is outdated, and the
>> whole
>> > process of generating platform specific cordova.js files needs to be
>> > rethought.
>> >
>> > Personally, this does not block me ... I do the following:
>> > ⚡ npm i
>> > audited 684 packages in 2.085s
>> > found 1 critical severity vulnerability
>> >   run `npm audit fix` to fix them, or `npm audit` for details
>> >
>> > ⚡ npx grunt
>> > ... succeeds
>> >
>> > ⚡ npx grunt compile:windows
>> > Running "compile:windows" (compile) task
>> > generated cordova.windows.js @ 243e7aac8cee0108927df0253118e36857ab9fc7
>> in
>> > 5ms
>> > Done.
>> >
>> > The typical way a platform is released is to use cordova-coho.
>> > ex. `coho prepare-platform-release-branch -r cordova-android --version
>> > 9.9.9`
>> > This takes care of all the tagging, building/copying of cordova.js to
>> the
>> > correct platform folder.
>> >
>> > About the mobile-spec workflow, I have not done this is a long time,
>> this
>> > was more important when we were breaking things a lot.  One expectation
>> of
>> > the tooling that may not be explicitly listed is that all repos are
>> > expected to be cloned as peers.  cordova-coho has commands that can help
>> > manage the multitude of repos for you.
>> >
>> > Not sure if this helps you move forward, I am happy to dig into this
>> more
>> > with you.
>> >
>> > Cheers,
>> >   Jesse
>> >
>> > @purplecabbage
>> > risingj.com
>> >
>> >
>> > On Tue, Oct 23, 2018 at 10:22 PM gandhi rajan 
>> > wrote:
>> >
>> > > Hi All,
>> > >
>> > > I was trying to understand the release process for Cordova platforms
>> as
>> > > mentioned in the following link -
>> > >
>> > >
>> >
>> https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md
>> > > .
>> > >
>> > > While following the steps mentioned to test plugins with
>> > > cordova-mobile-spec project, I got an error stating cordova-js module
>> is
>> > > not installed. When I tried to install cordova-js, the installation
>> fails
>> > > stating one critical severity vulnerability.On running npm audit on
>> > > cordova-js, it states that the critical vulnerability is related to
>> growl
>> > > version.
>> > >
>> > > Can someone let me know whether I m missing some steps which is
>> causing
>> > > this issue or it's a vulnerability that needs to be fixed as I m not
>> able
>> > > to proceed with cordova-js module installation?
>> > >
>> > > Any help is really appreciated. Thanks in advance.
>> > >
>> > >
>> > > --
>> > > Regards,
>> > > Gandhi
>> > >
>> > > "The best way to find urself is to lose urself in the service of
>> others
>> > > !!!"
>> > >
>> >
>>
>
>
> --
> Regards,
> Gandhi
>
> "The best way to find urself is to lose urself in the service of others
> !!!"
>
>

-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Re: [DISCUSS] cordova-android 7.1.2 patch release

[gandhi rajan]

Thanks a lot Chris. Will get in touch with you.

On Friday, October 26, 2018, Chris Brody  wrote:

> I should be able to assist you next week.
>
> On Thu, Oct 25, 2018, 12:51 PM gandhi rajan 
> wrote:
>
> > I can try out the release process but need some assistance as its first
> > time I m doing it. Anyone willing to provide some guidance for me in
> doing
> > this?
> >
> > On Thursday, October 25, 2018, Darryl Pogue  wrote:
> >
> > > Hey folks,
> > >
> > > There's been some issues with a bunch of packages published to Bintray
> > > jcenter, and we've been getting a lot of bug reports and PRs to
> > > reorder the repositories that gradle looks at. We've already merged a
> > > fix to master, and cherry-picked it to the 7.1.x branch (along with
> > > some other fixes).
> > >
> > > Julio also indicated that some of the cherry-picked fixes will resolve
> > > the longstanding issue of 3rd party plugin compatibility with the new
> > > Android Studio project structure.
> > >
> > > The list of changes and diff on the 7.1.x branch (since 7.1.1) is
> > > available for viewing at
> > > https://github.com/apache/cordova-android/compare/7.1.1...36c6f44
> > >
> > > Does anyone have any concerns or reasons to delay starting the release
> > > process for 7.1.2?
> > >
> > > Further to that, does anyone have time to start the release process?
> > > I'm swamped at work right now and unlikely to be able to look at it
> > > until mid-next week :(
> > >
> > > ~Darryl
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > > For additional commands, e-mail: dev-h...@cordova.apache.org
> > >
> > >
> >
> > --
> > Regards,
> > Gandhi
> >
> > "The best way to find urself is to lose urself in the service of others
> > !!!"
> >
>


-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Re: Facing issue in testing release process of Cordova platforms

[gandhi rajan]

Thanks a lot for the response Jesse and Raphinesse. Will try out the
suggested steps and check out the merge as well. Will get back with further
updates if I m stuck.

On Thursday, October 25, 2018,  wrote:

> I already updated cordova-js to use more modern tooling some time ago in
> https://github.com/apache/cordova-js/pull/176.  I just had not gotten
> around to merging it yet. I did so just now.
>
> Jesse  schrieb am Do., 25. Okt. 2018, 10:19:
>
> > Hi Gandhi,
> >
> > There is an issue with this repo in that cordova-js uses a jasmine-node
> > version that depends on a non-secure version of growl.  This is not a
> > trivial fix as moving to the recommended jasmine-node@2.0.1 is a
> breaking
> > change.
> > I am not completely of the mind that updating is the right approach here,
> > as I think in many ways the cordova-js project is outdated, and the whole
> > process of generating platform specific cordova.js files needs to be
> > rethought.
> >
> > Personally, this does not block me ... I do the following:
> > ⚡ npm i
> > audited 684 packages in 2.085s
> > found 1 critical severity vulnerability
> >   run `npm audit fix` to fix them, or `npm audit` for details
> >
> > ⚡ npx grunt
> > ... succeeds
> >
> > ⚡ npx grunt compile:windows
> > Running "compile:windows" (compile) task
> > generated cordova.windows.js @ 243e7aac8cee0108927df0253118e36857ab9fc7
> in
> > 5ms
> > Done.
> >
> > The typical way a platform is released is to use cordova-coho.
> > ex. `coho prepare-platform-release-branch -r cordova-android --version
> > 9.9.9`
> > This takes care of all the tagging, building/copying of cordova.js to the
> > correct platform folder.
> >
> > About the mobile-spec workflow, I have not done this is a long time, this
> > was more important when we were breaking things a lot.  One expectation
> of
> > the tooling that may not be explicitly listed is that all repos are
> > expected to be cloned as peers.  cordova-coho has commands that can help
> > manage the multitude of repos for you.
> >
> > Not sure if this helps you move forward, I am happy to dig into this more
> > with you.
> >
> > Cheers,
> >   Jesse
> >
> > @purplecabbage
> > risingj.com
> >
> >
> > On Tue, Oct 23, 2018 at 10:22 PM gandhi rajan 
> > wrote:
> >
> > > Hi All,
> > >
> > > I was trying to understand the release process for Cordova platforms as
> > > mentioned in the following link -
> > >
> > >
> > https://github.com/apache/cordova-coho/blob/master/docs/
> platforms-release-process.md
> > > .
> > >
> > > While following the steps mentioned to test plugins with
> > > cordova-mobile-spec project, I got an error stating cordova-js module
> is
> > > not installed. When I tried to install cordova-js, the installation
> fails
> > > stating one critical severity vulnerability.On running npm audit on
> > > cordova-js, it states that the critical vulnerability is related to
> growl
> > > version.
> > >
> > > Can someone let me know whether I m missing some steps which is causing
> > > this issue or it's a vulnerability that needs to be fixed as I m not
> able
> > > to proceed with cordova-js module installation?
> > >
> > > Any help is really appreciated. Thanks in advance.
> > >
> > >
> > > --
> > > Regards,
> > > Gandhi
> > >
> > > "The best way to find urself is to lose urself in the service of others
> > > !!!"
> > >
> >
>


-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Re: [DISCUSS] cordova-android 7.1.2 patch release

[gandhi rajan]

I can try out the release process but need some assistance as its first
time I m doing it. Anyone willing to provide some guidance for me in doing
this?

On Thursday, October 25, 2018, Darryl Pogue  wrote:

> Hey folks,
>
> There's been some issues with a bunch of packages published to Bintray
> jcenter, and we've been getting a lot of bug reports and PRs to
> reorder the repositories that gradle looks at. We've already merged a
> fix to master, and cherry-picked it to the 7.1.x branch (along with
> some other fixes).
>
> Julio also indicated that some of the cherry-picked fixes will resolve
> the longstanding issue of 3rd party plugin compatibility with the new
> Android Studio project structure.
>
> The list of changes and diff on the 7.1.x branch (since 7.1.1) is
> available for viewing at
> https://github.com/apache/cordova-android/compare/7.1.1...36c6f44
>
> Does anyone have any concerns or reasons to delay starting the release
> process for 7.1.2?
>
> Further to that, does anyone have time to start the release process?
> I'm swamped at work right now and unlikely to be able to look at it
> until mid-next week :(
>
> ~Darryl
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Facing issue in testing release process of Cordova platforms

[gandhi rajan]

Hi All,

I was trying to understand the release process for Cordova platforms as
mentioned in the following link -
https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md
.

While following the steps mentioned to test plugins with
cordova-mobile-spec project, I got an error stating cordova-js module is
not installed. When I tried to install cordova-js, the installation fails
stating one critical severity vulnerability.On running npm audit on
cordova-js, it states that the critical vulnerability is related to growl
version.

Can someone let me know whether I m missing some steps which is causing
this issue or it's a vulnerability that needs to be fixed as I m not able
to proceed with cordova-js module installation?

Any help is really appreciated. Thanks in advance.


-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Re: [Introduction] [Join community] Piotr Kosko

[gandhi rajan]

Warm welcome,  Piotr Kosko !!!

On Sat, Oct 20, 2018 at 10:53 AM Piotr Kosko  wrote:

> Hello,
>
> I am Tizen Web API developer. I am working for Samsung R&D Center (SRPOL)
> in Warsaw (Poland).
> I would like to join the mailing list of Cordova project as it is a great
> cross-platform web solution.
>
>
> Best regards,
> Piotr Kosko
> --
>
>
> Piotr Kosko
> Samsung R&D Insitute Poland
> Samsung Electronics
> p.ko...@samsung.com
>
>
>
>
>


-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Re: GitHub Project Board: Pull Requests

[gandhi rajan]

Looks great Jan. But for some reason I m not able to see the emojis in my
chrome browser. Does anyone else have the same issue?

On Mon, Sep 3, 2018 at 6:13 PM Jan Piotrowski  wrote:

> Hi,
>
> with the switch to GitHub for issues I started looking into GitHub
> Project boards to help us manage Issues and Pull Requests.
>
> The first concrete result of this is ready for feedback:
>
> Apache Cordova - Platforms Pull Requests
> https://github.com/orgs/apache/projects/7
>
> As the name implies, this board contains all Pull Requests for the
> Platform repositories (ios, android, windows, osx, browser). It can be
> used to 1) get an overview of all the PRs for several repositories at
> the same time and 2) help us maintainers to find PRs to comment on,
> test and approve or merge.
>
> The project board contains these columns:
>
> - 🐣 New PR / Untriaged (🤖/👩‍🔧)
> - 👷 Blocked: Work in Progress (👩‍🔧)
> - ⛔ Blocked: Tests failing (👩‍🔧)
> - 💥 Blocked: Conflict (👩‍🔧)
> - ⏳ Waiting for Review (👩‍🔧)
> - 🙅 Pending Approval (🤖)
> - ✅ Approved, waiting for Merge (🤖)
> - 🏆 Merged, waiting for Release (🤖)
> - ☠️ Closed/Abandoned (🤖)
> - 🎈 Released (👩‍🔧)
>
> The columns itself should cover all the common cases we can encounter
> with PRs (Did I miss anything that should be tracked?).
>
> The column a PR is currently located in is shown in the "Projects"
> section of the sidebar of the PR on GitHub. Each time a PR is moved,
> the PR gets a " moved this from  to " line added
> at the bottom. The emojis make parsing these info bits a lot easier.
>
> New PRs can be added to this board a) semi-automatically by clicking
> the "Cog" icon next to "Projects" in the sidebar of a PR on Github and
> then selecting the board or b) by using the "Add cards" functionality
> on the board itself. There is no way to fully automatically add new
> PRs to this board yet [1].
>
> The emojis at the end of the column description (🤖/👩‍🔧) explain who
> is responsible for getting PRs into or out of a lane. As you can see
> only the first 5 columns (and the last one) have to be handled
> manually, the rest is automated.
> Our "work" on this board is only to get all PRs from "New PR" to
> "Waiting for Review" in the board. Then the automation takes over by
> looking if a PR is approved, merged or closed on GitHub itself. At the
> end we can manually track what PRs were released to users.
>
>
> Feedback or Comments?
>
> If this is welcome, I will create identical project boards for tooling
> and plugins. [2]
>
> Best,
> Jan
>
>
>
> [1] If this project board is considered useful and will be used, there
> are options to automatically add new PRs to this column via GitHub
> apps. We certainly could use this, but I didn't want to spend the time
> to configure this up front.
>
> [2] It will be interesting to see how the automation will work for
> e.g. Plugins where we have >5 repositories. Probably we will also need
> a workaround the "5 repo per project board" limit from Github via an
> GitHub app.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Re: Reviving Face-to-Face video meetings?

[gandhi rajan]

Thanks for sharing the notes. It gives a big picture of what's happening
and was informative too.

On Wednesday, August 15, 2018, Jan Piotrowski  wrote:

> Sorry I couldn't be there, a construction crew decided to cut our
> neighborhood off the internet. Using that sweet 3G mobile internet
> with data cap (Man, mobile data is surprisingly expensive in Germany)
> right now.
>
> Thanks for keeping and posting the notes.
>
>
>
> 2018-08-15 19:16 GMT+02:00 Chris Brody :
> > Thanks Darryl for hosting and taking notes. I was wondering, just out
> > of curiosity, which time zone the times are in? CET with daylight
> > savings or something else?
> > On Wed, Aug 15, 2018 at 1:06 PM Darryl Pogue 
> wrote:
> >>
> >> Thanks everyone who attended, it was great to put faces to usernames
> >> and have the chance to chat things out!
> >>
> >> I tried to take some meeting notes, which are available here:
> >> https://docs.google.com/document/d/11ozgImr5HV9TqqriL9taRBoSrDE5s
> lKp0AqNFdYUpGs/edit#heading=h.rgw0j11b9pxn
> >>
> >> On Wed, Aug 15, 2018 at 7:51 AM Darryl Pogue 
> wrote:
> >> >
> >> > If you are participating in the meeting, you should be able to join
> >> > the hangout from this link:
> >> > https://hangouts.google.com/hangouts/_/t6zlmowc4jdyvfnlotns5eimime
> >> >
> >> > If you are wanting to watch the meeting and participate only in chat,
> >> > you can do that here:
> >> > http://youtu.be/wu130DQnMVQ
> >> >
> >> >
> >> > On Wed, Aug 15, 2018 at 6:28 AM Chris Brody 
> wrote:
> >> > >
> >> > > I just added my comments, looking forward to the link to the
> meeting.
> >> > > On Mon, Aug 13, 2018 at 11:52 PM Darryl Pogue 
> wrote:
> >> > > >
> >> > > > Rough Agenda (please suggest additions):
> >> > > > https://docs.google.com/document/d/1c_
> dqxVJ8B2RjACB3faIJNljEfpOoBWL0H9lulX82oFk/edit#heading=h.xymt8g6roq2
> >> > > >
> >> > > > On Mon, Aug 13, 2018 at 1:01 AM Shazron 
> wrote:
> >> > > > >
> >> > > > > Thanks Darryl! I'll try to make this one...
> >> > > > > On Sat, Aug 11, 2018 at 11:12 AM Darryl Pogue <
> dvpdin...@gmail.com> wrote:
> >> > > > > >
> >> > > > > > Okay, it looks like the date that works best for everyone is
> Wednesday:
> >> > > > > >
> >> > > > > > Wednesday, August 15th, 2018 at 15:00 - 17:00 UTC
> >> > > > > >
> >> > > > > > For that event in your local timezone, please consult
> >> > > > > > https://www.timeanddate.com/worldclock/fixedtime.html?msg=
> Cordova+Video+Meeting&iso=20180815T15&p1=1440&ah=2
> >> > > > > >
> >> > > > > > In the past we've used Google Hangouts on Air so that
> non-participants
> >> > > > > > are able to watch the meeting on YouTube and it's recorded
> for later.
> >> > > > > > I'll try to figure out what's involved in setting that up,
> and we can
> >> > > > > > fallback to something like Skype or Zoom if need be.
> >> > > > > >
> >> > > > > > I'll also try to put together a rough agenda Google Doc for
> review on Monday.
> >> > > > > >
> >> > > > > > Thanks,
> >> > > > > > ~Darryl
> >> > > > > >
> >> > > > > >
> >> > > > > > On Thu, Aug 9, 2018 at 2:21 AM Chris Brody <
> chris.br...@gmail.com> wrote:
> >> > > > > > >
> >> > > > > > > Looking forward to the final result (hope you send by
> email), thanks!
> >> > > > > > > On Thu, Aug 9, 2018 at 2:32 AM Darryl Pogue <
> dvpdin...@gmail.com> wrote:
> >> > > > > > > >
> >> > > > > > > > Yes! Sorry for missing my intended deadline here, some
> unexpected work
> >> > > > > > > > challenges combined with moving house and not having my
> full computer
> >> > > > > > > > set up yet have caused me to drop a few things, including
> following up
> >> > > > > > > > on scheduling this.
> >> > > > > > > >
> >> > > > > > > > I've set up a Doodle poll with dates for next week, let's
> try to have
> >> > > > > > > > a date picked by this coming Friday (August 10th).
> >> > > > > > > >
> >> > > > > > > > *** TIMES ARE IN UTC. PLEASE CHECK CONVERSION TO YOUR
> LOCAL TIME
> >> > > > > > > > BEFORE REPLYING. ***
> >> > > > > > > > https://doodle.com/poll/c6nhksdmv2tgd8rf
> >> > > > > > > >
> >> > > > > > > > I'm hoping we can find something that can work not only
> for North
> >> > > > > > > > Americans, but also for our European contributors as well
> as our
> >> > > > > > > > Japanese ones. However, given that those are roughly
> equally spaced
> >> > > > > > > > around the globe, somebody is probably going to be stuck
> with
> >> > > > > > > > something outside of ideal hours. You can click twice in
> the checkbox
> >> > > > > > > > to mark it as "possible, but not ideal".
> >> > > > > > > >
> >> > > > > > > > ~Darryl
> >> > > > > > > >
> >> > > > > > > > On Wed, Aug 8, 2018 at 7:14 PM Bryan Ellis <
> ellis.br...@gmail.com> wrote:
> >> > > > > > > > >
> >> > > > > > > > > Hi Darryl,
> >> > > > > > > > >
> >> > > > > > > > > I see it had past Aug 3rd and I wanted to find out if
> we are still planning to set up a web conference.
> >> > > > > > > > >
> >> > > > > > > > > I am looking forward to the web conference. Please let
> me kn

Re: Dealing with deprecated repos

[gandhi rajan]

+1 for archiving repos and documenting them.

On Wednesday, August 8, 2018, Shazron  wrote:

> Let's make it formal with what we had in the repo, perhaps a new page
> or section in the docs somewhere.
> On Wed, Aug 8, 2018 at 6:09 PM Jan Piotrowski 
> wrote:
> >
> > Please note that this part of the discussion with me playing devil's
> > advocate - I pretty much agree with what you are saying.
> >
> > Is there any way users can find out about new forks of deprecated
> > repos? Fork network view on Github maybe? Then adding a link to that
> > in the deprecation notice would be a nice move.
> >
> > Any other comments regarding a possible "Cordova Deprecation Policy"
> > than what Julio already wrote?
> >
> > -J
> >
> >
> > 2018-08-08 11:52 GMT+02:00 julio cesar sanchez :
> > > This is the deprecation policy from cordova-plugin-contacts
> > >
> > > Deprecation Notice
> > > This plugin is being deprecated. No more work will be done on this
> plugin
> > > by the Cordova development community. You can continue to use this
> plugin
> > > and it should work as-is in the future but any more arising issues
> will not
> > > be fixed by the Cordova community.
> > >
> > > All the deprecated repos have a similar deprecation notice.
> > >
> > > Other than that, I don't think we have something more official. Also, I
> > > don't know were/if that message was discussed.
> > >
> > > What I said on my previous message is my interpretation of "work", for
> me
> > > what I said is work, not sure if everybody agrees on that, and it's not
> > > official, just my opinion. Also my opinion of Cordova Community is
> > > everybody who wants to contribute, not just the committers.
> > >
> > > We have dozens of repos and hundreds of open PRs that we aren't able to
> > > manage, so keeping the deprecated repos open for issues/PRs in case
> > > somebody want to fix something will just bring frustration to those
> people
> > > as their PRs won't be reviewed/merged. And if we plan on continuing
> > > reviewing/merging on deprecated repos, why did we deprecate them on the
> > > first place?
> > >
> > > El mié., 8 ago. 2018 a las 11:26, Jan Piotrowski (<
> piotrow...@gmail.com>)
> > > escribió:
> > >
> > >> Great, then this seems to be Cordova's deprecation policy. Write it
> > >> down, publish it, link to it from the deprecated projects so users
> > >> know about it - problem solved.
> > >>
> > >> Just to be on the safe side: Was this previously discussed and
> decided?
> > >>
> > >> -J
> > >>
> > >> 2018-08-08 10:49 GMT+02:00 julio cesar sanchez <
> jcesarmob...@gmail.com>:
> > >> > No, when we deprecate something it means no more work will be done
> on it.
> > >> >
> > >> > Triaging issues, reviewing and merging other people prs and
> continuing
> > >> > doing releases it’s work. We aren’t supposed to do anything else
> when we
> > >> > deprecate.
> > >> >
> > >> > People can freely create and maintain a fork, but it won’t be
> official
> > >> and
> > >> > won’t live in the Apache repo.
> > >> >
> > >> >
> > >> > El miércoles, 8 de agosto de 2018, Jan Piotrowski <
> piotrow...@gmail.com>
> > >> > escribió:
> > >> >
> > >> >> Let me play devil's advocate:
> > >> >>
> > >> >> Archiving means disabling everything - issues, PRs, etc.
> > >> >> Don't we want to let people create PRs with bug fixes or changes
> (we
> > >> >> may or may not choose to merge) for other people to benefit from?
> > >> >>
> > >> >> -J
> > >> >>
> > >> >> 2018-08-08 3:40 GMT+02:00 Gearóid M :
> > >> >> > +1 on archiving deprecated repos, it's an easy way to make it
> very
> > >> clear
> > >> >> that it is no longer maintained
> > >> >> >
> > >> >> > On Wed, 8 Aug 2018, at 01:37, Chris Brody wrote:
> > >> >> >> +1
> > >> >> >> On Tue, Aug 7, 2018 at 11:32 AM julio cesar sanchez
> > >> >> >>  wrote:
> > >> >> >> >
> > >> >> >> > Archived repos are read only.
> > >> >> >> >
> > >> >> >> > People can still clone and/or fork them, they just can't send
> PRs
> > >> or
> > >> >> create
> > >> >> >> > new issues.
> > >> >> >> >
> > >> >> >> > I'm +1 on archiving them.
> > >> >> >> >
> > >> >> >> >
> > >> >> >> >
> > >> >> >> > El mar., 7 ago. 2018 a las 17:25, 
> escribió:
> > >> >> >> >
> > >> >> >> > > I suggest archiving them all and deal with any issues as
> they
> > >> >> appear. After
> > >> >> >> > > all, repos can be unarchived if necessary.
> > >> >> >> > >
> > >> >> >> > > Chris Brody  schrieb am Di., 7. Aug.
> > >> 2018,
> > >> >> 17:16:
> > >> >> >> > >
> > >> >> >> > > > Continuation of discussion from
> > >> >> >> > > >
> > >> >> >> > > >
> > >> >> >> > >
> > >> https://lists.apache.org/thread.html/affbc74f0ff4d34bc09657c3c302e1
> > >> >> 85cc98b946d260184847fdf191@%3Cdev.cordova.apache.org%3E
> > >> >> >> > > >
> > >> >> >> > > > I think it is not desired to actively support deprecated
> > >> repos. I
> > >> >> >> > > > think the easiest solution is to simply make those repos
> > >> archived.
> > >> >> >> > > >
> > >> >> >> > > > But what if there are people sti

Re: [DISCUSS] [Github Issues] Issue and PR template + Merge Conventions / Protected Branch

[gandhi rajan]

Hi Jan,

I like your suggestions. But curious to understand how to take care of
existing issues which are currently available in JIRA? Should it be ported
to respective git repos or will continue to remain as is till it's closed?

On Tuesday, August 7, 2018, Jan Piotrowski  wrote:

> Now that Github Issues are enabled on all repositories, it makes sense
> to create a (or several) new Issue and PR template(s) that doesn't
> point to JIRA any more and also uses the current state of the art.
>
> Current Cordova issue and PR template:
> - no issue template
> - https://github.com/apache/cordova-android/blob/master/.
> github/PULL_REQUEST_TEMPLATE.md
>
>
> 1. Issue template:
>
> Github supports multiple issue templates for some time now, which
> first lets users choose what type of issue they want to create:
> https://help.github.com/articles/about-issue-and-pull-request-templates/
>
> The template selection can look like this:
> https://github.com/fastlane/fastlane/issues/new/choose
> https://github.com/babel/babel/issues/new/choose
>
> I think we should definitely use this for Bug Report, Feature Request,
> Support Question. What sections should we suggest in our templates?
>
> Here are some additinal issue templates from around the web:
> https://github.com/stevemao/github-issue-templates/tree/master/emoji-guide
> https://github.com/devspace/awesome-github-templates
>
>
> 2. Pull Request template:
>
> I think we can drop the JIRA/issue requirement from the checklist
> completely - as a PR on Github is always the starting point of code
> changes now. If there is an (Github) issue the PR resolves, it should
> of course be linked (`closes #123` or similar), but this is not a
> requirement.
>
> Similar about commit message conventions - I don't think we need an
> issue ID in there as all code changes will be done via PRs which via
> "squash + merge" will include PR ID in the commit message (again
> fastlane as an example:
> https://github.com/fastlane/fastlane/commits/master)
>
> I would suggest we use something similar to this, which explicitly
> asks for running the tests and writing documentation:
> https://github.com/fastlane/fastlane/blob/master/.github/
> PULL_REQUEST_TEMPLATE.md
>
> What do you think regarding PR template?
>
>
> 3. Merge Conventions / Protected Branch:
>
> Connected to all that is my suggestion to protect the `master` branch
> so that by default nobody can commit there - all changes have to be
> made via Pull Requests. Pull Requests are by default merged via the
> "Squash + Merge" button / functionality so that all commits are
> squashed into one clean commit per change. This also enforces the
> commit message structure I posted above. (Of course committers can
> choose to _not_ use Squash + Merge if appropriate for the PR - e.g.
> when cherry picking commits from a release branch or similar).
>
> What do you think about this suggestion?
>
>
> Did I miss anything that is connected to these 3 topics?
>
> -J
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Re: [VOTE] cordova-browser@5.0.4 patch release

[gandhi rajan]

+1

On Tuesday, July 31, 2018, Chris Brody  wrote:

> Please review and vote on this cordova-browser@5.0.4 patch release by
> replying to this email (and keep discussion on the DISCUSS thread).
>
> Release issue: https://issues.apache.org/jira/browse/CB-14230
>
> The archive has been published to dist/dev:
> https://dist.apache.org/repos/dist/dev/cordova/CB-14230/
>
> The package was published from its corresponding git tag:
>
> cordova-browser: 5.0.4 (c61ce21186)
>
> Note that you can test it out via:
>
> cordova platform add https://github.com/apache/cordova-browser#5.0.4
>
> Upon a successful vote I will upload the archive to dist/, publish it
> to npm, and post the blog post.
>
> Voting guidelines:
> https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
>
> Voting will go on for a minimum of 48 hours.
>
> I vote +1:
> * Ran coho audit-license-headers over the relevant repos
> * Ran coho check-license to ensure all dependencies and
> subdependencies have Apache-compatible licenses
> * Ensured continuous build was green when repo was tagged
> * able to add to
> https://github.com/brodybits/cordova-dialogs-bootstrap-test using
> cordova platform add github:brodybits/cordova-browser#5.0.x, run, and
> try a couple dialogs with npm@2.15.11 (bundled with deprecated node
> v4.9.1) on Windows Edge, Windows Chrome, and macOS Safari
> * able to add to
> https://github.com/brodybits/cordova-dialogs-bootstrap-test using
> cordova platform add github:brodybits/cordova-browser#5.0.x, run, and
> try a couple dialogs with npm@5.6.0 (bundled with node v8.11.3)
> * more details in https://github.com/apache/cordova-browser/pull/55
>
> Proposed blog post in: https://github.com/apache/cordova-docs/pull/857
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Re: [VOTE] cordova-js@4.2.4 tools release (patch release)

[gandhi rajan]

+1

On Tuesday, June 26, 2018, Chris Brody  wrote:

> Can I get one more vote on this?
>
> I would like to release today if possible.
> On Fri, Jun 22, 2018 at 2:34 AM Jesse  wrote:
> >
> > +1
> >
> > * Ran coho verify-archive
> > * Ran coho audit-license-headers
> > * Ran coho check-license
> > * Ensured continuous build was green when repos were tagged
> > * checked out commit and ran tests
> >
> >
> >
> > @purplecabbage
> > risingj.com
> >
> > On Thu, Jun 21, 2018 at 11:08 PM, Chris Brody 
> wrote:
> >
> > > New email, should be in a new thread, requesting a vote:
> > >
> > > Please review and vote on this cordova-js 4.2.4 (patch release) by
> > > replying to this email (and keep discussion on the [DISCUSS] thread)
> > >
> > > Release issue: https://issues.apache.org/jira/browse/CB-14152
> > >
> > > Purpose is to release a single version of cordova-js with internal npm
> > > audit issues resolved, to be integrated with cordova-android,
> > > cordova-browser, cordova-ios, cordova-osx, cordova-windows, and all
> > > dependent tools packages.
> > >
> > > Artifacts for this cordova-common patch release have been published to
> > > dist/dev: https://dist.apache.org/repos/dist/dev/cordova/CB-14152/
> > >
> > > The package artifacts were published from their corresponding git
> tag(s):
> > >
> > > cordova-js: 4.2.4 (e040d9e934)
> > >
> > > Upon a successful vote I will upload the archives to dist/, publish
> > > them to npm, and post the corresponding blog post.
> > >
> > > Voting guidelines:
> > > https://github.com/apache/cordova-coho/blob/master/docs/
> release-voting.md
> > >
> > > Voting will go on for a minimum of 48 hours.
> > >
> > > I vote +1:
> > > * Ran coho audit-license-headers over the relevant repos
> > > * Ran coho check-license to ensure all dependencies and
> > > sub-dependencies have Apache-compatible licenses
> > > * Ensured continuous build was green when repos were tagged
> > >
> > > Thanks and best regards,
> > >
> > > Chris
> > >
> > > https://twitter.com/brodybits
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > > For additional commands, e-mail: dev-h...@cordova.apache.org
> > >
> > >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Re: Contributor Introduction

[gandhi rajan]

Welcome Eric. Great to hear from you.

On Thursday, June 7, 2018, Eric Corson  wrote:

> Hi everyone,
>
> My name is Eric Corson.
>
> I am currently a software developer at Asial and a maintainer of the
> Onsen UI framework.
>
> I am experienced with JavaScript, HTML, CSS and Java, as well as
> functional programming and type systems.
>
> I would like to contribute to Cordova with bug fixes and features. I'm
> looking forward to working with you all!
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Re: Contributor Introduction

[gandhi rajan]

Hi Ken,

Warm welcome. Really looking forward for your contributions. Cheers.

On Monday, May 14, 2018, 内藤謙一  wrote:

> Hi Everyone,
>
> My name is Ken Naito.
>
> I am an engineer and working on mobile application development at Monaca.
>
> I have wide experience in HTML, JavaScript, Java, and Objective-C via
> implementing Cordova applications and plugins on which Monaca uses.
>
> I would like to contribute to the Cordova community with bug fixes,
> feature implementations, and improvements.
>
> Regards,
> Ken
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Re: Contributor Introduction

[gandhi rajan]

Welcome Bryan. Appreciate your time.

On Friday, May 11, 2018, Bryan Ellis  wrote:

> Hey Everyone,
>
> My name is Bryan Ellis. I am currently working at Monaca as a Senior
> Software Engineer.
>
> I have a strong professional and educational background in Java,
> JavaScript, HTML, CSS, and other languages.
>
> Since I have been working with the Apache Cordova framework on a regular
> basis within Monaca, I am looking forward to contributing back to the
> community with bug fixes, feature implementations, and tooling
> improvements.
>


-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Re: regarding bug

[gandhi rajan]

Hi Sadhik,

When you build browser platform, the platform will be rebuilt picking the
code from root www project folder. Not sure what you mean by rerunning
browser platform. Please provide elaborate steps on what you are actually
trying to perform.

On Tue, May 8, 2018 at 10:13 AM, Sadhik Mulla  wrote:

> when i rerun apache browser platform all html files are removing
>



-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Re: Intro - Hazem Saleh

[gandhi rajan]

Welcome Hazem. Great job. Keep it coming.

On Tuesday, April 24, 2018, Hazem Saleh  wrote:

> Hello Cordova Dev Team!
>
> My name is Hazem Saleh. I just wanted to take a moment to introduce myself.
> I've been working in mobile products for many years using native and hybrid
> technologies. I'm an old Apache committer (and PMC member in one of Apache
> projects). I'm glad to contribute to Cordova project in my free time and I
> had a chance to create a quick refactoring PR:
> https://github.com/apache/cordova-plugin-camera/pull/319
>
> Looking forward to work with you.
>
> Thank you
> --
> Hazem Saleh
>


-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Re: [DISCUSS] Plugins release

[gandhi rajan]

Hi Joe, I m interested in becoming a committer and also submitted few PRs
too. Do let me know how to proceed about this?

On Wednesday, April 18, 2018, Joe Bowser  wrote:

> Hey
>
> This is technically off-topic, but I commented on the PR asking for a new
> PR and discussion on the list.  However, without additional committers, I
> don't see this happening in the short term.  If people are interested in
> becoming committers on this project, people should let us know on this
> mailing list.  We can definitely use the help.
>
> I hope this clears things up a bit.
>
>
>
> On Tue, Apr 17, 2018 at 11:27 AM, Niklas Merz 
> wrote:
>
> > Hello everyone,
> >
> > I am watching another issue for some time and I would like to see it
> going
> > forward.
> >
> > Cordova InAppBrowser WKWebview support
> > https://issues.apache.org/jira/browse/CB-7179?page=com.atlas
> > sian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel&
> > focusedCommentId=16160433#comment-16160433
> >
> > Dave Alden did some great work and commented it, but now it seems stuck.
> > How can we promote the effort to get WKWebview for the IAB plugin? Or is
> > there no chance to get that in the official plugin?
> >
> > Thanks for your help.
> >
> > Best regards
> > Niklas
> >
> > -
> >
> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > For additional commands, e-mail: dev-h...@cordova.apache.org
> >
> >
>


-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Re: [DISCUSS] Android & iOS release

[gandhi rajan]

Hi Steve,

Can you please have a look at this PR -
https://github.com/apache/cordova-docs/pull/811

It's related to Cordova doc changes.

On Tuesday, April 17, 2018, Steven Gill stevengil...@gmail.com> wrote:

> Going to aim to do a release this week. Let me know if there are any PRs I
> should look at.
>


-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Fwd: Regarding Cordova website running using Make

[gandhi rajan]

Hi All,

We are planning to remove Makefile and its related documentations for
building cordova website.

Please revert if you have any concerns.

-- Forwarded message --
From: gandhi rajan 
Date: Thu, Apr 5, 2018 at 7:51 PM
Subject: Regarding Cordova website running using Make
To: dev@cordova.apache.org


Hi All,

we do have an option of building and running Cordova website using gulp as
well as make. But there is no mention of 'make' instructions in 'developing
the website' section of Cordova docs.

Have created a PR to include website running  instruction using 'make' as
follows:

https://github.com/apache/cordova-docs/pull/811

Please let me know whether this instructions should be documented as we
have mixed opinions on this. Thanks in advance.


-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"




-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Fwd: Regarding Cordova website running using Make

[gandhi rajan]

Hi All, Any comments on this?

-- Forwarded message --
From: *gandhi rajan* 
Date: Thursday, April 5, 2018
Subject: Regarding Cordova website running using Make
To: dev@cordova.apache.org


Hi All,

we do have an option of building and running Cordova website using gulp as
well as make. But there is no mention of 'make' instructions in 'developing
the website' section of Cordova docs.

Have created a PR to include website running  instruction using 'make' as
follows:

https://github.com/apache/cordova-docs/pull/811

Please let me know whether this instructions should be documented as we
have mixed opinions on this. Thanks in advance.


-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"




-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Regarding Cordova website running using Make

[gandhi rajan]

Hi All,

we do have an option of building and running Cordova website using gulp as
well as make. But there is no mention of 'make' instructions in 'developing
the website' section of Cordova docs.

Have created a PR to include website running  instruction using 'make' as
follows:

https://github.com/apache/cordova-docs/pull/811

Please let me know whether this instructions should be documented as we
have mixed opinions on this. Thanks in advance.


-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Re: [DISCUSS] cordova-android release

[gandhi rajan]

+1

On Saturday, February 17, 2018, Steven Gill  wrote:

> cordova-android release. Going to do a minor or patch release for android.
> Any issues or concerns?
>


-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"