Overview
As DevLake's awesome community continues to grow, we would like to keep track of the community contributions so that we can identify community members to promote to committers over time. This is a natural DevLake use case and I propose a "Community Overview" dashboard for this purpose.
This dashboard will focus on contributions in the format of pull requests, issues, and comments on either of those. Other types of contributions need to be tracked elsewhere.
Metrics & Panels
- Number of Unique PR Authors (and the trend)
- Number of Unique Issue Authors (and the trend)
- (Optional) Number of Unique Comment Authors (and the trend)
- New PR Authors [Selected Time Range] (This panel is a table showing a list of new PR authors with their PR counts)
- New Issue Authors [Selected Time Range] (This panel is a table showing a list of new Issue authors with their Issue counts)
- Committers (A list of current committers, not sure where we can get this data though, from Apache GitHub org or Apache API?)
- Committer Candidates (A list of users with the following info: when they join the community (first PR / Issue date), PR counts, Issue counts, comment counts, and etc.)
- Create a panel to show current month added_lines/deleted_lines/dev_eq for community contributors
- Create a panel to show the monthly changes added_lines/deleted_lines/dev_eq for community contributors
Feel free to propose more metrics and panels.
Data Issues
- The
creator_id column of the Issues table is empty
- Should we standardize the naming among
creator_id (Issues), author_id (pull_requests), and user_id (pull_request_comments)?
- GitHub plugin doesn't create entries in
Users table
Overview
As DevLake's awesome community continues to grow, we would like to keep track of the community contributions so that we can identify community members to promote to committers over time. This is a natural DevLake use case and I propose a "Community Overview" dashboard for this purpose.
This dashboard will focus on contributions in the format of pull requests, issues, and comments on either of those. Other types of contributions need to be tracked elsewhere.
Metrics & Panels
Feel free to propose more metrics and panels.
Data Issues
creator_idcolumn of theIssuestable is emptycreator_id(Issues),author_id(pull_requests), anduser_id(pull_request_comments)?Userstable