News for hackers. Stuff that matters.
Re:“Please don't waste maintainers' time on your KPI grabbin... by NikolaNovak on Friday June 25, 2021 @11:28AM (#27631997)
KPI = Key Performance Indicator = "thing we decided is important for us to measure and increase"

As such exactly what it is, will depend on company/industry/market/team/project/etc. It may be revenue or units sold or widgets made or turnover or customer satisfaction or days without accident etc. In principle, it communicates to teams what is important to business and helps everybody focus and sync.... with usual real-world caveats and implementation risks.

I imagine here, for a large-company linux team, a "KPI" was "how many commits you made" - they measure it, they track it, and reward/recognize/punish team members based on it. So people start working toward increasing the KPI in any feasible way - if you only want me to increase the KPI of commits done, OK, fine, I'll do some commits.

Re:“Please don't waste maintainers' time on your KPI grabbin... by falcor84 on Friday June 25, 2021 @04:09PM (#27635634)
>thing we decided is important for us to measure and increase

This is a great explanation, and I just wanted to nitpick that for some KPI's (e.g. percentage of defective components, or latency), you would aim to "decrease" the KPI, and in some rare instances, you'd want to keep the KPI within a range (e.g. resource utilization, or inventory size, when you want a predefined amount of buffer).