Request for clarification on the status of the repository

[scris]

I failed to find any official updates into this repository for the whole past month. And at the same time, as all of the privileges required to contribute into this repository is on first-party contributors, this repository is not coming with great community efforts.

Thus I'm requesting if there can be a clarification on the true status of this repository. Will we still be able to see any first-party efforts (that is the best situation)? Or if not, will this repository be a repository that's more community-driven? Thanks!

[sync-by-unito[bot]]

➤ PM Bot commented:

Jira ticket: RDART-1107

[nirinchev]

It's community driven. The team at MongoDB will be available for some minimal assistance with releases/PR approvals, but we won't be actively developing features. In the beginning, our preference is that contributors fork the repo and submit PRs from their forks. As we identify competent and active contributors, we'd be willing to work with them to give them push access to the repo.

[dotjon0]

From what we understand MongoDB have committed to carrying out maintenance on this repo for the next 12 months (with some offered 24 months through extension application) from the depreciation announcement date last month - to facilitate 'production usage' during this period.

Questions

1. Are MongoDB are carrying out 'maintenance' on Device Sync and this repo until September 2025 (or September 2026 if approved by MongoDB via extension application)?
2. What is the scope of 'maintenance', does it included 'bugs' reported?
3. Are MongoDB assigning the correct level of 'maintenance' resource to Device Sync and the Flutter Realm SDK so that we can use Device Sync and the Flutter Realm SDK in 'production usage' until September 2025 (September 2026 if approved by MongoDB via extension application)?
4. There have been no 'maintenance' updates to the Flutter Realm SDK in over a month despite various open bugs - why is this?

Concerns

So far, we are getting deja vu when MongoDB depreciated the Flutter Realm SDK in Q4 2023 without notice - where all updates, maintenance, support, etc was halted immediately with no notice for the Flutter Realm SDK and the whole Flutter Realm SDK team re-assigned/etc to other areas of MongoDB. From what we have seen so far, it feels very much the same where MongoDB customers are in the dark and communications are lacking. Its a shame Device Sync and Flutter Realm SDK have been depreciated, but well all get this can happen and understand - however, we do all expect and need MongoDB to clarify that they are fully behind the Flutter Realm SDK until September 2025 (or September 2026 if approved by MongoDB via extension application) so that your customers have confidence in using Device Sync and Flutter Realm SDK in 'production usage' during this period.

Many thanks as always

[nirinchev]

Sorry for the confusion, let me try to clarify. We're addressing production-impacting bugs reported via the support portal. There haven't been such for the Flutter SDK, which is why it's been a little quiet here + people being on vacation or working on other things. Bugs reported on Github or ones that have workarounds will be evaluated on a case-by-case basis during our sync up meetings, but we expect not to work on the majority of those and instead rely on the community to resolve them. To give a more concrete example, a bug that impacts the generator for a company that is using the local database and hasn't gone in production is unlikely to be picked up, whereas a bug that prevents shipping new releases due to a new requirement from Google/Apple is.

Hope that clears it up - if you have further questions, feel free to post them here or reach out to your account executive.

[dotjon0]

Thanks for the clarification @nirinchev, thats super useful to understand in terms of knowing we should use the MongoDB support portal for production bugs/issues. Appreciated, hope you have a great rest of week.