Hi, @Xiangdong thank you for helping to clarify my original intention. you are right, I really want to list some components to let users choose which component the given issue belongs to.
@Jialin I think approach 4 would be more meaningful for IoTDB. Could you please add the detailed description for each component, such as, describe the relationship between `tsfile` and (`tsfile/hive-tsfile/spark-tsfile/Hadoop-tsfile`), and which changes belong to `Other` component, etc., which can help us better understand the reasons for such classification. On the other hand, we will further discuss whether there is optimization space for this component classification. What do you think? Best, Jincheng Xiangdong Huang <[email protected]> 于2020年1月9日周四 下午4:46写道： > > No that is not the Apache Way. No one should be in charge of an area > > I think Jincheng's mean is, we can list some components to let users > choose which component the given issue belongs to. > > As for which components should be listed, we need to have a discussion. > > > No one should be in charge of an area > > Yes everyone can assign an issue to himself/herself. > > Best, > ---------------------------------- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院 > > > jincheng sun <[email protected]> 于2020年1月9日周四 下午4:38写道： > > > > No that is not the Apache Way. No one should be in charge of an area. > > > > Oh, great thanks for correcting me Justin, maybe it's my language > > expression problems. I mean some contributors and committers will be very > > interested in some components, then spend more time, and be more familiar > > with the code. > > > > Best, > > Jincheng > > > > > > Justin Mclean <[email protected]> 于2020年1月9日周四 下午4:27写道： > > > > > Hi, > > > > > > > When our community grows stronger, each\ module may have some > specific > > > person in charge. > > > > > > No that is not the Apache Way. No one should be in charge of an area. > > > > > > Thanks, > > > Justin > > >
