Great idea Julio. I've updated the readme to point to the forked plugin.
Simon Mac Donald
http://simonmacdonald.com
On Thu, Sep 3, 2020 at 7:09 PM julio cesar sanchez
wrote:
>
> The push plugin is already forked and got a few code updates, so if you
> could point to it in the phonegap one would
The push plugin is already forked and got a few code updates, so if you
could point to it in the phonegap one would be good. Will have a different
name, so people will have to replace it.
For the barcode, the aar used on android is 4 year old and it’s built from
a zxing app that was abandoned 2
Yeah, no worries folks. If you don't have the bandwidth to pull them
under the Apache umbrella I completely understand.
As for licensing, we'd be able to figure it out. I work with 4 lawyers
on this stuff so they would be able to figure out a path that works.
Simon Mac Donald
At this point I would be a little reluctant to start supporting more
plugins.
Issues and unmerged PRs seem to keep piling up in multiple places. Here are
a couple of very sad examples:
- https://github.com/apache/cordova-ios/pull/795
- https://github.com/apache/cordova-plugin-file/pull/242
On
It could be integrated into Apache.
What exactly would the process of integrating look like?
I suspect it would start with a vote email?
Since the existing plugin license is MIT, what happens here? I don't know the
rules or process on how we can change the license. I had read that there were
Thanks Simon
We'll look at this. Erisu appears to already be actively working on
havesource/cordova-plugin-push
Cheers,
Jesse
On Fri, Aug 28, 2020 at 1:22 PM Simon MacDonald
wrote:
> Hi folks,
>
> Long time no chat. As you are no doubt aware Adobe announced they are
> no longer in the
Hi folks,
Long time no chat. As you are no doubt aware Adobe announced they are
no longer in the PhoneGap business. To that end I archived the
following plugins that are still being used widely:
phonegap-plugin-push - 7,659 weekly downloads
phonegap-plugin-barcodescanner - 11,058 weekly
...@brian.io wrote:
Post 3.0 we'll want to encourage the community to:
1. Remove their code from phonegap/phonegap-plugins and into their own
repos (we've already started this)
2. Follow the Plugman spec (we just started doing this)
3. Publishing using the Plugman discovery (we have not shipped
phonegap/phonegap-plugins and into their own
repos (we've already started this)
2. Follow the Plugman spec (we just started doing this)
3. Publishing using the Plugman discovery (we have not shipped this yet)
We should help them do this too. Just want to get this message out there.
support one
platform.
On Wed, Jul 3, 2013 at 2:09 PM, Brian LeRoux b...@brian.io wrote:
Post 3.0 we'll want to encourage the community to:
1. Remove their code from phonegap/phonegap-plugins and into their own
repos (we've already started this)
2. Follow the Plugman spec (we just started doing
Excellent Suggestion. Plugin management is a huge focus for the next few
months and likely the major change for cordova 3.0. Expect improvements.
I'll let others speak to the specifics of the current plugin versioning
plan, but its great to have outside feedback on what we should focus on.
Yes, the plan is to have plugins versionned and backwards compatible with
previous versions of Cordova. Depending on what cordova version you have
installed there will/should be a specific version of that plugin that works
with it. I will kick off a thread about this.
On Tue, Mar 19, 2013 at
Hey Ally, good to hear from you and awesome feedback!
Your thread came at a good time because Anis and Braden are starting to
tackle these issues in a sane way.
As Anis mentioned, a discussion thread should be jumping up today. You can
also track the plugin progress through the plugman code (no
Hi all (especially Shazron, Simon and anyone else working day-to-day on the
Plugins repo),
There seems to be a trend at the moment with the plugins repo for users to get
angry and jump on the entitlement train when the plugin they wanna use isn't
maintained and updated quickly enough, even
Hi Tommy,
currently i was working on one step already
I am proposing that we go through the plugins and where we *can* discern who
the author *is*, try and contact them and ask them to host the plugin in
their own repo as we have started to do (and therefore have their own issue
to resurrect it.
I've started it off here:
https://github.com/phonegap/phonegap-plugins/issues/995
On Thu, Jan 24, 2013 at 1:44 AM, Tommy-Carlos Williams
to...@devgeeks.orgwrote:
Hi all (especially Shazron, Simon and anyone else working day-to-day on
the Plugins repo),
There seems to be a trend
volunteers to take it
over into their own repo. If there are no takers, we archive it in the
same repo until someone wants to resurrect it.
I've started it off here:
https://github.com/phonegap/phonegap-plugins/issues/995
On Thu, Jan 24, 2013 at 1:44 AM, Tommy-Carlos Williams
Gettin ppl on board w/ publishing to their own github is a great
start. Make sure to inform them of plugman [1]. It is very likely we
will nuke the phonegap/phonegap-plugins repo once plugman is stable.
(A month or so.)
[1] https://github.com/imhotep/plugman
On Thu, Jan 24, 2013 at 2:08 PM
:
Gettin ppl on board w/ publishing to their own github is a great
start. Make sure to inform them of plugman [1]. It is very likely we
will nuke the phonegap/phonegap-plugins repo once plugman is stable.
(A month or so.)
[1] https://github.com/imhotep/plugman
On Thu, Jan 24, 2013 at 2:08 PM
[mailto:mikeywbro...@gmail.com] On Behalf Of
Michael Brooks
Sent: Thursday, October 11, 2012 11:40 AM
To: callback-...@incubator.apache.org; alu...@gmail.com
Subject: Re: Phonegap-Plugins Repo
I highly recommend that your pull request is a README.md that redirects to your
plugin's repository, instead
If you want the exposure that the phonegap-plugins repo provides, then
yes, you want to use GitHub.
If you follow Mike's advice, the link from github can point to any
openly-accessible repository. Your own hosted git, SVN, bitbucket,
whatever.
On 12/17/12 12:33 PM, Amirzada, Bijan bij
21 matches
Mail list logo
