is the plugin still maintain?

[lyseiha]

No description provided.

[jspizziri]

@billmalarky, there is still a good amount of interest in this package. Would you be open in bringing on new maintainers?

[billmalarky]

I would be, I've been very busy with work but yes I would be.

…

On Fri, Sep 24, 2021, 2:41 PM Jacob Spizziri ***@***.***> wrote: @billmalarky <https://github.com/billmalarky>, there is still a good amount of interest in this package. Would you be open in bringing on new maintainers? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#62 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAOFGU5IXTE4ZXRRLQWXOJDUDTIAJANCNFSM4KQH4W7Q> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[jspizziri]

@billmalarky , thanks for the response.

How would you like to select potential maintainers?

[iBotPeaches]

We still heavily use this plugin internally and Realm has been our biggest issue with the changing ecosystem. The plugin still is hooked to 2, but we are on 6 and even 10 looks quite tempting.

I think whatever you decide. Folks should take the same amount of care and effort of a good testing/ci process to ensure no regressions and document how Realm and these dependencies are involved together.

Like I wouldn't mine throwing up some GitHub Action conversions since the travis stuff is dead to keep the project alive in the sense of checking for if whomever will take the time to review/merge.

[iBotPeaches]

Just to update my above comment, nothing has changed for us and we still heavily use this plugin. We've forked it and begun some QoL updates as I described for GitHub Actions, Realm update and some fixes for jest. Mainly because the Hermes move with Realm is a big component for us.

https://github.com/sourcetoad/react-native-queue

[deevus]

@billmalarky This package has some great potential but needs a new maintainer. I'd be willing to submit a PR but there are currently open PRs that have presumably gone stale.

It seems as if @iBotPeaches et al could be good candidates if you were willing to give them the keys.

There are also some forks with promise such as https://github.com/inkitt/react-native-queue-asyncstorage by @inkitt which replaces Realm with AsyncStorage. I am actually using this one with some minor patches.

Some things I'd love to see:

• The storage provider be abstracted out into plugins such as react-native-queue-plugin-realm and react-native-queue-plugin-asyncstorage for example.
• Thread safety using mutexes or similar
• Delaying jobs
• Able to access the job + errors in the lifecycle events