The latest articles on DEV Community by Udi (@udiudi). https://dev.to/udiudi https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1766%2Fea8e255b-468b-4936-86b0-fb18af87c724.jpeg https://dev.to/udiudi en Udi Sat, 13 Jul 2019 18:26:31 +0000 https://dev.to/udiudi/what-s-the-merge-rate-of-dev-to-my-side-project-4hf5 https://dev.to/udiudi/what-s-the-merge-rate-of-dev-to-my-side-project-4hf5 <p>Hi all!</p> <p>Today I want to show you something I've been working on lately, and ask for any feedback and ideas about the next steps :)</p> <p>I've built a web app that analyzes repositories on GitHub and shows them on a dashboard like <a href="https://rails.devlytics.io/rails">this one of Rails</a> or the one of <a href="https://thepracticaldev.devlytics.io/dev.to">dev.to</a>.</p> <p>The initial idea was to give a comfortable view of the team's performance, raise possible issues and present insights.<br> Since GitHub bought a competitor in that field that offered similar features, I'm pivoting slightly to present <a href="https://rails.devlytics.io/rails?compare_to=laravel/framework">comparison</a> between different repositories and considering my next steps.</p> <p>Going forward, I'm thinking the following can be useful to get the most out of what I built thus far and offer value:</p> <ul> <li><p>Badges repositories can add to their README page for merge rate, average response times and etc.</p></li> <li><p>Personal rankings for contributors: average review cycles, how often their pushes fail tests, improve coverage, PR sizes and so on.. things that should encourage a better way of working. </p></li> <li><p>Smarter Insights - where are the problematic areas in the codebase based on how quickly PRs of that area are merged, how many review cycles it takes and so on..</p></li> <li><p>Rankings of open-source projects: I'm on the fence about this one. I don't want to rank open-source projects based on how quickly PRs are addressed or issues are resolved, but I'm trying to figure out a way for making maintainers' life easier and proud of their work.</p></li> </ul> <p>What do you think? </p> <p>Oh yea, did you know that <a href="https://thepracticaldev.devlytics.io/dev.to">dev.to</a> has a merge rate of 91%?</p> showdev sideprojects Udi Fri, 13 Jan 2017 14:51:26 +0000 https://dev.to/udiudi/hi-im-udi-mosayev https://dev.to/udiudi/hi-im-udi-mosayev <p>I have been coding for a little while.</p> <p>You can find me on GitHub as <a href="https://github.com/udiudi" rel="noopener noreferrer">udiudi</a></p> <p>I live in Israel.</p> <p>I'm doing freelance work for companies.</p> <p>I mostly program in these languages: Javascript and Ruby.</p> introduction