Looking for maintainers

[Rapsssito]

Hello everyone!
I have created react-native-tcp-socket, since the original react-native-tcp repository was abandoned long ago. As @phillbaker commented in the original repository, non active user has maintainer access on that repository, so react-native-tcp cannot be moved.

There are some forks still being actively maintained, like @aprock's one, so I wanted to ask as much react-native-tcp's forks maintainers as possible for help bringing react-native-tcp back to life in this repository.

I will post bellow a list with the maintainers I could find. If you are willing to help, reply to this issue please. Everyone is welcome!

• @phillbaker
• @aprock
• @hawkingnetwork
• @developmentnow
• @marcelio911
• @davidstoneham

[aprock]

So, Instead of forking it, if you'd like I can grant you access to the repository and rights to update the npm package since that is the one that is published?

…

-Andy ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Thursday, October 10, 2019 4:39 PM, Rapsssito ***@***.***> wrote: Hello everyone! I have created react-native-tcp-socket, since the original [react-native-tcp](https://github.com/PeelTechnologies/react-native-tcp) repository was abandoned long ago. As ***@***.***(https://github.com/phillbaker) [commented](PeelTechnologies/react-native-tcp#108 (comment)) in the original repository, non active user has maintainer access on that repository, so react-native-tcp cannot be moved. There are some forks still being actively maintained, like ***@***.***(https://github.com/aprock)['s one](https://github.com/aprock/react-native-tcp), so I wanted to ask as much react-native-tcp's forks maintainers as possible for help bringing react-native-tcp back to life in this repository. I will post bellow a list with the maintainers I could find. If you are willing to help, reply to this issue please. Everyone is welcome! - ***@***.***(https://github.com/phillbaker) - ***@***.***(https://github.com/aprock) - ***@***.***(https://github.com/hawkingnetwork) - ***@***.***(https://github.com/developmentnow) — You are receiving this because you were mentioned. Reply to this email directly, [view it on GitHub](#1?email_source=notifications&email_token=AABKAWMAXZNPABFYSZDI7T3QN64MHA5CNFSM4I7THEN2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HRCIW2Q), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AABKAWLCLLIYZ5STMRHTWVDQN64MHANCNFSM4I7THENQ).

[aprock]

meaning the one under my account. https://github.com/aprock/react-native-tcp I started the project at Peel, and then left and forked it so development could continue.

…

-Andy ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Friday, October 11, 2019 9:53 AM, Andy Prock ***@***.***> wrote: So, Instead of forking it, if you'd like I can grant you access to the repository and rights to update the npm package since that is the one that is published? -Andy ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Thursday, October 10, 2019 4:39 PM, Rapsssito ***@***.***> wrote: > Hello everyone! > I have created react-native-tcp-socket, since the original [react-native-tcp](https://github.com/PeelTechnologies/react-native-tcp) repository was abandoned long ago. As ***@***.***(https://github.com/phillbaker) [commented](PeelTechnologies/react-native-tcp#108 (comment)) in the original repository, non active user has maintainer access on that repository, so react-native-tcp cannot be moved. > > There are some forks still being actively maintained, like ***@***.***(https://github.com/aprock)['s one](https://github.com/aprock/react-native-tcp), so I wanted to ask as much react-native-tcp's forks maintainers as possible for help bringing react-native-tcp back to life in this repository. > > I will post bellow a list with the maintainers I could find. If you are willing to help, reply to this issue please. Everyone is welcome! > > - ***@***.***(https://github.com/phillbaker) > > - ***@***.***(https://github.com/aprock) > > - ***@***.***(https://github.com/hawkingnetwork) > > - ***@***.***(https://github.com/developmentnow) > > — > You are receiving this because you were mentioned. > Reply to this email directly, [view it on GitHub](#1?email_source=notifications&email_token=AABKAWMAXZNPABFYSZDI7T3QN64MHA5CNFSM4I7THEN2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HRCIW2Q), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AABKAWLCLLIYZ5STMRHTWVDQN64MHANCNFSM4I7THENQ).

[Rapsssito]

@aprock I really appreciate your fork, I've used it a lot! However, I have come across a lot of people having troubles getting help about that library because the issues are located in Peel's repository. Also, contributors are still creating PR's for that repository, ignoring that the one in npm is your fork. Looking through npm package list, I have also found a lot of other forks born from ignored PR's in the original repository.

I think it is worth sacrificing the name of library, in exchange for getting an active and unified repository. We could use this one or, since you created the most used fork, you could create a react-native-tcp-sockets repository, mark the fork as moved and start getting issues and PR's there. It is very important for the library to receive active feedback, so it can evolve and adapt. (Also @phillbaker wouldn't have to be checking Peel's repository all the time looking for ignored PRs).

In addition, I have published this package in npm, so anyone can use it in their projects.

[aprock]

Those are fair points. Best of luck!

…

-Andy

On Fri, Oct 11, 2019 at 10:13 AM, Rapsssito ***@***.***> wrote: ***@***.***(https://github.com/aprock) I really appreciate your fork, I've used it a lot! However, I have come across a lot of people having troubles getting help about that library because the issues are located in Peel's repository. Also, contributors are still creating PR's for that repository, ignoring that the one in npm is your fork. I have also found a lot of other forks born from ignored PR's in the original repository. I think it is worth sacrificing the name of library, in exchange for getting an active and unified repository. Since you created the most used fork, you could create a react-native-tcp-sockets repository, mark the fork as moved and start getting issues and PR's there. It is very important for the library to receive active feedback, so it can evolve and adapt. (Also ***@***.***(https://github.com/phillbaker) wouldn't have to be checking Peel's repository all the time looking for ignored PRs). I have published this package in [npm](https://www.npmjs.com/package/react-native-tcp-socket), so anyone can use it in their projects. — You are receiving this because you were mentioned. Reply to this email directly, [view it on GitHub](#1?email_source=notifications&email_token=AABKAWOF4J3TCULVU4DPP4DQOCX37A5CNFSM4I7THEN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBAUMCQ#issuecomment-541148682), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AABKAWINBX4WD3GAFVIV7YTQOCX37ANCNFSM4I7THENQ).

[phillbaker]

@aprock would you mind enabling issues on your fork? That at least addresses one of the concerns.

[Rapsssito]

That would be a great start! However, I don't think hosting the library on a fork is maintainable in the long run. @phillbaker or @aprock would you like to become maintainers of this library or maybe create a new one, marking the fork as moved?