Project Status

[samschurter]

Just wondering if this project is still active. I noticed a lot of features in the backlog that were marked as "Not Planned" recently. A lot of those would have been very useful.

[waprin]

@samschurter which features? and where do you even see this backlog? its open source so we can always do ourselves but just curious (Im both using this project and planning to blog about the general topic so curious what use case people are looking for)

[samschurter]

@waprin if you look at the closed issues, there are a bunch of issues that gannonh had created for enhancements, but all of them were suddenly closed as "not planned" a couple weeks ago. When I see that, it makes me think that a maintainer no longer plans on committing time to a project, maybe because they have run out of time or because the project has been superseded by something else. If that's the case, then I'll fork it privately and just hack on it for my own use without worrying about opening PRs. On the other hand, if gannonh does plan to maintain this, I'll try harder to make sure my changes can be merged back in.

Firebase also very recently released an official MCP. I don't like that it looks extremely rushed and haphazardly put together, but I imagine that it will get better with time.

The main feature that is a dealbreaker for using this MCP is the service account key. We only use application default credentials for development. After that, non-default databases, multiple project support, and advanced queries were the most interesting issues that are now not planned. In general though, anything that deals with Auth, Firestore, Storage, Rules, or Remote Config is likely to come in handy in the future for me.

[waprin]

@samschurter appreciate the info. interestingly neither this repo nor the official one has the simple feature I need (count queries). But this one was easier to fork than Google's and Im pretty happy with it in the sense that its' small and easy to understand. Let's keep an eye on options as they evolve.