Update or confirm project maintenance status

[fohlin]

Thanks for publishing this project! The README states

Mainteinance Status: Actively Maintained

but the activity seems to have stagnated and there are a few sensible PRs hanging.

There is absolutely no shame in admitting that time or energy is lacking. If @priyankpat is blocked, I would suggest updating the README to say Maintenance status: seeking maintainers. If @priyankpat is available as maintainer, it think it would be a great comfort to potential users of this project to have that confirmed.

(We are implementing Remote Config in our Capacitor-based app and would be willing to contribute. Maybe @mic345 is interested as well, considering the extensive PR submitted. Any way forward here is good. 🙂)

[crabbydavis]

Ya I ended up pulling @mic345 's branch to get a working version of this plugin

[gugahoi]

A little disappointing that this has been left to rot despite contributions from the community.

@crabbydavis I can't seem to find that fork in npm, how did you go about pulling it?

[crabbydavis]

@gugahoi I went to his fork and downloaded it - https://github.com/mic345/firebase-remote-config
I put it in the root of my project and linked it as if doing local testing

[gugahoi]

Gotcha. I guess that's not a great long term solution. For now I have published the changes under @joinflux so that we can leverage them across our products, including in our automated pipelines. I have also made some changes to suit my own use cases but am happy to get others involved to collaborate, if they are interested:

https://www.npmjs.com/package/@joinflux/firebase-remote-config
https://www.npmjs.com/package/@joinflux/firebase-analytics

I have tested them in web and iOS but not yet in Android and everything worked as expected for me.

[muhrifqii]

@gugahoi please enable issue tracker on joinflux fork

[eufelipemateus]

i am using firebase native code..