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

LOOKING FOR NEW REPO OWNER #42

Closed
oxyii opened this issue Mar 29, 2020 · 21 comments
Closed

LOOKING FOR NEW REPO OWNER #42

oxyii opened this issue Mar 29, 2020 · 21 comments
Labels
help wanted Extra attention is needed

Comments

@oxyii
Copy link
Collaborator

oxyii commented Mar 29, 2020

I have no time to work on this repo for community. Please comment if you can do it. I will transfer this repo and npm package into your account

@oxyii oxyii added the help wanted Extra attention is needed label Mar 29, 2020
@oxyii oxyii pinned this issue Mar 29, 2020
@kopax
Copy link
Contributor

kopax commented Apr 7, 2020

Hello @oxyii and thanks for sharing this work.

This is a must in the react-native-web ecosystem and I was very pleased to find your work here.

I feel like this is a bad thing for the package that the main maintainer is leaving the project now. May I ask why do you want to leave this project? If it's finance haven't you considered asking for some sponsoring instead? I am pretty sure some corp will be glad to contribute that way so efforts can be shared.

FYI: this was the only module that fitted my requirement, after 5 minutes I believe it's an excellent module. I can also say that you kind of saved my ass.

@oxyii
Copy link
Collaborator Author

oxyii commented Apr 7, 2020

@kopax Thanks for your appreciating this work.
This package was originally written as part of a commercial project. The project owner allowed me to share this package.I did not plan to upgrade the package initially. Just support.

But the features of the package do not satisfy all the needs of the community. Someone needs buttons on top, someone needs a different swipe speed, and so on ... For me personally, the package has enough features. I continue to use version 1.x in a commercial project.

Now the commercial project has received additional funding. If before he occupied all my working time, now I do not have enough 24 hours in a day. I stopped responding to Issues (( And this is VERY bad for the community. Therefore, I want to give the package in good hands.

@thanhtunguet
Copy link

I have reviewed the code and want to rewrite it using Typescript ;)

@oxyii

This comment has been minimized.

@oxyii
Copy link
Collaborator Author

oxyii commented May 8, 2020

@thanhtunguet Okay, now you can work with npm package. Thank you for your help! Please change repo url in package.json to your fork. Or let transfer this repo with issues

@kopax
Copy link
Contributor

kopax commented May 8, 2020

I have reviewed the code and want to rewrite it using Typescript ;)

Khi nao anh bac dau lam? :)

@thanhtunguet
Copy link

I have reviewed the code and want to rewrite it using Typescript ;)

Khi nao anh bac dau lam? :)

I have to start working this weekend. I need to modify this package to meet my project requirements and want to upgrade this package using new React features and Typescript

@oxyii
Copy link
Collaborator Author

oxyii commented May 9, 2020

@thanhtunguet Please open issues in your fork. I'll try to transfer existing issues and close issues behavior here.

@oxyii
Copy link
Collaborator Author

oxyii commented May 9, 2020

@thanhtunguet Or delete your fork then I can transfer repo to you

@kopax
Copy link
Contributor

kopax commented May 9, 2020

Just wondering @thanhtunguet but will you just add Ts or do you have any plan for the future?

I still see some weird hack to refresh the slider, this, for example, could be solved internally, I have seen my self doing a lot of hacks in some views to get beyond this. It would be nice to know how do you see the future of this package.

@thanhtunguet
Copy link

Just wondering @thanhtunguet but will you just add Ts or do you have any plan for the future?

I still see some weird hack to refresh the slider, this, for example, could be solved internally, I have seen my self doing a lot of hacks in some views to get beyond this. It would be nice to know how do you see the future of this package.

I just want to rewrite with new React hook api and customize it to meet my requirements. I may not have time in the future to maintain this package and just want to be a contributor, not a maintainer.

@thanhtunguet
Copy link

@thanhtunguet Or delete your fork then I can transfer repo to you

Sorry I just want to contribute, not to maintain this package cause I may not have time

@oxyii
Copy link
Collaborator Author

oxyii commented May 9, 2020

@thanhtunguet Okay, I understand. Thank you

@oxyii
Copy link
Collaborator Author

oxyii commented May 13, 2020

@thanhtunguet Please refresh your fork. RNW 0.12 support has been added

@jarvisluong
Copy link
Contributor

@oxyii hi! Our company @reactrondev is using this package in our own product and is interested in maintaining this package. Would it be possible to transfer?

@oxyii

This comment has been minimized.

@jarvisluong
Copy link
Contributor

@oxyii the npmjs account name is reactron.dev 😄

@oxyii
Copy link
Collaborator Author

oxyii commented Jul 27, 2020

@jarvisluong please add access rights for me on your org here. Exactly - creating new public repos. I cannot transfer without rights

@oxyii oxyii unpinned this issue Jul 27, 2020
@jarvisluong
Copy link
Contributor

@oxyii You should receive an invitation email now

@oxyii
Copy link
Collaborator Author

oxyii commented Jul 27, 2020

I need access rights here (on github) not on npmjs.com. On npmjs.com you already can publish new builds

@oxyii
Copy link
Collaborator Author

oxyii commented Jul 27, 2020

Done! Now react-native-web-swiper in @reactrondev org. Thank you!

@oxyii oxyii closed this as completed Jul 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

4 participants