Thank you for your opinion. I updated accordingly as below.
- Time escaped since latest response for open issues/PRs whose due date is not set. - Whether the the issue/pr expires. - Total time escaped since created (just for reference) - Time escaped since /lgtm
On Wed, Apr 15, 2020 at 1:15 AM Jianmin Wang jianmin@iscas.ac.cn wrote:
Hi Fred,
The follow is my thought, only for your reference.
- Time escaped since latest response for open issues/PRs
+1. This information is useful for the issue which wasn’t set due date. If assignee have already set due date, maybe this information is useless and due date is more important.
- Total time escaped since created
I think the first time escaped is more useful than this one. Especially the duration of issues is different.
- Time escaped since /lgtm
+1
- 每个未关闭的Issue/PR从最近一次comment到当前日期的持续时长。
+1 这个信息对于没有设置截止日期的 issue 来说比较有用，但是如果设置的截止日期，或许就应该参照截止日期来度量，看是否过期。
- 每个未关闭的Issue/PR从创建到当前的持续时长。
我认为相比于第一个信息，这个信息可能用处不大，毕竟不同的 issue 持续的时间是很不同的。
- 每个为关闭的PR从第一个/lgtm标签到当前的持续时长。
+1
Best Regards,
Jianmin
On 14 Apr 2020, at 11:29 PM, Fred Li yongle.li@gmail.com wrote:
Hi all,
On today's weekly meeting of openEuler community governance, we had the following discussion. How to improve the response to PRs and Issues? Solution:
- Time escaped since latest response for open issues/PRs
- Total time escaped since created
- Time escaped since /lgtm
To explain myself clearly, I write it in Chinese again. 背景： 我们发现有不少Issue或者PR的响应不够及时，这个影响到了开发的进度或者用户的感受，对于社区发展不利。
困难： 作为开源社区，大部分开发者是来自不同的公司，大家在社区里面的投入比例和优先级各不相同，无法设置比如SLA这样的要求。
可能的解决方案： 从技术上做个统计，共计如下几个度量项
- 每个未关闭的Issue/PR从最近一次comment到当前日期的持续时长。
- 每个未关闭的Issue/PR从创建到当前的持续时长。
- 每个为关闭的PR从第一个/lgtm标签到当前的持续时长。
这些数据或许可以帮助大家查看没有处理的issue或者pr。
如果您有任何建议或者想法，请在本邮件回复。谢谢！
-- Regards Fred Li (李永乐) _______________________________________________ Community mailing list -- community@openeuler.org To unsubscribe send an email to community-leave@openeuler.org