Blacklight-maps seems fantastic if you don’t need the geoblacklight features.

(1) I’ve had lots of requests for an “OR” option on the main facet limits–like SearchWorks has. The advanced search has this feature. We have a facet for ‘Record Type’ (e.g. publication, object, oral history, film, photograph, etc) and we have users who would like to search across e.g. film or photograph. That could be implemented with a checkbox. Unfortunately it’s a little above my Rails chops & time at this point to implement.
(2) We do geographic name expansion and language stemming. It would be sweet to be able to let users turn those features off. Jonathan Rochkind wrote an article awhile back on how to do that–again, I unfortunately lack Rails chops & time to implement that.

To reduce upgrade/compatibility churn, I wonder if it might be helpful to avoid landing changes in master/release until they are fully baked. For major refactorings/ruby API changes, do all dev in master until the feature is done churning and everyone relevant is satisfied with it being complete. As opposed to right now it seems as if iterative development on new features sometimes happens in masters and even in releases, before a full picture of what the final API will look like exists. Eg SearchBuilder refactorings.

A more active and transparent Blacklight development process. We would be happy to contribute more, but it’s difficult to know a longer-term vision of the community.