> 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
That is exacly what i mean. And yes, the final document should be in English. -- 此致！Best Regards 陈明雨 Mingyu Chen Email: chenmin...@apache.org At 2022-03-11 14:47:18, "OpenInx" <open...@gmail.com> wrote: >> 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 <gabrielleeb...@gmail.com> >wrote: > >> This will be a useful part and I have one more suggestion. >> We should re-organize our roadmap with DIP just like Apache >> <https://github.com/apache/airflow/issues/10176> Airflow community >> <https://github.com/apache/airflow/issues/10176>. 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, 陈明雨 <morning...@163.com> 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" <lingm...@apache.org> 写道： >> > >> 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 >> > > >> > >王博 <wangbo13...@gmail.com> 于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. >> > >> >> > >> 陈明雨 <morning...@163.com> 于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 >> > >> >> > >>
