Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HELP WANTED - SEEKING COLLABORATORS #60

Closed
tjwoon opened this issue Apr 6, 2016 · 22 comments
Closed

HELP WANTED - SEEKING COLLABORATORS #60

tjwoon opened this issue Apr 6, 2016 · 22 comments

Comments

@tjwoon
Copy link
Owner

tjwoon commented Apr 6, 2016

Hi!

Firstly I would like to apologise for being inactive in this repo for so long. I had originally planned to fix the issues raised and to perhaps add support for the Play Services Google Vision feature. However, it is quite clear now that I am simply not able to dedicate enough time to manage this project well...

It is very encouraging to see everyone in this community continue to improve the project, and it is a shame for everyone's effort to be met with no response...

Would anyone like to step up and become this repository's primary maintainer? @dcousens @luissilvaos @BarTsouri @wesleywesley ?

TJ

@dcousens
Copy link
Contributor

dcousens commented Apr 7, 2016

I'm happy to step up as a primary maintainer, though I expect my time will be spent mostly in reviewing/merging/testing PRs, not necessarily active/exploratory development (at least, unless it is necessary).

I'd think it'd be best to have several co-maintainers.

@tjwoon
Copy link
Owner Author

tjwoon commented Apr 11, 2016

Hi @dcousens. Thank you for volunteering :) I have added you as a collaborator in the repo. You are now the primary maintainer of this project. Feel free to reach out to me if there are any questions about the existing code, etc.

Thank you!

@tjwoon tjwoon closed this as completed Apr 11, 2016
@tjwoon tjwoon reopened this Apr 11, 2016
@tjwoon
Copy link
Owner Author

tjwoon commented Apr 11, 2016

Co-maintainer positions are still open. @dcousens please feel free to nominate anyone too

@dcousens dcousens self-assigned this Apr 11, 2016
@dcousens
Copy link
Contributor

@tjwoon do you mind if I publish to npm? Do you want me to add you as a publisher also?

@uniphonic
Copy link
Contributor

@tjwoon @dcousens I'm actively using this plugin in a project, and am open to being a co-maintainer. I think we should get some of those pull requests reviewed. Thanks!

@dcousens
Copy link
Contributor

@uniphonic awesome! Which PRs did you have in mind?

@tjwoon
Copy link
Owner Author

tjwoon commented Apr 13, 2016

@uniphonic Thanks :) I've added you as a collaborator

@tjwoon
Copy link
Owner Author

tjwoon commented Apr 13, 2016

@dcousens I prefer to create the NPM package and grant read/write access to all maintainers.

I'm not too familiar with NPM user access... Is this what I should do?

$ npm publish .
$ npm owner add <username> <packageId>

FYI I plan to publish this repo as cordova-plugins-cszbar

@dcousens
Copy link
Contributor

@tjwoon that sounds right (npm publish should work, no .)
I think (may be wrong though) even just npm owner add dcousens would work, no packageId needed if you are in the repository.

@tjwoon
Copy link
Owner Author

tjwoon commented Apr 13, 2016

@dcousens I have created the NPM package and added you as an owner.

Note that the version I published still contains incorrect installation instructions (it was [fbb4a31])... Instead of republishing with new version number, I think we can just wait for the real next version.

@dcousens
Copy link
Contributor

@tjwoon sounds good 👍

@uniphonic
Copy link
Contributor

@tjwoon Thanks for adding me!
@dcousens The PRs #36 and #39 are the ones I had most in mind. I've merged those in with my own fork, which is in #65
Is there a process we should have before merging in PRs? Have it reviewed by another contributor?

@dcousens
Copy link
Contributor

dcousens commented Apr 15, 2016

@uniphonic the common approach I've taken on all other repositories I maintain is:

  • Documentation/README updates can be merged on 1 ACK
  • Everything else at least 2 ACKS

Which feels like common sense I suppose. Thoughts?

@tjwoon
Copy link
Owner Author

tjwoon commented Apr 27, 2016

@dcousens sounds like a good way to work, except this repo is quite small in terms of number of maintainers, so 2 ACKs is gonna slow things down.

@dcousens
Copy link
Contributor

@tjwoon this is true, though I think its probably worth it at least for just releases?

@tjwoon
Copy link
Owner Author

tjwoon commented May 4, 2016

@dcousens, yes sounds good for releases :)

On 30 Apr 2016, at 12:37 PM, Daniel Cousens notifications@github.com wrote:

@tjwoon https://github.com/tjwoon this is true, though I think its probably worth it at least for just releases?


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub #60 (comment)

@dcousens dcousens removed their assignment Jan 3, 2017
@dcousens
Copy link
Contributor

dcousens commented Jan 27, 2017

@tjwoon I've run out of time for this, apologies for not getting a release out.

@priya011
Copy link

we are using scan barcode in my app.I added this plugin cordova plugin add cordova-plugin-cszbar in my project. It is working in android but in IPad not working. Camera is not opening in Ipad.

@jdnichollsc
Copy link

Guys, can you check the pull requests please? 👍

@miguelverdasca
Copy link

I try to run this component on my iPad, with iOS 10.3.3 and when clicking to scan the QRCode, it jumps out of the app.

Is it possible to validate this situation? And solve?

I'm using this version: https://github.com/OutSystems/csZBar.git#v1.3.3-OS3

Thanks guys,
Miguel Verdasca

@gaokehao
Copy link

gaokehao commented Apr 1, 2020

Hi!

Firstly I would like to apologise for being inactive in this repo for so long. I had originally planned to fix the issues raised and to perhaps add support for the Play Services Google Vision feature. However, it is quite clear now that I am simply not able to dedicate enough time to manage this project well...

It is very encouraging to see everyone in this community continue to improve the project, and it is a shame for everyone's effort to be met with no response...

Would anyone like to step up and become this repository's primary maintainer? @dcousens @luissilvaos @BarTsouri @wesleywesley ?

TJ

Hi! I want to be a maintainer, I hope i can improve it. Thanks!

@tjwoon
Copy link
Owner Author

tjwoon commented Oct 1, 2020

Dear all - for the past few years, I have had no interest or time to maintain this repo in any way. I have also lost my NPM access and cannot publish updated versions.

There is no point maintaining this repo - I recommend that you fork it if you would like to keep this project going, and publish it afresh on NPM. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants