-
Notifications
You must be signed in to change notification settings - Fork 181
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
Comments
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. |
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! |
Co-maintainer positions are still open. @dcousens please feel free to nominate anyone too |
@tjwoon do you mind if I publish to npm? Do you want me to add you as a publisher also? |
@uniphonic awesome! Which PRs did you have in mind? |
@uniphonic Thanks :) I've added you as a collaborator |
@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?
FYI I plan to publish this repo as |
@tjwoon that sounds right ( |
@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. |
@tjwoon sounds good 👍 |
@uniphonic the common approach I've taken on all other repositories I maintain is:
Which feels like common sense I suppose. Thoughts? |
@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. |
@tjwoon this is true, though I think its probably worth it at least for just releases? |
@dcousens, yes sounds good for releases :)
|
@tjwoon I've run out of time for this, apologies for not getting a release out. |
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. |
Guys, can you check the pull requests please? 👍 |
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, |
Hi! I want to be a maintainer, I hope i can improve it. Thanks! |
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. |
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
The text was updated successfully, but these errors were encountered: