This message was deleted.

Not to question the decision of using Google Doc, but why not go back to the old school markdown (or Asciidoc) design doc that were embedded in Gradle repository (or design-specs repo)? Most users that participate in the development have a GitHub account. The comment, version history, branching, comment history, activity tracking can all fit in the normal developer workflow.

Good question @daniel, we use Google Doc internally to brainstorm what the designs specs are and sometimes are collaborating in real time with each other on these documents. That real-time ness is often easier in Google Docs than GitHub. These docs are also textually heavy and not as much code heavy and at least for us Google docs is much better with support for spelling and grammar than GitHub. Plus, we often include tables, which are also in GitHub but not as easy. Like you mentioned, we could also use Github and have similar results. The real reason for Google Docs is that we are including the community in what we are already doing, just making it public. The current workflow of our developers is using the google docs and changing that to GitHub would change how they work.

Can the spec I wrote prior to departig regarding automated dependency updating with tools like Dependabot also get added to this drive?

Let me look into this for you!

@Piotr Jagielski and @Sterling should be able to track down this document 🙂

Oh I found it 😉

Perfect!

Much appreciated, do old links I sent to people redirect to this doc? Or is this a completely new doc?

Old links should work (at least they did for other files), I moved it rather than making it new