+1
Thanks,
Tejaskriya
On Tue, 15 Apr, 2025, 07:00 Devesh Singh,
wrote:
> +1
>
> Thanks & Regards
> Devesh Singh
>
>
> On Tue, 15 Apr, 2025, 2:59 am Dinesh Chitlangia,
> wrote:
>
> > +1
> >
> >
> > Thanks,
> > Dinesh
> >
> > On Mon, Apr 14, 2025, 1:42 PM Ritesh Shukla wrote:
> >
> > > Hi,
> >
+1
Thanks & Regards
Devesh Singh
On Tue, 15 Apr, 2025, 2:59 am Dinesh Chitlangia, wrote:
> +1
>
>
> Thanks,
> Dinesh
>
> On Mon, Apr 14, 2025, 1:42 PM Ritesh Shukla wrote:
>
> > Hi,
> >
> > We should shift our design discussions from Google Docs to Markdown files
> > managed through GitHub Pu
+1
Thanks,
Dinesh
On Mon, Apr 14, 2025, 1:42 PM Ritesh Shukla wrote:
> Hi,
>
> We should shift our design discussions from Google Docs to Markdown files
> managed through GitHub Pull Requests. This approach would:
>
>1. Keep our discussions in the same system as our code, creating a more
>
+1
Initially I was reluctant because of the cost of converting Google Docs to
Markdown.
However, worry no more! Google Docs has built-in support for Markdown!
Follow the instructions in this page
https://support.google.com/docs/answer/12014036?hl=en
So if anyone writes an initial draft in Google
Hi,
We should shift our design discussions from Google Docs to Markdown files
managed through GitHub Pull Requests. This approach would:
1. Keep our discussions in the same system as our code, creating a more
cohesive history
2. Make our design documents more accessible to developers alr
