-
Notifications
You must be signed in to change notification settings - Fork 257
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
Any plan to move plugin to npm #11
Comments
+1 |
+1, @VersoSolutions please move to |
bump @VersoSolutions |
|
Bump @ctrevisan |
hi @dcousens because in the npm page but in @VersoSolutions version I think...them are not the same |
@bau720123 you are correct, I just got around to testing this, and probably shouldn't have mentioned that without actually testing. |
It looks to me like @VersoSolutions have abandoned this repository/plugin because there's been no response from them ever since. If your project is seriously dependent on this plugin, I advise you download / clone it to your desktop and add it to your cordova projects locally. |
Shall we fork? |
@dcousens, do you know if some one already forked and published in npm? |
@dcousens @lucasfeliciano if we fork, who will be responsible for active maintenance of the plugin?? |
I could do that, but the problem is that I know almost nothing about objective c so that might be a problem for maintain it. |
@writeosahon I'm able to debug and perform some maintenance, however going forward as things change, its likely I would need contributor support for devices/platforms I can't test on. |
@lucasfeliciano @dcousens ok guys!! in that case, go ahead and fork. Please leave a comment with a link to the fork in this thread so people interested can easily locate your fork and use it. Thanks guys |
I've published to NPM as "cordova-universal-clipboard": https://www.npmjs.com/package/cordova-universal-clipboard Please make pull requests to the repo: https://github.com/Visigo/CordovaClipboard where we'll try to maintain the plugin. |
thanks @AllSeeingEye |
Hello @VersoSolutions .
Corodova have announced that all plugins should be prepared to move to npm (read http://cordova.apache.org/announcements/2015/04/21/plugins-release-and-move-to-npm.html).
Please, hope you're making plans to move as well? Your plugin is very very important to thousands of developers.
Thanks
The text was updated successfully, but these errors were encountered: