OpenStreetMap's DevOps Efficiency: A Data-Driven Dora Metrics Analysis

Re:OpenStreetMap's DevOps Efficiency: A Data-Driven Dora Met... by dhruvagga on Tuesday September 24, 2024 @06:30AM (#41635086)

Do you think lead time as a concept matters so much in open source repos? As in, if a contributor feels like contributing they will otherwise not. Because there's no accountability, the lead time becomes pointless - wdyt?

[ Parent | on HN ]

Re:OpenStreetMap's DevOps Efficiency: A Data-Driven Dora Met... by jayantbhawal on Tuesday September 24, 2024 @06:33AM (#41635106)

Good point, but I’d say lead time still matters. Even in open source, slow responses can kill motivation. Quick feedback keeps contributors engaged and makes the project feel more active.

[ Parent | on HN ]

Re:OpenStreetMap's DevOps Efficiency: A Data-Driven Dora Met... by dhruvagga on Tuesday September 24, 2024 @06:35AM (#41635112)

hmm.. ok

And I don't understand how to correlate your Dep. frequency here with PR merges. There's one point where the project might build vs considering every PR merge as a deployment. Don't you think that would shake the metrics rating for this repo as per your assessment?

[ Parent | on HN ]

Re:OpenStreetMap's DevOps Efficiency: A Data-Driven Dora Met... by jayantbhawal on Tuesday September 24, 2024 @06:38AM (#41635124)

We track PR merges as potential deployments to measure flow and efficiency, even if not every merge triggers an immediate deploy. It’s more about tracking how fast the code moves through the pipeline.

[ Parent | on HN ]

Re:OpenStreetMap's DevOps Efficiency: A Data-Driven Dora Met... by shivc on Tuesday September 24, 2024 @06:49AM (#41635173)

I guess another way to think about lead time in open source might be to gauge the overall project health: more active and engaged community that is. What do you think??

[ Parent | on HN ]