-
Notifications
You must be signed in to change notification settings - Fork 6
Project Health Reporting (take 2) #135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
During today's TOC call, @psmulovics commented that this is a great improvement from #125, but has distinct room for improvement. @psmulovics Can you please elaborate on the gaps / room for improvement? Both @chris-twiner and @caradelia have accepted the call for feedback, and intend to comment here before the next TOC call. |
Sure. Due to the data being 'human quantified' instead of 'scientific quantified', we do have entries saying '1.25K' instead of '1250' which makes it hard to display, needs manual intervention, etc. Same way, some of the data types, like dates, get mistakenly converted to other format, like '7/1/2024 12:00:00 AM' becoming '1.71T' in the report. Also, there are missing spots in the report, eg data that is missing. Also, we need to have better understanding for reports on what 'total activities', 'retention', etc actually means. |
Thanks for the valuable feedback @psmulovics and thanks @eddie-knight for gathering feedback. I agree on 'human' VS 'scientific' quantified data, especially on data exports. Regarding the 'missing spots', it would be great to have more details on which metrics are missing. Regarding the understanding for 'total activities', 'retention', etc , I'd ask you to use the LFX Insights UI tips, as shown below. Thank you! ![]() |
Thank you for the feedback. I work on LFX as head of product & design. I can add a backlog item to see if we can make our downloads more human friendly. Also, we can investigate the use case around automating the send of the report as a future feature. Please see this documentation on reports - https://docs.linuxfoundation.org/lfx/insights/v3-beta-version-current/reports that should clarify to provide better understanding. |
Follow up of #125
The following health metrics have been built for the CDM project, using the following LFX Insights reports:
CDM (manual) report:
From Velocity (last quarter) - https://insights.lfx.linuxfoundation.org/foundation/finos/velocity?project=isda-cdm&routedFrom=Github&dateFilters=Last%2012%20Months&dateRange=2023-07-26%20to%202024-07-25&compare=PP&granularity=month&hideBots=true
Performance Metrics
CSVLead Time
CSVWait Time for 1st Review
CSVFrom Productivity (last quarter) - https://insights.lfx.linuxfoundation.org/foundation/finos/productivity?project=isda-cdm&routedFrom=Github&dateFilters=Last%20Quarter&dateRange=2024-04-01%20to%202024-06-30&compare=PP&granularity=week&hideBots=true&repository=all
Commits per Active Day
CSVNew Contributors
CSVFrom Reports > Contributors (last quarter) - https://insights.lfx.linuxfoundation.org/foundation/finos/reports/contributors?project=isda-cdm&routedFrom=Github&dateFilters=Last%20Quarter&dateRange=2024-04-01%20to%202024-06-30&compare=PP&granularity=week&hideBots=true&repository=all
Total Contributors
CSVActive Contributors
CSVFrom Reports > Activities (last quarter) - https://insights.lfx.linuxfoundation.org/foundation/finos/reports/activities?project=isda-cdm&routedFrom=Github&dateFilters=Last%20Quarter&dateRange=2024-04-01%20to%202024-06-30&compare=PP&granularity=week&hideBots=true&repository=all
Total Activities
CSVActivities
CSV (Warning! This returns an empty CSV)Still unclear how to use
Reports > Retention
on https://insights.lfx.linuxfoundation.org/foundation/finos/reports/retention?project=isda-cdm&routedFrom=Github&dateFilters=Last%2012%20Months&dateRange=2023-07-26%20to%202024-07-25&compare=PP&granularity=month&hideBots=trueAttaching spreadsheet with one sheet per CSV export - CDM metrics (May-July 2024).xlsx
As next steps:
For all security aspects related with project healthcheck, we're considering to adopt/contribute to the OSPS Baseline, currently led by @eddie-knight
The text was updated successfully, but these errors were encountered: