## Description: Seamless multi-master sync, that scales from Big Data to Mobile, with an Intuitive HTTP/JSON API and designed for Reliability.
## Issues: There are no issues requiring board attention ## Membership Data: Apache CouchDB was founded 2008-11-19 (11 years ago) There are currently 64 committers and 15 PMC members in this project. The Committer-to-PMC ratio is roughly 4:1. Community changes, past quarter: - No new PMC members. Last addition was Nick Vatamaniuc on 2017-11-07. - No new committers. Last addition was Jay Doane on 2019-01-05. ## Project Activity: The Vote[1] to adopt FoundationDB as CouchDB’s future underlying distribution and storage technology has passed unanimously. See the two previous board reports for more context. Current planning includes both a CouchDB 3.0 and a CouchDB 4.0 milestone. 3.0 will include the best version of the current, mostly Erlang-based project, with many new features contributed by various project partners (but notably IBM). This will be the LTS version for people who won’t be able to migrate to the newer technology foundation. There are a number of technical limitations that we are happy to adopt as a project going forward, but that might be deal- breakers for some users. As such, we’ll serve those users best with an excellent edition of the original technology stack. LTS-timelines are TBD. CouchDB 4.0 which is already under development concurrently will include a mostly[tm] API compatible version of CouchDB built on top of FoundationDB. API differences are going to be communicated clearly and migration paths documented thoroughly. For a little bit of context: with the addition of clustering, CouchDB 2.x turned from an accidentally strongly consistent database (because it was a single-node database) to an eventually consistent database, losing some essential properties in favour of scalability and fault tolerance. With the help of FoundationDB, those properties last after 1.x are going to be regained, while retaining scalability and fault tolerance, and while putting the CouchDB foundational underpinnings on a modern distributed database stack that would easily take us 10+ years to build. IBM is spearheading this effort within the ASF and is adding more resources to the CouchDB project in terms of development, release management, infrastructure as well as project management [1]: https://s.apache.org/couchdb-fib-vote ## Community Health: All parts of the existing community are participating in the 3.x and 4.x efforts. While no new committer-candidates have emerged yet, there is a small influx of new and promising voices.
