Re: [DISCUSS] Moving JIRA issues to Github

> The one I was thinking of was cordova-plugins. Do we want some way to track > issues for inactive platforms too or should those be considered permanently > closed? Possibly. I think we will still have JIRA around w/ deprecated components, maybe? I'm not sure. Shaz? > For example a new platform

Re: [GITHUB MOVE] Phase 1 Complete, next steps

Yes! On Aug 2, 2017 6:16 PM, "Filip Maj" wrote: > at some point should we migrate / create a cordova-discuss repo [1] to > the apache org? > > [1] https://github.com/cordova/cordova-discuss > > On Wed, Aug 2, 2017 at 12:42 PM, Shazron wrote: > > Phase 1

Re: [DISCUSS] Moving JIRA issues to Github

>> Since it looks like not all repositories will be migrated where should their issues go? > All repositories will be migrated. The one I was thinking of was cordova-plugins. Do we want some way to track issues for inactive platforms too or should those be considered permanently closed? >> What

Re: cordova 8 proposal

Thanks for kicking this off. Lotsa good stuff in there, but lots to sort through. Recommend everyone take a look! On Wed, Aug 2, 2017 at 4:51 PM, Steven Gill wrote: > Let me know what you think! > https://github.com/cordova/cordova-discuss/pull/72

Re: [GITHUB MOVE] Phase 1 Complete, next steps

at some point should we migrate / create a cordova-discuss repo [1] to the apache org? [1] https://github.com/cordova/cordova-discuss On Wed, Aug 2, 2017 at 12:42 PM, Shazron wrote: > Phase 1 complete: > https://issues.apache.org/jira/browse/INFRA-14347 > > We need to: > >

Re: [DISCUSS] Moving JIRA issues to Github

> Since it looks like not all repositories will be migrated where should their > issues go? All repositories will be migrated. > What about issues for repositories that don’t yet exist Can you give me an example? > or cross-cutting issues? I think if you absolutely need issues related to

Re: [DISCUSS] Moving JIRA issues to Github

I have a few questions about moving issues to GitHub. I haven’t used Github issues much so these all may be easily solvable. * Since it looks like not all repositories will be migrated where should their issues go? What about issues for repositories that don’t yet exist or cross-cutting issues? *

[GitHub] cordova-lib pull request #587: CB-13056 : added deprecation notice for webos

Github user asfgit closed the pull request at: https://github.com/apache/cordova-lib/pull/587 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[GitHub] cordova-lib pull request #585: CB-13057 : added deprecation warning for cord...

Github user asfgit closed the pull request at: https://github.com/apache/cordova-lib/pull/585 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

cordova 8 proposal

Let me know what you think! https://github.com/cordova/cordova-discuss/pull/72

[GitHub] cordova-plugin-dialogs pull request #96: CB-12895 : setup eslint and removed...

GitHub user audreyso opened a pull request: https://github.com/apache/cordova-plugin-dialogs/pull/96 CB-12895 : setup eslint and removed jshint ### Platforms affected ### What does this PR do? Setup eslint and removed jshint. ### What testing has

Re: [DISCUSS] Moving JIRA issues to Github

If people post their issue at the wrong repo (which of course can and will happen from time to time), there is a way to move them over with minimal loss of information: https://github.com/ionic-team/ionic/issues/12542 https://github.com/ionic-team/ionic-cli/issues/2597 This works for issues

[GitHub] cordova-plugin-device pull request #70: CB-12895 : Setup eslint and removed ...

GitHub user audreyso opened a pull request: https://github.com/apache/cordova-plugin-device/pull/70 CB-12895 : Setup eslint and removed jshint ### Platforms affected ### What does this PR do? Setup eslint and removed jshint ### What testing has

[GitHub] cordova-plugin-media-capture pull request #82: CB-12895 : Added eslint and r...

GitHub user audreyso opened a pull request: https://github.com/apache/cordova-plugin-media-capture/pull/82 CB-12895 : Added eslint and removed jshint ### Platforms affected ### What does this PR do? Added eslint and removed jshint ### What

Re: [DISCUSS] Moving JIRA issues to Github

I think the ease of use of GitHub issues overcomes potential problems about cross-referencing issues. Worth noting on this topic that GitHub already provides good support for referencing pull requests from issues across repos / orgs. The benefit of having issues and PRs in one place, to me, is a

