Hacker Newsnew | past | comments | ask | show | jobs | submit | dhruvagga's commentslogin

what are you smoking up bro?!


I'll have what he's having


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?


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.


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?


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.


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??


too much truth in one comment.


Is this the new Omegele where the conversations can't happen? haha


Any service suggestions?


This looks super interesting!


We recently launched Middleware(https://github.com/middlewarehq/middleware) - Open Source Software for Engineering Analytics. We made an architectural change first of splitting the product into core and non-core features. We put core in one repo and non-core in other repos.

We made the core part open source and our paid offering takes up the rest of the product as addons! So, we maintain only one codebase and avoid the hassle of drifts.

Happy to offer more insight.


Yes, I would love to learn more. So, how do you manage the code between core and non-core versions? Do you copy from one to the other via automations or is it some other way?


Thanks @jayantbhawal!


Glad you liked it! One of the early insights we got for driving productivity in organisations was the tools overwhelming the leaders with data, rendering no action. We have tried our bit to keep high signal to noise ratio and offer interactive views instead of just data dumps.


Thank you @aravindputrevu! Our team spent the last few months in chiseling out the core of our product to open-source! Glad you liked it :)

Engineering productivity is a complex topic and a crucial decision is to pick a framework which is non-monitoring, non-gameable. DORA metrics fits well right in.


Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: