Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
The Project Health Dashboard shows a quick snapshot of the project's health by combining metrics from the OSSF Scorecard project and the CNCF CLOMonitor project to compute the overall best practices score for the projects.
This feature gives you complete visibility on areas to improve in accordance with the OSS best practices guidelines for project setup, as well as the ability to monitor the project's health and take immediate action when it begins to deteriorate. This dashboard will also act as a checklist of sorts for the projects when they are ready to graduate.
Project managers, technical committee members (TSO/TOC), and community administrators/managers use this dashboard to analyze the selected projects as they progress from one stage to the next in terms of maturity to ensure they meet the foundation's standards.
This feature will be available to all LF users, i.e., anyone with the LFID.
On a regular basis, a number of checks are performed on each repository listed in the database.
Checks are grouped into check sets.
One or more check sets
are applied to a single repository, and each check set specifies the number of checks that will be performed on the repository.
The check’s file must declare the following information:
ID
: check identifier.
WEIGHT
: weight of this check, used to calculate scores.
CHECK_SETS
: check sets this new check belongs to.
This check determines whether the project has generated executable (binary) artifacts in the source repository. For more details, see the check documentation.
ID: code_review
This check determines whether the project requires code review before pull requests (merge requests) are merged. For more details, see the check documentation.
ID: dangerous_workflow
This check determines whether the project’s GitHub Action workflows has dangerous code patterns. For more details, see the check documentation.
ID: dependency_update_tool
This check tries to determine if the project uses a dependency update tool, specifically dependabot or renovatebot. For more details, see the check documentation.
ID: maintained
This check determines whether the project is actively maintained. For more details, see the check documentation.
ID: sbom
List of components in a piece of software, including licenses, versions, etc.
This check passes if:
The latest release on Github includes an asset which name contains sbom. Regexps used:
The repository’s README
file contains a SBOM section that explains where they are published to, format used, etc. Regexps used to locate the title header:
ID: security_policy
Clearly documented security processes explaining how to report security issues to the project.
This check passes if:
A security policy file is found in the repository. Globs used:
A security policy reference is found in the repository’s README
file. This can be in the form of a title header or a link. Regexps used:
A security policy file is found in the default community health files repository.
ID: signed_releases
This check tries to determine if the project cryptographically signs release artifacts. For more details, see the check documentation.
ID: token_permissions
This check determines whether the project’s automated workflows tokens are set to read-only by default. For more details, see the check documentation.
The best practices health score is defined as the aggregated score based on the scores computed for each segment defined under the categories Documentation, License, Best Practices, Security and Legal. In calculating the final score, each component carries its own weight.
The weight of the segment is the sum of the weights of each check in that segment. A check is the best practice identifier as defined by the CNCF community. For more information, see checks.
The best practice score is calculated only for GitHub project repositories.
The default values for every check in a segment are defined here.
For the computation logic of the scores, refer to the code.
The best practices health score is calculated for each repository that is configured or enabled for the check. For instance, only the repository Kubernetes can be enabled for computing scores, excluding the rest of the repositories.
Click to expand and see the check sets
for each segment.
ID: license_approved
Whether the repository uses an approved license or not.
This check passes if:
The license identified matches any of the following:
ID: license_scanning
License scanning software scans and automatically identifies, manages, and addresses open source licensing issues.
This check passes if:
A FOSSA
or Snyk
link is found in the repository’s README
file. Regexps used:
A link pointing to the license scanning results is provided in the .clomonitor.yml metadata file.
ID: license_Apache_2.0
Identifier extracted from the provided license file.
This check passes if:
A license file is found in the repository and we can detect the license used. Globs used:
A license Apache-2.0 can be obtained from GitHub.
ID: analytics
Project websites provide some web analytics.
This check passes if:
A Google Analytics 3 (Universal Analytics) Tracking ID is found in the source of the website configured in GitHub. Regexps used:
A Google Analytics 4 Measurement ID is found in the source of the website configured in Github. Regexps used:
The HubSpot tracking code is found in the source of the website configured in Github. Regexps used:
ID: artifacthub_badge
Projects can list their content on Artifact Hub to improve their discoverability.
This check passes if:
An Artifact Hub
badge is found in the repository’s README
file. Regexps used:
ID: cla
The CLA defines the conditions under which intellectual property is contributed to a business or project.
This check passes if:
A CLA check is found in the latest merged PR on GitHub. Regexps used:
This check will be automatically marked as exempt if the DCO check passes but this one does not.
ID: community_meeting
Community meetings are often held to engage community members, hear more voices, and get more viewpoints.
This check passes if:
A reference to the community meeting is found in the repository’s README
file. Regexps used:
ID: dco
Mechanism for contributors to certify that they wrote or have the right to submit the code they are contributing.
This check passes if:
The last commits in the repository have the DCO signature (Signed-off-by). Merge pull request and merge branch commits are ignored for this check.
A DCO check is found in the latest merged PR on GitHub. Regexps used:
This check will be automatically marked as exempt if the CLA check passes, but this one does not.
ID: github_discussions
Projects should enable GitHub discussions in their repositories.
This check passes if:
A discussion that is less than one year old is found on GitHub.
ID: openssf_badge
The Open Source Security Foundation (OpenSSF) Best Practices badge is a way for Free/Libre and Open Source Software (FLOSS) projects to show that they follow best practices.
This check passes if:
An OpenSSF
(CII) badge is found in the repository’s README
file. Regexps used:
ID: recent_release
The project should have released at least one version in the last year.
This check passes if:
A release that is less than one year old is found on GitHub.
ID: slack_presence
Projects should have presence in the CNCF Slack or Kubernetes Slack.
This check passes if:
A reference to the CNCF Slack or Kubernetes Slack is found in the repository’s README
file. Regexps used:
ID: adopters
List of organizations using this project in production or at stages of testing.
This check passes if:
An adopters file is found in the repository. Globs used:
An adopters reference is found in the repository’s README
file. This is in the form of a title header or a link. Regexps used:
ID: changelog
A curated, chronologically ordered list of notable changes for each version.
This check passes if:
A changelog file is found in the repository. Globs used:
A changelog reference is found in the repository’s README
file. This can be in the form of a title header or a link. Regexps used:
A changelog reference is found in the last GitHub release content body. Regexps used:
ID: code_of_conduct
Adopt a code of conduct to establish community standards, promote an inclusive and welcoming initiative, and outline procedures for handling abuse.
This check passes if:
A code of conduct file is found in the repository. Globs used:
A code of conduct reference is found in the repository’s README
file. This can be in the form of a title header or a link. Regexps used:
A code of conduct file is found in the default community health files repository, for example.
ID: contributing
A contributing file in your repository provides potential project contributors with a short guide to how they can help with your project.
This check passes if:
A contributing file is found in the repository. Globs used:
A contributing reference is found in the repository’s README
file. This can be in the form of a title header or a link. Regexps used:
A contributing file is found in the default community health files repository.
ID: governance
Document that explains how the governance and committer process works in the repository.
This check passes if:
A governance file is found in the repository. Globs used:
A governance reference is found in the repository’s README
file. This can be in the form of a title header or a link. Regexps used:
The maintainers file contains a list of the current maintainers of the repository.
This check passes if:
A maintainers file is found in the repository. Globs used:
A maintainers reference is found in the repository’s README
file. This can be in the form of a title header or a link. Regexps used:
ID: readme
The readme file introduces and explains a project. It contains information that is commonly required to understand what the project is about.
This check passes if:
A readme file is found in the repository. Globs used:
ID: roadmap
Defines a high-level overview of the project’s goals and deliverables ideally presented on a timeline.
This check passes if:
A roadmap file is found in the repository. Globs used:
A roadmap reference is found in the repository’s README
file. This can be in the form of a title header or a link. Regexps used:
ID: website
A url
that users can visit to learn more about your project.
This check passes if:
A website url
is configured in the GitHub repository.
The project trends dashboard is a data-driven platform that presents a customized mix of KPIs for one project or its sub-projects to enhance the performance of the project. This is accomplished by displaying measurements, stats, and insights that are unique to a particular project or strategy.
The dashboard is the same as the Global Project Trends dashboard. The dashboard provides a statistical analysis of the project specific data.
A Contributor Strength dashboard provides a statistical analysis of all the contributors who are actively involved in supporting the selected project and subprojects .
For more information about contributors, see People Analytics.
It also shows a line chart that displays the periodic growth or decline in the total number of contributors for the selected time period, across the project and project memberships. Hover over the graph points to view the total number of active contributors for a particular time period.
For the current release, GitHub and Git are the two data sources used to calculate contributors across all monitored repositories during the selected time period.
The analysis is done based on the following parameters:
Contributor ID data is based on the user ID, identity ID, and email ID.
User roles such as author , co-author, reviewer, signer, etc.
Project IDs and subproject IDs are selected from the repositories.
This is a block at a fixed position on the chart that shows the 'Total Contributors' for the select project and project memberships. The percent change value is defined as an increase or a decrease in the total contributors compared to the previous period.
For more information, see Technical Contributors.
The dashboard is the same as the dashboard. Unlike the projects trend that gives data for all the projects in the Linux Foundation, this dashboard provides a statistical analysis of the selected project's specific data.
The dashboard is the same as the Global Project Trends dashboard. Unlike the projects trend that gives data for all the projects in the Linux Foundation, this dashboard provides a statistical analysis of the selected project's specific data.
The dashboard is the same as the commits metric from the Global Project Trends dashboard. Unlike the projects trend that gives data for all the projects in the Linux Foundation, this dashboard provides a statistical analysis of the selected project and sub-project data.
The dashboard is the same as the Contribution Affiliation metric from the Global Project Trends dashboard. Unlike the projects trend that gives data for all the projects in the Linux Foundation, this dashboard provides a statistical analysis of the selected project and sub-project data.
For more information, see Contribution Affiliation.
The dashboard is the same as the LOC added and deleted metric from the Global Project Trends dashboard. Unlike the projects trend that gives data for all the projects in the Linux Foundation, this dashboard provides a statistical analysis of the selected project and sub-project data.
For more information, see LOC Added and LOC Deleted.
The dashboard is the same as the Pipeline metric from the Global Project Trends dashboard. Unlike the projects trend that gives data for all the projects in the Linux Foundation, this dashboard provides a statistical analysis of the selected project and sub-project data.
For more information, see .
The dashboard displays the average lead time that the pull requests/changesets spend in various stages before being merged/closed.
The funnel view shows the number of days that the pull requests or changesets spend waiting for review, being reviewed, being approved, and being merged across all projects during the selected time range.
The dashboard is the same as the Issue History metric from the Global Project Trends dashboard. Unlike the projects trend that gives data for all the projects in the Linux Foundation, this dashboard provides a statistical analysis of the selected project and sub-project data.
For more information, see Issue History of Global Trends .
Technical Contributors dashboards provide analytics of a project or project group's technical contributors. The dashboard is specific to projects and project groups and aggregates identities and profile of technical contributors who are actively contributing to a project or a project group.
The dashboard provides a statistical analysis of total contributors since the start of the project. The line chart shows the count of the total number of technical contributors across commits, pull requests/change sets, and issues aggregated since the start of the project.
For the current release, GitHub and Git are the two data sources used to calculate contributors across all monitored repositories during the selected time period.
The analysis is done based on the following parameters:
Contributor ID data is based on the user ID, identity ID, and email ID. The contributor ID can be the user ID and identity ID (unclaimed).
User roles such as author , co-author, reviewer, signer, etc.
Project IDs and subproject IDs are selected from the repositories.
On the chart, you can analyze the following data:
The X-axis shows the time when the project started. The Y-axis shows the number of contributors. Hover over the points on the charts to see the total contributor value for the selected month.
The percent change value is defined as the increase or decrease of the total contributor count compared to the previous period.
To analyze the contributor dashboard, click CONTRIBUTOR LEADERSHIP at the bottom of the chart that takes you to the Community Management > People dashboard.
A Contributor Strength dashboard provides a statistical analysis of all the contributors who are actively involved in the specific project and its sub projects.
To know more about the contributors, see Glossary.
Commit, Issue, Issue Comment, Pull Request, Pull Request Comment, Pull Request Review, Gerrit change set, Gerrit patch set, Gerrit comments, and Gerrit approval are the data to get contributors' activity.
To analyze the key metrics of this dashboard for a particular project group, follow the below steps:
On the side navigation menu of the LFX Insights, click All Projects. This opens the main All Projects dashboard.
Select the project for which you want to see the metrics.
Alternatively, you can select a project from the drop-down in the left navigation pane.
On the left navigation pane, select projects from the drop-down.
Select the project name from the search box.
Once you select the project, you will see the following two menus on the left navigation page:
Once you select the project, you will see the following two menus on the left navigation page:
Project Analytics
Community Analytics
Click Project Analytics>Technical Contributors>Contributor Strength to see the Contributor Strength dashboard.
The dashboard shows the metrics of selected projects. To see the data for sub projects, select the sub project from the drop-down.
The dashboard shows the total number of unique pull request contributors across all monitored repositories during the selected time period. A unique contributor is someone who performs multiple activities but is counted as one.
For the current release, GitHub, Git, and Gerrit are the data sources used to calculate contributors across all monitored repositories during the selected time period.
Pull request activities include PRs submitted, comments, reviewed (review comments + approved + requested changes), merged, and rejected.
Using the bar chart, you can analyze the following data:
Total contributors for the selected time period and the percentage change.
Total number of submitters for the selected month. Hover over the graph to see the total number on the bar.
To analyze the PR contributor dashboard, click CONTRIBUTOR LEADERSHIP at the bottom of the chart that takes you to the Community Management > People dashboard.
The dashboard shows the total number of unique submitters and assignees across the monitored issue management tools during the selected time period. A unique contributor is someone who performs multiple activities but is counted as one.
The Issues activity includes issues from a repository, an item in a task list, a note in a project, a comment on an issue or pull request, and a specific line of code.
Using the bar chart, you can analyze the following data:
Total issue contributors for the selected time period and the percentage change.
Total number of submitters for the selected month. Hover over the graph to see the total number on the bar.
For more information, see Commits.
The dashboard shows the analysis of technical contributors by cohorts. The 6 point radar charts show the data of contributors who are actively contributing to only a single project and those who are contributing to multiple projects.
A contributor is said to be active in multiple projects when they are contributing to any other project within the same project group or outside of the project group during the same time period selected.
Contributing to more than one repo under the same project is not considered as contributing to multiple projects.
Hover over the chart points to see the total number of the contributors engaged in one or multiple projects.
The dashboard shows the total number of unique commit contributors across all monitored repositories during the selected time period. Commit contributors can author and co-author a commit that is visible on GitHub.
For the current release, GitHub and Git are the two data sources used to calculate contributors across all monitored repositories during the selected time period.
The analysis is done based on the following parameters for the selected period:
The impact by the contributors is calculated based on the number of commits in all the monitored repositories. Distinct SHAs are calculated as commit IDs.
Project IDs and subproject IDs are selected from the repositories.
Commits will appear on the contributions graph if they meet all of the following conditions:
The commits were made within the past year.
The email address used for the commits is associated with your GitHub account.
The bar chart shows the total commit contributors and the rate of change percentage for the selected time period. Hover over the chart to see the commit contributors for that particular month.
To analyze the contributor dashboard, click CONTRIBUTOR LEADERSHIP at the bottom of the chart that takes you to the Community Management > People dashboard.
The dashboard shows the following two metrics:
If you want to go back to the dashboard from any other screen, simply click the tab on the Dashboard to toggle between dashboards.
The bar chart shows the total number of active contributors with known corporate affiliations for the contributions made during the selected time period.
To learn more about corporate contributors, see common-terms.
Using the bar chart, you can analyze the following data:
Total affiliated contributors for the selected time period and the percentage change.
Total number of affiliates for the selected month. Hover over the graph to see the total number on the bar.
The bar chart shows the total number of active contributors who have been identified as independent contributors for the technical contributions made during the selected time period.
Using the bar chart, you can analyze the following data:
Total independent contributors for the selected time period and the percentage change.
Total number of independent contributors for the selected month. Hover over the graph to see the total number on the bar.
The Unaffiliated dashboard shows a statistical analysis of contributors who are not affiliated with any organization or whose organization affiliation is unknown.
To learn more about unaffiliated contributors, see common-terms.
Using the bar chart, you can analyze the following data:
Total unaffiliated contributors for the selected time period and the percentage change.
Total number of unaffiliated contributors for the selected month. Hover over the graph to see the total number on the bar.
To analyze the unaffiliated contributor dashboard:
Click CONTRIBUTOR LEADERSHIP at the bottom of the chart that takes you to the Community Management > People dashboard.
Select the pre-filtered time period.
Select the project and Technical Contribution as the activity cohorts and Active as the people cohort.
The CM dashboard in this case will only show contributors with missing affiliations.
The dashboard shows a doughnut chart that displays the top 10 organizations by the number of technical contributions across commits, pull requests, and issues. Hover over the colored chart to view the organization's total technical contribution and the percentage values.
The metric in the center of the donut chart shows the total number of active organizations with a percentage increase or decrease compared to the previous period.
To analyze the unaffiliated contributor dashboard:
Click CONTRIBUTOR LEADERSHIP at the bottom of the chart that takes you to the Community Management > Organization dashboard.
Select the pre-filtered time period.
Select the project and Technical Contribution as the activity cohorts and Active as the people cohort.
A Contributor Acquisition dashboard provides a statistical analysis of all the new users who have grown to become active contributors and maintainers in the specific project and its sub projects.
To analyze the key metrics of this dashboard for a particular project group, follow the below steps:
On the side navigation menu of the LFX Insights, click All Projects. This opens the main All Projects dashboard.
Select the project for which you want to see the metrics.
Alternatively, you can select a project from the drop-down in the left navigation pane.
On the left navigation pane, select projects from the drop-down.
Select the project name from the search box.
Once you select the project, you will see the following two menus on the left navigation page:
Once you select the project, you will see the following two menus on the left navigation page:
Project Analytics
Community Analytics
Click Project Analytics>Technical Contributors>Contributor Acquisition to see the dashboard.
The dashboard shows the metrics of selected projects. To see the data for sub projects, select the sub project from the drop-down.
The dashboard shows a statistical analysis of technical contributors across different cohorts that is defined by corporate or individual affiliation to the project.
The three-dimensional chart shows the unique count of active contributors for corporate, unaffiliated, and independent cohorts. Hover over the chart points to see the total contributors from each cohort.
In the above chart, you can see the three different cohorts on each axis. In some cases, you can also have contributors from any one or two cohorts for the selected time period.
The dashboard shows the following two metrics:
If you want to go back to the dashboard from any other screen, simply click the tab on the Dashboard to toggle between dashboards.
The bar chart shows the data of the active contributors who have contributed to a project or a project group for the first time.
The annotation block shows the average count of active and new contributors in percent increase or decrease compared to the same metrics for the previous period.
Click Contributor Acquisition at the bottom of the chart that takes you to the Technical Contributors > Contributor Acquisition dashboard pre-filtered for the time period selected and the project.
The bar chart shows the data of the drifting away contributors who were active in the last year but did not contribute across commits, PRs, or issues in the last 6 months.
The annotation block shows the average count of drifting away contributors in percent increase or decrease compared to the same metrics for the previous period. The percentage increase or decrease is calculated for the same time period by comparing the drifting contributor count at the start and end of the selected time period.
Click Contributor Leadership at the bottom of the chart that takes you to the The Community Management > People dashboard pre-filtered for the time period selected, the project and Technical Contribution as the activity cohort and Drifting Away as the people cohort.
The dashboard provides a statistical analysis of the number of contributors who contributed towards commits, pull requests, or issues for the first time during the selected time period.
On the stacked bar chart, you can analyze the following data:
The X-axis shows the time when the project started. The Y-axis shows the number of new contributors. The colors on the chart show affiliated, unaffiliated, and independent contributors. Hover over the charts to see the new contributor value for the selected month.
The annotation box shows the percent change value of total affiliated and total unaffiliated contributors compared to the previous period.
The Observations board gives the following insights:
The count of new contributors joining the project increased or decreased by X% compared to the preceding period.
An average of X new contributors joined the project during the selected time period.
The number of new contributors affiliated with an organization is X% more or less compared to unaffiliated new contributors.
An average of X new contributors identified themselves as independent developers during the selected time period.
Click VIEW ALL to view the Community Management > People > Technical Contributors > New & Promising dashboard.
The dashboard shows the following two matrices:
If you want to go back to the dashboard from any other screen, simply click the tab on the Dashboard to toggle between dashboards.
The leadership table lists the top 10 contributors who contributed the most to a project or a project group during the selected time period. It lists the display name, system user name, their organization name, commits, Loc added and so on.
The leadership table lists the top 10 organizations actively involved in commits, pull requests, and issues.
The dashboard shows the most active new & promising organizations that have recently started contributing toward code and issues.
Hover over the bars to see the organization's name and the contribution it made.
The contributions are specific to the time period selected.
If the name of the organization does not fit in the bubble, then the first 4 letters of that organization are shown followed by an ellipsis.
The bar shows the total value of the bar itself.
The hover text should show the organization name along with the value.
Click VIEW ALL to view the Community Management > Organization > Technical Contributors > New & Promising dashboard.
The dashboard shows a doughnut chart that displays a comparison between the new organizations and the existing organizations. You can analyze the total technical contributions across commits, PRs, and issues into cohorts of those made by new and existing organizations. Hover over the chart to see the total new organizations and the total existing organizations.
The graph also shows the total organizations and their percent increase or decrease as compared to the previous period.
Click VIEW ALL to view the Community Management > Organization > Technical Contributors > New & Promising dashboard.
The dashboard shows a doughnut chart that displays a comparison between the technical contributions made by the new organizations and the existing organizations. You can analyze the total technical contributions across commits, PRs, and issues into cohorts of those made by new and existing organizations.
The graph also shows the total technical activities by the organizations and their percent increase or decrease as compared to the previous period.
To get the data, click VIEW ALL to view the Community Management > Organization > Technical Contributors > Most Active dashboard.
The Dashboard shows the impact on the selected projects by the new contributor. The chart combines two data sets with a line chart that helps you to compare the data. The chart shows the total number of commits pushed by new contributors vs total commits during the selected time period.
On the chart, you can analyze the following data:
Hover over the chart to see the new contributor commits vs total for the selected month.
The annotation box shows the percent change value of total commits by new contributors compared to the previous period.
The commits by new contributors include the number of code commits authored and co-authored by new contributors.
The total commits include all the commits authored and co-authored by other non-new, i.e., existing contributors.
The commits shown in the graph exclude empty commits, merge commits, and commits by bots.
Click VIEW ALL to view the Community Management > People > Technical Contributors > New & Promising dashboard.
The dashboard shows the following two matrices:
If you want to go back to the dashboard from any other screen, simply click the tab on the Dashboard to toggle between dashboards.
Click Order by drop-down to select the order of the table based on your priorities from the drop-down.
The leadership table lists the top 10 new contributors who contributed the most to a project or a project group during the selected time period. It lists the display name, system user name, their organization name, commits, Loc added, and so on.
The leadership table lists the top 10 new organizations actively involved in commits, pull requests, and issues. It lists the organization name, organization logo, their organization name, commits, PR activities, issues, Loc added, and so on.
The dashboard shows a doughnut chart that displays a comparison between the new contributors and the existing contributors. You can analyze the total technical contributions across commits, PRs, and issues into cohorts of those made by new and existing contributors. Hover over the chart to see the total new contributors and the total existing contributors.
To get the data, click VIEW ALL to view the Community Management > People > Technical Contributors > Most Active dashboard.
The dashboard shows a doughnut chart that displays the segregation of the organizations based on their employee strength. You can analyze the newly participating organizations by the cohorts of their current employee strength.
If the organization's employee strength is less than 100, then the organization is considered small.
If the organization's employee strength is between 100 and 999, then the organization is considered medium.
If the organization's employee strength is greater than 1,000, then the organization is considered large.
To get the data, click VIEW ALL to view the Project Analytics >Technical Contributors > Participating Organizations dashboard.
The dashboard provides a statistical analysis of the total number of contributors who actively participated in technical contributions and those who drifted away.
A contributor is considered drifting away if they have not performed any activity across commits, PRs, or issues in the last 6 months but were active at some point in the last year.
On the multicolor bar chart, you can analyze the following data:
The two-color bar shows the total number of active contributors and the number of contributors drifting away for the selected month. The blue color on the bar shows active contributors, and the orange color shows the contributors drifting away.
The annotation boxes on the chart show the active contributors and drifting away contributors' percent change compared to the previous period.
The observation matrix shows the following insights:
The month when there was the highest number of contributors drifted away last year.
The average number of contributors drifted away last year.
The percent change in the number of drifted away contributors last year.
To get the data, click VIEW ALL to view the Community Management > People > Technical Contributors > Drifting dashboard.
The dashboard shows the top 10 organizations that contributed the most to a project or a project group during the selected time period. These organizations are actively engaged in commits, pull requests, issues, and so on. The table lists the organization name, organization logo, their organization name, contributors, activities, commits, PR activities, issues, and so on.
To know more about the active organizations, see Glossary.
Click Order by drop-down on the dashboard to select the order of the table based on your priorities from the drop-down.
The number of contributors in the table list is the total number of contributors who are active during the selected time period.
To get the data, click VIEW ALL to view the Community Management > Organization > Technical Contributors > Most Active dashboard.
The leadership table lists the contributors who contributed the most are drifted away during the selected time period. It lists the display name, system user name, their organization name, commits, Loc added, and so on.
Click Order by drop-down to select the order of the table based on your priorities from the drop-down.
The chart combines two data sets with a line chart that helps you compare the total number of active contributors affiliated with organizations compared to independent developers.
On the chart, you can analyze the following data:
Hover over the chart to see the comparison between corporate contributors and independent contributors for the selected month.
The annotation box shows the percent change value of the total corporate and the total independent compared to the previous period.
The dashboard shows the following two matrices:
If you want to go back to the dashboard from any other screen, simply click the tab on the Dashboard to toggle between dashboards.
The chart combines two data sets with a line chart that helps you compare the count of the total number of organizations that were identified to be participating in the project for the first time with those organizations that have been participating since before the selected time period.
On the chart, you can analyze the following data:
Hover over the chart to see the new organizations vs. existing organizations for the selected month.
The annotation box shows the percent change value of the total new organizations and the total existing organizations compared to the previous period.
An organization qualifies to be a new organization if either all its employees (contributors affiliated with this organization) are first-time contributors or if this organization was newly affiliated (contributors moving to a new company) during the selected time period.
The bar chart shows the total number of organizations whose employees are identified as drifting away and have not participated in any technical activity since the last 6 months but have been active at some point in the last 1 year.
On the chart, you can analyze the following data:
Hover over the chart to see the drifted away organizations for the selected month.
The annotation box shows the percent change value of the total drifted away organizations compared to the previous period.
An organization is considered to be drifting away only if all its affiliated employees have drifted away.
If the affiliation of an individual changes from one organization to another and the individual is still active, the old organization is considered to be drifting away.
When an individual ends their affiliation with an organization, the organization's contribution to that project also ends if this individual was the only active contributor from that organization in the project.
The dashboard shows the top 10 organizations based on the number of commits pushed across all monitored repositories during the selected time period.
The different sizes of the bar chart vary based on the number of commits pushed by the respective organization for the project. Hover over the chart to see the organization's name and the total commits pushed across all monitored repositories.
Commits will appear on the contributions graph if they meet all of the following conditions:
The commits were made within the past year.
The email address used for the commits is associated with your GitHub account.
The dashboard shows the top 10 organizations based on the number of pull requests across all monitored repositories during the selected time period.
Pull request activities include PRs submitted, commented, reviewed (review comments + approved + requested changes), merged, and rejected.
The different sizes of the bar vary based on the number of PRs by the respective organization for the project. Hover over the chart to see the organization's name and the total PRs across all monitored repositories.
The dashboard shows a doughnut chart that displays the segregation of the organizations based on their employee strength. You can analyze the newly participating organizations by the cohorts of their current employee strength.
If the organization's employee strength is less than 100, then the organization is considered small.
If the organization's employee strength is between 100 and 999, then the organization is considered medium.
If the organization's employee strength is greater than 1,000, then the organization is considered large.
The dashboard shows the top 10 organizations based on the number of issues submitted and assigned, resolved or rejected across all monitored repositories during the selected time period.
The different sizes of the bar vary based on the number of issues by the respective organization for the project. Hover over the chart to see the organization's name and the total number of bugs across all monitored repositories.
The dashboard shows a doughnut chart that segregates the active organizations based on the technologies that are associated with these organizations.
Hover over the chart to see the technology and the number of active organizations.
For the current release, GitHub and Git are the two data sources that are supported across all monitored repositories during the selected time period.
The analysis is done based on the following parameters:
The organization name, ID , logo, industry type , and the total number of employees.
Technical contributor ID, commits SHA , email IDs, message IDs, etc.
The organization's industry types.
The doughnut chart shows the segregation of the total number of organizations by their membership status. Hover over a color to view the number of organizations by their membership status.
Members are the organizations that have become official members of the Linux Foundation.
Non-members are organizations who have not become official members of the Linux Foundation.
For more information, see active membership.
Code Velocity tab provides various insights related to the code that has been submitted by various contributors to the various open source project.
Code Velocity tab provides insights on the following:
Commit Analysis
Pull Request Pipeline
Issue Request Pipeline
To access Code Velocity, perform the following steps:
1.Login to Insights.
2.On the vertical sidebar navigation menu, click Code Velocity.
Pull Request (PR) Pipeline provides various insights related to the PRs carried out for the open source project. Pull Request Pipeline provides various graphs that provides you information on PRs analysis. There are various graphs such as:
Pull Request History
Request Pipeline
Cycle Time
Pull Request Trends
Contributor Type
Active Submitters
Time to Merge
Time in Review
New Contributor Efficiency
Top 10 Contributors
Top 10 Organizations
You can filter the data related to PR as per your desired date range. By default, time range is Past 1 Year. You can change the time range for a certain time period. For more information, refer Date Range.
You can filter the PRs using various other filter like:
Filter by
Repository
Repository Tags
Searching by various individual repositories
Sub Projects
Every dashboard has a filter at the top of the dashboard to select either Repositories or Repository Tags. A Repository tag is a logical group created by clubbing two or more repositories under an org. One repository can belong to multiple repository groups. A repository tag is unique to a project.
This line graph provides the count of the total number of PRs submitted and merged aggregated for all time over the selected time period.
Observations window provides various observations carried out on the Pull Request Pipeline. Some of the observations that are displayed are listed in the following list:
The total number of PRs submitted increased/decreased by X% during the ${selected time period}.
An average of X PRs were merged during the ${selected time period}.
The total number of PRs merged increased/decreased by X% during the ${selected time period}.
X% of total changes were merged without any approval during the last ${selected time period}.
This funnel chart provides you the total number of code change requests in the form of PRs or changesets submitted, reviewed, accepted and merged during the selected time period.
GitHub's accepted/approved state configured differently for every repository. This "Approved" metric is counted based on at least one review with "Accepted state".
Submitted - Number of PRs created/submitted during the given time range + the number of PRs still in open at the end of the time period.
Reviewed - Number of PRs with at least one Review (comment or approval or requested changes). The review must be done during the selected time period.
Accepted - Number of PRs with at least one approval. The approval must be done during the selected time period.
Merged - Number of PRs merged (not rejected).
For Gerrit:
Submitted - Number of Changesets created/submitted the given time range + number of changesets still in open
Reviewed - Number of chanegstes with at least one Review (comment or review value +1, +2, -1, -2)
Accepted - Number of changesets with at least one approval (review value +1, +2)
Merged - Number of changesets merged/closed (not -2)
This funnel chart provides you the sum of the average time it takes in each step of the PR/changeset cycle.
The annotation block shows the total Average PR Cycle time i.e. the sum of the averages for each stage. It also shows the percentage change compared to previous period.
Waiting for Review - Shows the average of the time between a PR is submitted/created and time to get the first review_comment or review_approval or review_requested_chages for all PRs merged or closed during the selected time period.
In Review - Shows the average of the time a PR received its first review to the time a PR received its first approval for all the PRs merged or closed during the selected time period.
In Approval - Shows the average of the time a PR received its first approval to the time a PR was merged or closed for all the PRs merged or closed during the selected time period.
This bar graph provides the count of the total number of PRs submitted and merged during the selected time period.
This donut chart provides the analysis of code change request contributors by reviewers and submitters.
Total PR contributors are unique identities who are PR submitters, PR reviewers (review_comment, review_requested_changes, review_approval) and PR mergers.
PR submitters are strictly those who have submitted at least 1 PR during the selected time period.
PR reviewers are strictly those (can be submitters as well) who have reviewed at least one PR during the selected time period.
This bar graph provides you the count of the total number of unique PR submitters analyzed by cohorts of existing and new submitters contributing during the selected time period.
New PR Submitters are also Active.
New submitters are strictly those identities or profiles who have submitted PR for the first time for the project.
This line chart provides you the average time, in days, it takes for a PR to be merged during the selected time period.
This line graph provides you the average time in days required for pull request to be reviewed during the selected time period.
This line graph provides the average time it takes for the first PR submitted by a new contributor to be accepted and merged.
The Lead time will either be higher or at least same as the time in Review
This list provides you the details of the top 10 contributors for the project in last one year. The top contributor of the project is calculated based on the PRs submitted on the project.
This list provides various details such as:
Name
Identity
Organization
Last activity
PRs submitted
PRs reviewed
PRs merged
PR comments
You can order the list based on PRs submitted, reviewed, merged and comments.
On Click of All Technical Contributors, all the technical contributors of the project are listed.
This list provides you the details of the top 10 organizations that contributing to the the project in last one year. The top organization of the project is calculated based on the PRs submitted on the project.
This list provides various details such as:
Organization name
Contributors
Last activity
PRs submitted
PRs reviewed
PRs merged
PR comments
You can order the list based on PRs submitted, reviewed, merged and comments.
You can download all the charts that are displayed in the PR Pipeline page by click of the download icon that is provided on top of all the charts. The downloaded chart is saved on your local drive in the PNG format.
A Documentation dashboard provides various insights related to the documentation activities that are available with specific open source projects.
Confluence is the main data source used to calculate the participants involved in documentation activities.
To analyze the key metrics of this dashboard for a particular project group, follow the below steps:
On the side navigation menu of the LFX Insights, click All Projects. This opens the main All Projects dashboard.
Select the project for which you want to see the metrics.
On the vertical sidebar navigation menu, click Documentation.
Code Base tab provides various insights related to the code repositories that are available with various open source project.
Code Base tab provides insights on the following:
Repositories
Repositories that need Attention
To access Code Base, perform the following steps:
1.Login to Insights.
2.On the vertical sidebar navigation menu, click Code Base.
A repository is one which contains all of your project's files and each file's revision history. Repositories provides various insights related to the code repositories that are used in the open source project. Repositories provides various graphs that provides you information on different aspects of the repositories. There are various graphs such as:
Active Repositories
Watchers Vs Stars
Forks
Inactive Repositories
Programming Language Distribution
Open PRs
Open Issues
Repositories
You can filter the data related to repositories as per your desired date range. By default, time range is Past 1 Year. You can change the time range for a certain time period. For more information, refer Date Range.
You can filter repositories using by:
Sub Projects
The Repository widget provides you with an overview information on repositories used in the development of various open source projects. This widget provides you the following details:
Total number of active repositories
Total number of stars
Total number of Watchers
Total number of Forks
Total number of LOC
Total number of commits
This line chart provides you the aggregated number of repositories with active code contribution activity that include commits, PRs and issues for a particular time period. This chart also includes a percentage change compared to the previous time period.
Observations window provides various observations carried out on the repositories. Some of the observations that are displayed are listed in the following list:
The number of active repositories decreased by X% during the Past X Year.
On an average X repositories per Month were active during the Past X Year.
The number of inactive repositories increased by X % during the Past X Year.
An average of X repositories per Month were inactive during the Past X Year.
This line chart provides you the number of watchers compared to the number of stars for all repositories for a particular time duration..
This line chart provides you the number of forks created across all repositories for a particular time duration.
This bar graph provides you the number of repositories with no code related activity for a particular time period.
This donut chart provides you the breakdown of programming languages in the code base.
This bar graph provides you the number of pull requests that have been submitted but not merged for a particular time period.
This bar graph provides you the number of issues that have not yet been assigned or reviewed that is no activities like comments for a particular time period.
This list provides you the list of all repositories.
This list provides various details such as:
Repository Name
Active Contributors
Commits
Days since last commit
PRs Submitted
PRs Merged
Days since last PR submitted
Issue Created
Issue Closed
Days since last issue created
You can order the list based on commits, active contributors, days since last commit, PRs submitted, PRs merged, Days since last PRs merged, issue created, issue closed and days since last issue submitted.
Commit Analysis provides various insights related to the commits carried out for the open source project. Commit Analysis provides various graphs that provides you information on commit analysis. There are various graphs such as:
Total number of commits
Commit Trends
Contributors / Organization
Code Changes
Documentation
Pair Programing Commits
Code by Day
Programming Languages
Commit-To- Merge Time
Top 10 Contributors
Top 10 Organizations
You can filter the data related to commit analysis as per your desired date range. By default, time range is Past 1 Year. You can change the time range for a certain time period. For more information, refer Date Range.
You can filter the commit analysis using various other filter like:
Filter by
Repository
Repository Tags
Searching by various individual repositories
Sub Projects
Every dashboard has a filter at the top of the dashboard to select either Repositories or Repository Tags. A Repository tag is a logical group created by clubbing two or more repositories under an org. One repository can belong to multiple repository groups. A repository tag is unique to a project.
This line graph provides the count of the total number of commits aggregated since the start of the project analyzed over the selected time period.
Observations window provides various observations carried out on the commit analysis. Some of the observations that are displayed are listed in the following list:
The percentage change in the number of commits increased/decreased during the selected time period.
The most number of commits submitted was the highest during X-Y period.
For computing the average commits, only the unique commits submitted during the selected time period should be considered and averaged out based on the data points (buckets) on the graph.
This bar graph provides the total number of commits performed during the selected time period. Hover over the bar to see the total commits for that particular months. The annotation block show the total commits for the selected period and the rate of change compared to previous time period.
This bar graph provides the total number of number of unique contributors actively committing code to the project during the selected time period.
On click of View Contributors, you can view the list of people contributing to the project. For more, refer People.
This bar graph provides the total number of number of unique organizations actively committing code to the project during the selected time period.
This line graph provides the count of the total number of commits pushed and analyzed by those containing actual lines of code changes vs those that are empty or identified as merge commits.
This donut chart provides you the total number of commits that are intended to update documentation or assets like images for the project.
This line graph provides the total count of the number of commits signed-off by more than one author.
Pair Programming are enabled by default and are identified by the parsing the git trailers for more than one Author, generally given by 'Co-Authored' or 'Signed-off by' trailers.
A co-author should be different that the actual author of the commit, hence pair programming commits should be not identified by merely looking at multiple occurrences of the git trailers and rather by also checking the authors and co-authors involved in the commit and tag a commit as pair programming commit only if both are different individuals.
This radar chart provides you the total commits submitted and aggregated across each day of the week.
The aggregation applies to only commits submitted during the selected time period.
Only commits authored or co-authored are considered.
This bubble chart provides you the total number of programming languages used across the commits submitted and determined by analyzing the files (checking the extensions) modified or added for each commit.
If a file type cannot be determined, it is marked as 'Unknown'.
This speedometer chart provides you the average time, in days, for a commit to be committed to a branch. For each commit, the efficiency is computed by taking the difference between the time it was added and the time it was committed.
This list provides you the details of the top 10 contributors for the project in last one year. The top contributor of the project is calculated based on the commits submitted on the project.
This list provides various details such as:
Display name
System name
Organization name
Last activity
Commits authored
Commits co-authored
LOC added
LOC deleted
Files modified
You can order the list based on commits authored, commits co-authored, LOC added, LOC deleted and Files modified.
On Click of View All, all the contributors of the project are listed.
This list provides you the details of the top 10 organizations that contributing to the the project in last one year. The top organization of the project is calculated based on the commits submitted on the project.
This list provides various details such as:
Organization name
Organization Logo
Contributors
Last activity
Commits authored
Commits co-authored
LOC added
LOC deleted
Files modified
You can order the list based on commits authored, commits co-authored, LOC added, LOC deleted and Files modified.
Repositories that needs attention provides list of repositories that needs attention of the project maintainers. These repositories were active some time back and now thy are sort of idle from a particular time period.
This list provides the following details:
Short Name
Active Contributors
PRs Open
Issue Backlog
Avg. PR Lead Time (Days)
Avg. Issue Resolution Time (Days)
You can order the list based on active contributors, issue backlog, issue resolution time, PR lead time and PRs open.
Issue Request Pipeline provides various insights related to issues raised and resolved for the open source project. Issue Request Pipeline provides various graphs that provides you information on issues. There are various graphs such as:
Issue History
Resolution Pipeline
New Issues
Backlog
Contributor Type
New Contributors
Average Time To Resolve
Issue Resolution Efficiency
Efficiency
Top 10 Contributors
Top 10 Organizations
You can filter the issues using various other filter like:
Filter by
Repository
Repository Tags
Searching by various individual repositories
Sub Projects
Every dashboard has a filter at the top of the dashboard to select either Repositories or Repository Tags. A Repository tag is a logical group created by clubbing two or more repositories under an org. One repository can belong to multiple repository groups. A repository tag is unique to a project.
This bar graph provides the aggregate number of submitted and resolved issues.
Since this is the aggregated count, the count will never go down.
Observations window provides various observations carried out on the Issue Request Pipeline. Some of the observations that are displayed are listed in the following list:
The number of issues submitted increased by X% during the ${selected time period}. /* If the %increase is 0, the observation should say, No new issues were submitted during the ${selected time period}.
An average of X issues were submitted submitted during the ${selected time period}.
The number of issues resolved increased by X% during the ${selected time period}. /* If the %increase is 0, the observation should say, No new issues were resolved during the ${selected time period}.
An average of X issues were resolved during the ${selected time period}.
The highest growth in the number of issues submitted was seen between X-Y.
Most number of issues were closed during the time period between X-Y.
This funnel chart provides you the issue resolution pipeline showing bottlenecks and key data points such as issues waiting to be closed, commits pushed, pull requests submitted and more.
This bar graph provides you the trend of new issues submitted and resolved in a particular time frame.
This line chart provides you the breakdown of issues that are in development and those that are still open.
This line chart provides you the count of the total number of submitters and assignees over the selected time period.
This line chart provides you the count of the total number of new submitters and new assignees over the selected time period.
This line chart provides you the average time, in days, it takes for the issues to be closed or resolved during the selected time period.
This radar chart provides you the analysis of number of issues resolved by measuring their time to resolve into cohorts of different time periods which is less than a day, between 1-7 days, between 7-15 days, 15-30 days and more than 30 days.
This line chart provides you the average time in days required before initial comment made on a submitted issues and the time to assign the issue.
This list provides you the details of the top 10 contributors for the project in last one year. The top contributor of the project is calculated based on the issues submitted on the project.
This list provides various details such as:
Display Name
System Username
Organization Name
Last activity
Issues submitted
Issues Assigned
Issue comments
You can order the list based on issues submitted, assigned and and comments.
On Click of Active Contributor Leaderboard, all the active contributors of the project are listed.
This list provides you the details of the top 10 organizations that contributing to the the project in last one year. The top organization of the project is calculated based on the issues submitted on the project.
This list provides various details such as:
Organization name
Organization logo
Industry
Active Issues Contributions
Issues submitted
Issues Assigned
Issue comments
You can order the list based on Issue submitted, assigned and comments.
You can download all the charts that are displayed in the Commit Analysis page by click of the download icon that is provided on top of all the charts. The downloaded chart is saved on your local drive in the PNG format.
You can download all the charts that are displayed in the Commit Analysis page by click of the download icon that is provided on top of all the charts. The downloaded chart is saved on your local drive in the PNG format.
You can filter the data related to issues as per your desired date range. By default, time range is Past 1 Year. You can change the time range for a certain time period. For more information, refer .
You can download all the charts that are displayed in the issues Pipeline page by click of the download icon that is provided on top of all the charts. The downloaded chart is saved on your local drive in the PNG format.
The dashboard shows the total number of participants engaged in creating or updating documentation since the start of the project.
The analysis is done based on the following parameters:
Distinct contributor ids that represents all contributors that have participated before the time period.
All organization ids and timestamp that have contributed in the selected time period.
The dashboard shows the following two metrics:
If you want to go back to the dashboard from any other screen, simply click the Tab on the Dashboard to toggle between dashboards.
The bar chart shows the count of the total number of contributors actively creating or updating community documents during the selected time period.
The annotation block shows the average count of active contributors in percent increase or decrease compared to the same metrics for the previous period.
The bar chart shows the total number of documents writers who were active in the last year but did not contribute in the last 6 months.
The annotation block shows the average count of drifting away writers in percent increase or decrease compared to the same metrics for the previous period
The dashboard provides a statistical analysis of the total number of contributors who contributed towards community documentation for the first time in the selected time period.
On the stacked bar chart, you can analyze the following data:
The X-axis shows the time when the project started. The Y-axis shows the number of new participants. Hover over the charts to see the new contributor value for the selected month.
The dashboard shows a doughnut chart that displays a comparison among active email participants by cohorts of Corporate, Unaffiliated and Independents without corporate affiliations.
The analysis is done based on the following parameters:
Distinct contributor ids as contribution counts.
All organization ids when no organization name then shows as unaffiliated, when organization name is as individual then independents else corporate .
The dashboard shows the top 10 organizations that were identified by participant affiliations and ordered by the most number of email activities to a project or a project group during the selected time period.
For more information about the active organizations, see Glossary.
The leadership table lists the top 10 individuals who contributed the most to a project or a project group during the selected time period. It lists the display name, the system user name, their organization name, and the documentation activities.
The Activity Analysis dashboard provides various insights related to the documentation carried out for open-source projects.
Confluence is the main data source used to calculate the participants involved in documentation activities.
The graph shows the count of the total number of document activities during the selected time, analyzed by the type of activity.
The analysis is done based on the following parameters:
The number of document activities is calculated based on documentation content type such as new pages count, edited pages count, blog posts count, and attachments count.
The graph shows the total document activities across the community documents aggregated by each day of the week. The 6-point radar charts show the data of the documentation activities for multiple projects.
The dashboard shows the following two metrics:
If you want to go back to the dashboard from any other screen, click the Tab on the Dashboard to toggle between dashboards.
The bar chart shows the list of the top 10 pages by the number of editions performed during the selected time period.
The bar chart shows the top 10 organizations identified by participant affiliations and ordered by the most number of email activities
The graph shows the total number of organizations contributing towards documentation aggregated since the start.
Confluence is the main data source used to calculate the participants involved in documentation activities.
The analysis is done based on the following parameters:
The number of distinct contributor IDs from the beginning of time to our date. This represents all contributors that have participated before the time period.
All the organization IDs and timestamps that have contributed in this time period.
The dashboard shows the following two metrics:
If you want to go back to the dashboard from any other screen, click the Tab on the Dashboard to toggle between dashboards.
The chart shows the total number of organizations actively contributing toward documentation during the selected time period.
The analysis is done based on the following parameters:
The Contributor IDs are counted as contributors count.
The graph shows the total number of organizations, identified by the affiliated individuals who haven't been active in the last 6 months but were active at some point in the last year.
The count of the total number of organizations that are identified as participating for the first time towards documentation during the selected time period
The dashboard shows the most active new & promising organizations that have recently started contributing toward code and issues.
Hover over the bars to see the organization's name and the contribution it made.
The contributions are specific to the time period selected.
The bar shows the total value of the bar itself.
The hover text should show the organization name along with the value.
The dashboard shows a doughnut chart that displays the analysis of affiliated contributors by their affiliations to member and non-member organizations.
In the case of a sub-project, the membership affiliation is based on the parent project. Hence, if an organization is a member of the parent project, they are also members of sub-projects.
If the project (group or standalone) does not have active members but the contributing organizations have active LF membership, they are not considered as members of the current project. Meaning this chart only represents active members for the selected project or project group.