@Urbanecm: in theory, this request can be (somewhat easily) fulfilled by editing a configuration file for mapframe sites and deploying it into production. The ability to do that requires admin rights to edit the file and the ability to do production releases during normal SWAT windows.
The issue that we have is that we, the Maps team, do not have the engineering resources to support any requests for feature updates or any bugs that aren't critical, as I noted in my comment earlier.
We are having an internal conversation on the feasibility of updating the mapframe site configuration file—as a one-off request—for your wiki and for the 3 other site requests that we've received. We still will not be able to support any feature requests or minor bug fixes related to the map service, but if we decide to undertake this one-off request, it would allow further usage of the maps service on 4 Wikipedias that currently only have access to the maplink functionality.
I know how can be this request processed - I process similar requests on regular basis. So just to be sure I understand you correctly. The problem is that you can't maintain the extension?
@Urbanecm We do not expect any particular technical issues with enabling mapframe to more small wikis (large wikis like enwiki might be an issue in term of load).
The maps-team is very short on engineering resources at the moment. So the risk is that additional use cases will be discovered by new communities and that we won't have the resources to implement those new use cases. We have enough resources to maintain the extension in its current state and to fix any current feature that is obviously broken, but not to evolve it. As long as this restriction is understood, we have no objection to enabling mapframe further. We just want to manage the expectation...