> My prediction is that very soon there will be a high profile open source fork of mongodb driven by an Apache style board and community That won't solve any o

> My prediction is that very soon there will be a high profile open source fork of mongodb driven by an Apache style board and community That won't solve any of the problems. The symptoms you describe also happen in the Apache Groovy "community", if you can call it that. Although they joined Apache's incubator in April last year (2015) and were promoted to a full project in November, the project manager "chair" privately owns the groovy-lang.org DNS name and if you click on most links for Groovy at Apache, they redirect to groovy-lang.org without any warning. He also keeps a private mailing list of groovy users which he collected by running a weekly newsletter for a year which he no longer maintains, and hasn't merged them with the Apache Groovy users mailing list. They run a separate build system for Groovy treating the Apache process as an add-on process, all against Apache guidelines. He refuses to refer to Groovy as "Apache Groovy" on first use which is what the ASF requires of project managers. Joining Apache is just another distribution strategy for them, despite the talk in Groovy circles a year ago about getting a proper governance structure. It didn't solve Groovy's problems, and it won't solve MongoDB's.