Community Fork Inquiry - hoping for one or more co-maintainers (or, ideally, for this project to add maintainers ❤️)

[prometheas]

I wish I had a better idea for how to proceed, but after having attempted to reach out to the author in issue #30 (and PR #39, which I'd opened back in 5 Dec 2021), as well as via email, it's not looking likely that it will see any updates that address the very outdated peer dependencies (which are the source of weekly dependabot false vulnerability alerts for my team 😅) and has since even lost compatibility with Expo SDK 44 (#40).

@csath - I hope you have the opportunity to see this in the next few days and can manage to add one or two of us as co-maintainers to this repo as you'd offered to me directly via email on 22 Nov, as not forking would really be the ideal outcome 🙏 but also completely understand if you're juggling too much with life to give these requests attention at the moment ❤️

In any case, it's been ages since this repo has accepted any PRs or made any releases, so I fear I'm at a loss for what else I might try to do address this problem for the community of users, and most recently the library is outright broken by the latest updates to Expo, so the only path to keeping this useful little package up to date enough to at least continue to be functional I could come up with is to explore whether it may be possible to create a community fork — one with at least two maintainers 😄

Anyway, this is meant to be a conversation starter — hoping there's a path forward for this handy piece of OSS!

[cristianoccazinsp]

The package is still usable for me, although with all the issues you've posted. I normally create a fork and fix breaking changes for myself until the owner accepts the PR, but I would sure try to help maintaining this if there's a fork.

[prometheas]

@cristianoccazinsp - as a potential short-term solution, have you seen this fork, which includes the fixes recommended in #40? (The fork is by the same person who opened the issue.)

[prometheas]

Great news, folks - the author @csath has very kindly just added me as a maintainer, and I was successfully able to accept my own PR moments ago.

Two important points I'd like to highlight, however:

1. I should very expressly note that I'm quite busy myself, and permissions on this repo do not presently include adding additional maintainers (which I think is a reasonable first step, even if I may still prove to be a bottleneck), but this is at least a very meaningful start to getting this project up to date and usable again! I'll definitely be relying on community support with PRs for much of the maintenance effort. I am committed to doing my best here, however, so please don't be afraid to "spam" me with mentions on issues or PRs here, if it seems to be taking me awhile to respond 😅

2. I also do NOT have the permissions to publish package updates to NPM, and frankly would prefer to achieve that securely via Github Actions. Given that the author is quite busy with personal affairs, whoever, please know that it may quite some some before I achieve NPM package updates anytime soon, so I would recommend resolving your project's dependency on this package via github instead for the time being.

In any case, I'm happy to be able to close this issue out with a path forward that retains this as the official repo!