Re: [GITHUB MOVE] Phase 1 Complete, next steps

This makes me so happy :) On Wed, Aug 2, 2017 at 12:42 PM, Shazron wrote: > Phase 1 complete: > https://issues.apache.org/jira/browse/INFRA-14347 > > We need to: > > 1. Update some of our tools, mainly Coho, to point directly to Github, > since the git-wip-us.a.o repo is now

[GitHub] shazron closed pull request #40: Test again, the sequel. No JIRA prefix.

shazron closed pull request #40: Test again, the sequel. No JIRA prefix. URL: https://github.com/apache/cordova-browser/pull/40 This is an automated message from the Apache Git Service. To respond to the message, please log

[GitHub] shazron closed pull request #39: CB-123 - Test again

shazron closed pull request #39: CB-123 - Test again URL: https://github.com/apache/cordova-browser/pull/39 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use

Re: [DISCUSS] Moving JIRA issues to Github

My concern with GitHub issues is that we have a tonne of repos and issues can easily span across them, and we'd lose the one central place for issue tracking and triage. I worry that we'd be inundated with issues on the wrong repos, or without additional information, and triaging would become an

[GITHUB MOVE] Phase 1 Complete, next steps

Phase 1 complete: https://issues.apache.org/jira/browse/INFRA-14347 We need to: 1. Update some of our tools, mainly Coho, to point directly to Github, since the git-wip-us.a.o repo is now gone. 2. Update our docs 3. Update our website (contribution) I think we need to do 2. and 3. once Phases 2

[DISCUSS] Moving JIRA issues to Github

Phase 1 of our move to Github is complete, see: https://issues.apache.org/jira/browse/INFRA-14347 We need a migration plan for moving JIRA issues to Github Issues before we enable Github Issues on those repos. Once we figure those out, we can proceed with Phase 2:

[GitHub] shazron commented on issue #39: CB-123 - Test again

shazron commented on issue #39: CB-123 - Test again URL: https://github.com/apache/cordova-browser/pull/39#issuecomment-319768397 Test comment (with prefix) This is an automated message from the Apache Git Service. To

[GitHub] shazron commented on issue #40: Test again, the sequel. No JIRA prefix.

shazron commented on issue #40: Test again, the sequel. No JIRA prefix. URL: https://github.com/apache/cordova-browser/pull/40#issuecomment-319768329 Test comment (no prefix) This is an automated message from the Apache Git

[GitHub] cordova-plugin-battery-status pull request #58: CB-12895 : Added eslint and ...

GitHub user audreyso opened a pull request: https://github.com/apache/cordova-plugin-battery-status/pull/58 CB-12895 : Added eslint and removed jshint ### Platforms affected ### What does this PR do? Added eslint and removed jshint ### What

[GitHub] cordova-plugin-network-information pull request #58: CB-12895 : added eslint...

GitHub user audreyso opened a pull request: https://github.com/apache/cordova-plugin-network-information/pull/58 CB-12895 : added eslint and removed jshint ### Platforms affected ### What does this PR do? Added eslint and removed jshint ### What

[GitHub] cordova-plugin-vibration pull request #59: CB-12895 : added eslint and remov...

GitHub user audreyso opened a pull request: https://github.com/apache/cordova-plugin-vibration/pull/59 CB-12895 : added eslint and removed jshint ### Platforms affected ### What does this PR do? ### What testing has been done on this change?

[GitHub] cordova-plugin-inappbrowser pull request #235: Download permissions

Github user adirel closed the pull request at: https://github.com/apache/cordova-plugin-inappbrowser/pull/235 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or

[GitHub] cordova-plugin-inappbrowser pull request #235: Download permissions

GitHub user adirel opened a pull request: https://github.com/apache/cordova-plugin-inappbrowser/pull/235 Download permissions ### Platforms affected ### What does this PR do? ### What testing has been done on this change? ###

[GitHub] cordova-plugin-inappbrowser issue #221: CB-12834: (android) Fix bug when ope...

Github user adirel commented on the issue: https://github.com/apache/cordova-plugin-inappbrowser/pull/221 I join this request. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature

[GitHub] cordova-plugin-file pull request #213: Add mandatory iOS 10 privacy descript...

Github user shishlina closed the pull request at: https://github.com/apache/cordova-plugin-file/pull/213 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if