Hi,

> Last week, I add a label named “solution” for the issues which are 
solutions of common / uncommon issues, like [1].

Great~

I have added many labels [1], let's label the issues and PRs!

[1] https://github.com/apache/iotdb/labels?page=1&sort=name-asc

Thanks,
--
Jialin Qiao
School of Software, Tsinghua University

乔嘉林
清华大学 软件学院

> -----原始邮件-----
&gt; 发件人: "孙泽嵩" <[email protected]>
&gt; 发送时间: 2020-11-16 14:35:21 (星期一)
&gt; 收件人: [email protected]
&gt; 抄送: 
&gt; 主题: Re: Some suggestions about label
&gt; 
&gt; Hi Jialin,
&gt; 
&gt; It’s nice of you to help refactor the labels.
&gt; 
&gt; Last week, I add a label named “solution” for the issues which are 
solutions of common / uncommon issues, like [1].
&gt; 
&gt; Do you think it is acceptable?
&gt; 
&gt; [1] https://github.com/apache/iotdb/issues/2039
&gt; 
&gt; Best,
&gt; -----------------------------------
&gt; Zesong Sun
&gt; School of Software, Tsinghua University
&gt; 
&gt; 孙泽嵩
&gt; 清华大学 软件学院
&gt; 
&gt; &gt; 2020年11月16日 14:32,Jialin Qiao <[email protected]> 写道:
&gt; &gt; 
&gt; &gt; Hi Benedict,
&gt; &gt; 
&gt; &gt; Welcome!  +1 for adding labels in github issue. I could help refactor 
the labels.
&gt; &gt; 
&gt; &gt; I do not remember the result of the discussion last year... 
&gt; &gt; I suggest enhancing the github issue, since most people just look 
through the github issue instead of Jira.
&gt; &gt; 
&gt; &gt; Thanks,
&gt; &gt; --
&gt; &gt; Jialin Qiao
&gt; &gt; School of Software, Tsinghua University
&gt; &gt; 
&gt; &gt; 乔嘉林
&gt; &gt; 清华大学 软件学院
&gt; &gt; 
&gt; &gt; &gt; -----原始邮件-----
&gt; &gt; &gt; 发件人: "Xiangdong Huang" <[email protected]>
&gt; &gt; &gt; 发送时间: 2020-11-16 11:31:40 (星期一)
&gt; &gt; &gt; 收件人: dev <[email protected]>
&gt; &gt; &gt; 抄送: 
&gt; &gt; &gt; 主题: Re: Some suggestions about label
&gt; &gt; &gt; 
&gt; &gt; &gt; Hi,
&gt; &gt; &gt; 
&gt; &gt; &gt; Thanks.
&gt; &gt; &gt; I think we had discussed this topic about one year ago, and then 
we added
&gt; &gt; &gt; some modules in JIRA.
&gt; &gt; &gt; 
&gt; &gt; &gt; +1 to re-organize the modules in jira and labels of github 
issue. :D
&gt; &gt; &gt; 
&gt; &gt; &gt; Best,
&gt; &gt; &gt; -----------------------------------
&gt; &gt; &gt; Xiangdong Huang
&gt; &gt; &gt; School of Software, Tsinghua University
&gt; &gt; &gt; 
&gt; &gt; &gt;  黄向东
&gt; &gt; &gt; 清华大学 软件学院
&gt; &gt; &gt; 
&gt; &gt; &gt; 
&gt; &gt; &gt; Benedict Jin <[email protected]> 于2020年11月15日周日 下午11:46写道:
&gt; &gt; &gt; 
&gt; &gt; &gt; &gt; Hello everyone. I am new here. I see a lot of active issues 
and pull
&gt; &gt; &gt; &gt; requests in our project. It can be seen that the community 
is very active.
&gt; &gt; &gt; &gt; If possible, I would like to make a little suggestion about 
label. We can
&gt; &gt; &gt; &gt; learn from some experience of Apache Druid. The label 
classification can be
&gt; &gt; &gt; &gt; improved in terms of the difficulty of the problem, the 
kind of module, and
&gt; &gt; &gt; &gt; third-party components. Initial communication with @乔嘉林, 
the modules can
&gt; &gt; &gt; &gt; probably be summarized as cli, python-client, java-client, 
jdbc,
&gt; &gt; &gt; &gt; c++-client, go-client, storage-engine, query-processing, 
wal, documents,
&gt; &gt; &gt; &gt; examples, query planner, sql parser, file sync, schema 
manager, compaction,
&gt; &gt; &gt; &gt; rpc, cluster etc. And summarize the third-party components 
into
&gt; &gt; &gt; &gt; hadoop-tsfile, hive-tsfile, spark-tsfile, spark-iotdb, 
flink-tsfile,
&gt; &gt; &gt; &gt; flink-iotdb, rocketmq-iotdb, grafana etc.
&gt; &gt; &gt; &gt;
&gt; &gt; &gt; &gt; In addition, it is also considered whether jira can be 
unified in github
&gt; &gt; &gt; &gt; issues for management. On the one hand, it can be unified 
to facilitate
&gt; &gt; &gt; &gt; retrieval, and on the other hand, considering the network 
environment may
&gt; &gt; &gt; &gt; make it impossible to access jira in some areas. Finally, I 
wish the
&gt; &gt; &gt; &gt; project better.
&gt; &gt; &gt; &gt;
&gt; &gt; &gt; &gt; FYI, https://github.com/apache/druid/labels .
&gt; &gt; &gt; &gt;
&gt; &gt; &gt; &gt;
&gt; &gt; </[email protected]></[email protected]></[email protected]>
&gt; 
</[email protected]></[email protected]>

Reply via email to