It's great to compose the design document and review the document with google doc. My suggestion is once we finish the review process it is better to use ASF wiki to host these documentation. Because some people may have some trouble to access the google doc.
Just my 2 cents. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Thu, Mar 10, 2022 at 9:09 PM OpenInx <open...@gmail.com> wrote: > > Besides, the wiki page from apache org is a good place to share the > design idea, but it is not a perfect tool for others to comment and > discuss. we cannot just select the specific line to share the > thoughts from reviewers. In general, the wiki page is friendly for > writers but it's not for reviewers. The google document is a perfect tool > in my mind for both writers and reviewers. Let me take an example document > [1] from apache iceberg community. In this page, we can see a lot of > interaction like questions and replies. That's really helpful for the > authors & reviewers to exchange their thoughts. So I will recommend > adopting the google document, and we can create a page (in wiki page or > apache doris official document page) to collect all those google design > documents. > > [1]. > https://docs.google.com/document/d/1bN6rdLNcYOHnT3xVBfB33BoiPO06aKBo56SZmuU9pnY/edit > > On Thu, Mar 10, 2022 at 8:54 PM OpenInx <open...@gmail.com> wrote: > > > > Probably most of the current Doris development comes from China, so we > > do not refuse to use Chinese to write DSIP, because when describing some > > complex content, it may be > > > easier to express clearly in Chinese. > > > For DSIPs written in Chinese, Doris PMC members will assist with English > > translation when appropriate. > > > > Although Apache Doris was born from China and its core contributors come > > from China, I still don't think it's reasonable to accept any technical > > design document which is not written in English. Indeed, it may be easier > > to express technical details clearly in Chinese for people from China, but > > it also implies: it will be harder to understand & get the points for a > > non-Chinese speaker. I believe this is not good for growing the diversity > > of the Apache project , according to my several apache experience. > > > > In general, I will suggest accepting the standard English technical > > design document in the apache doris community, so that everyone from > > everywhere can discuss, understand, comment, share their thoughts. > > > > > > On Thu, Mar 10, 2022 at 5:27 PM luzhijing <543881...@qq.com.invalid> > > wrote: > > > >> +1 > >> > >> > >> > >> > >> ------------------ 原始邮件 ------------------ > >> 发件人: > >> "dev" > >> < > >> morning...@163.com>; > >> 发送时间: 2022年3月10日(星期四) 中午1:25 > >> 收件人: "doris-dev"<dev@doris.apache.org>; > >> > >> 主题: [Discuss] About Doris Improvement Proposals > >> > >> > >> > >> Hi All: > >> I would like to start using "Doris Improvement Proposals(DSIP)" to save > >> all design doc of major features of Doris. > >> The motivation of DSIP and details can be found here[1]. > >> > >> > >> Please feel free to discuss. > >> > >> > >> [1] > >> https://cwiki.apache.org/confluence/display/DORIS/Doris+Improvement+Proposals > >> > >> > >> > >> -- > >> > >> 此致！Best Regards > >> 陈明雨 Mingyu Chen > >> > >> Email: > >> chenmin...@apache.org > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@doris.apache.org For additional commands, e-mail: dev-h...@doris.apache.org
