Re: [Discuss] About Doris Improvement Proposals

[OpenInx]

> 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"
> 主题: [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

Re: [Discuss] About Doris Improvement Proposals

[OpenInx]

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  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">
>> 主题: [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
>
>

Re: Re: [Discuss] About Doris Improvement Proposals

[OpenInx]

> But I would like to have a lower threshold to help the Doris community
quickly establish a mechanism for DSIP. This is equivalent to a cold start
process. In the meantime, PMC members will help with the translation of the
Chinese documentation.

Personally,  I will not suggest changing the normal apache way to establish
some kinds of mechanism. The correct direction is accepting general English
design document to apache doris board.  If there is a contributor who is
really not good at English technical writing, then he/she can request
PMC/committers from community to help to do the translate & pre-review
privately. But if he/she plan to publish the design document to apache
doris community,  it should be a general English document so that everyone
from the community can start do the reviewing in the same baseline.


On Fri, Mar 11, 2022 at 2:20 PM Gabriel Lee 
wrote:

> This will be a useful part and I have one more suggestion.
> We should re-organize our roadmap with DIP just like Apache
>  Airflow community
> . This will help
> developers
> a lot to understand what we are doing and participate in some jobs.
>
> On Fri, 11 Mar 2022 at 14:02, 陈明雨  wrote:
>
> > 1. For the existed or developing feature, this depends on the situation,
> > such as the subsequent vectorization transformation related to Compaction
> > or Stream load, I think it is necessary to form a DSIP.
> > 2. How to ensure that this rule can be implemented for a long time?
> > As reviewers, we can ask for the DSIP, for example:
> > https://github.com/apache/incubator-doris/pull/8437
> >
> >
> >
> >
> > --
> >
> > 此致！Best Regards
> > 陈明雨 Mingyu Chen
> >
> > Email:
> > chenmin...@apache.org
> >
> >
> >
> >
> >
> > 在 2022-03-11 13:53:31，"ling miao"  写道：
> > >> How to ensure that this rule can be implemented for a long time?
> > >Maybe we can review the wiki is filled every month by hosting regular
> > >developer conferences.
> > >
> > >We can put the writing DIP wiki in the development process description
> > >document. (Just like the development process description for other
> > projects)
> > >For those who submit PR directly without DIP, contributors can comment
> to
> > >remind him to submit DIP first.
> > >
> > >Ling Miao
> > >
> > >王博  于2022年3月11日周五 13:48写道：
> > >
> > >> +1
> > >> I have two more questions.
> > >> Frist:
> > >> For many projects that have been already completed or doing, do I need
> > to
> > >> supplement this wiki?
> > >> Such as Vectorization or Stability optimization of Load Process .
> > >> Second:
> > >> How to ensure that this rule can be implemented for a long time?
> > >> Maybe we can review the wiki is filled every month by hosting regular
> > >> developer conferences.
> > >>
> > >> 陈明雨  于2022年3月10日周四 13:25写道：
> > >>
> > >> > 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
> > >>
> > >>
> > >>
> > >> --
> > >> 王博  Wang Bo
> > >>
> >
>