You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[Updated Issues Count](./community-service-and-support.md#updated_issues_count) | Determine the number of issues updated in the last 90 days. | 2000 | 19.721%
46
46
[Close PR Count](./community-service-and-support.md#close_pr_count) |The number of PR accepted and declined in the last 90 days.| 4500 | 19.721%
47
-
[Issue First Response](./community-service-and-support.md#issue_first_response) |Average/Median first comments response (in days) for new issues created in the last 90 days. This excludes bot responses,, the creator's own comment, or an action assigned by the issue. If the issue has been unanswered, the first response time is not counted.| 15 | 14.372%
48
-
[Bug Issue Open Time](./community-service-and-support.md#bug_issue_open_time) | Average/Median time (days) that bug issues have been opened for issues created in the last 90 days.|60|12.876%
49
-
[PR Open Time](./community-service-and-support.md#pr_open_time) |Average/Median processing time (days) for new change requests created in the last 90 days, including closed/accepted change requests and unresolved change requests.|30|12.876%
47
+
[Issue First Response](./community-service-and-support.md#issue_first_response) |Average/Median first comments response (in days) for new issues created in the last 90 days. This excludes bot responses,, the creator's own comment, or an action assigned by the issue. If the issue has been unanswered, the first response time is not counted.| 15 | -14.372%
48
+
[Bug Issue Open Time](./community-service-and-support.md#bug_issue_open_time) | Average/Median time (days) that bug issues have been opened for issues created in the last 90 days.|60|-12.876%
49
+
[PR Open Time](./community-service-and-support.md#pr_open_time) |Average/Median processing time (days) for new change requests created in the last 90 days, including closed/accepted change requests and unresolved change requests.|30|-12.876%
50
50
[Issue Comment Frequency](./community-service-and-support.md#issue-comment-frequency) |Determine the average number of comments per issue created in the last 90 days.|5|10.217%
51
51
[Code Review Count](./community-service-and-support.md#code-review-count) |Determine the average number of review comments per pull request created in the last 90 days|8| 10.217%
Copy file name to clipboardExpand all lines: metrics-models/productivity/community-service-and-support.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,15 +33,15 @@ The more code you contribute, the more PR requests you need to close (accept or
33
33
### Issue First Response
34
34
35
35
* Definition: Average/Median first comments response (in days) for new issues created in the last 90 days. This excludes bot responses,, the creator's own comment, or an action assigned by the issue. If the issue has been unanswered, the first response time is not counted.
36
-
* Weight: 14.372%
36
+
* Weight: -14.372%
37
37
* Threshold: 15 days
38
38
39
39
We use this indicator to sense "Community temperature". And for contributors who join the community, if their questions are answered in a timely manner by the community, there's a good chance that they would be retained and continue to contribute to the community (according to [Mozilla Research](https://docs.google.com/presentation/d/1hsJLv1ieSqtXBzd5YZusY-mB8e1VJzaeOmh8Q4VeMio/edit#slide=id.g43d857af8_0177)) . At the same time, we found that more and more robots have been used to assist with Issue processing in recent years, so we eliminated robot interference and focused on human replies.
40
40
41
41
### Bug Issue Open Time
42
42
43
43
* Definition: Average/Median time (days) that bug issues have been opened for issues created in the last 90 days.
44
-
* Weight: 12.88%
44
+
* Weight: -12.88%
45
45
* Threshold: 60 days
46
46
* Note: Issue that labeled by Bugs.
47
47
@@ -50,7 +50,7 @@ The Bug type Issue represents how efficiently the community handles issues that
50
50
### PR Open Time
51
51
52
52
* Definition: Average/Median processing time (days) for new change requests created in the last 90 days, including closed/accepted change requests and unresolved change requests.
53
-
* Weight: 12.88%
53
+
* Weight: -12.88%
54
54
* Threshold: 30 days
55
55
56
56
We are seeking for the change request fast close, including code merged or rejected. Otherwise the longer it takes for a change request to be resolved, the greater the risk that merge-conflict will occur, while other change requests that depend on it will also be stalled.
@@ -95,9 +95,9 @@ Metrics Name | Eigenvector | Weight
[Contributor Count](./activity.md#contributor-count) | Determine how many active code commit authors, pr authors, review participants, issue authors, and issue comments participants there are in the past 90 days | 2000 | 18.009%
20
20
[Commit frequency](./activity.md#commit-frequency) |Determine the average number of commits per week in the past 90 days.| 1000 | 18.009%
21
-
[Updated Since](./activity.md#updated-since) |Determine the average time per repository since the repository was last updated (in months).| 0.25 | 12.742%
21
+
[Updated Since](./activity.md#updated-since) |Determine the average time per repository since the repository was last updated (in months).| 0.25 | -12.742%
22
22
[Org Count](./activity.md#organization-count) | Number of organizations to which active code contributors belong in the past 90 days. |10|11.501%
23
23
[Created Since](./activity.md#created-since) |Determine how long a repository has existed since it was created (in months).|120|7.768%
24
24
[Issue Comment Frequency](./activity.md#issue-comment-frequency) |Determine the average number of comments per issue created in the last 90 days.|5|7.768%
Copy file name to clipboardExpand all lines: metrics-models/robustness/activity.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ As an outcome indicator of this model, it identifies the sustainability and quan
34
34
35
35
## Updated Since
36
36
* Definition: Determine the average time per repository since the repository was last updated (in months).
37
-
* Weight: 12.74%
37
+
* Weight: -12.74%
38
38
* Threshold: 0.25 months
39
39
40
40
This metric is used to indicate how often the project is updated. It identifies good communities for development collaboration and management, and makes frequent iterative and incremental development to promote continuous improvement in software quality. But the industr domains of a software project also determines that the frequency of its iterations is not always as high as possible, some Linux distribution projects, for example, exhibit a very typical pattern of code iterations with periodic release planning. Here we focus on the trend of the project during each cycle, and the relative results compared with the projects belong to the similar domains.
@@ -138,7 +138,7 @@ Metrics Name | Eigenvector | Weight
0 commit comments