As discussed at this week's community call, we would like to find a way to improve velocity and reduce futz when making changes which involve release notes, docs and API, while still preserving the standalone capability of data-plane-api as the canonical API reference.

The proposal is to do something similar to what Istio have recently proposed (https://groups.google.com/d/msg/istio-dev/znLqMD-j-4o/AGvNAN2cAQAJ). We will have APIs and docs in envoyproxy/envoy, and then run a nightly job or a webhook bot to copy the API protos to envoyproxy/data-plane-api.

This will allow all the docs, release notes and API changes to be made alongside the implementation work in the main repo. This should not impact any existing users of the API protos.

We should ensure that the repo sync includes some SHA to allow consumers to be aware of the relationship between envoyproxy/data-plane-api commits and envoyproxy/envoy