There are few challenges in following PR,
1. There should be 2 JIRA,
- For issues for discussion, we need have Design JIRA
- For code, need to have code JIRA
2. If same same Jira for design and code, need have 2 PR for 1 JIRA
So both above approach does not seems good for small changes / discussion.
We can see / conclude the approach for discussion for small changes /
design.
Regards
Sumit
On Tue, Apr 15, 2025 at 10:50 PM Ritesh Shukla <rit...@cloudera.com.invalid>
wrote:
> On Tue, Apr 15, 2025 at 9:34 AM Tsz Wo Sze <szets...@apache.org> wrote:
>
> > +1 on md over google doc.
> >
> > > ... Google Docs do not show up in Google searches ...
> >
> > This is bad for our design docs. How about the other search engines?
> >
> >
> > I don't know of any search engine that searches through all public docs
> for a certain topic. Also, even Jiras don't show up quite prominently in
> Google searches from anecdotal experience unless one adds the term jira to
> the search.
>
> We should eventually move all the core design docs into the website which
> will show up in searches.
>
--
*Sumit Agrawal* | Senior Staff Engineer
cloudera.com <https://www.cloudera.com>
[image: Cloudera] <https://www.cloudera.com/>
[image: Cloudera on Twitter] <https://twitter.com/cloudera> [image:
Cloudera on Facebook] <https://www.facebook.com/cloudera> [image: Cloudera
on LinkedIn] <https://www.linkedin.com/company/cloudera>
------------------------------
