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
[
https://issues.apache.org/jira/browse/CB-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13561622#comment-13561622
]
Yaniv De Ridder commented on CB-2281:
-
I'm having a look now.
Cordova
[
https://issues.apache.org/jira/browse/CB-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13561623#comment-13561623
]
Yaniv De Ridder commented on CB-2280:
-
Done.
- I did a pull-request for cordova-docs
On Wed, Jan 23, 2013 at 4:58 PM, Michael Brooks mich...@michaelbrooks.cawrote:
Before we move forward, I have a few questions about the no master
approach.
There is *no* master branch, so that community-driven pull requests will be
forced to think about which branch to request against.
-
[
https://issues.apache.org/jira/browse/CB-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13561627#comment-13561627
]
Yaniv De Ridder commented on CB-2281:
-
Ok so the feature works fine.
It is actually a
[
https://issues.apache.org/jira/browse/CB-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13561629#comment-13561629
]
Yaniv De Ridder commented on CB-2281:
-
http://d.pr/i/K68D Show/Hide the Status Bar
[
https://issues.apache.org/jira/browse/CB-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13561846#comment-13561846
]
Andrew Grieve commented on CB-2225:
---
The first fix wasn't working properly (was applying
[
https://issues.apache.org/jira/browse/CB-2271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Grieve resolved CB-2271.
---
Resolution: Fixed
We now serialize initial webview loads behind-the-scenes.
Fix commit:
[
https://issues.apache.org/jira/browse/CB-2271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Grieve updated CB-2271:
--
Fix Version/s: (was: 2.3.0)
2.4.0
Creating multiple CDVViewControllers at
I have been quietly listening on this thread, but thought I should at
least share my opinion.
I don't think adding contribution rules helps anyone. Git is
complicated enough as it is, and this just all seems like bureaucracy.
I think master should always contain the latest stable code, and be
[
https://issues.apache.org/jira/browse/CB-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shazron Abdullah resolved CB-2289.
--
Resolution: Invalid
Not the place for this. Cordova core does not have a BarcodeScanner plugin
The founding goal we're trying to accomplish here is that we don't want
everyone sitting on changes to be in the next version while we use master
to prep a release.
I don't think having one branch for prepping the release and another for
main development is a lot of bureaucracy.
On Thu, Jan 24,
I've written summaries on the bug of storage locations that exist on iOS
Android. I'm wondering if any other platforms want to participate in this
discussion before we start proposing new (maybe platform-specific)
LocalFileSystem constants?
On Tue, Jan 22, 2013 at 9:58 AM, Andrew Grieve
Amrit Kahlon created CB-2293:
Summary: File Tranfer of picture fails on every other picture
Key: CB-2293
URL: https://issues.apache.org/jira/browse/CB-2293
Project: Apache Cordova
Issue Type:
Sure. We could come up with standard boilerplate migration text,
@github_username them in a new issue and see what happens, and give them 2
weeks - then we add the a standard UNMAINTAINED text to the README.
Beyond doing that, there's not much we should or can do.
Moving them to our own repos,
On Thu, Jan 24, 2013 at 11:09 AM, Braden Shepherdson bra...@chromium.orgwrote:
The founding goal we're trying to accomplish here is that we don't want
everyone sitting on changes to be in the next version while we use master
to prep a release.
I don't think having one branch for prepping the
Thanks Shazron,
I am more than happy to help go through and try and contact authors.
As for taking over some semi-abandoned plugins, haven't we all already sort of
had to in the past? Heh.
There are a couple off the top of my head that I use regularly enough that if
the author can't be
Just to clarify - there should be *no* using of the git cherry-picking
command, only git merge.
Jesse - not sure what you're referring to with branch must be named x.
The latest revision of the proposal has only two branches: master and next.
Do you mean you don't like the name next?
Maybe the
Thanks for clarifying Andrew. et al, I guess I was mis-understanding some
of the earlier discussion around naming stuff.
So everything is going to master all the time, and we only care about
'next' if we are inReleaseMode and it is a bug fix?
if(inReleaseMode isBugFix) {
Nice! even simpler. :)
On Thu, Jan 24, 2013 at 3:44 PM, Jesse purplecabb...@gmail.com wrote:
Thanks for clarifying Andrew. et al, I guess I was mis-understanding some
of the earlier discussion around naming stuff.
So everything is going to master all the time, and we only care about
'next'
[
https://issues.apache.org/jira/browse/CB-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562021#comment-13562021
]
Shazron Abdullah commented on CB-1957:
--
[~developer.artworld] This issue is about the
Do we have any plans to move the Cordova Network API so that it aligns with the
current W3C draft of the
https://dvcs.w3.org/hg/dap/raw-file/tip/network-api/Overview.html?
I'm just curious because I'm currently working on the Cordova-FirefoxOS
implementation and this is the approach that FxOS
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,
[
https://issues.apache.org/jira/browse/CB-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562223#comment-13562223
]
Benn Mapes commented on CB-1593:
I was able to fix both the bugs and will make a pull
[
https://issues.apache.org/jira/browse/CB-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562231#comment-13562231
]
Webmaster Grumpy commented on CB-1807:
--
bug is still in 2.3.0
keep getting 0 in return
[
https://issues.apache.org/jira/browse/CB-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562262#comment-13562262
]
Andrew Grieve commented on CB-1807:
---
What OS / device are you using?
[
https://issues.apache.org/jira/browse/CB-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562275#comment-13562275
]
Webmaster Grumpy commented on CB-1807:
--
samsung gt-i9300
Android
This is the first I've ever heard of people on the internet acting entitled
to something for free. This type of behaviour shocks me and I may just
swear off this whole inter-webs thing.
Anyway, yeah the plugins repo is in need of a clean up. I like what Tommy
suggested about contacting authors
[
https://issues.apache.org/jira/browse/CB-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562522#comment-13562522
]
Christophe A. Guilmart commented on CB-1593:
That look great ! thanks a lot.
I
30 matches
Mail list logo
