-
-
Notifications
You must be signed in to change notification settings - Fork 523
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
Creating a proper maintainable fork #399
Comments
Thanks a lot for the warm words. It was actually very painful to let the package die like that. I considered this, but I was worried that people won't "trust" the forked one and will always come back to the "original". I will be glad to do that, and some help would be nice 🙂 |
Let's see if some other folks have something to say ;) I don't doubt ppl will help looking at how many outstanding issues and pull requests are there. |
I would be down |
In light of the critical issues that have accumulated in the original package, I have taken the initiative to create a fork of the package and continue supporting it independently. I am pleased to introduce intl_phone_field_extended, which incorporates important fixes and will continue to receive updates and improvements. Let's make this package great again! Any feedback and pull-requests are highly appreciated |
Thanks @Alex-Kocharyan! This is the beauty of OSS. If you are still actively maintaining your fork a couple of months from now, ping me and I will put a link to it in this one to redirect people. Wish you luck ✨ |
Thank you for taking the initiative of developing this neat package! I have read some issues from the community that I wasn't able to address yet, since I couldn't reproduce them. So any contributions could be invaluable in resolving them. |
use intl_mobile_field package |
Hey @marcaureln, if you can send a single PR fixing the issues, I am happy to update the package amd fix it |
No way! Where have you been? |
@marcaureln A question to you as you were a maintainer of the package.
Why not create a proper fork and continue work on new package where you have a full authority on publishing the package to pub.dev? Seems like this package is liked by the community and you were doing great job at maintaining it (kudos for that).
Wdyt?
The text was updated successfully, but these errors were encountered: