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

Keep RxBluetoothKit Alive #420

Open
fraune opened this issue Jul 5, 2023 · 5 comments
Open

Keep RxBluetoothKit Alive #420

fraune opened this issue Jul 5, 2023 · 5 comments

Comments

@fraune
Copy link

fraune commented Jul 5, 2023

It appears that Polidea/RxBluetoothKit has not reviewed or merged any Pull Requests since 2020.

I would like to help keep this library alive. Could someone with the appropriate access help by doing one or more of the following?

  • Become active in engaging with the community again
  • Grant me permission to review/accept Pull Requests
  • Transfer ownership of the library to a willing maintainer

I would love to hear thoughts and ideas around this, since there is not another Bluetooth library for RxSwift of this size and reliability.

Cross-posted on the RxBluetoothKit Glitter.

Tagging anyone that GitHub says is on the Polidea team
@adam-stasiak @agatapst @jakublipinski @kkucharc @literator @potiuk @slawomir-andrian

@potiuk
Copy link
Member

potiuk commented Jul 5, 2023

Poliidea has been acquired and unless some individuals want to keep it running, I think best approach is to fork it and develop on your own. The Apache licence allows it, you can fork it and release/develop on your own. I think there is no need to transfer ownership.

@fraune
Copy link
Author

fraune commented Jul 5, 2023

My concern is that there are already 300 forks of this repo, and I believe most are for adding a feature or fixing a bug that specifically affects an individual or single team. As time goes on, it will become more difficult to source great code from many individuals across many forks.

@potiuk
Copy link
Member

potiuk commented Jul 5, 2023

I think its up to you to make one that will be the main one. I don't think there is anyone who can transfer ownership to you officially, so you need to make sure to build enouhg of value yourself to make it the "main" fork.

@potiuk
Copy link
Member

potiuk commented Jul 5, 2023

BTW. You can start with gathering those 300 repos and bringing their fixes into your fork and ask them to switch to yours. That's what I'd do if I wanted to provide value for others.

@fraune
Copy link
Author

fraune commented Jul 5, 2023

I understand. I've never attempted something like that before, but I think it may be worth the effort. Thanks for your perspective and for letting me know that this repo probably won't receive any more updates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants